FSX to Prepar3D Migration Tool updated to version 1.4

  • Posted:

It’s been a month. The longest development cycle so far has resulted in the following new features:

  • Migration Tool can now be run under Windows XP (32 bit only). Since 64 bit Windows XP is in many aspects experimental, it is doubtful that we’ll see 64 bit XP support in the future.
  • Installers are handled much better in 1.4. If there is uninstallation information somewhere on your system preventing from installing the same addon twice, a quite complex algorithm tries to find and temporarily remove such entries.
  • Full registered FSUIPC and EZdok support. If you wish to run TrackIR through EZdok or fly with older planes such as PMDG 747, just fire up Prepar3D in Legacy Mode. There are no known side effects.
  • There was a bit of a problem with utilities that tried to access shader files. This has been fixed.
  • And as a safety measure, to prevent you from running FSX while virtual FSX is enabled, FSX.exe in root FSX folder get temporarily disabled when you enable virtual FSX. If you try to run FSX, you will see a notice telling you to run the Migration Tool and disable virtual FSX.

Version 1.4 can be downloaded from product page. Updating is easy, simply disable virtual FSX in Migration Tool, close the program and then run the downloaded installer.

FSX to Prepar3D Migration Tool version 1.3 now available

  • Posted:

Based on the feedback we’ve gotten so far, we have released version 1.3 of FSX to Prepar3D Migration Tool.

Changes are as follows:

  • There was some trouble with backing up original FSX and later restoring it. Background service making sure that virtual FSX installation is intact sometimes restored a few files even after you had just disabled virtual FSX installation. This synchronization issue is now of course fixed.
  • There is now better support for EZdok Camera Addon, meaning that yes, you can now use TrackIR with Prepar3D. Use Prepar3D Legacy Mode (see readme on that) to run its control panel. Once you have configured it, it will start with Prepar3D without causing you more trouble. There are still minor problems with registered versions of FSUIPC, which report as not registered in Legacy Mode.
  • If your Prepar3D installation does not have dll.xml or exe.xml configuration files, then they will be created automatically. Previously, if Prepar3D didn’t have exe.xml, then exe.xml didn’t appear in virtual FSX installation either, and if any addon created exe.xml, then it didn’t get copied over to Prepar3D.

And as always, you can get version 1.3 from product page.

Last, but not least – I would like to point out that we opened public support forum at simFlight Forums. Thanks to Miguel Blaufuks and the team at simFlight!