3 minutes ago, GSalden said:

It is more to keep all Addon files outside of the P3Dv5 root. That both ways work fine is true.

Again, keeping the files outside or inside the sim, doesn't make any difference ( good or bad ), if the actual scenery files from V4 need updates to show correctly in V5. There are difference which cannot be fixed by simply using an installation method or the other.

You must change the actual files and, as I've said, while it's reasonably easy to do for the original scenery developer, that knows how his scenery was made and ( assuming he was in the V5 beta ), knows how and where his sceneries are affected, it can be a nightmare for users, trying to figure it out why something doesn't look right.

32 minutes ago, newtie said:

Are you sure? No files get overwritten anywhere? Mark

The P3D installers name each folder with the version name so that not one single file from one version can be seen by another version.

Back on the scenery install topic. I created two partitions on my HD. One very basic with nothing on it but a web browser. I install on that drive into a fake P3D folder and track down all the scenery files and create an add-on.xml

Some or those installs put a lot of files in the base sim folder.

 

20 minutes ago, virtuali said:

Again, keeping the files outside or inside the sim, doesn't make any difference ( good or bad ), if the actual scenery files from V4 need updates to show correctly in V5. There are difference which cannot be fixed by simply using an installation method or the other.

You must change the actual files and, as I've said, while it's reasonably easy to do for the original scenery developer, that knows how his scenery was made and ( assuming he was in the V5 beta ), knows how and where his sceneries are affected, it can be a nightmare for users, trying to figure it out why something doesn't look right.

Out of curiosity, how does this effect photoreal scenery? For example MegaSceneryEarth, and any autogen packages that cover them (e.g. Nuvecta)? Are there any updated necessary for that as well?

14 minutes ago, Benjamin J said:

Out of curiosity, how does this effect photoreal scenery? For example MegaSceneryEarth, and any autogen packages that cover them (e.g. Nuvecta)? Are there any updated necessary for that as well?

Curious also.  I know rob was using the MSE Utah.  I currently use Cali north/south, utah, arizona, colorado, phoenix, florida, nevada in P3DV4

17 minutes ago, Benjamin J said:

Out of curiosity, how does this effect photoreal scenery? For example MegaSceneryEarth, and any autogen packages that cover them (e.g. Nuvecta)? Are there any updated necessary for that as well?

If there is only a scenery + texture folder without extra files it should work both ways..

Rob has already tried several MSE sceneries in V5 ( see his vids )

Edited April 13, 20206 yr by GSalden

3 minutes ago, GSalden said:

If there is only a scenery + texture folder without extra files it should work both ways..

Rob has already tried several MSE sceneries in V5 ( see his vids )

MSE should be as easy as add the new scenery.

or Drop .xml into p3d add-on and done.

Too bad most dev don't trust their customers or else this would have been done along time ago.

1 hour ago, Sesquashtoo said:

You have pretty much made up my mind...that I will certainly have a virgin, separate install of P3D v5, and will populate that install with 3rdP content that has been officially noted as now V5 enabled/modified for.  So, I will enjoy what new features there are...will get use to flying and manipulating the settings and general feel and usage of v5,...but will have a fully functional v4.5 to fly in conjunction. Yep..that's what the plan is for tomorrow!

My plan as well. I have ordered a new 2TB M2 SSD that will be P3DV5 only. 

Greg

 

1 hour ago, Reader said:

The P3D installers name each folder with the version name so that not one single file from one version can be seen by another version.

Thanks.

I'm more inclined to try the new version knowing that I don't have to make a 'trade'. :>)

1 hour ago, micstatic said:

Curious also.  I know rob was using the MSE Utah.  I currently use Cali north/south, utah, arizona, colorado, phoenix, florida, nevada in P3DV4

 

1 hour ago, GSalden said:

If there is only a scenery + texture folder without extra files it should work both ways..

Rob has already tried several MSE sceneries in V5 ( see his vids )

True, forgot about that! Thanks guys for reminding me of this. So at least it'll work. I only asked because Umberto suggested that some sceneries will need updating if they already use 'modern' P3Dv4.4.-specific features, such as PBR etc. I'm not sure if there has been any change in how photoreal scenery is implemented, so that it would require an update. I sure as hell hope not... The thought of downloading a special version of P3Dv5 makes me cringe. Like you, @micstatic, I have a lot of MegaSceneryEarth installed, as well as bunch of Matthias' photosceneries. Hundreds of gigabytes of data I'd rather not have to reinstall.

6 minutes ago, Benjamin J said:

 

True, forgot about that! Thanks guys for reminding me of this. So at least it'll work. I only asked because Umberto suggested that some sceneries will need updating if they already use 'modern' P3Dv4.4.-specific features, such as PBR etc. I'm not sure if there has been any change in how photoreal scenery is implemented, so that it would require an update. I sure as hell hope not... The thought of downloading a special version of P3Dv5 makes me cringe. Like you, @micstatic, I have a lot of MegaSceneryEarth installed, as well as bunch of Matthias' photosceneries. Hundreds of gigabytes of data I'd rather not have to reinstall.

No issues with pr scenery from MSE or from Matthias...

PR scenery are only photo tiles + AG. 

If the developer adds custom objects that use new features then you need to pay attention to that and wait for a V5 installer.

But that is mainly with airports.

I guess that Orbx won’t release the TE series tomorrow with all new features. 
So you probably will install the current versions with new installers through Central.

1 minute ago, GSalden said:

No issues with pr scenery from MSE or from Matthias...

PR scenery are only photo tiles + AG. 

If the developer adds custom objects that use new features then you need to pay attention to that and wait for a V5 installer.

But that is mainly with airports.

I guess that Orbx won’t release the TE series tomorrow with all new features. 
So you probably will install the current versions with new installers through Central.

Well, that is the point, right...? That is exactly what I'm expecting, but I'm hoping to hear from somebody with access to the beta about this. If you indeed have that access - then I'm glad to hear that you can confirm my hypothesis.

6 hours ago, DJJose said:

Let us not forget about SODE. A new version is needed and updates to each airport that requires SODE will need to be offered by the dev. As Ricardo from LatinVFR pointed out.

Most of my sceneries still install the old fashion way with files going everywhere including effects, global scenery, sounds, etc. We could try to trick the installers but we would still need to check the SODE files. Make a backup of the SODE folder just in case.

Oliver is the expert in this area so I'll defer to him.

SODE 1.67 is for V5 and is available now.

I believe addons which are in the Prepar3d V4 addons directory (or externally installed) - those should be super easy to work in P3Dv5

Well those inside the root directory - well that will be annoying as files could be in multiple directories.  Devs should follow the new method - save time and agony.  It would be fun to see A2A birds pop up immediately as they follow the new method of installation for p3dv4 anyway.

Edited April 13, 20206 yr by Skywolf

Why it's so difficult to wait 3-4 weeks, while the things with add-ones settle down. Then the same gang of "early adopters" will be crying river of tears blaming developers etc.