Sign in to follow this  
Jim Young

Installing 3rd Party Software into Updated Versions of P3D

Recommended Posts

With the pending release of an updated version of P3D, AVSIM members who have problems installing 3rd Party Software into updated versions of P3D should contact the vendor for instructions on how to install the software.  In most cases the vendor will have to release an updated installer.  Please do not use these forums for discussing how to modify a 3rd Party addon to make it work in a later version of P3D. 

 

When the new version of P3D is released, it may take some time for 3rd Party vendors to create an installer for the new version.  We recommend you keep the current version installed and install the next version in another folder if you would like to continue using your addons.  Most likely addon vendors will have new installers or instructions for installing their product(s) soon after the release of the updated P3D version.

 

Some 3rd Party vendors may charge a fee for providing an update to their respective software for installation into later versions of P3D.  If this is the case, it could be against the vendor’s EULAs or license agreements for you to attempt to install a current version of their product(s) into a later version of P3D.  Discussions regarding those vendors that require a new EULA and/or installer for V3 will be prohibited.
 
Photos and video:  Photos and videos showing 3rd Party Software whose EULA would be violated for updated versions of P3D will be removed at the discretion of our moderators. If 3rd Party vendor's software can be installed into later versions of P3D without modification then this information will be allowed and can be discussed.  Otherwise it will be removed.  
 
Please use this forum to discuss the update to P3D such as installation problems, P3D configurations, display driver configurations, and issues such as those relating to FPS and Virtual Address Space (VAS).  Once the 3rd Party Software products have been updated for use in later versions of P3D, you can then begin discussing the addons.
 
Thanks to everyone for your cooperation.

Share this post


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

3d party software? lol

 

I believe you were looking for 3rd party, right?   I had to scratch my head over that one, thinking we were on the verge of implementing cutting edge software to make the plane pop out of the screen. :)

 

Good thinking with this article though and hopefully, it'll cut down on the needless banter with folks wanting to hack their sims.

 

Thanks Jim.

 

-Jim

Share this post


Link to post

With the pending release of an updated version of P3D, AVSIM members who have problems installing 3rd Party Software into updated versions of P3D should contact the vendor for instructions on how to install the software.  ...

 

...Thanks to everyone for your cooperation.

Well Jim, I don't know if I do or don't have problems, but...

 

I've read the manual for the FSCubed Scenery Backup Tool and I see no place that they claim to handle a new OS (think registry entries - hidden and otherwise). Or, for that matter, I don't see anything indicating it will handle anything like ORBX which stores data outside of the parent FSX folder structure. Has anyone actually tried to use it?Doug

Yup; I backed up my Prepar3d v2.5 scenery files last weekend, which produced a 351GB. At a theoretical 50% compression! I am astounded to find I have almost 3/4 TERRABYTES of scenery files!!!

 

I backed up a And ...theoretically, I will be restoring to P3d V3.0 shortly after 12am (-5 Zulu)...I will let you know.

 

Chas

Share this post


Link to post

Jim,

 

Can I ask, does this apply also to developers who have left the field?  Earth Simulations springs to mind, and people will have to modify their current (extremely good) ES scenery to work in v3, as there will be no other avenue to do so since the developer is out of business and no longer providing support...  In such a scenario, help and support provided by Avsim members could be invaluable - Could you advise please?

 

Thanks K

Share this post


Link to post

Kevin - Jim can expand on this but we realize that there will be many situations that just don't "fit" the guidelines and need to be dealt with individually.

 

I would think that developers who are out of business present an unique situation.

 

Vic

Share this post


Link to post

You can add Jon Patch's Vancouver 3+ and Victoria, another two masterpieces now orphaned.

 

Kind regards, Michael

Share this post


Link to post

 

 


I believe you were looking for 3rd party, right?

 

That's correct Jim.  I corrected the typo's.  Thanks for your help!

 

Best regards,

Share this post


Link to post

I just purchased P3D V3 this afternoon and before being allowed to add it to my cart, I was greeted with a rather lengthy EULA which I actually read completely, taking note of add-on installs and LM's stance on it's own software.  I highly encourage everyone to actually take the time to read it.  This reinforces Jim's latest statements and comments, which are not to be taken lightly.

 

On a related note, I'll be having fun downloading this beast tonight. lol

 

-Jim

Share this post


Link to post

Jim,

 

As you just closed a topic I started, a question for clarification: I understood your post such that avsim would not want users to discuss ways to use a 3rd party add-on with V3 before the developer gives its consent to it. This sounds reasonable to me.

However, asking about the time line, schedule or plans to make an add-on compatible by the developer would be interesting for everyone who wants to benefit from V3 now and who wants to find out an estimate of the if and when he/she can count on the availability of an updated version.

Basically, because no one can read all forums all the time, this would help users manage their expectations. If you don't want this to be shared on avsim not a problem, just let us know please. I find it always useful to share update information for the community.

 

Cheers

Hans

 

Share this post


Link to post

This is real simple Avsim has always had an ultra tight butthole for this stuff. If you have any questions about this there are other places on the internet that can answer them just don't ask about them here.

Share this post


Link to post

Well Jim, I don't know if I do or don't have problems, but...

 

 

Yup; I backed up my Prepar3d v2.5 scenery files last weekend, which produced a 351GB. At a theoretical 50% compression! I am astounded to find I have almost 3/4 TERRABYTES of scenery files!!!

 

I backed up a And ...theoretically, I will be restoring to P3d V3.0 shortly after 12am (-5 Zulu)...I will let you know.

 

Chas

351 Gb of scenery ?

 

Luckely I am not the only one with a lot of scenery :

- 513 SSD --> 455 Gb scenery

- 256 SSD --> 215 Gb scenery

- 128 SSD --> P3D + 30 Gb scenery

Share this post


Link to post

This is real simple Avsim has always had an ultra tight butthole for this stuff. If you have any questions about this there are other places on the internet that can answer them just don't ask about them here.

I believe, more appropriately, that if you feel you need to ask such a question, you can always send a PM. :)

 

-Jim

Share this post


Link to post

Jim,

 

As you just closed a topic I started, a question for clarification: I understood your post such that avsim would not want users to discuss ways to use a 3rd party add-on with V3 before the developer gives its consent to it. This sounds reasonable to me.

However, asking about the time line, schedule or plans to make an add-on compatible by the developer would be interesting for everyone who wants to benefit from V3 now and who wants to find out an estimate of the if and when he/she can count on the availability of an updated version.

Basically, because no one can read all forums all the time, this would help users manage their expectations. If you don't want this to be shared on avsim not a problem, just let us know please. I find it always useful to share update information for the community.

 

Cheers

Hans

We are just trying to nip the possible discussions into how you can install PMDG aircraft into v3 in the bud (they have already released their installers so that's okay now.  We are just suggesting you wait until a 3rd party developer provides instructions or an installer.  Meanwhile, you have plenty of time to play with P3Dv3 to see what it looks like.  How is it configured?  What are some new features?  What are fps like?  But, immediately everyone seems to discuss 3rd party addons and whether they are compatible or not.  Why would you want to know that?  Every 3rd party addon made for FSX and P3D v3 will be compatible.  Compatibility questions sometimes lead to EULAs but not all of the time.  Anything related to the LM EULA will be removed immediately so while people are discussing 3rd party compatibility, someone else is wondering why the LM EULA does not allow products in P3Dv2 to be automatically ported over to the new version v3 and then we have major problems.  When you bought an addon, there was a developer who made the product.  Maybe he wants to charge you for the update to v3?  Then we are going to see people mad at the developer as their EULA only allows installation into v2.5 and not for 3.0.  So, please wait until you get the word and don't go trolling for people to tell you how to make it compatible.  AVSIM forums are not going to be used for those who troll for ways to get around a developers EULA.  This is one reason why websites have moderators... to police the community to make sure people abide by the AVSIM Terms of Service.  EULAs are there and so are EULA busting.  Why can't I discuss EULA's or get upset when one does discuss how to circumvent an developer's EULA?  I know there are a lot of you who have done a lot of EULA busting in your lifetime.  It's fun.  It's like hacking.  Fun stuff.  Sometimes people break the law in their local communities just for the heck of it and it see if they can get away with it.  It's not my law that we protect EULA's.  It's the AVSIM's law (Terms of Service) that were passed by the AVSIM Board of Directors' and CEO of AVSIM (before my time). 

 

If you want to break the suggestions the moderators and I came up with to help you move up to v3 and continue to push for whether a product is compatible or not with the new P3D, then expect actions as our moderators deem appropriate.

 

Best regards,

Share this post


Link to post

Jim

 

Just so we're clear - L-M EULA has never proscribed retro-compatibility - indeed in V3 they've even improved merging for older FS9-based product. Issues of compatibiity are not, never were, and never will be a problem of Lockheed-Martin licensing.

 

The rules should ONLY be focussed on the bypassing of addon developers EULA and interpretations of proper use.

 

There is, as we are seeing already, quite a pressing need for a compatibility topic that discusses whether a new installer supposedly for V3 is actually compatible. I don't want to pick individual cases, but you used PMDG as the example and it is already clear that their new installer is NOT V3 compliant as it does not obey L-M's instructions on NOT pervading the core file structure. 

 

I would say THAT is very necessary - even vital - topic for discussion. I would also say that in a proprietary forum such topics are unlikely to remain on view for long.

Share this post


Link to post

Jim

 

Just so we're clear - L-M EULA has never proscribed retro-compatibility - indeed in V3 they've even improved merging for older FS9-based product. Issues of compatibiity are not, never were, and never will be a problem of Lockheed-Martin licensing.

 

The rules should ONLY be focussed on the bypassing of addon developers EULA and interpretations of proper use.

 

There is, as we are seeing already, quite a pressing need for a compatibility topic that discusses whether a new installer supposedly for V3 is actually compatible. I don't want to pick individual cases, but you used PMDG as the example and it is already clear that their new installer is NOT V3 compliant as it does not obey L-M's instructions on NOT pervading the core file structure. 

 

I would say THAT is very necessary - even vital - topic for discussion. I would also say that in a proprietary forum such topics are unlikely to remain on view for long.

 

+1

Share this post


Link to post

but you used PMDG as the example and it is already clear that their new installer is NOT V3 compliant as it does not obey L-M's instructions on NOT pervading the core file structure.

O, please, let it go, Louis. No one has to obey LM on this. It is a recommendation and it seems a lot if not most developers will ignore it. So PMDG's installers ARE officially and actually v3 compatible, period, just as the Orbx installers will be, which will also install into the v3 folder. The biggest change in the core file structure has been made by LM itself: various parts are installed completely separate now and can be updated without even touching the other parts. If a developer decides to follow the recommendation, great, but don't wait for everyone to do this and don't treat perfectly fine v3 compatible installers as if they aren't compatible.

Share this post


Link to post

Jim

 

Just so we're clear - L-M EULA has never proscribed retro-compatibility - indeed in V3 they've even improved merging for older FS9-based product. Issues of compatibiity are not, never were, and never will be a problem of Lockheed-Martin licensing.

 

The rules should ONLY be focussed on the bypassing of addon developers EULA and interpretations of proper use.

 

There is, as we are seeing already, quite a pressing need for a compatibility topic that discusses whether a new installer supposedly for V3 is actually compatible. I don't want to pick individual cases, but you used PMDG as the example and it is already clear that their new installer is NOT V3 compliant as it does not obey L-M's instructions on NOT pervading the core file structure.

 

I would say THAT is very necessary - even vital - topic for discussion. I would also say that in a proprietary forum such topics are unlikely to remain on view for long.

+3

Share this post


Link to post

Jim

 

Just so we're clear - L-M EULA has never proscribed retro-compatibility - indeed in V3 they've even improved merging for older FS9-based product. Issues of compatibiity are not, never were, and never will be a problem of Lockheed-Martin licensing.

 

The rules should ONLY be focussed on the bypassing of addon developers EULA and interpretations of proper use.

 

There is, as we are seeing already, quite a pressing need for a compatibility topic that discusses whether a new installer supposedly for V3 is actually compatible. I don't want to pick individual cases, but you used PMDG as the example and it is already clear that their new installer is NOT V3 compliant as it does not obey L-M's instructions on NOT pervading the core file structure.

 

I would say THAT is very necessary - even vital - topic for discussion. I would also say that in a proprietary forum such topics are unlikely to remain on view for long.

I am not trying to prohibit any discussions here. I and some moderators put this together as suggestions for installing addons into any updated versions of P3D. I suggested at the end to discuss the P3D.cfg settings and the fps and how good the product is instead of coming here and asking whether a product is compatible or can be installed in P3Dv3. Wait for the installers or go to the developers website and download the installer or get instructions on how to get your addon installed into P3D. We wanted to be careful that no one got into EULA or license agreements between you and the vendor. This topic is all suggestions. We are not trying to add anything to the AVSIM Terms of Service here. We will enforce any violation of the AVSIM Terms of Service and any Lockheed Martin EULA discussions prohibited by another pinned topic here. So far I think most of us have been cooperative and keeping most of the discussions about the P3Dv3 product to how well it is working and some config discussions.

 

If it is okay for the developer of the fs9 based products to place his product into P3Dv3, then there is no problem. Many of the developers of FS9 products have products made for FSX, FSX-SE, and P3Dv2 and 3. They are charging money for these updated programs. The old FS9 related product might work well in P3Dv3 and LM does not have any problems with this. The developer of the FS9 product might have a problem though. He or she spent a lot of money and time and effort to upgrade his old fs9 products to work properly in FSX, FSX-SE, or P3Dv2 or 3. So, if the developer of the FS9 product has no problems with you putting his/her products in P3Dv3, then I see no problems with the discussing this in this forum. I have always thought that what you do in the privacy of your own house is your business. But, coming here and telling the world how to get around buying the developers updated versions of his old fs9 product and installing it into P3Dv3 cannot be allowed. Can it?

 

I realize that back in the good old days of FS2000, FS2002, and earlier, many members were telling everyone how to install the older products into the newer products. Microsoft and commercial developers were even telling them how to do it too. Commercial developers turned a blind eye to it all but then decided to get serious and come up with EULA's and license agreements between you and them to prevent this from happening. This is their product that they developed and spent a lot of time and money to develop it. Now they would like to make some money for all of their hard work. Many commercial developers still turn a blind eye but many, like PMDG, have decided they want to fully enforce their EULA. They have a business to run and I don't want AVSIM Forums to be used by some to circumvent EULAs and install their old products into this new product. So it is dangerous territory when you start discussing how to get around a developer's EULA that was made between you and the vendor instead of purchasing their updated version. Why have EULA's if many, not all, are going to violate their terms?

 

I realize there are many FS9 products that have no EULA's and those products can be discussed here to let our members know how you got the product to work in P3Dv3. There are FS9 products that were never ever updated and those can be discussed here. But please be careful with those products with EULA's.

 

I hope you understand AVSIM's position. You should also be aware that P3Dv3 may crash or freeze because you installed old fs9 or fsx products. If you get a crash or freeze, you should not expect LM to provide support for P3dv3 and all of your addons. You do it at your own risk. If you do have a crash or freeze, the old products would be the first ones I would suspect. P3Dv3 runs perfectly without any addons but when you start installing these addons and problems occur, I don't think you should blame LM for your problems. My two-cents.

 

Best regards,

  • Upvote 1

Share this post


Link to post

There are 3rd party developers that take their time , read months, to make their addon installers P3Dv3 compatible. ...

 

Imho if there are ways to make an addon compatible now I really would like to know and not wait for months.

 

Eg : I use the Ifly CBE in P3Dv2. Updated installers for the regular P3Dv2 Ifly won't be released for quiet a while.

The CBE , working in P3Dv2 won't be updated at all.

 

So if someone is succeeding in getting it to work I really would like to know.

 

Just my 2 cents...

Share this post


Link to post

OK, then accept the fact that:

 

1: You will be committing to a full reinstall when the modules are updated.

2: The timescales mean any 60-day refund on V3 is going to be meaningless. They are very strict on the 60-day limit, quite rightly IMHO.

3: The rush to simply allow installation may preclude or prevent optimisation to suit the new platform. 

4: You may be breaching the addon EULA. 

 

Then install away, it's your sim and you can do what you want - except come to this forum for assistance when something doesn't work, or tell anyone else when it does !

 

Some might feel that last bit is the real deal-breaker. I can't see this policy ending well, Gerard. But hey, at least you will get practised in re-installation - probably a lot more if  L-M use the opportunity to create more point updates.

Share this post


Link to post

Just not so - it's the 3rd party product would need the re-install - as it has been with 2.5, where the P3D update reverted the bits that the 3PD had modded.  And anyway, even if,  my install of P3D took just about 5 minutes.  So if you backed up the install files its no problem.  I back up all  installers, the FS and the 3PD stuff, including OrbX.

 

Ever get the feeling you're the only one marching in step?

Share this post


Link to post

351 Gb of scenery ?

 

Luckely I am not the only one with a lot of scenery :

- 513 SSD --> 455 Gb scenery

- 256 SSD --> 215 Gb scenery

- 128 SSD --> P3D + 30 Gb scenery

That is 702 GB Uncompressed... And that is over three drives, 2 of which are SSD…

 

The FSCubed author is going to be working with me as to how to restore into the 3.0 environment.

 

Regards,

 

Chas

Share this post


Link to post

Chas - There is already a V3 version available. The instructions say to snapshot using the V2.5 version and restore using the V3.

 

Haven't tested it.

 

@gerard - the problem comes when the dev decides the will charge for the new installer and we have been telling users how to port it over free of charge.

 

Unfortunately not everything is black or white.

 

Vic

Share this post


Link to post

The problem is people think that their license applies to whatever sim they want to apply it to. Ask. If you get no response, assume no... only an actual yes from said developer means the license applies to whatever sim.

Share this post


Link to post

My problem was, the author indicated that FSCubed for P3Dv3.0, restored all files from the 2.5 backup into the native home directory of P3D ...And that presented real problems for me because I don't have the Drive space on Drive I:

 

... I will quote from the my convos with the author below;

-----------

Baher,

 

Greetings. I have now purchased and downloaded P3d, and I started asking myself, what am I going to do with the files that are already in place, and have not moved and the files that are going into the new P 3-D?

 

In other words I have scenery files on drive L:, I:,N:. See the enclosed Scenery.cfg text file.

 

Drive I: is the 250GB home drive of P3DV2.on my 500GB SSD .The other 250GB Is drive L: holding scenery. L: does not/should not move. The same goes for the scenery files on Drive N:.

 

When I upgrade to P3D V3, I am going to take the existing P3D v2.5 folder from Drive I:, and MOVE it to an archive folder on another drive, thus freeing up space for the P3D V3 install and its files on Drive I:.

 

P3D V3 will then be installed in the space left by P3D v2.5 on Drive I: . Therefore, the ONLY Scenery FILES that will need restoring are those that used to reside on Drive I:.

 

...NOT on drive L: or Drive N:, thus the need for selected/selective backup and restore. Just how do I do that? I see nothing in the manual about a selective or partial restore.

 

I am sure you have thoroughly tested FSCubed for P3Dv3.0, but put yourself in my shoes.

 

I already have functioning scenery files already in place on L: and N:

 

Why would I over-write them with an untested product?

 

Thanks,and have a wonderful day!

 

Chas

(iPD)

 

---

On Oct 2, 2015, at 4:25 PM, Baher Abouelfittouh <baher.hosni@simdesigngroup.com> wrote:

 

If you carefully read the featured for FSCubed, you will find that it collects all the scenery from wherever it is on your PC. That means, it will not overwrite anything. FSCubed will restore all the scenery within your sim's folder. That means that the drive containing your new sim needs to be big enough to accommodate the totality of your scenery.

 

Hope that helps

 

I am open for more help and support at any time

 

------

I can't afford a Terrebyte size SSD...SELECTIVE RESTORE is the only acceptable answer for me....ahhhh welllll.

 

Thanks,and have a wonderful day!

 

Chas

(iPD)

----

On Oct 2, 2015, at 4:32 PM, Baher Abouelfittouh <baher.hosni@simdesigngroup.com> wrote:

 

Let me make you feel better about this undertaking. If you allow me a few days, I can show some gratitude for the healing vibes by helping you manually do the migration!

 

What say you? ;)

-----

"Sounds wonderful!

 

Waiting with baited breath!

 

Thanks,and have a wonderful day!

 

Chas

(iPD)

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