forums.naturalpoint.com

I play WWII fighter combat games and noticed that every time I began to focus on a target to kill it, the TrackIR would begin jumping all over the place as though I was raising a hand in front of the IR LEDs on the Track Clip Pro.
I had jacked the brightness of the IR LEDS to full, set the filter to full with no impact.

I was back in the full screen camera view when I noticed 2 horizontal red dots just to the right of my Left mounted TrackClip?!?! They would appear if I looked straight at the screen and vanish if I looked away.. What could that be I wonder?...

I wear Glasses!! The 2 horizontal red dots where my lenses!! I was reflecting the IR emitters from the TrackIR base mounted on my monitor, back at the base which would cause interference. The red dots get bigger and stronger as I move forward too.

So far I found REDUCING the brightness of the IR Emitters with full filters helps some. Getting further back from the monitor helps some more (I'm about 2+ feet away). But I'm open to any other ideas how I can leave my glasses on and not reflect the IR light.

Thanks

Solved and BUG identified!

So I have the TrackClipPro. This means I have active IR emitters attached to my head that send IR to the receiver. The IR from the receiver is only needed if I'm using the passive baseball cap reflectors that come with the kit. So the question became, "Why are the camera based emitters lit??"

I checked the configurations settings in the TRACKIR 5.4 setup tool and it was set for the TrackClipPro (highlighted in yellow on the button) which is exactly how it had been set when I initially ran it. So why was the emitter in the Camera lit if it knew I had the head mounted emitter??

I'm a professional programmer (Business software) and I've encountered code bugs in the past where a setting is available and the code set to use the setting and store the values all set but no initial value provided or a bad initial value. Perhaps the UI had a highlight value for the button but no underlying value for the setting. The test is to click the other button and then immediately click right back to the proper button. The initial click makes the initial setting in the back end of the code and the next setting puts the setting to were you want it.
The instant I did that the camera based IR leds turned off and the tracking totally stabilized! My issue is resolved!

I would ask NaturalPoint to check your code for a bug between the initial button display value of the TrackClipPro button and its backend value for the setting. It looks like it will display initially even though the system is set to NON TrachClipPro on the back end.

For end users with jumpy display try cycling the Tracking target buttons (The ones marked "TrackClip" and "TrackClipPro")

Manx,

Thank you for the original post and the solution you have found. I have verified this information and sent it on to my developer for review.

Regards,