I thought I’d start an upvote thread for the elevator trim issue. It’s hard to believe that even today, on 09.15.20, there is no mention of this as an issue - let alone as a fix on the roadmap - in the dev update.
(I have created a zendesk ticket for this issue with lots of documentation, and the zendesk ticket has been closed, so Microsoft knows about it.)
The issues:
- The elevator trim is too sensitive; moving the trim even 2% creates huge pitch changes
- The elevator trim is (randomly?) bound to multiple keystrokes and joystick buttons / axis, and sometimes even the mousewheel or button
- The AP cannot hold an accurate vertical speed or altitude
- This issue doesn’t seem to happen in every install; unsure what “system demographic” it falls into
Possible workarounds:
- Deleting all bindings from all devices, and then re-binding seems to help a bit
- Making a change in the flight_model.cfg seems to help a little
Caveats to the workarounds:
No matter what we do, a 1% or 2% change in elevator trim still induces way too much of a pitch change. 2% movement should barely change the pitch, not violently pitch the aircraft by 10 degrees or more.
So let’s upvote this issue and get Microsoft’s attention!
Here’s an extensive list of threads on this subject, so you know it’s a real thing:
https://forums.flightsimulator.com/t/elevator-trim-cockpit-view/263908
https://forums.flightsimulator.com/t/saitek-yoke-elevator-axis-broken/130490
https://forums.flightsimulator.com/t/elevator-trim-cessna/172287
https://forums.flightsimulator.com/t/elevator-trim-issues/189787
https://forums.flightsimulator.com/t/broken-elevation-trim/227492
https://forums.flightsimulator.com/t/just-breath-on-the-trim-and-bam/253721/21
https://forums.flightsimulator.com/t/elevator-trim-out-of-control/146764/21