Sign in to follow this  
Richard Sennett

V3 Developer updated software thread

Recommended Posts

Just throwing this out there - can we have one thread here when someone is aware of a V3 updated addon we can post it here ? 

Share this post


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

You beat me to it.

 

KSFOHD cannot be installed with 2.xx still on the drive, BTW.

 

I removed my old version and it installed just fine.

Share this post


Link to post

How do you uninstall the version 2.xx?

Jim

 

 

EDIT: forget it... I figured it out!

Share this post


Link to post

PrecipitFX updated - just launch exe and V3 option is there to choose

Share this post


Link to post

PMDG NGX and B777...not recommended to install with multiple versions, but can be done (legally).

ASN (beta)  build 5751 (new version already out after a problem with initial release)

All Virtuali interfaced products (FSDreamteam/Flightbeam) -- requires at least v 3.0.0.8 of bglmanx.dll (Addon Manager)

Drzweicki EETN (Talinn) released new version today with V3 installer

FSUIPC beta 4.945a detects and installs into V3, but throws a warning since it was built on a pre-release P3D3 beta

UTX Canada v2 (release imminent) comes with native v3 installer, patches for UTX USA/EU V2 expected in days

MyTraffic 6.0 installable by pointing installer to V3 directory (dev is soliciting feedback from anyone having issues)

Radar Contact V4 and most other add-ons that use pure FSUIPC connectivity to the sim (QuantumLeap, VasMon etc)

 

Regards

Share this post


Link to post

I managed to get Aivlasoft EFB working but an official update from them should be out shortly.

 

vPilot also seems to work with no issues (with all legacy and current simconnect libraries installed)

 

No issues with the Majestic Q400 although again, the official update from them is not yet out.

Share this post


Link to post

Isn't it just easier to copy the V3 registry entries as V2 (which is all the difference there is - a 2 became a 3) and install everything as it was V2?

 

If there are no EULA stuff you have to respect, that can be done and works like a charm. In my country you own the software you buy, so forgive me if you can't by some reason.

Share this post


Link to post

Richard, maybe you can update your first post and list this compatible addons in first post? I think it will be much better. 

Share this post


Link to post

Isn't it just easier to copy the V3 registry entries as V2 (which is all the difference there is - a 2 became a 3) and install everything as it was V2?

 

If there are no EULA stuff you have to respect, that can be done and works like a charm. In my country you own the software you buy, so forgive me if you can't by some reason.

 

No, substantial changes have been made in V3, Not only that, the primary P3D folders are now NOT the place to place addons - this is precisely why we need this topic as it's almost certain that several of these quick release solutions are NOT actually P3D compliant, so we need to highlight those that are.

Share this post


Link to post

No, substantial changes have been made in V3, Not only that, the primary P3D folders are now NOT the place to place addons - this is precisely why we need this topic as it's almost certain that several of these quick release solutions are NOT actually P3D compliant, so we need to highlight those that are.

 

Sure. I just didn't want to reinstall everything i had.

 

I think that it was about time that developers would stop cluttering the FSX/P3D folders with their software and also modifying original FS files which is pretty bad as well (although sometimes required with FSX - older software). With active development that should stop.

Share this post


Link to post

We are two days in to V3. Now is not the time to be rushing to install anything.

 

It looks already like developers are not heeding L-M recommendations, and I for one would like to understand the implications of this before I point any installer or manually add ANY addon to the mix. 

Share this post


Link to post

It looks already like developers are not heeding L-M recommendations, and I for one would like to understand the implications of this before I point any installer or manually add ANY addon to the mix. 

The implications are, next time LM comes with an update or hotfix, you - and me - can start re-installing P3D3 anew, as it was in P3D2. Very bad.

 

Im my eyes the new guidelines are one of the most clever features of P3D3. If they would be respected by our beloved developers, of course.

 

Kind regards, Michael

Share this post


Link to post

It looks already like developers are not heeding L-M recommendations ...

It will certainly take some time until 3rd party can catch up with the changes.

 

On the other hand, people desperately want to use their products in the new P3D, so I can very well understand the developer dilemma.

Share this post


Link to post

 

It looks already like developers are not heeding L-M recommendations, and I for one would like to understand the implications of this before I point any installer or manually add ANY addon to the mix.

 

Yes, I would prefer to install my existing addons to comply with the new file and folder structure implemented for v3. If we stick to that, then we should all be able to avoid any excessive reinstall headaches when the core sim is upgraded.

Share this post


Link to post

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.

Share this post


Link to post

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!

Share this post


Link to post

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. 

Share this post


Link to post

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.

Share this post


Link to post

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?

Share this post


Link to post

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

Share this post


Link to post

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.

Share this post


Link to post

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

Share this post


Link to post

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

Share this post


Link to post

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

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