Does it look like it will get fixed before the long weekend?
I havent hardly played FSX yet because I can't look around.
a. good -proves the value of the product
b. bad -need a solution that I have been waiting a month for
Does the same problem manifest itself with the TIR4 or is it immune?
I would suspect this is a software issue so it will not do me any good. I'd like to hand-me-down the three to my brother and get the 4, but can't without a solution forthcoming.
FSX with Trackir 3 and Vector Expansion
Re: FSX with Trackir 3 and Vector Expansion
It can have the same issue on a TrackIR 4 system, as a TrackIR 3 system.
As I have stated previously, with the blue light activating on the unit, after starting FSX. The TrackIR unit is "talking" to part of FSX. What then is occuring is a breakdown in communication within FSX itself. There is no simple fix from us, as our software is talking to the simconnect application within FSX.
A couple of things to try.....
1 - Try an install of IPv^ for windows
http://support.microsoft.com/default.aspx/kb/555577
2 - Uninstall firewall software, and test to see if this resolves the issue.
As I have stated previously, with the blue light activating on the unit, after starting FSX. The TrackIR unit is "talking" to part of FSX. What then is occuring is a breakdown in communication within FSX itself. There is no simple fix from us, as our software is talking to the simconnect application within FSX.
A couple of things to try.....
1 - Try an install of IPv^ for windows
http://support.microsoft.com/default.aspx/kb/555577
2 - Uninstall firewall software, and test to see if this resolves the issue.
Re: FSX with Trackir 3 and Vector Expansion
I am having the same problem discussed above, however I am using Zone Alarm as my firewall. I assume that this is the same issue as with the McAfee Firewall?
Thanks,
-Jinks
Thanks,
-Jinks
Re: FSX with Trackir 3 and Vector Expansion
Yep, try the followin steps from Microsoft.........
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.
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.