Please do not use this thread to discuss how to install someone's addon. As is stated at the top of this forum, that type of discussion is not allowed.

 

This thread is here simply to help users understand that a v3 compatible addon now needs to adhere to new expectations by Lockheed-Martin regarding installation location.

Thanks Ed, for explaining all this. Good to know as we move forward. 

Just to be clear, I can install p3d on my SSD and add-ons on my HDD? 

Yes.

Yes.

Thanks. 

Seems like the Fly Tampas Copenhagen installer finds the P3D v3 folder right away. Works great as well with VAS being considerable lower!

Seems like the Fly Tampas Copenhagen installer finds the P3D v3 folder right away. Works great as well with VAS being considerable lower!

 

Well, that's just wrong, according to L-M recommendations.

Just to be clear, I can install p3d on my SSD and add-ons on my HDD? 

 

You should think about which add ons you would want to put on an HDD though. You put P3D on an SSD for a reason and some add ons should be put on that SSD for the same reason. Most of the add ons that would have been installed into the P3D v2 folder I would also install on the SSD.

Official Lockheed-Martin guidance on add-on installs is here:

http://prepar3d.com/SDKv3/LearningCenter/add-ons/add-on_configuration.html

 

and here:

http://prepar3d.com/SDKv3/LearningCenter/add-ons/add-on_instructions_for_developers.html

 

Additionally, there's a thread at the official Prepar3D forums where Saul James explains how the end-user should set things up:

http://www.prepar3d.com/forum/viewtopic.php?f=6312&t=113619

Well, that's just wrong, according to L-M recommendations.

 

Hm, ok how do you know? 

 

I haven't tested myself. Just saw a post by someone I follow on Instagram having installed this scenery into P3D v3. I asked him how he did it and he replied the old installer found the v3 folder right away.

Interesting that Saul at LM has pointed out that ORBx scenery still needs to go in the main Prepar3D folder. Is that until new installers are created, or are ORBx treated as a special case?? :huh:

I think what Saul means is that some addons, e.g. ORBX, have to be installed in the main folder structure due to the way they operate and manipulate certain core files.

Saul's explanation on setup is a suggestion based on what he personally is doing, it is not a rule - same as the new structure is recommended not you must. There is no standard (yet?)

The blunt truth is that if a developer does't follow the recommendations, there is nothing LM can or really want to do - P3D and the 3PDs need each other. If the add-on is liable to need reinstalling after P3D update or god forbid a partial or full P3D reinstall, it's you as user that chooses - don't buy or take the risk.

 

Orbx puts own textures in world folders amongst others - for pure scenery .bgls etc it is not inconceivable that the scenery and texture folders could be outside and just referenced in the scenery library, however, it's those mods in the FS base structure that make it problematic - textures, autogen etc and I don't even know what with things like the animations. The jury is out whether can't or won't applies. Certainly OrbX won't be the only ones who maybe read recommended and think, yes, when we've got time.

 

FWIW at the moment, v3 running well on my machine, but of course no add-ons like complex aircraft, no FTX, no complex airports, just scenery adds where all I need is scenery library paths. Can't do sensible test runs without a lot more in and certainly hoping not to wait forever while completely new installers/folder structures set up by developers. That said, LM accidentally refunded my 2.5 subscription and I don't think I'll renew unless v3 falls apart. I can wait a few weeks for FTX, and I'm sure the first v3 installers from 3PD add-ons will use old structure - as some already have. Scenery already held externally is no problem, so?

All right for the youngsters, but at 2 years per version i might get to v5, but then too past it or worse (anyway I've still got a fairly good FSX with ALL the add-ons - including those that don't work/don't show in P3D

Birdmanmike... when L-M tells developers to change where they're installing... it would be wise for developers to listen.

 

It is possible to override what Prepar3D sees for textures without overwriting the ones that are part of the core installation. It just requires that one do the correct configuration.

Birdmanmike... when L-M tells developers to change where they're installing... it would be wise for developers to listen.

 

It is possible to override what Prepar3D sees for textures without overwriting the ones that are part of the core installation. It just requires that one do the correct configuration.

 

 

Orbx made it clear today they won't change their way of doing things so their add ons will install into the v3 folder and they will overwrite core files. No matter what LM thinks of it.

Certainly OrbX won't be the only ones who maybe read "recommended" and think, yes, when we've got time.

 

They don't even think 'when we've got time'. Here's the quote:

 

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