How do I install PMDG 747 QOTS on a second drive?

[riwig 3]

I have followed the thread: https://www.avsim.com/forums/topic/511794-how-to-manually-add-sceneryaddons-into-p3d-v4-the-right-way/

and with great success added my scenery and add-on aircrafts to my second drive to keep my P3D installation clean. Have some problem with Carenado's PC12 and Dornier DO2288 but I manged to get them properly installed.

My setup on the second drive is similar to the P3D v4 folder structure with SimoObjects, Sound, Scenery, Gauges, Fonts, Effects. Have my add-on.xml in Documents folder and the add-ons.cfg in the AppData\Roaming... folder.

The problem I have encounter is with Carenado's aircrafts they will not install on the second drive due to " No Prepar3D installation there..." Solved by copying the prepare3D.exe to the drive and everything went smooth.

Now when I want to install PMDG 747 QOTS and the 777 200 I am stuck. There is no option to chose where to install this add-on. It will only install in the default P3D folder\SimObjects.

Any suggestion how I can direct the installer to my second drive would be highly appreciated?

Richard

[greggerm 312]

That will probably be a tough one to work out. PMDG installations will automatically target the simulator's home directory, so the only way to move it to an outboard location would be to do so after installation.... but at a minimum this will break the PMDG Operation Center functionality. It might also cause other issues above and beyond that - you never know!

Perhaps they will adjust their installation methods down the road to better support user directed install locations, but for now you will probably need to leave it as-is.

-Greg

[riwig 3]

Hi Greg,

Thanks for your reply. That was what I thought too. Just wanted to check if someone has managed to find a solution for it. Have filed a ticket at PMDG and waiting to see if there is any workaround.

Regards,

Richard

[riwig 3]

Just received an answer from PMDG and it will be possible going forward. For now it is no workaround. Just install in the default folder.

Richard