Prepar3D v3.x Compatibility

[louisdecoolste 12]

I think it's great L-M are thinking about undisturbed updates that mean nothing gets lost in translation, but a bit strange to be hearing about it only now. 

 

Still, sets a precedent for a start-from-scratch installation for V3 that indicates my preference for `wait and see` as the canny choice. There will need to be new installers for most everything.

[mr340 56]

Wait so does this mean we can now install add on to another Drive and not into P3D Folder?

[WarpD 824]

Yes, it means it should be installed outside the Prepar3D core folders which would clearly allow for a separate drive.

[mr340 56]

Amazing something that i always wanted . Thank you very much Ed

[bthiago 8]

That`s really nice. Is the update will separte what you already have on the V2.5?

[Dazzlercee23 66]

I assume that airport addons that create a directory within the P3D folder, and are self contained within that folder, e.g. UK2000, FlyTampa etc, will still work but not follow the new guidelines.

 

I would imagine such addons could simply be moved outside of the core folders and the scenery library updated to suit.

[mwilk 1,106]

 

 

Prepar3D core folders which would clearly allow for a separate drive.

 

Ed,

      Is that the reason for the SSD recommendation for V3?

[WarpD 824]

That`s really nice. Is the update will separte what you already have on the V2.5?

Prepar3D v3 isn't an update, it's a completely separate installation from prior versions.

[Kuragiman 227]

That is a great idea but it also has convinced me not to upgrade just yet.    I have well over 40 payware airports, Active Sky NEXT, GEX, UTX, Accufeel and TON of other materials that I guarantee aren't going to be updated anytime soon that would not function under LM new installation structure.   Guess I'll have to hold off for 6 months or so and see how the 3rd Party universe is responding.        About 30% of my airports required migration tools.   These will now be rendered useless piles of wasted money in the 3.0 scheme.

[GSalden 4,656]

Downloading ..... He he he

[birdmanmike 6]

credit card back in pocket for moment then . . . scenery always been in folders outside where possible - but effects? sounds?  ES, UK2000, Aerosoft, all got these.   I thought LM was making least point updates/hotfixes as in-situ updates not needing full download - and don't say it's now four components - it's still gigabytes and gigabytes to download on a 2mb connection  ;-(

 

can't get on LM server anyway,  double  :-(

 

oh well, FSX not deleted yet . . .

[JasonW 32]

This doesnt sound good for those of us clinging on to Ultimate Traffic 2. 

[kevinfirth 1,394]

Just to be clear.....are texture/sound files etc no longer installed in the relevant folders within the Lockheed Martin/Prepar3D folder structure? If that's the case, then I am wondering about compatibility with Earth Simulations products. Quite a large number of files were installed in those folders, and there is very little chance that we will ever see updated installers for each product...

Chris we can sort this hopefully I think. We should be able to try to find which files go where and do a manual move to a v3 compliant folder structure..

I assume that airport addons that create a directory within the P3D folder, and are self contained within that folder, e.g. UK2000, FlyTampa etc, will still work but not follow the new guidelines.

 

I would imagine such addons could simply be moved outside of the core folders and the scenery library updated to suit.

Happy days for me, I installed just about everything I could in 2.5 into a separate scenery HD so a lot of it is sitting there waiting to go

[Patriot3810 182]

can someone create a list so i know whats safe to try to install? i wiped my computer for p3d v3 and want to keep it as clean and tidy as possible, asn already has a beta update out.

[vgbaron 3,617]

Well it's been out for a few hours now and we already have updated installs for GEXP3D and ASN.

 

The single biggest complaint that I have seen in these forums during updates is - "I don't want to have to reinstall all my add-ons again - I'll pass on this update, etc".

 

LM is attempting to introduce a structure where, if followed by developers, will result in NOT having to reinstall all add-ons each time there is an update. There will be a transition period where it will be a PITA to get things squared away but WE will benefit in the long run.

 

Although they do not publicly comment much, it should be apparent to anyone paying attention that LM "does" listen to our complaints.

 

Vic