joepoway

How not to mess up a perfectly good P3Dv4 install?

Recommended Posts

The following is a recent article in Simgazine by Robert Randazzo     

How not to mess up a perfectly good Prepare3D installation 

http://www.simgazine.com/how-not-to-mess-up-a-perfectly-good-prepare3d-installation-by-robert-randazzo/

Myself and others find it interesting that  PMDG's 777 v4  still puts tons of files in Simobjects within P3Dv4 as Orbx doesn't install outside of P3Dv4 either.

But my question is this:

I recently added MT6 to my P3Dv4 install using the external my documents Prepar3D v4 Add-ons folder with the appropriate add-on.xml file and everything works well and I didn't have to edit any files within P3Dv4 at all. This process seems to follow the same method that A2A is using when I added the recently released aircraft (C172 and T6) for P3Dv4 and I am quite happy with this approach and am not worried about C: drive memory issues with having P3Dv4 and add-ons on the same drive.

However I am concerned after reading the above article and others that the method I and many others have used for MT6 and the RA Duke Turbine will still cause some sort of internal conflict with P3Dv4 in terms of either things that still get written to P3Dv4 internally when it sees the new add-on and we acknowledge acceptance of the new add-on.xml file or the fact that the installed version of MT6 although outside of P3Dv4 is not really compatible with it. Perhaps either of these factors could cause potential performance issues?

Can anyone shed any light on these concerns or add to my understanding of this potential issue or anything Robert Randazzo touches upon?

 

Thanks in advance

Joe

Share this post


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

It was originally posted here on Avsim and not at Simgazine.   It's a large thread to peruse.

 

Share this post


Link to post

And because it has been discussed over and over - I'm shutting this down.

Vic

Share this post


Link to post
Guest
This topic is now closed to further replies.