Requesting native support for independently implementing logical dead zones at the extremes of a physical axis range (i.e. no output change in response to input change), see image. I’ve not found anything concrete in regard to additional axis sensitivity options on the roadmap, though it’s an often-discussed topic in the forums.
It would also be great to be able to further manipulate the curve after setting one or both ends, satisfying additional axis sensitivity config functionality requests, though I’d be happy enough with a linear scale between extremity deadzones for my throttle.
I recognize the pitfall of believing that “anything I don’t understand must be easy to implement”, but it does seem like it would be a small (and much-needed) extension to existing configuration options for axis curves. I was dismayed to find out my new physical setup will prevent me from using the sim without an additional external software layer (independent of the OS, MSFS, or device manufacturer software) that may incur its own costs and cause its own problems. I’d sure prefer to avoid that - and a highly/fully configurable axis is typically a basic component of any flight sim. Even non-hobbyists may want to prevent a response to a bumped control.
Some related posts (didn’t do an exhaustive search; there are probably more):
/t/joystick-extreme-dead-zone-should-be-on-input/362585
/t/how-can-i-apply-a-dead-zone-at-the-start-of-an-axis/329877
/t/throttles-with-detents-how-to-calibrate-axes/361612
/t/how-do-you-handle-detents-in-fs/362340
/t/mapping-throttles-with-detents/378917
