I'm very curious to see how popular texture replacement products like for example FTX Global or REX will solve the challenges imposed by the new recommendations.

didn't have to update P3D for hotfixes/updates, they did it themselves.  It was the 3rd party stuff needed updating sometimes.  These are LM recommendations to avoid that in future, but are more likely to be followed for new developments, not existing stuff surely.  In fact it's not so hard to deal with aircraft/effects/sounds or scenery but  quite a lot of existing 3rd P does make serious changes to texture folders and such - think REX , FScene, UTX - and OrbX ain't going to change in the near future.  Hard to see  how the right textures would be pulled in if held externally.

Saul put a post on the LM forum (under "space") explaining suggested paths, but it does require user/developer changes to the respective .cfgs.   If the .cfgs are updated in an LM fix then those mods need to be remade after. 

 

edit: ah I see Penz just beat me to it re textures!

I'm very curious to see how popular texture replacement products like for example FTX Global or REX will solve the challenges imposed by the new recommendations.

 

Me too, if they use some `offsite` storage and texture replacement practice (as both the above do) then it will be necessary for a reinstall or fallback option to restore original files in order for updates to install properly, for troubleshooting purposes or simply to avoid duplication (which only one of the above currently does).

 

There's no intrinsic difficulty storing information/files outside the core structure, but when those files change the core structure by supplanting on a like-for-like or name-for-name basis, then there is going to have to be a reversion capability. 

As Louis has said previously, a solid structure is required to be set in stone if LM wish to pursue external addon installations.

 

Although it would take up more disk space, duplicate texture, scenery, gauges etc,etc folders should be created externally to the main folder structure where addons can be installed. A simple flag can then be set in the cfg to instruct P3D to read from these folders, thus preserving the originals.

 

Texture replacement addons would then not overwrite the core, original textures and reversion would simply be a matter of resetting a flag.

The FSUIPC registration window does not pop up for me when installing the latest beta.  It recognizes P3D v3 and installs but then doesn't give me the window to enter my registration information.  Anyone else have this problem?

Although it would take up more disk space, duplicate texture, scenery, gauges etc,etc folders should be created externally to the main folder structure ...

That's how I have done to test my own stuff, adding entries to "my" folders to the P3D appdata config files.

 

Still testing how it works. I suppose a texture replacement addon could take priority over the stock files by altering the sequence in "texture.cfg".

I'm very curious to see how popular texture replacement products like for example FTX Global or REX will solve the challenges imposed by the new recommendations.

Ok... this is easy. Assuming that the order of entries in the texture.cfg file is the order of searching for a given file (it should be)... then whichever version of a physical file you find first is the one that gets used.

REX4 and soft clouds inside info - thanks Tim as per instructions if I were you do not install wave animations and sun flare 

 

All good, except for a couple things:

 

1. Sun, flare and effects need to be altered per v3.

2. Wave animation alterations, so waves animate at higher altitude

 

Other than that, select P3D v.2.5 in REX4, then locate the MAIN P3Dv3 folder and you're good to go

The FSUIPC registration window does not pop up for me when installing the latest beta.  It recognizes P3D v3 and installs but then doesn't give me the window to enter my registration information.  Anyone else have this problem?

 

 

You are not alone, made a topic about on Pete's forum but he is away for two more days i think. ;-)

On FSUIPC, if you install the latest non-beta production release into FSX or P3D V2 and register it, then install the 4.945a beta, it'll find and install to P3D V3 on its own and then you should get a registration window that lets you keep the existing resitration.  At least that's how it worked for me.

 

Regards

Is it just me or is this v3 sun smaller than the v2 one...

I installed P3D V3 and rebooted and went in checked it out and everything seemed normal

 

I then installed Flightbeam KSFO.. and all hell breaks lose

 

Its trying to reactiviate every single FSDT airports that I have..because I added a new SSD for the P3D v3  and I just hit enter multiple trimes to get out of it.. I didn't have the patience to go and register each of the FSDT airports (I have all of them) and then when it tries to load KSFO It freezes with black screen saying out of memory.. I am rebooting my machine now.

 

edited to add:

 

I restarted my machine and loaded the saved KSFO and it seems ok. I have 2.5G available VAS while sitting in KSFO

I'm very curious to see how popular texture replacement products like for example FTX Global or REX will solve the challenges imposed by the new recommendations.

Orbx already said they won't follow the recommendation. So no challenges for them to solve. Simple as that. After all, it's only a recommendation.

Lewis B. of A2A has posted on their official forums that their P3d V2 installers worked properly with the last P3d V3 closed beta release, but A2A is still testing them with the release version of V3.

Lewis B. of A2A has posted on their official forums that their P3d V2 installers worked properly with the last P3d V3 closed beta release, but A2A is still testing them with the release version of V3.

Great news. Bit odd though because yesterday or the day before Scott of A2A posted that making their planes v3 compatible could be very complicated and that it would come at a cost... which on its own was also odd because there already are users who us A2A planes in v3...