At a glance
- On consoles, keyboard/mouse is supported, but it is disabled during console-only raids. Isolated raids are exempt from that restriction.
- When searching solo or leading a squad on console, enabling Keyboard and Mouse in crossplay settings restricts matchmaking to raids containing PC players.
- Aim assist works only with a controller and activates after a brief delay when switching from keyboard/mouse. Tune slowdown and auto-tracking separately.
Use the reworked device menus, not an old preset
Update .192 reorganized controls by input mode and added aiming options. Record your bindings first, then tune one variable at a time. The September PS5 values below are historical examples, not a tested preset for this menu.
Sony controllers have native PC support in .192. Check which input system is active before comparing behavior. In .205, one finger moves the menu cursor and a tap clicks; two fingers scroll lists or pan/zoom the map. Raid touchpad aiming still needs its separate setting.
Update .208 adds a tab for Xbox keyboard and mouse settings. In .196, flashlight and laser can be rebound separately, although both default to L on keyboard; a previously separate laser binding resets to L. Recheck it after updating.
Sources: Update 0.4.0.192 · Update 0.4.0.196 · Update 0.4.0.205 · Update 0.4.0.208
Check device, raid type and crossplay before queueing
- Isolated (PvE)
- Keyboard/mouse restriction does not applyDo not confuse Isolated with Open + Solo.
- Console-only raid
- Keyboard/mouse disabled for that raidController input continues to work; personal control settings are retained. The game warns before entry.
- Console solo player / squad leader
- Crossplay → Keyboard and MouseWhen enabled, matchmaking is restricted to raids containing PC players.
- Switching to controller
- Aim assist after a brief delayAim assist does not work while playing with keyboard/mouse.
Sources: Update 0.4.0.182
Aim assistance and comfort controls added in .182
- Test aim slowdown strength and target auto-tracking independently. Maximum assist distance also depends on sight magnification.
- If accidental melee interrupts aiming, try the controller option that disables melee attacks while aiming.
- If breathing movement is uncomfortable, try the new setting that reduces camera sway from breathing. It is separate from Reduce camera bobbing.
- When a device warning seems inconsistent, record the selected raid, active input and squad leader’s crossplay option. These rules do not establish a universal fix for every peripheral or matchmaking bug.
Sources: Update 0.4.0.182
Older PS5 example: use as a comparison
These personal values come from SiNisterFPS’s September 16 PS5 Pro narration (9:44–15:08), before the .182 aim-assist rework. They are not a tested preset for the revised controls. Options → Controls → Main is the menu path shown in that older walkthrough.
- Controller aim speed
- 0.85Creator preference. Reduce it if you repeatedly overshoot the target.
- Nonlinearity
- 0.5The creator found this more comfortable than 0. Compare small corrections and larger turns yourself.
- Left / right stick deadzone
- 2% / 2%His sticks have some drift. Your controller may need different values.
- Aim assist
- OnCreator preference; leave other settings steady while testing aim.
- Aim acceleration / vibration
- Off / offOptional preferences, not requirements for accurate aim.
Tune one variable at a time
We recommend testing in this order to separate stick drift from sensitivity issues. Adjust the settings that affect your aim; different problems may need different changes.
- Record your original values so you can restore them.
- Stand still and release both sticks. Increase only the affected stick’s deadzone until unwanted movement stops.
- Aim at a stationary reference. Adjust aim speed until you can turn to it without repeatedly passing it.
- Compare nonlinearity at the same aim speed. Test both tiny corrections and a full turn; keep the response you can control.
- Test aiming-down-sights sensitivity separately, then try one low-risk raid before changing more values.
Check leaning and hold-to-aim inputs
- For the default PS5 lean input described in the video, enter aiming with L2 before pressing L1 or R1. Avoid pressing the combination simultaneously if it opens the wheel.
- For hold-to-aim, the creator clears the “Aiming” binding under Weapon while retaining “Aiming 2”. Record the original mapping and preserve a working aim binding before testing this change.
- Update 0.4.0.115 fixes an issue with opening the map using B / Circle, according to the official notes. If that specific action fails, check your installed build before rebinding unrelated controls.
Sources: SiNisterFPS controller setup: 9:44–15:08 · Update 0.4.0.115
Sources & references
- SiNisterFPS controller setup: 9:44–15:08Video
Menu path, personal settings and button sequence from the September 16 PS5 Pro video transcript. We have not independently checked the footage or tested the settings in-game.
- Update 0.4.0.115Official
Fix for the gamepad B / Circle action on the map.
- Update 0.4.0.182Official
Update 0.4.0.182 adds console keyboard/mouse support and separate aim-slowdown and auto-tracking sliders. Isolated raids allow keyboard/mouse; console-only raids disable it. Check the selected mode and the squad leader’s crossplay settings before troubleshooting sensitivity.
- Update 0.4.0.192Official
Update 0.4.0.192
- Update 0.4.0.196Official
Update 0.4.0.196
- Update 0.4.0.205Official
Update 0.4.0.205
- Update 0.4.0.208Official
Update 0.4.0.208