ISSUE DESCRIPTION
Your game pretends that there is a “negative” range on my controller’s triggers. It puts “zero” in the exact middle of the axis, which is idiocy. My trigger can’t go BACKWARD. It’s not like a thumbstick.
This has serious negative implications on brakes, which never ■■■■ work. No matter what I do, I can ONLY get my brakes to release by pulling the triggers all the way–which of course causes my rudder to steer all the way right or left at random. This makes taking off and landing a practical impossibility unless I just unbind the brake axis. Which is a DEFAULT BINDING, by the way.
FIX IT.
MEDIA
SEE?!
Have you tried to reverse the axis?
Of course I have. That does absolutely nothing. Reversed or otherwise–even with ONE set to reversed and the other NOT set to reversed–they both behave EXACTLY the same, and the behavior is completely broken.
Above is my current setup – one reversed, the other not. Here’s the result of pulling both triggers all the way:
And here the triggers are released!
I can’t see the full screen in your capture. What commands do you have mapped to the triggers, Left/Right Brake or Left/Right Brake Axis?
I haven’t actually done any mapping, here; the game has a default configuration for X-Box controllers going way back, I suppose. I eventually became so frustrated with the behavior that I just turned it off and used the trigger to brake.
I also threw out my controller and bought a throttle and stick for use with the helicopters in game. Presumably, therefore, all of this is working as intended–assuming, that is, that it was intended to force me to buy a bunch of stuff from VKB.
I never had this issue with Xbox controller on Windows, it’s a while since I upgraded to stick/throttle but my memory of this is that the main brake control was one of the buttons (B maybe?).
The response curve looks like it’s intentional - given the triggers are bound to the rudders primarily I’d guess that the intention of these bindings is to add a little brake with the rudder to assist steering on ground (which is why it does nothing until half travel according to the curve).
I’ll take a look when I get home.
That curve is very intentional–it’s not the default; it’s my attempt to fix the problem. 
The bindings in question don’t add braking to rudder, per se–rather, they activate braking (in addition to rudder, maybe? …not sure on that point–it could be that the rudder is excepted from the binding when you hit the additional shortcut key) when you hit the brake button on the controller AND pull the triggers. In any case, the operation of the rudder isn’t really important here.
So anyway, what’s happening on my machine is just like I said–the operation of the axis reverses for whatever reason after you actually use it. I could never get to the bottom of why, so I’m back to flying only aircraft with tricycle undercarriages because taildraggers still just want to nosedive when I hit the (digital-only) brakes.
I’m with you now - I’d misread the bit about ‘default binding’ as the ‘brakes were default bound to the triggers
Right, that’s my bad–it’s been so long since the original post that I don’t really remember what context it had or didn’t have. Anyway, by default, yes, the triggers are bound to the brakes as described–you hold down X and pull the triggers to apply analog braking. However, the mapping I applied was an unsuccessful attempt to fix the problem that I had with that default binding. I never have figured out why there’s a problem with it, but basically what happens is that you end up needing to hold the triggers to turn the brakes OFF, which is the opposite of what anyone would want. Inverting the axis makes no difference, which is why I made a bug report instead of just asking what I was doing wrong–because it seems to me like either inverting or not inverting is BOUND to work, but neither one does.
