Input profiles support ramps, but they only do so globally for an axis. E.g. if you assign the signed square ramp to stick X, it is used no matter if the input comes from a keyboard or from a joystick.
But keyboard feels much better with a linear ramp, and joystick feels much better with a signed square ramp!
We need a way to define this fine-grained. It’s the reason why the keyboard controls in the current RC feel off compared to the last release.
✔️ FIXED BUG: Input: No Per-Key Ramp
Re: 🔴 OPEN BUG: Input: No Per-Key Ramp
Will be in the next version.
Re: ✔️ FIXED BUG: Input: No Per-Key Ramp
Fix has landed.
Binding an HID axis to a game axis now allows to specify the ramp. I do explicitly not allow it for keys and buttons, as ramps make little sense with them and “linear” always feels best so far.
This was critical for the new flight model because the legacy TAW guardrails have been removed from it – and suprisingly, it was them giving the flight model its characteristic feel.
Binding an HID axis to a game axis now allows to specify the ramp. I do explicitly not allow it for keys and buttons, as ramps make little sense with them and “linear” always feels best so far.
This was critical for the new flight model because the legacy TAW guardrails have been removed from it – and suprisingly, it was them giving the flight model its characteristic feel.