315: A Temp Solution to Fly P3Dv3 with Existing Addons

The new Prepar3D Version 3 (P3Dv3) takes the same approach P3Dv3_00as its predecessors to include the version number in its system registry (from Prepar3D to Prepar3D v2 to Prepar3D v3).   Making many addons have to rebuild a new installer in order to recognize the change, even when the new P3Dv3 is installed onto the same drive and same program directory as the previous version.

For those who wouldn’t want to wait for the release of new compatible installers, here’s a quick temporary solution to run the new P3Dv3 with existing addons from earlier versions.

I am using Orbx’s addon as an example.   And the region used in P3Dv2 is set to FTX Global Hybrid.

My Prepar3D version 2 is installed on P:\Prepar3D, and version 3 on P:\Prepar3Dv3.

Step 1)
Go to P3Dv3 program directory, rename the Autogen folder to Autogen_ORIGINAL.   Then copy the whole Autogen folder from version 2 to here.





Step 2)
Go to “C:\ProgramData\Lockheed Martin\Prepar3D v3” directory,  rename terrain.cfg to terrain_ORIGINAL.cfg.
Then copy version 2’s terrain.cfg file from “C:\ProgramData\Lockheed Martin\Prepar3D v2” to this directory.


Step 3)
In the same directory, rename scenery.cfg to scenery_ORIGINAL.cfg.
Copy version 2’s scenery.cfg file from “C:\ProgramData\Lockheed Martin\Prepar3D v2” to this directory.


Step 4)
Open and edit the scenery.cfg copied from version 2, and specify the location of all Orbx scenery entries to version 2’s program directory (P:\Prepar3D in my case).


Step 5)
Go to “C:\Users\Tom\AppData\Roaming\Lockheed Martin\Prepar3D v3” and rename DLL.XML to DLL_ORIGINAL.XML.
Then copy version 2’s DLL.XML from “C:\Users\Tom\AppData\Roaming\Lockheed Martin\Prepar3D v2” to this directory.


Step 6)
Similar to Step 4), edit the DLL.XML copied from version 2 and specify the path of all related modules to version 2’s program directory.


That’s it.   P3Dv3 can now run with the addons previously installed for earlier versions.

However, this temporary solution isn’t without trade-offs.   For example, all associated files, such as effects, sounds, ai traffic, etc, coming with the original addons are not copied.   Moreover, there could be anomalies found in some areas.

Surely that could be properly fixed by hand but the process involved is a lot more complicated.    It’s better to leave the job to the developer.

For now, we can fly with all we already installed after all…well, in a way.


An Alternative
One may also take the approach described in Post 57 for adding addons to P3Dv3 before a matching installer is released.   However, effort may not be sensible if large number of addons are involved.




2 thoughts on “315: A Temp Solution to Fly P3Dv3 with Existing Addons

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.