Phantom88
Charter Member
Looks like we can get our FTX Scenery working in P3D V2
http://airdailyx.blogspot.com/2013/11/a-guide-for-installing-orbx-scenery.html
http://airdailyx.blogspot.com/2013/11/a-guide-for-installing-orbx-scenery.html
-
Please see the most recent updates in the "Where did the .com name go?" thread. Posts number 16 and 17.
FTX/Orbx and P3D V2 "Work Around"
- Thread starter Phantom88
- Start date
Thanks Phantom.
Im always worried to place things in the registry.
Also, I had heard there were conflicts with the ORBX scenery with dual names in the flora. Bringing over some ORBX packs into V2 caused people to have to do a complete reload of V2. Not to mention poor Francois who touched his Registry and now he cant even get P3D to load. It refuses to fully load or launch. Not good.
Im always worried to place things in the registry.
Also, I had heard there were conflicts with the ORBX scenery with dual names in the flora. Bringing over some ORBX packs into V2 caused people to have to do a complete reload of V2. Not to mention poor Francois who touched his Registry and now he cant even get P3D to load. It refuses to fully load or launch. Not good.
gman5250
Charter Member
I ran this fix early on and had mixed results. It's a good code and well intended.
After working with this switch, I ended up removing the link and going back to a neutral setup.
There are lots of "cures" floating around that may provide temporary solutions to the ORBX/P3D v2 autogen display anomaly. None of these will address the core issue, which is being worked on by the ORBX team and LM.
I'd wait for the approved installers to come from ORBX and avoid integrating any phantom code(s) into an architecture that is already highly complex. Once the OEM code is approved the temp fixes will not be needed and possibly could create new conflict.
IMHO.
After working with this switch, I ended up removing the link and going back to a neutral setup.
There are lots of "cures" floating around that may provide temporary solutions to the ORBX/P3D v2 autogen display anomaly. None of these will address the core issue, which is being worked on by the ORBX team and LM.
I'd wait for the approved installers to come from ORBX and avoid integrating any phantom code(s) into an architecture that is already highly complex. Once the OEM code is approved the temp fixes will not be needed and possibly could create new conflict.
IMHO.