Mission file creator/editors settings being "imprinted" onto a mission file, overriding client settings (for those unenforceable in the mission editor)

[Nin]

I am unsure if this has already been reported, however ever since I have been hosting servers with DCS, an issue has arisen where if a user creates a mission file, then uploads it to the server, that users settings are saved within the mission file and will override those settings for any clients who connect even if they have that setting switched off. This behaviour can be overridden by using the "enforce" toggle within the mission editor, but for settings such as TO assist this option is not available. 

For example, if a mission file is created on a system where rudder assist is enabled for the P51 for example, then loaded onto the server, all users who then connect to the server will experience rudder assist on the P51 even if they have it disabled. The inverse is also true in that if a mission file is created with rudder assist disabled, and the user has rudder assist enabled, they will not experience rudder assist even though it is enabled.

I have so far tested this for external views being enabled/disabled in the "misc" settings, as well as takeoff assist for the TF-51, and rudder assist for the TF-51.   All behave as described above.

To re-create:

1. Disable external view, and then make a mission file
2. Load this mission file onto a dedicated server
3. On a PC with external view Enabled, join the server
4. You will not be able to use external view even though it is Enabled on the client
5. Repeat/test above steps for other settings such as rudder/TO assist for prop aircraft

Edited November 19, 2022 by Nin