Sensory Overload Controls Reference

Sensory Overload keeps the action set tiny so difficulty can live in perception — but the precision path matters. Developer interviews explain a shift toward mouse movement for fair high-speed control, paired with a point-sized avatar. This page is the practical bindings and habits reference for demo and pre-launch practice.

Read Mechanics Deep Dive for the design why. Apply habits in How to Play.

Design baseline: mouse-forward precision

Pancak3s has described moving off pure WASD-style strafing toward mouse movement so micro-corrections stay trustworthy at dropper speeds. In practice:

• Use the mouse for fine lateral placement
• Avoid holding keyboard strafe as your only plan
• Treat every correction as a short flick, then return to calm

Always verify the live build’s settings screen — patches can add sensitivity sliders and accessibility crosshair tools (Accessibility Settings).

Common action map (verify in-game)

Input family	Typical actions
Mouse	Precision movement / aim-style corrections
Keyboard (when bound)	Optional modifiers, pause, menu, legacy move binds
Jump	Space / face button (build-dependent)
Fast-fall / commit	Bound hold input for vertical squeezes
Pause	ESC / menu

Older community tables listing Arrow keys / WASD as primary move still appear online. Treat them as legacy notes unless your current demo build still exposes those binds. The fairness thesis in modern messaging is mouse-forward.

Controller

• Left stick: movement (flick, do not drag)
• Face button (A on Xbox-style): jump
• Keep deadzones tight enough for micro-corrections without tremor deaths
• Pause freely when vestibular lock hits

Controller is valid — especially on Steam Deck — but expect to practice stick discipline the way mouse players practice flicks.

Steam Deck

Deck is supported and tested per developer notes. Combine:

• Stable FPS caps
• Comfort distance (screen not under your nose)
• Accessibility outlines if glyphs blur
• Shorter sessions than desktop

Precision habits

• Short corrections beat held strafe
• Recenter after every dodge
• Fast-fall is intentional, not permanent
• Do not rebind mid Vertigo learning block
• After deaths, name the input mistake (“held too long”) before retrying

Troubleshooting

• Floaty feel: unstable FPS — see System Requirements
• Overshoot: lower sens slightly; prefer flicks
• Invisible obstacles on old GPU: update demo; check Compatibility renderer notes in Patch Notes
• Nausea from motion streaks: disable speed lines in Accessibility

Practice circuit

1. Sensitivity check for sixty seconds
2. Practice Mode checkpoint on one hard gate
3. Full Vertigo validation
4. Stop on comfort signals (Comfort Checklist)

Device consistency

If you swap PC mouse and Deck stick in the same week, expect a re-learn tax. Finish a learning block on one device before switching.

Controls mastery is quiet. When the binding layer disappears, the tunnel can finally teach pattern instead of panic.

Mouse setup details

• Pick a sensitivity where a small wrist flick equals one lane width at your typical fall speed
• Avoid accelerating wildly between desktop and game profiles mid-learning week
• If you overshoot, lower sens slightly before inventing new keyboard binds
• Clean mousepad tracking matters more than RGB — hitchy sensors create fake “unfair” deaths

Keyboard as secondary

Keep jump and fast-fall on predictable keys even if movement is mouse-forward. Do not experiment with exotic rebinds during your first Vertigo literacy week. After Practice Mode proves a habit, then consider QoL rebinds.

Controller stick discipline

• Flicks over holds
• Return to neutral after every correction
• Tighten deadzones until tremor stops killing you, then stop tightening
• Map pause to a reachable button; vestibular lock is an input problem too

Accessibility overlays on the binding layer

Crosshair shape and thickness change how you aim micro-moves. Rebuild sensitivity after major crosshair changes — a thick plus can feel slower than a thin ring even at identical sens. Guide: Accessibility Settings.

Binding myths

• “Keyboard-only is the only fair way.” Outdated relative to current mouse-forward messaging.
• “Controller cannot micro-correct.” False; stick flicks work when deadzones are sane.
• “Rebinding mid-Ranked will save the run.” Usually it only adds confusion.

Weekly controls audit

Once per week, spend three minutes on a blank sensitivity check, then one Practice gate, then one Normal validation. Log whether deaths were read fails or input fails using the taxonomy from Mechanics Deep Dive. Controls pages go stale when patches add options — re-read Patch Notes after updates.

Your hands should become boring. Boring hands clear tunnels.