Deus 2 Version 2.00 May Have A Bug - Affects At Least Relic Program

[Jeff McClendon]

I haven’t bothered to even test it since realistically I never user Disc IAR above setting 1. 

I guess I should find out but like you said, yours doesn’t show this “bug” and all of 2 people have commented on his YouTube video about it and on other forums, there is very little traffic about this “bug”.

[iron_buzz]

15 hours ago, Chase Goldman said:

 

What TNSS is saying is that if you have Relic set up to give you a pure iron signal in the nail/nickel/swing configuration shown (as expected when you swing down the barrell of the nail) and then you transition to any other program (other than Gold Field) and then return to relic, you will get intermittent non-ferrous audio and TIDs (that don't correspond to the nickel TID, they look to be in the high 80's when I was able to catch a glimpse of the screen).  Indicating that perhaps IAR has been altered which may be causing iron falsing or some other unknown bug/issue.

Anyway, despite several attempts with the same setup, I have not been able to replicate TNSS's "bug" at all.  Not even close.  I can make blips occur with certain coil edge manipulations (even without transitioning out of Relic) but with a normal swing down the barrel of the nail, solid iron tone and ID no matter how many transitions out of relic or other non-relic program adjustments I do. 

Maybe he has a coil issue or a buggy install.  Though Jeff's statement that TNSS has seen this on previous versions, indicates it may not be unique to ver 2.00, pointing again to perhaps a TNSS unique hardware or configuration issue.

I don't have the "issue" and really am not losing sleep over it, regardless based on my tests and hundreds of successful hours on v 2.0 Relic Program (yes, it's my "Go To" program).  And I do a lot of target interrogation which has me frequently transition out of relic.

I would be interested to know if anyone else has been able to replicate it (other than the one or two folks who commented on his channel who said they saw it too).  I'm actually kind of surprised by people just taking these findings (mine included) at face value as gospel rather than proving to themselves whether they are present for their specific setups based on how simple the test is to set up and run.  Especially since they may manifest differently for different combinations of equipment and targets.

Without additional replication by other D2 experienced folks, I'm attributing this something unique with TNSS's gear.

Whatever the case, TNSS has done the right thing and has passed this on to XP to sort out and address, if necessary.  XP has not acknowledged an issue but they are looking into it at TNSS's request.

Thanks, Chase.  Yeah, I agree that it sounds like much ado about next to nothing.  It does sound (former programmer here) that some variable or parameter is not getting cleared or reset properly, but under extremely unlikely circumstances.   Its something that XP would want to know about and correct, of course, but I'm not losing any sleep over it, I guess.

Thanks for doing the translation for me... you're a true MVP!