Sign in to follow this  
WarpD

Prepar3D v3.x Compatibility

Recommended Posts

With Prepar3D v3 from Lockheed-Martin being released today, I think it might be time to point out a few conditions of 'compatibility' that need to be revealed to the simming public:

 

1 - If a given addon installs anywhere inside the core Prepar3D folder structure, it's not compatible.

2 - If you need to use something like the Estonia Migration Tool to install, it's not compatible.

 

Believe it or not, if you ensure the addons you install to v3 are compatible... it will prevent you from having to reinstall addons when L-M releases point release updates to v3.

 

So, talk to your addon providers and encourage them to adhere to the v3 addon installation process correctly so that in the end, everyone will be happy.

 

This message brought to you by the letter 'Y' and the number '12'.

Share this post


Link to post
Help AVSIM continue to serve you!
Please donate today!

Did the folder structure change that much?  Configuration files are no longer located in c:\programdata?

Share this post


Link to post

Lockheed-Martin have made it clear they want no third-party content in their core installation folders at all. It will ensure that updates are easier on the end user. How and what installed what/where/by/how/etc has changed in v3. As example, it's possible for L-M to update only the client portion of the sim and thus reduce download size significantly. This means you would only uninstall the client and then install the updated client.

 

I see 4 installers that make up the Prepar3D v3 sim install. While the end user only runs a single installer, that actually calls 4 individual installers: Content, Professional, Professional Client and Scenery. (examples).

 

It is indeed quite different and addon developers need to adhere to the requirements for compatibility.

Share this post


Link to post

What about freeware scenery packages that were installed manually into Addon Scenery? Where are they now installed? I guess you are probably going to say that they are "no longer compatible", but that isn't the answer I am looking for.

Share this post


Link to post

I'm a bit confused. I read on the P3D website:

"Is Prepar3D v3 still backwards compatible with legacy content?

Yes. The Prepar3D development team has partnered with several developers to ensure that most legacy content is backwards compatible."

 

That sounds like quite the opposite of what you're telling, Ed. I dont know if you have any information, but if you do, could you please shine some light on this?

Share this post


Link to post

1 - If a given addon installs anywhere inside the core Prepar3D folder structure, it's not compatible.

Pretty cool, that makes a lot of sense!

 

Thanks for the HU WarpD. :smile:

 

- JP

Share this post


Link to post

Thank you Ed. Makes sense, but it will definitely be a pain in the rear... 

 

It had to be done :)

Share this post


Link to post

 

Makes sense, but it will definitely be a pain in the rear...

 

It may just prove to be a show stopper for me if compatibility isn't as good as I hoped it would be. I think that I will step back for the moment, and see what happens. I can still enjoy P3D v2.4 whilst I have a think about it.

Share this post


Link to post

What about freeware scenery packages that were installed manually into Addon Scenery? Where are they now installed? I guess you are probably going to say that they are "no longer compatible", but that isn't the answer I am looking for.

They would need to be installed into a folder elsewhere. Say create a folder named 'Addon Scenery' on a drive somewhere... put your scenerys in it and then update Prepar3D's scenery.cfg file to correctly see them or use the built in scenery library interface... either will work. But there is no valid reason to place them in the core sim folders. They just don't need to be there.

I'm a bit confused. I read on the P3D website:

"Is Prepar3D v3 still backwards compatible with legacy content?

Yes. The Prepar3D development team has partnered with several developers to ensure that most legacy content is backwards compatible."

 

That sounds like quite the opposite of what you're telling, Ed. I dont know if you have any information, but if you do, could you please shine some light on this?

That's not the opposite of anything. You're reading a great deal into their statement. At no point did even I state that you can't continue to install into the core sim's folders with old addons that were not set up to work with Prepar3D... sure, they'll install. However, that's not the correct method of installation for v3 and to be honest there's no legitimate reason to need to install into the core sim folders any longer.

 

There are config files that tell the core sim where to locate everything from scenery to fonts, gauges, sounds, textures... etc. They no longer need to reside inside the core sim folders but can instead be placed outside of them. By adhering to that... updates to the core sim will be far more painless in the future.

Share this post


Link to post

Do you include simobjects (aircraft) in your addon reference or just scenery?

 

I assume texture replacement addons like FTX Global, REX etc will have to be in the core folder structure and therefore require reinstallation following upgrades (just like previous versions).

Share this post


Link to post

Everything, including SimObjects.

Share this post


Link to post

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...

Share this post


Link to post

If you're talking global... if they're not replacing files that already exist (not sure how L-M wants that addressed) then yes they should be in their own installation folders elsewhere with appropriate entries in the correct configuration files for the core sim.

Share this post


Link to post

Makes perfect sense - just link to everything from the core sim. Your addon installations will stay intact during upgrades etc.

Share this post


Link to post

That already makes it a bit clearer to me, thanks Ed. I'm just a user and I dont know much about files-structure and such, so I'm not always convinced I understand things right when programmers are talking tech-talk, so to speak.

Share this post


Link to post

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.

Share this post


Link to post

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

Share this post


Link to post

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

Share this post


Link to post

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

Share this post


Link to post

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

Share this post


Link to post

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.

Share this post


Link to post

 

 


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

 

Ed,

      Is that the reason for the SSD recommendation for V3?

Share this post


Link to post

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.

Share this post


Link to post

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.

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this