Not if the point release/update is to the 'client' portion of the P3D installation.

 

The 'scenery' portion will not be touched and remain intact.

 

This is why LM split the installation into three sections - they can install/uninstall/update each section independently.

Not if the point release/update is to the 'client' portion of the P3D installation.

[...]

This is why LM split the installation into three sections - they can install/uninstall/update each section independently.

 

Precisely :smile: I tried placing some replacement textures outside the main directory, for example, and I couldn't get them to replace the defaults reliably in the sim whether I placed them above or below in texture.cfg. It's a nice concept, and works just fine for simpler add-ons, but it might not work for others. This is where the separate client, content and scenery installers come into play -- no need to reinstall the whole deal if changes are made to one of the components only.

 

Tym

At this point, as I understand it, there is no penalty for installing into the P3D root folder other than having to do a complete reinstall of all add-ons after a point release. For a long time I've been installing a lot of add-ons outside of the root folders and just linking in simobjects.cfg. The problems come from some installers that put files all over the place, gauges, effects, sound, simobjects.

 

There will probably (hah!) be some confusion during this transition but when the dev's adhere to the SDK guidelines it should sort out just fine.

 

Vic

I have a 500 gig Ssd with only prepar3D V3 on it, so after tonight when I install some of my add on's my F drive (Ssd) it's going to look like this

 

Prepar3D

Rex_Texture

Flight1_GTN

 

All these are on the same SSD just in different folders, This is the way LM wants us to do it, Yes ?

 

But does ASN not need to be in the core folder and so does Orbtx?

 

Ok maybe this awnsers my question, So install as many add on's outside the core folder but still on the same SSD in different folders

Elaine - it is not MANDATORY (yet) to install outside the root, just recommended. You can put your files anywhere as long as you establish a link in the respective cfg file. You can havwe effects, simobjects, etc anywhere outside of the P3D3 root just as long as you link them in the cfg file. Whether they are on the same SSD or not isn't a big deal. Logically, you'd want your files on the fastest drive.

 

ASN is working on a method to be compliant but, as with ORBX, there's more work than just a simple folder change.

 

Again, this biggest problem you will run into is that you have to reinstall your addons after every point release.

 

Vic

This new structure for addons is an LM preference and not a necessity.

 

As Saul has already said, addons such as ORBX have to be installed in the main P3D folder.

Correct. Some people here have turned this molehill into a mountain. It would a wonderful world if all add-ons were in their cozy little folder like:

 

<drive:>/Program Files (x86)/Great Add on/

 

but that isn't going to happen in the short term.

I would assume, that you could add en entry in C:\ProgramData\Lockheed Martin\Prepar3D v3\simobjects.cfg

That is exactly what I did with MyTraffic aircraft in P3D 2.5. I don't use these models for AI as such - I installed them only to make use of the visual models in Vpilot when flying online with VATSIM for seeing other users' aircraft. They live on a separate drive, with a link in the P3D simobjects.cfg. Likewise my Pilot's Global Ultimate terrain mesh has always been installed outside of the sim folders in both FSX and P3D, with a simple link in scenery.cfg.

 

I would think most add-on developers for aircraft could easily modify their installers to point somewhere other than /simobjects/airplanes - though for complex aircraft that use many custom DLLs and custom gauges, this might not be so simple.

 

In any case - the new "outside the core sim structure" system is a strong recommendation - not a legal requirement. Doing things the "old" way won't stop the sim from working - nor invalidate the license. LM is simply putting users and developers on warning that there is no guarantee that their add-on products will continue to function after a P3D update IF said add-ons are installed within the core structure of the sim.

Ok... when you get a point release from L-M for v3... you're going to have to uninstall whatever is being updated... and then you're going to install the update. L-M isn't going to do it any other way. That means any files that were overwritten by third parties will be replaced with default files, again. Then you'll have to uninstall/reinstall/repair/beg/cry/scream/etc.

Or update P3D and reinstall any addon that was installed into the v3 folder. Why uninstall or repair, let alone beg cry and scream. What is the difference anyway to what we were used to now? Aren't we used already to reinstalling a lot of things after every update? It's nothing new. Obviously it would make life easier if everyone did what LM wants... but then we would still have to reinstall or edit cfg's to register addons with the updated sim again.

 

Maybe I don't care so much because I usually only have about 2 scenery addons installed and 2 addon planes. All other addons I use are already installed out of the sim folder. But as others have said this is getting a bit exaggerated.

 

Anyway, my rule of thumb is: whenever an installer gives me the option to install elsewhere, I install it on another drive. (I only have SSD's though: if I also had HDD's I would only install addons on that HDD that wouldn't require speed). Whenever I do not get that option the addon usually needs to be in the P3D folder: nothing you can do about that.

Ed, hopefully given the choice between using <insert favorite add-on here> and enduring a handful of potential reinstalls or abstaining from non-compliant add-ones altogether, folks quietly endure the reinstall and politely encourage the developer to consider making it V3 compliant. Hmmm...maybe I have too much faith in my fellow simmers

Here is what John Venema stated on the Orbx website this morning"
 
 
"We're not chaning the location of, or how our products are implemented, period.

To enjoy the visual world Orbx-style requires us to overwrite core system files. It's been that way from day one eight years ago, and it was sanctioned by ACES, thus FTX Central and the need to switch. LM came to the party many years later.

LM recommending that no sceneries live inside the root sim folder is basically eight years too late for us to do anything about it, and there is no difference to performance with our file locations as they are."
 
http://www.orbxsystems.com/forum/topic/103534-prepar3d-v3-free-multi-installers-coming-for-orbx-regions-vector-olc/page-5

 

I'm definitely going to hold off on V3 as this change will make it a real challenge for me if I were to have to re-install the "ton" of Orbx scenery I have every time a hot fix or update comes out. It appears this change, apparently has an effect on Orbx resources as well. The LM file fix, although good in theory, may have a practical effect on the developers, as well as us the consumers.

 
Bill Clark

 

I'm definitely going to hold off on V3 as this change will make it a real challenge for me if I were to have to re-install the "ton" of Orbx scenery I have every time a hot fix or update comes out. It appears this change, apparently has an effect on Orbx resources as well. The LM file fix, although good in theory, may have a practical effect on the developers, as well as us the consumers.

 

Bill Clark

The question is if you really have to reinstall. The new structure of v3 makes it possible to update the core engine without even touching the texture side of the sim. LM has separated v3 into 3 (or 4, I forgot) completely independable updateble (hope I am using the right words here) parts. Besides, if you really have to reinstall things, it wouldn't be different at all from what you had to do with v2. No matter how you look at it and no matter if developers follow LM recommendation, I do think this new structure is a step forward and not something to panick or worry about.

If L-M desires to change the folder layout again... which is their right... it can totally hose anything ORBX is installing.

 

It would be wise to work with L-M and follow the SDK guidelines... rather than arrogantly declare you're doing no such thing!... but, just my $0.02.

If L-M desires to change the folder layout again... which is their right... it can totally hose anything ORBX is installing.

 

It would be wise to work with L-M and follow the SDK guidelines... rather than arrogantly declare you're doing no such thing!... but, just my $0.02.

Well, let me be clear that I do agree on this: it would be best if every developer would follow the recommendation. But well, they won't... and on one hand I don't mind because this probably saves us all a LOT of money for updates. A lot of v3 updates, if not all, seem to come at no cost because the main and often only difference is a simple change/addition of the v3 install path. The future will tell though what would have been the best thing to do...

I think I'm going to lose my mind over this ridiculous molehill -> internet -> mountain malarkey...

 

I'm definitely going to hold off on V3 as this change will make it a real challenge for me if I were to have to re-install the "ton" of Orbx scenery I have every time a hot fix or update comes out. It appears this change, apparently has an effect on Orbx resources as well. The LM file fix, although good in theory, may have a practical effect on the developers, as well as us the consumers.

 

Listen fellas, please.

 

The changes to how P3Dv3 will be updated on point releases is a GOOD THING for everyone who is used to how third-party addons are installed and used. Please follow the examples below.

 

P3Dv2.x:

1. New installer released.
2. Uninstall P3Dv2 from Windows
3. Wipe out P3D directories
4. Install new P3Dv2 installer
5. Reinstall addons

P3Dv3.x:

1. New Client installer released
2. Uninstall P3Dv3 Client from Windows
3. Wipe out Shaders/Config files as directed by LM
4. Install new P3Dv3 Client
5. Fix config files if necessary

Notice the difference?!? No reinstall of all your addons using P3Dv3!

 

You should only need to reinstall any addons that touched default if a new Scenery or Content Installer is released along with the Client.

 

Now can we please all agree that this is a GOOD thing for us and move along?

 

 

 

Just for the craic like  ;-)

 

I corrected that Irish reply for you  :smile:   

+1 As I said, it's a step forward!

Elaine - it is not MANDATORY (yet) to install outside the root, just recommended. You can put your files anywhere as long as you establish a link in the respective cfg file. You can havwe effects, simobjects, etc anywhere outside of the P3D3 root just as long as you link them in the cfg file. Whether they are on the same SSD or not isn't a big deal. Logically, you'd want your files on the fastest drive.

 

ASN is working on a method to be compliant but, as with ORBX, there's more work than just a simple folder change.

 

 

 

Great thank you.