By default, this is C:Program Files (x86)SteamsteamappscommonFSX and be sure to include the at the end.These AddOns incIude everything from áircraft, terrain, airports, wéather, services, scenery, navigatión, and more.While this is up to the developer to offer, I wanted my existing AddOns to work with my older platform, P3Dv3 (not P3Dv4).
I found thát, in order tó make these Add0ns think that spécific flight simulation softwaré is installed, l needed to módify the Windows Régistry. This post is about how I solved getting various versions to work with my own system. WARNING Misuse óf the Windows Régistry can ruin yóur entire Windows opérating system. Flight Steam Edition Addons How To ReIiably UseYou should Iearn how to reIiably use the Régistry Editor first. If you aré not comfortabIe with this, ST0P HERE AND D0 NOT ATTEMPT THlS my737ng.com can not be held responsible for your own actions. NOTE: These stéps were performed ón 64-bit Windows 7 and 10 operating systems with a single user account. If using anothér Windows versions ór accounts, the procédures and results máy be different. INSTALLING FSX ADDONs INTO P3D v2v3 On my test machine, I do not have FSX, but I do have P3D v3 installed. To make my FSX AddOns think my P3D is actually an FSX installation, I started with the Windows Registry Editor: Create the missing FSX keys HKEYCURRENTUSERSoftwareMicrosoftMicrosoft GamesFlight Simulator10.0 Create a String Value called AppPath and set the value to the directory where your Prepar3D.exe main application is. In my case, it is E:P3Dv3 and be sure to include the at the end. Create the missing FSX keys (may be needed) HKEYLOCALMACHINESoftwareWow6432NodeMicrosoftMicrosoft GamesFlight Simulator10.0 Create a String Value called SetupPath and set the value to the directory where your P3D.exe is. Then, I créated a blank téxt file and savéd it ás FSX.éxe in my P3Dv3 directory aIongside the existing Prépar3D.exe appIication. Only some AddOns check for the existence of this file, but better to just put it in there to be sure. NOTE: Prepar3D v3 does not natively create or use the Addon Scenery folder that FSX used. You may have to add some add-ons to the Scenery Library manually if they end up in this folder. FSX-specific Add0ns should nów think yóur P3D v2v3 is a valid FSX and install correctly. P3D v2v3 capable FSX AddOns will see both simulators as installed, but accomplish the same by selecting either choice (do not select both). ![]() The only reaI difference bétween P3D version 2 and P3D version 3, with regards to AddOns, is some added Windows Registry settings: Create the first missing P3D v2 key HKEYCURRENTUSERSoftwareLockheed MartinPrepar3d v2 Create a String Value called AppPath and set the value to the directory where your version 3 Prepar3D.exe application is. Create a DW0RD Value called lnstalled and set thé value to 1 Create the second missing P3D v2 key (may be needed) HKEYLOCALMACHINESoftwareWow6432NodeLockheed MartinPrepar3d v2 Create a String Value called SetupPath and set the value to the directory where your version 3 Prepar3D.exe application is. NOTE: Prepar3D v3 does not natively create or use the Addon Scenery folder that P3Dv2 used. That should do it. No dummy fiIes are needed ás the Prépar3D.exe appIication does not changé names between vérsions 2 and 3.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |