Since there is a friend David who is asking for more description to allow FIPs to work in SE, here’s the details:
1)
Type “%AppData%\Microsoft” in File Explorer to go to the “\Roaming\Microsoft” directory.
If you have FSX boxed version on the computer as well, you will see both “FSX” and “FSX-SE” folder under the directory. Otherwise, you will see “FSX” only.
2)
Click on the “FSX-SE” folder and open the “exe.xml” file.
Note that this is the only file you’ll need to edit to allow FIPs to work in SE.
3)
Inside the file, you will see the following script:
<Launch.Addon> <Name>Addon Application</Name> <Disabled>True</Disabled> <Path>C:\MyPath\Addon.exe</Path> <CommandLine></CommandLine> </Launch.Addon>
It is the “template” to be used for new addons adding to SE.
4)
Make a copy of the “template” script and paste it underneath itself.
5)
Then, edit the new script as shown below in red color accordingly:
<?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>True</Launch.ManualLoad> <Launch.Addon> <Name>Addon Application</Name> <Disabled>True</Disabled> <Path>C:\MyPath\Addon.exe</Path> <CommandLine></CommandLine> </Launch.Addon> <Launch.Addon> <Name>Saitek Panel(s) Plugin for FSX</Name> <Disabled>False</Disabled> <Path>C:\Program Files (x86)\Saitek\ProFlight FSX Plugin\SaiFlightSimX.exe</Path> <CommandLine></CommandLine> </Launch.Addon> </SimBase.Document>
Ensure to use “False” for <Disabled></Disabled>.
And there should be nothing between <CommandLine></CommadLine>.
Note that the directory path of SaiFlightSimX.exe shown above is for the new Saitek driver version 7 only.
The path for older drivers is different, but I am not going to elaborate it here because there’s no reason to keep using the old drivers really.
6)
Lastly, save the file and exit.
That’s all and the FIPs will now work in SE.
