Set up and rescue your bindings
Back up a working layout and isolate detection, binding and axis problems.
Back up a working layout and isolate detection, binding and axis problems.
Keep a return point before changing assignments.
Use Options > Keybindings > your device > Advanced Controls Customization > Control Profiles > Save Control Settings.
A named control-profile XML is saved in the selected game's mappings folder.
Keep a separate copy of the export. A control profile is not a backup of every game preference.
The same published instructions in one readable view. Use the steps above for controls and practice panels.
Keep a return point before changing assignments.
Use Options > Keybindings > your device > Advanced Controls Customization > Control Profiles > Save Control Settings.
Expected result: A named control-profile XML is saved in the selected game's mappings folder.
If it did not work: Keep a separate copy of the export. A control profile is not a backup of every game preference.
A game binding cannot repair missing hardware input.
In the device's own supported tester, move one axis and identify which controller and axis respond.
Expected result: Only the intended input moves, with a stable rest position and usable range.
If it did not work: Resolve connection or calibration problems in the device instructions first. Some connected accessories appear as axes of their host controller.
Use the device selector before capturing an assignment. These menu steps follow CIG support updated 17 February 2026, rechecked 21 October; no current-build hands-on test is claimed.
Open Options > Keybindings. Select Joystick / HOTAS at the lower right, then Advanced Controls Customization at the lower left. Use the lower-right peripheral ticker to select the device you intend to edit.
Expected result: The selected device page matches the input you are about to assign.
If it did not work: For two sticks or a separate throttle, check the device identity from the earlier identification step before editing another page.
Scroll to the intended action and left-click it to inspect any existing assignment. Double-click to capture, then operate only the intended input.
Expected result: The action shows the captured key or button assignment.
If it did not work: If another input was captured, right-click the selected action to unbind it and repeat with the intended input.
Review the listed actions using the same input. Select through the conflicts and accept or change the assignment deliberately.
Expected result: You know which actions share the input and which assignment you retained.
If it did not work: If switching between mouse and joystick produces odd responses, compare their similar action and action-mode assignments. Do not use Reset to defaults as a first repair.
Direction, range and device order are different problems.
Observe the action at rest, through a small movement and at the far end; change only its inversion if direction alone is wrong.
Expected result: The axis operates in the intended direction with a predictable neutral state.
If it did not work: If input jumps or never reaches neutral, inspect calibration and the chosen axis type. A non-centering throttle stays where you leave it.
A deadzone and a response curve solve different problems.
After calibration, adjust only the affected deadzone or curve and compare the same small movement again.
Expected result: You can explain what the change improved.
If it did not work: Avoid universal sensitivity recipes. A large deadzone removes small inputs; changing several settings hides which one helped.
A correct axis can belong to the wrong side of a two-device layout.
If device roles swapped, compare the detected device identities with your saved assignments before changing bindings.
Expected result: You know whether the issue is order or an individual action.
If it did not work: RSI documents device inspection and an explicit index swap in its profile guide. Do not swap guessed indices repeatedly.
A profile can contain different devices or older actions.
When importing a compatible XML through Control Profiles, review each input group in the assignment dialog.
Expected result: Only the intended groups are replaced.
If it did not work: Choose None for a group you want to preserve. Inspect movement and mode actions before relying on an older profile.
Device-page and assignment steps checked against CIG support 21 Oct 2026; documented February menus, not a gameplay test.. Reference information, not a claim of current-patch playtesting.
RSI control-profile management, updated 17 February 2026; checked 14 October 2026RSI peripheral keybindings, updated 17 February 2026; checked 14 October 2026