P3D v4 Security issue P3D Addon XML

To me the addon xml method is inviting some to repack your product and give it out to others or put your product online for others to download. Do you think most developers will not use this?
 
Last edited:
There is nothing stopping them from doing that now.... the addon XML process is the way Prepar3D is going to require installations. They (L-M) are wanting out of the business of fixing Prepar3D installations that were mangled by someone's addon. Customers are also now demanding the use of the addon XML process as it makes re-installation of Prepar3D and addons much, much easier.
 
There is nothing stopping them from doing that now.... the addon XML process is the way Prepar3D is going to require installations. They (L-M) are wanting out of the business of fixing Prepar3D installations that were mangled by someone's addon. Customers are also now demanding the use of the addon XML process as it makes re-installation of Prepar3D and addons much, much easier.
You can stop them from doing that now. I have because we have required files that are in several different locations. Also our installer has to check to make sure files exist to make sure they can only install to the actual sim folder with folders and files. This help a whole lot from repackers sending to torrents sites. That is not good if P3D forces an XML method as even PMDG has has not merged to that system. This would also render thousands of addons to not work until developers update their products. Good luck on that P3D!:rotfl:

I do admit it may be a good idea to force scenery to be addon XML only.
 
Last edited:
L-M has stated that they may lock the sim folders down in future versions. I strongly recommend you find a way to work with the new process.
 
I may of heard this is a method to have a file or a model file look for registry info or some other file that will help prevent the model from being in the wrong location work on another computer. Is this true? Where can i get help with something like this?
 
Top