Aim and Input Settings

Concrete settings documented by the developer

The January 29, 2026 demo update added Manual Aim in Gameplay Settings, reticle opacity in Interface Settings, and a toggle for switching targets while firing. It also lets you click the starter-weapon button again to change its equipped side.

What to do now

1. Choose Manual Aim in Gameplay Settings when you want direct aiming instead of the targeting behavior used by the other mode.
2. Use the target-switch-while-firing setting when firing prevents the target change you expect; the update changed its default to allowed.
3. Adjust reticle opacity in Interface Settings when the reticle is hard to read.
4. Click the starter-weapon button again to change which side equips it.

Source: the developer's January 29 aiming and adjustments update. These are documented update facts, not a September hands-on retest.

Isolate the input problem

Begin with the current in-game control screen because exact keyboard, mouse and controller assignments can change. Record the game version, input device and binding you are testing. Move to an open area, clear the current target if possible and repeat one input several times before changing a setting. This establishes whether the problem is consistent or tied to a crowded encounter.

Target selection can make a movement or weapon input look unreliable. Test the same action with no target, with a visible target and with terrain between the RIG and the target. If behavior changes only in one state, describe that state when comparing community reports. A preference for weapon-side bindings is not itself a defect; the useful question is whether the current settings screen accepts and retains the chosen input.

Menu navigation should be tested separately from combat. Open the menu, use the displayed back action and confirm whether the previous screen returns. If a binding resets after restart, note when the reset occurs and whether the demo save was present. Those details are more actionable than combining targeting, movement and menu symptoms into one report.

When checking a workaround, preserve the original settings before editing them. Change one binding, close and reopen the relevant menu, then repeat the same action in the same location. If the result changes only after a restart, include that transition. If no current developer post documents a fix, label the result as a reproducible observation rather than a permanent solution. The official Steam discussion area can help find matching symptoms, while the developer devlog is the better place to confirm that a change was intentionally shipped.

A reproducible control report

1. Name the input device, current binding and game version.
2. State whether a target was selected and whether terrain blocked line of sight.
3. List the smallest sequence that reproduces the symptom, including the expected and observed result.
4. Retest after restoring one default binding rather than resetting the entire configuration.
5. Compare the date with the official developer devlog before assuming an older workaround is still needed.
6. Keep a short record of the original setting, the single change and the result after reopening the menu and restarting the game, so another player can repeat the same test.

Source review date: September 14, 2026.