Now you cannot lock the flight model settings from server side.
This can be fixed by simple migrating these settings to class Difficulties in .Arma3Profile:
RTDEnabled=1; Helicopter flight model
RTDFullHUD=1; Show Gauges
RTDRoughLanding=0; Rough Landing
RTDWindDynamic=1; Wind Effects
RTDAutoTrim=0; Auto-Trim
RTDStressDamage=1; Stress Damage
Description
Description
Details
Details
- Legacy ID
- 125652079
- Severity
- None
- Resolution
- Open
- Reproducibility
- N/A
- Category
- Feature Request
Event Timeline
Comment Actions
In my opinion, options should allow more flexibility
Like each options can take a number between 0 and 3
0 : Not active (forced, can't be changed by players)
1 : Active (forced, can't be changed by players)
2 : Not active (can be changed by users)
3 : Active (can be changed by users)
Why ?
Because something like "Show Gauges" options should be free to choose by players
Comment Actions
Or even better, allow controlling it by script (though default value should still come from class difficulties as that's where it fits best).
And, of course, on Elite all the tough stuff should be enabled by default.
Comment Actions
I totally agree on this. Squads should be able to 'force' all rotorlib difficulties so being a pilot really becomes a skill that needa to be trained. Instead of the 'everyone can hop in and fly'. Especially the autotrim not being forced to be disabled is a killer for that.
For PvP I can see why this is an issue aswell. Eveeyone will go autotrimm enabled and fly arround like crazy.
I dont see why the forced disabling option was never there...?
Comment Actions
Sure, but before aeronautical considerations, i didn't find any mean to force simple difficulty as "map" (to decide if player can see units on map (extended map info) or not, and when (conditions).
Difficulties are too much hard coded.