ASOBO : open the FLIGHT_MODEL.CFG, I´ve a right to modify my purchased content

… and protect the files in a different way, if really necessary !

I must modify some parameters for the pitch behavior for some planes to get halfway some real feeling.

Sometimes this pitch behavior in this sim and some planes makes me really angry, immersion killer number one.

I´ve to adjust my pitch curve for my Thrustmaster Cougar with hal-sensors-mod to around -70% !?

I thought this should be a serious simulator and not a game !

2 Likes

your purchase content is not yours though

it only grants you the right to use the software and its content. You dont own any game, even physical copies

have fun reading the EULA

that said, I agree it would be nice if we could modify planes as we see fit, to fix them

14 Likes

It would be nice to: agreed.

I have a right to: no you don’t.

3 Likes

Opening this is a double-edged sword. Because what’s stopping them from being shared with other people if it’s not encrypted to be DRM managed by your account.

Just look at the exact same addons coming from other stores. They have their purchase validation check in the beginning sure but once it’s installed, it’s installed to the Community folder, unencrypted. Once that happens, people can just copy it and share it with their friends and now they’re infringing the copyright.

Same thing in here. Once your purchased market content is unencrypted to be editable, there’s no way to stop people from just copy and share it with other people.

The only thing I can think of is to allow the SDK and the DevMode to open access to the purchased content and all its files. That way, we’re still encrypting the content files, but it’s accessible from the MSFS itself you can make modifications to it, then save it, and it would encrypt again just for you. It’s a win-win solution in my opinion.

1 Like

Where to start ?

(1) I 100% agree with DRM, and the encoding of the valuable IP of the developers.
But some of the basic .cfg file, really do not have to be encrypted, to protect the plane from being pirated.

(2) You cannot just move an encrypted plane from Official, and put it in Community, and share it with others. The DRM works here, so it that will not work.
Full disclosure- I have not tried it, but I must assume the DRM system prevents that !!

(3) The planes you purchase through the Ms_Store, being encrypted, can obviously be copied and shared, but will not run on the copied to PC - so there is no point, They are DRM protected.

(4) Many of the plane you buy from 3rd party developers, get installed and locked to your system, and will not work correctly (or at all) if moved to another PC.

The 3rd party developers are NOT stupid !!

The main reason for wanting to NOT have some of the .cfg files encrypted, is NOT to enable Piracy – but to allow corrections to those files to help make their planes fly in a more realistic manner, because, unfortunately, the developers do not always get it right, or if they do, a MSFS update “Can” cause those setting to need modification.

The bottom line is, that NOT including all the .cfg files in the .fsarchive encrypted files, will make NO DIFFERENCE to the DRM protection of those planes.

However,

One valid argument can be made for keeping them form being edited by the user.
If the user edits them and has an issue, and then tries to get the DEV’s Tech support to help sort out the issue they have caused by the edit… it is a major issue for the developer, and a drain on their resource, to try to help fix, something that the user has been able to edit.and mess up.

NOTE:

FBI Anti-Piracy Warning: The unauthorized reproduction or distribution of a copyrighted work is illegal. Criminal copyright infringement, including infringement without monetary gain, is investigated by the FBI and is punishable by up to five years in federal prison and a fine of $250,000.

There are multiple reasons why DRM exists.

The best way of communicating this is through Zendesk under the “feedback” dropdown.