TIR4 bug with Aces High

[snomhf]

Well it apparently hasn't solved the problem because I (and others) are running Build 30 and the bug is alive and well.

[VincentG]

looking into the issue..

[Dizz]

I've had this same issue since 29 and get it consistantly in FSX, IL2, and Lockon. I've just installed the new 30 driver and it doesn't seem to happen as often, but it does still occur.

[VincentG]

ok....

When it occurs, are you lossing track of the IR lights on the tracking screen?

[Dizz]

Yes, I look to the side for several seconds to read a navigation map. Sometimes, not always, when I look back at the monitor and the TIR4 re-aquires the reflectors, it looses track and I'm looking straight down into the seat pan/floor. I've noticed I can make it occur more often when I keep my head down slightly. For example, I'm looking at a map to my left and TIR looses track and recenters. Then I look at my keyboard and then back up to the monitor. When TIR re-aquires the reflectors, it forces the view straight down.

I'm really not trying to be difficult here, I really do like TIR and refuse to fly anything without it now. It's just frustrating (to both of us I'm sure) that I can so easily repeat this error and we can't find a fix.

[VincentG]

Unfortunately, I have only had it happen to me once, and then I couldn't get it to do it again.....

[snomhf]

This is very easy to reproduce. I have even done it with the "heads" in the TIR setup software. I have not noticed any appreciable difference with build 30. It happens probably one out of every five times I try it. If I look over at a map laying on the desk for 30 seconds or look out toward the television in the next room (my head is turned almost 90 degrees from the monitor) and bring my head back to the monitor, my view is looking down at my lap.

If you were to go to the Aces High forums you would find this to be a well discussed topic where guys are saying the same thing as I am. I'm just the only one apparently who has come here to report it. It's not just a couple of random users having this problem.

[VincentG]

We are looking into it....

[Mace2004]

Vincent, with all due respect this is not a new problem. Several of us reported this during the .029 Beta testing and I for one specifically posted a complaint that it was not fixed when .029 became the "final" version. It's not fixed with .030 either. This is becoming much more than a "small" issue as it happens quite regularly and is similarly mentioned in regular posts to the AH forums. A "Small" issue would be something slightly irritating that gets identified and fixed yet this was reported during .029 beta yet still exists even with .030. I know it's not my system as I can reinstall .028 and it goes away but, of course, I lose the new features of .029/.030. Others have reported the exact same results when switching back to .028. Also, snomhf is understating the problem when he says "30 seconds", it doesn't take anywhere near that long for it to occur, it occurs within a second or two of moving outside the sensor field of view. Anything we can do to help you get this fixed?

Mace

[VincentG]

OK, it is being looked into, and we are trying to understand what is causing it. Also we see that it is occuring regularly to some customers, but you need to also be aware that I have been unable to reproduce the issue on a regular basis. I have tried, across several systems, and across several OS installs.