Another unhappy fsx user.

[david1964]

Love my trackir4 to bits,every game that supports t4 works a treat except one......FSX.Ive upgraded drivers to current ones,un-installed then re-installed but still nothing,trackir connects with FSX(blue light and gauges/head on trackir move)but no cigar,ive read the posts about this and im having troubles still(FSX was installed 27th dec).Anyone got ideas please?
David

[VincentG]

OK, so you are getting the blue light activating on the bottom of the TrackIR unit, when FSX is running?

Are you running any firewall software? If so, try the following steps...

Using FSX Add-Ons with Firewalls and Antivirus Programs

Many new Flight Simulator add-on products connect to Flight Simulator X (FSX) via the new SimConnect Application Programming Interface (API). When you run FSX with an add-on installed, some non-Microsoft firewall and antivirus applications (such as ZoneAlarm) may detect that FSX is attempting to make a network connection and display a dialog asking you to allow or block this connection.

This �network connection� is necessary for the add-on to connect with FSX. It�s a local connection between the add-on and FSX (via a network localhost/127.0.0.1 connection), and does not involve a connection to the Internet. Be assured: FSX is not trying to send personal data about you through the Internet.

Note that Microsoft Windows Firewall will not exhibit this behavior. It will, however, alert you if an add-on is actually trying to access the Internet.

In order for your FSX add-on to work properly with FSX you MUST allow this connection to be made. If you do not allow the connection to be made, the add-on you are trying to run (and all subsequent add-ons that connect to FSX through the SimConnect API) will not work properly.

Some non-Microsoft firewall and antivirus applications will block this "localhost" connection between an add-on and FSX automatically, without any notification. In this case, you must configure the firewall or antivirus application to include both FSX and the add-on (specifically, the fsx.exe file and the addon's .exe file, if it has one) in the list of �trusted exceptions.� If this is not done, the add-on will not work properly with FSX. Please refer to the documentation for your specific firewall or antivirus application for details on how to add programs to the list of trusted exceptions

[david1964]

Thanks for reply,i will check the firewall again to be sure,i looked at it b4 from a different post.

[david1964]

Ive checked firewall and thats ok,ive even turned off the firewall(mcafee)and still no joy.Ive never had trouble b4,i thought the performance was going to be the problem but its turned out trackir4 is giving me the headache.

[VincentG]

I have seen this come up, on a few systems, where the blue light is on, but it still isn't working properly. Generally, it has happened on systems with McAfee running, it is still hampering the communication with the TCP/IP stack. Some customers have had some success installing IPv6 then uninstalling it, as this causes the TCP/IP stack to reinstall.

[david1964]

OH dear,looks like im screwed then.

[VincentG]

There might be some ports that need to be opened within the firewall software, but Microsoft might have a better understanding of which ones FSX is using.

[david1964]

Thanks,FSX is looking more like a bad call at this time.

[VincentG]

Some people have "tested" FSX, with there firewall software uninstalled, just to make sure that the issue is with the firewall software, and not with FSX.

[Barred]

ust to add to what Vincent has said.

I use a 3D program that uses the TCP/IP stack heavilly to communicate internally. If I have McCaffe or Norton running then my 3D application stops communicating. Symantic know about it but do nothing.