Some friends email me saying that they are interested to know how I upgraded (“migrate” I think is more accurate) my Saitek drivers to the Logitech version. Again, as mentioned a few times, such a migration is not necessary if the Saitek drivers are working fine.
Anyway, it does no harm if anyone want to keep up with the Logitech version. But ensure to AVOID using version 0.8.144.0 as it has error. Version 188.8.131.52. is fine, which I am currently using.
Followings are the steps I took for the migration:
Back up, Back up and Back up. This is the first and the most important step to the migration process.
If possible, not only just make copies of everything in the “C:\Program Files (x86)\Saitek\ProFlight FSX Plugin” and “C:\Program Files\Saitek\DirectOutput” directories, but also do a system backup (using Acronis True Image, for example) just in case.
Right click Windows taskbar and choose to open “Task Manager”. If “DirectOutputService Windows Service” exists, right click it and end it.
Uninstall Saitek’s “Pro_Flight_FSX_Plugin” and “Pro_Flight_Instrument_Panel” via Control Panel.
Restart the computer.
Install the Logitech’s FIP Driver first (again, AVOID using 0.8.144.0 version) and follow the instructions onscreen.
When prompt, connect only ONE FIP to a USB port directly on the computer (not on the USB hub); otherwise, errors might occur.
Then follow to run the Logitech’s FSX_Plugin.
If installation is successful, the FIP will start a slideshow displaying the company’s flightsim products on the screen.
Go to the appropriate simulator’s cfg directory as shown below:
P3Dv3: %appdata%\Lockheed Martin\Prepar3D v3
P3Dv4: %appdata%\Lockheed Martin\Prepar3D v4
Check if the exe.xml file in the cfg directory containing the following scripts:
<Name>Logitech Plugin for FSX</Name>
<Path>C:\Program Files (x86)\Logitech\FSX Plugin\LogiFlightSimX.exe</Path>
If not, add the scripts to the exe.xml file.
Also, remove the scripts of the previous Saitek drivers (in similar format) in the file if found.
Load up the simulator.
If everything is OK, a default gauge will be shown on the FIP, meaning the driver migration is successful.
It is better to restart the computer one more time before adding the other FIPs (if any) to the computer or to the USB hub as one did before the migration.
Then copy the gauges that were backed up in the first step to the new Logitech directory — C:\Program Files (x86)\Logitech\FSX Plugin.
Under the Logitech drivers, the xml file that contains the listing of the current gauge is “LogiFlightSimX.xml”.
One can copy the contents from the previous SaiFlightSimX.xml to this LogiFlightSimX.xml in order to restore the gauges that were used before the migration.
Note that it may be required to press the Up/Down buttons on the FIP to select what gauges to display during the first run.