Tomesk Posted June 27, 2016 Share Posted June 27, 2016 I don't have the option for Prepar3d V3 when trying to install the PNW and PFJ regions. CRM, NRM and SAK all installed fine. I have the latest version from the Flight Sim Store. PNW - 180 PFJ - 140 Any ideas? Link to comment Share on other sites More sharing options...
Doug Sawatzky Posted June 27, 2016 Share Posted June 27, 2016 Hmmm...I just did a new PNW and PFJ install into P3Dv3 and had the option with no issues. Link to comment Share on other sites More sharing options...
Tomesk Posted June 27, 2016 Author Share Posted June 27, 2016 I think FTX Central 2 f'ed things up. My prepar3d v2 and v3 have the same installs according to the utility which is NOT true. A uninstaller would be nice but ORBX products don't seem to ever have one. Any ideas how to uninstall FTX Central? Link to comment Share on other sites More sharing options...
Museumkeeper Posted June 27, 2016 Share Posted June 27, 2016 6 hours ago, Tomesk said: I think FTX Central 2 f'ed things up. My prepar3d v2 and v3 have the same installs according to the utility which is NOT true. A uninstaller would be nice but ORBX products don't seem to ever have one. Any ideas how to uninstall FTX Central? Hi I have just downloaded PNW and it has an option to install in P3D v3 when you run the installer. I would suggest that you re-download the file again from your FSS account. As FTX Central v2 is not required when you are installing an Orbx download, I cannot see it causing a problem. It certainly did not in my install. Kind regards Ian Link to comment Share on other sites More sharing options...
Penzoil3 Posted June 27, 2016 Share Posted June 27, 2016 Use the utility to correct the registry entries. Link to comment Share on other sites More sharing options...
Tomesk Posted June 28, 2016 Author Share Posted June 28, 2016 16 hours ago, Ian S said: I would suggest that you re-download the file again from your FSS account. Re-download did the trick. Very strange that they didn't rename/reversion as the new dl was a slightly different zip file. 15 hours ago, Penzoil3 said: Use the utility to correct the registry entries. Fixed the v2 - v3 conflict. Thanks Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.