Bindings: Zero controls when receiving conflicting input
Added cvar "input-conflict-zerocontrol" (default: 1) that causes controls that are being simultaneously affected by more than one device states from the same input device to be cleared to zero.
This corrects a behavioral compatibility issue where holding down a turn key when already turning to the other direction would cause the control position to first go through the half-speed stage before zeroing.
Another possible solution to address this issue would be to track staging per control rather than per input device state (i.e., now there is a timer for each key of the keyboard and none for the control itself), but implementing that would be too much work during Candidate phase. It should be done at a later time, though.
Added by skyjake almost 13 years ago
Added by
Bindings: Zero controls when receiving conflicting input
Added cvar "input-conflict-zerocontrol" (default: 1) that causes
controls that are being simultaneously affected by more than one
device states from the same input device to be cleared to zero.
This corrects a behavioral compatibility issue where holding down
a turn key when already turning to the other direction would cause
the control position to first go through the half-speed stage
before zeroing.
Another possible solution to address this issue would be to track
staging per control rather than per input device state (i.e., now
there is a timer for each key of the keyboard and none for the
control itself), but implementing that would be too much work
during Candidate phase. It should be done at a later time, though.