I’m curious: aircraft sold on the in-game marketplace are “DRM protected”, ie. encrypted. But some of these aircraft are also available from other vendors, in a version that goes into the Community folder, so their data files are available. If someone created a mod to improve aspects of such an aircraft, would that mod work with the marketplace version of the aircraft as well or does the VFS treat that version in some special way, so its files cannot be overriden by something in the Community folder?
The fact that having the WT G1000 and NXi installed at the same time breaks some functionality of the NXi seems to indicate that modding marketplace content is possible, right?
The Cessna Flight Dynamics Performance Modification by Dakfly is a perfect example of how an encrypted plane can be modded without compromising the data protection. However, it is also a Herculean effort for freeware, and thus is an exception, and not the rule.
Yes. Which is why there are Wishlists items (you can participate and browse those) to unlock the encryption. Realistically, in order to protect the files, the compromise would be to unlock the Configuration files, where the majority of modder changes occurs. Protecting the rest of the files would preserve antipiracy and product valuation.
In order to adjust the flight model, only cfg files are necessary; To adjust instruments, xml files are needed. Some modifications would require 2 or 3 of them…
(…)files cannot be overriden by something in the Community folder
To patch an encrypted plane from the store, you have to modify one file in the plane folder from the store (and then put your mod in community) otherwise, the mod does not override the existing parts. You basicaly tell the sim that one of the 3 previous domains is not encrypted anymore (but you have to provide ALL the files it contains)
Honestly, this is a mess and very frustrating not to be able to see all the aspects of the plane when modding. You can not fix a “simple” bug like the black screen from the kitfox since the last update…
No, encrypted files are treated like any other by the VFS once they are unencrypted.
There are some rules that may make it seem like files are being ignored, but, that has more to do with the way FS looks for files… for example, last I knew, a panel.xml file does not work well without a panel.cfg file in the same directory. But, that’s not an encryption thing. I also had issues getting a cameras.cfg file to work in a livery. I had to create a separate package for it to work. But, that was a long time ago, so it might have been my fault.
The problem is you cannot override single parameters from the cfg files. I tried that without success. I wanted to enable the default autopilot on some planes to use it with mobile companion app. I know some people say an AP in a plane like a Husky is stupid. But I find it very useful on cross country flight to get your eyes away from the VSI, because in a flightsim you don’t feel what the airplane does.
However I’m a flightsim guy since FS98 and I’m used to have access to the CFG files even from payware planes. For me, it’s very frustrating now that I’m not able to fix simple things and make the planes work with other 3rd party addons.
Well, you learned it the hard way : considering your (understandable) appetite for tuning and customizing, don’t buy anymore drm plane
This is what I’ve decided; I’d love the Husky, but no thanks.
when you say you tried to “modify the flight_model.cfg file”, how were you modding it?
It should be possible, but, you’d have to create an entirely new flight_model.cfg file. You can’t just create a portion of one.
You would create a package (like a livery package), and at the top of the file, I don’t remember the exact text, but you’ll need the “base_model=blah_blah_blah” so it knows what plane to use your new file with.
Somebody created a modded Longitude. You could use that as a model of how to redefine an encrypted plane.
Essentially, you’ll have to fully define the flight characteristics. You can’t selectively change options.
