All our FSX products supports Lockheed Martin Prepar3D natively, up to the most current 1.4 version, without any need to do any special installation procedure. The installers correctly detects Prepar3D, and configure our software to run in Prepar3D mode.
Since there are still many 3rd party addons that don't support Prepar3D, there are tools available to fool installers and software modules that were made for FSX only, to install and run into Prepar3D as if it were FSX. One of these tools is the "FSX to Prepar3D Migration Tool" program.
The way it work in FSX Legacy mode, while allowing to run non-Prepar3D compliant products, it will create problems with our own software, which IS 100% Prepar3D compatible, since it needs to rely on the actual file version in order to change its working mode between different FSX releases ( SP2 or X-Pack ) and different P3D releases too (1.3 or 1.4).
We now updated the Addon Manager .DLL so that it can be configured to recognize this unusual situation (Prepar3D disguising itself as being FSX), here's how to proceed to configure our software to run with the "FSX to Prepar3D Migration Tool" program in Legacy mode:
- Disable the FSX to Prepar3D Migration Tool Legacy mode and the Virtual FSX folder
- Install any FSDT product in Prepar3D normally (our installer will detect P3D as such as will ask to install there)
- Create a batch file to start Prepar3D that will set an Environment variable to configure the Addon Manager and force the version detection:
You can save this file as Prepar3D.BAT in the Prepar3D root folder and start Prepar3D from that one, instead of the main .EXE. Find an already made Prepar3D.BAT file attached to this message, if you don't want to create a new one, simply copy it in the Prepar3D root folder
- You can now turn the FSX to Prepar3D Migration Tool Legacy mode back on, so it will be able to run other non-compliant software
It's suggested you install all your FSDT software at once, and then do this configuration as the final step. If you are still running P3D 1.3, the value of the AddonManagerForcedVersion variable should be set to 3708 instead.