3 minutes ago, anden145 said:

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
 

Thanks

 

I installed P3D V6 and my first impressions after transferring several scenarios from P3D 5.4 are as follows:

the Aerosoft scenarios (EDDF-EGLL-LSZH-LIMC-LIRN) gave no problems.

Flightbeam (KDEN-KIAD-KMSP) O.K while KSFO on the runways and buildings I experienced constant flickering.

Orbx apts not loading OBJECTFLOW, have problems especially on runways.

To me the AI traffic I had on P3D 5.4 works fine on P3D V6.

Improved the light of the scenarios and, if not completely resolved, improved the anti-asialing.

QW787 does not work, while the old King Air 350 works fine.

My, for now, negative note are the textures of P3D V6 and I hope that Orbx fixes the compatibility of FTX Global Base otherwise we reverted to the awful vanilla textures of previous versions.

Of course I only did quick apt shifts and will try other scenarios and other planes to see compatibility with previous versions.

21 minutes ago, vjeanmarc said:

Thanks

Does this work if p3d v5 is not installed? I am only using the registry fix. I assume you mean  mklink /J no quotes  C:\ProgramData\Lockheed Martin\Prepar3D v5 then C:\ProgramData\Lockheed Martin\Prepar3D v6 no quotes all in command prompt as admin. I have never created a symbolic link. I kinda feel stupid.

9 minutes ago, Patriot3810 said:

Does this work if p3d v5 is not installed? I am only using the registry fix. I assume you mean  mklink /J no quotes  C:\ProgramData\Lockheed Martin\Prepar3D v5 then C:\ProgramData\Lockheed Martin\Prepar3D v6 no quotes all in command prompt as admin. I have never created a symbolic link. I kinda feel stupid.

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.

Edited July 4, 20232 yr by anden145

For those users who are saying that the PMDG planes work fine in v6.....are you simply linking the PMDG files from an existing v5 installation (as opposed to installing the products from scratch)? If so, I assume that this is the reason why your results differ from those indicated by PMDG. They are probably describing their results when installing directly into v6. Whether there are any ulterior motives behind this is probably something that is best left for individual AVSIM members to consider

Just now, Christopher Low said:

For those users who are saying that the PMDG planes work fine in v6.....are you simply linking the PMDG files from an existing v5 installation (as opposed to installing the products from scratch)? If so, I assume that this is the reason why your results differ from those indicated by PMDG. They are probably describing their results when installing directly into v6. Whether there are any ulterior motives behind this is probably something that is best left for individual AVSIM members to consider

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

i used the pmdg installers with just the registry that is listed above. I haven't had time yet to test things extensively, But I have the v6 almost maxed out with 60fps locked. I plan on doing a flight in the 777-200 tonight.

Did you guys install the fsdreamteam gsx and airports the same way as the planes? I was also going to give flight beams airports a try, Then I am set until Active sky comes out with it's new product. I believe it's a new purchase for active sky when it's released, and well deserved. Active sky has been dumped and left for dead the past few years.

9 minutes ago, Patriot3810 said:

Did you guys install the fsdreamteam gsx and airports the same way as the planes? I was also going to give flight beams airports a try, Then I am set until Active sky comes out with it's new product. I believe it's a new purchase for active sky when it's released, and well deserved. Active sky has been dumped and left for dead the past few years.

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

Well seems like the Aerosoft 330 does not work using the registry trick according to a user on the forum.

Just now, carlanthony24 said:

Well seems like the Aerosoft 330 does not work using the registry trick according to a user on the forum.

It might now, using the symbolic link suggested, But i am not trying it again. The textures were a disaster and i was getting 7 fps, For some reason real light that's required to install wouldn't with the Installer. It might now.

I have 3 addons i'm interested in:

1) ADE: if v6 works same as v5, this means I can install all my FSX airports there, and I'll just have to recreate my default airport exclusions.

2) Lorby P3D Addon Organizer. I know that, with existing addons (those which I already have in v5), I could just copy the Addon.xml files from My Documents\P3Dv5 addons to My Documents\P3Dv6 addons, but for new ones?

3) Has anybody tried forcing the FSL birds into v6? FSL gave a similar speech as PMDG's, but people found a way...

Lorby has a P3Dv6 beta add on organizer available too   addon-organizer 1.60 b01.zip

All Latin vfr airports from p3d v3 forward work in p3d v6. I am gonna check a few more.

Has anyone got Vertx DA-62 or Realair Legacy installed to V6?