forums.naturalpoint.com

Alright, after reading through the forums, and looking up online, I am having a issue which is like what I am reading from others. I just bought FSX today, and like the subject line reads, have the Trackir 3 with Vector.

After playing a little while, I noticed that I cannot get Trackir to work in game. Now, I have the green light, as well as the blue light on, and it works in all other games, except FSX. I get no response in Virtual or 2D mode in the game, but the lights are on. I tried to install the newer drivers, both with and without restarts in between. I have tried to find newer BIOS and video drivers... I have tried to have the boxes check and unchecked for trap,... I have tried pretty much everything, and have been building computers since 1994, plus I use TrackIR in OFP, LOMAC, and Falcon 4/Allied Assault, sooooooo, I am thinking that is less technical that I am looking for, and maybe more the simple, maybe a checkbox that is not checked, or vice versa.

Should I try removing the Trackir software again, and then clean the registry as well, then reboot and install the Trackir again?

I have the Macafee suite for antivirus/firewall/privacy service running.

Thanks for your time and assistance with this frustrating situation.

-Amarak

Try temporarily uninstalling the McAfee suite, and seeing if this helps the issue. We are seeing some issues isolated to the TCP/IP stack, which can get tied up with McAfee.

Ok, did this, and TrackIR works in FSX, so what now to protect my computer? Can I reinstall the McAfee and play, or will I have to choose between computer protection and game play? Thank you. (sounds sarcastic, and in a little way, it is )

Well, I would try installing it. Generally, when it has resolved the issue, installing it afterwards causes no ill effects on FSX.

Will do, thank you for your time and assistance. Great product, and support.

No issue, glad I could help.

Is there a fix in the works? I have no desire to blow away all of my McAfee settings by uninstalling and reinstalling it.

Currently the issue is tied to the TCP/IP stack, and the "wrapper" that is installed with firewall software.

So no? It can't be fixed?

We are currently working on the issue, among several others, and hope to have more information posted soon.