XB1 wireless controller does not always remember the in-game applied Deadzone settings. Quite often after rebooting the computer, the deadzone settings will have been reset to 0%.
This is important because the controller tends to not return to centre particularly well, and this messes up autopilot (for example, the A320 autopilot won’t follow headings, leading to frustration and aircraft rolling out of control). Setting the deadzone to 10% fixes this autopilot behavioural issue.
Is the issue that the settings are being reset? Or that the controller is not taking the settings? I seem to be running into the second- I can set deadzone in the settings, and it remains there when I check, but the deadzone is not actually being applied to the control.
Looks to be a mixture of both. For me, setting to 10% and saved into a new profile is not remembered next time the game is booted.
There’s something else though. If you have an xb1 pad, set left stick x axis to 100% deadzone, load up the a320 and notice that when you move the left stick left and right, the Airbus side stick moves fully in one direction but not at all the opposite. That doesn’t seem right - if I set 100% deadzone, the sensitivity graph suggests we should not see inputs registered along that axis which makes sense.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.