anden145

Good God! This thread sure took a turn for the worse... 😕

I just love how you make such claims, with a certainty, as you've wrote the FWB software for Airbus, yourself.. 🙄

@turbomax Please see the post here for more information. 🙂

Create a symbolic link between the two folder: C:\ProgramData\Lockheed Martin\Prepar3D v5\ and C:\ProgramData\Lockheed Martin\Prepar3D v6\ Copy and paste the following into a CMD (run as admin!): mklink /J "C:\ProgramData\Lockheed Martin\Prepar3D v5" "C:\ProgramData\Lockheed Martin\Prepar3D v6"

Since you setting up a 'fake' registry for tricking addons into thinking Prepar3D v5 is installed, insert license information for Prepar3D v5 in this. 🙂 Also why I inserted possible licenses relating to Prepar3D v5 as options. 😉 Hope you found it helpful.

I haven't tested it extensively, but so far, the PMDG airplanes looks, sounds, activates and flies normally. However, PMDG themselves (who should have the most knowledge about this) have said, that they experienced 'unsatisfactory' results, when installing them into Prepar3D v6. So I definately won't rule out, that there could be some quirks or weird issues with them.

GSX and SODE works fine (same method with registry and symbolic link) 🙂

I installed it directly into Prepar3D v6, using the registry 'fix' (tricking the installers into thinking it was Prepar3D v5).

Yes, it works ONLY if Prepar3D v5 is NOT installed. The reason being, that symbolic links cannot be created, if there's a folder already existing with the same name. Therefore, IF Prepar3D v5 is installed, you either need to manually rename the folder Prepar3D v5 to something else (Prepar3D v5_OLD or something) or use Prepar3D v4 instead, and then create the Symbolic link. If you haven't Prepar3D v5 installed, then there shouldn't be any issues.

Besides using the registry fix, linked below, you also need to create a symbolic-link between the following folders C:\ProgramData\Lockheed Martin\Prepar3D v5\ -> C:\ProgramData\Lochheed Martin\Prepar3D v6 Do the following: Copy and paste the following into a command-prompt (Run as Admin): mklink /J "C:\ProgramData\Lockheed Martin\Prepar3D v5" "C:\ProgramData\Lockheed Martin\Prepar3D v6" That should work. 🙂 Close ORBX app (or any other application, which rely on the exe.xml/terrain.cfg files etc) or restart the computer if necessary. Then try again. 🙂 Please see registry 'fix' here EDIT !!! The above solution (with Symbolic-links) probably won't work, if you already have Prepar3D v5 installed! If you have Prepar3D v5 installed, you could use Prepar3D v4 instead... Don't think it would make a huge difference. I have only tried it with creation of symbolic links to v5. v4 should work, but I haven't testet it. You could make a backup of the Prepar3D v5 folder and then rename it and then create the symbolic link (as described above)... But beware, that you could potentially mess up your Prepar3D v5 installation.

Can be installed through the ORBX Central app. It was automatically installed, when installing GSX Level 2 (or just GSX) 🙂

Nice! Thanks, Ray. I'd thought it wouldn't be that easy, since they re-created the atmospheric environment... 🙂

GSX Level 2 works flawlessly. So does SODE. I really hope that HifiSim would update ActiveSky. I really miss the weather radar in my PMDG planes! 🙂

PMDG 737NGXu seems to be working as well. With the registry 'trick' done. I also managed to get ChasePlane to be installed, but it isn't launching, so I guess something needs to be done from the developers side? In order for ORBX (incl. ChasePlane) to be installed, I had to create a symbolic link between "C:\ProgramData\Lockheed Martin\Prepar3D v6" and C:\ProgramData\Lockheed Martin\Prepar3D v5". EDIT: Regarding PMDG: Now, they already said, that they had 'bad' (or not satisfactory) results with just installing it into Prepar3D v6. Personally I don't see any, at the moment - but I haven't flown it extensively (yet) and there maybe systems or other weird things happening. We'll see... So far they've been installed, activated and loaded fine.

@F737MAX Where is the terrain.cfg file located in Prepar3D v5? Is it in "C:\ProgramData\Lockheed Martin\Prepar3D v5" or somewhere else?

I don't know. I don't have v5 installed... At first, it complained about the exe.xml file. I then created a symbolic-link between C:\ProgramData\Lockheed Martin\Prepar3D v6 and C:\ProgramData\Lockheed Martin\Prepar3D v5. Which helped for that particular error. But then it threw the terrain.cfg error instead...

Hmm ... I cannot get ORBX installer to work. Keeps complaining that my terrain.cfg is corrupt 😕

@Ray Proudfoot Small guide created here. Hope it's sufficient. 🙂

Hi all, Was asked to create this small guide, so here goes... 🙂 I took advice from this excellent post from @micstatic here. This "registry trick" is for installing (un-updated) addons into Prepar3D v6. In theory, this can be used for any version of Prepar3D, but I'm gonna be focused on Prepar3D v6, and tricking addons into thinking that Prepar3D v5 is installed. Now, this isn't foolproof and some addons doesn't seem to work despite of this. Maybe other things needs to be done, to make this work. This guide also takes into account, that you haven't any previous versions of Prepar3D installed! Please note, that if you have Prepar3D v5 installed and are making this registry change, problems may arise, so please be cautious! Also, backup your registry, before editing/changing this. There's no undo-button! 🙂 Alright - here goes: Open Notepad.exe up, and paste the following into it: Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin] [HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v5] "Installed"=dword:00000001 "AppPath"="<INSERT-PATH-TO-PREPAR3Dv6-HERE>" Save the file as P3D-HKEY-USER-Registry.reg Open Notepad.exe again and paste the following into it: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin] [HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v5] "License"="<INSERT-LICENSE-HERE>" (License can be Academic/Professional/ProfessionalPlus) "SetupPath"="<INSERT-PATH-FOR-PREPAR3DV6-HERE>" Save the file as P3D-HKEY-LOCALMACHINE.reg Close Notepad. Run the two registry-files by double-clicking on each of them (follow the instructions which appears). Please be aware when changing registry-entries! Always backup your registry, beforehand. In theory you could use Prepar3D v4 instead, if you don't wanna mess your existing Prepar3D v5 up. I wouldn't advice to go below Prepar3D v4, due to architecture changes. Hope this was helpful.

Check here: https://www.avsim.com/forums/topic/635629-registry-trick-for-installing-addons-in-p3d-v6/

What do you mean 'source'? If you mean 'method', then simply do the registry "trick". That's what I did with the PMDG 777.

Well - the PMDG 777-200LR seems to be working. It was installed, activated and loaded fine. Sounds OK too...

Have you tried installing ChasePlane?

Wonder if HifiSim will update ActiveSky to P3Dv6 ?

Aaaand we're back at abysmal download speeds... Come on, Microsoft... *SIGH*