I have just purchased one Saitek Instrument Panel (FIP) and done as per instructions. (Installed software prior to plugging in the hardware) It scrolls through the product images but doesnt register with FSX i.e. doesnt display guages, just keeps scrolling product images. I've got Saitek multi, radio and switch panels and have uninstalled all and reinstalled in different order but no luck. I have Windows 7 (x64) and notice the FIP uses DirectOutput in Programs directory for the product images but rest of guages data /folders etc is in Programs x64 directory. Is that normal? Has anyone who has had this issue ( I know some have) worked out how to fix it. I have also downloaded the latest drivers from Saitek but that doesnt help. I also read somewhere that saitek forgot to add script into an xml file re Windows7 users. If that's correct, does anyone have it.

Have you tried installing FSUIPC?

I have a regd version of FSUICP and FSX wont accept that either. Cant get it into the Add-on dropdown list. Does this give any clues as to what the issue is re FIP

Tried loading FSUIPC. No luck. Installed & re-installed correctly according to the install log in FSX\modules folder.

Here's extra info - Any comment will be helpful as I suspect the same issue is causing the Saitek and FSUIPC problem.

 

In ...AppData\Roaming\Microsoft\FSX\

 

DLL.XML

the relevant script reads as -

<Launch.Addon>

<Name>FSUIPC 4</Name>

<Disabled>False</Disabled>

<Path>Modules\FSUIPC4.dll</Path>

</Launch.Addon>

...Seems to be correct.

 

FSX.CFG

I notice that in the [Trusted] listing, the last 3 entries have a "=-1" value whereas all the others in the list have a value of =2 plus there is a duplication of the SaiFlightSimX.exe (with different code and different value)

 

C:\Program Files (x86)\Saitek\DirectOutput\SaiFlightSimX.exe...=0 (codes removed for brevity)

C:\Program Files (x86)\Saitek\DirectOutput\SaiFlightSimX.exe...=-1

C:\Program Files (x86)\SPAD\SPAD.exe...=-1

C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.dll...=-1

 

The above looks odd to me especially as 2 are the addons I have an issue with and the other (SPAD) Ive only just loaded and not looked at as yet.

Can anyone advise.. are these 3 "-1" values correct and/or does zero or minus = not trusted.

 

EXE.XML

In this file (same folder) the script reads as per below and looks ok to me.

I believe the Saitek FIP works with the SaiFlightSimX.exe which is one of the -1 [Trusted] values above.

 

<?xml version="1.0" encoding="Windows-1252"?>

<SimBase.Document Type="Launch" version="1,0">

<Descr>Launch</Descr>

<Filename>exe.xml</Filename>

<Disabled>False</Disabled>

<Launch.ManualLoad>False</Launch.ManualLoad>

<Launch.Addon>

<Name>Saitek Panel(s) Plugin for FSX</Name>

<Disabled>False</Disabled>

<Path>C:\Program Files (x86)\Saitek\Pro Flight Panels\SaiPanels.exe</Path>

<CommandLine>-run</CommandLine>

</Launch.Addon>

 

<Launch.Addon>

<Name>Saitek DirectOutput RadioStack</Name>

<Disabled>False</Disabled>

<Path>C:\Program Files (x86)\Saitek\DirectOutput\SaiFlightSimX.exe</Path>

<CommandLine>-run</CommandLine>

</Launch.Addon>

 

<Launch.Addon>

<Name>SPAD</Name>

<Disabled>False</Disabled> <ManualLoad>False</ManualLoad>

<Path>C:\Program Files (x86)\SPAD\SPAD.exe</Path>

<CommandLine>-run</CommandLine>

</Launch.Addon>

</SimBase.Document>

 

 

SIMCONNECT.XML

I see in this file that the address and port fields have no data.

Is that correct? Seems to me if no data needed then the field would not be there.

 

<?xml version="1.0" encoding="Windows-1252"?>

<SimBase.Document Type="SimConnect" version="1,0">

<Descr>SimConnect</Descr>

<Filename>SimConnect.xml</Filename>

<Disabled>False</Disabled>

<SimConnect.Comm>

<Disabled>False</Disabled>

<Protocol>Auto</Protocol>

<Scope>local</Scope>

<Address></Address>

<MaxClients>64</MaxClients>

<Port></Port>

<MaxRecvSize>4096</MaxRecvSize>

<DisableNagle>False</DisableNagle>

</SimConnect.Comm>

</SimBase.Document>

Having the same problem with my FIPs and also with the Saitek X52 Pro, where the MFD does not work. Saitek says that the old version of X52 Pro does not work in Win7 64, something about prom in the X52 Pro. Guess what I have? Yes, one of the first that came out on the market.

 

Could it be a similar problem with the FIPs?

 

Goran

Thought I'd finish this for any others with similar issue. Did all the things suggested out there on the web.. no go and gave up. Recently relooked at it and looked closer at  C / Programs86 / Saitek / Direct Output / SaiFlightSimX xml file
It had following script as the first entry under the GuageList heading.
 <X52Pro>
    <ComNav radio1="true"/>
    <ComNav radio1="false"/>
    <Adf/>
    <Dme/>
    <Xpndr/>
    <Autopilot/>
    <VorHdg/>
  </X52Pro>

I had X52Pro drivers in my PC from previousl use and I had downloaded the updated saitek FIP drivers, uninstalled / re-installed all drivers a few times over past months trying to fix the issue. The above script clearly makes no sense and seems to be a mixture of both X52Pro and latest FIP drivers. It looks like the original xml file was never cleanly overwritten or rewritten. I deleted the above script amd the FIP works perfectly as per original drivers intend it to. Now not sure if I should risk installing the updated FIP drivers as it is those additional guage functions  that I purchased the FIP for.