Page MenuHomeFeedback Tracker

Disabled/disconnected controllers are included in axis averaging
New, WishlistPublic

Description

Controllers that are disabled (and/or not present) but still bound are still included in the averaging of axis controls.

Details

Legacy ID
2737998075
Severity
None
Resolution
Open
Reproducibility
Always
Category
Controls
Steps To Reproduce
  1. Have two or more controllers.
  2. Bind the controllers to the same axis actions. I used helicopter cyclic for my testing.
  3. Get in a helicopter and test the axes. Notice that the sensitivity is lower than with one joystick, showing the axes are being averaged, as intended.
  4. Disable all but one joystick and repeat the test. No change to sensitivity.
  5. Unbind all but one joystick and repeat the test. Full sensitivity is restored.

Repeat the whole process, but instead of disabling the other joysticks, disconnect them without unbinding their axes. Notice the low sensitivity until the non-present controllers are totally unbound from the axes.

Additional Information

I've confirmed the issue is present across fixed-wing and helicopters, AFM and SFM, so it's not related to any one flight model.

Event Timeline

Raynor_D edited Additional Information. (Show Details)
Raynor_D set Category to Controls.
Raynor_D set Reproducibility to Always.
Raynor_D set Severity to None.
Raynor_D set Resolution to Open.
Raynor_D set Legacy ID to 2737998075.May 8 2016, 12:41 PM

Currently within version 1.50, when multiple controllers are connected (ie joystick rudder and separate rudder pedals), the game averages both rudder devices instead of treating each device axis separate. I made mention of this bug elsewhere within another joystick bug.

I could have sworn I opened a bug for multiple controllers conflicting, but maybe not.