Official defaults versus your layout
| Action | Official note | Boundary |
|---|---|---|
| Weapon/spell toggle | Keyboard R; gamepad B | Verify remaps and Steam Input |
| PC quick hotkeys | 1–8 | Assignment contents are player-specific |
| Autorun | Keyboard Q | No default gamepad bind; can be set |
| Sheathing | Tap the relevant control | Full device gesture map not published |
| Wheel weapons | Favorites | Not simply the equipped list |
Record a remap without calling it a default
Keep three columns in your notes: the action, the official patch-note default and the binding you actually use. If Steam Input translates a controller button to a keyboard key, record both layers. This helps distinguish an assignment conflict from a game behavior change.
Change one action at a time and test it outside a critical encounter. If two actions share the same key, record which one responds and the input context rather than assuming the game supports a particular priority order.
Controller and Deck are separate checks
The store’s Partial Controller Support label and Valve’s earlier Steam Deck test do not independently verify the new Update 17 mappings. A community statement that B or another input behaves differently needs device, profile and build details before it can contradict the official note.
No site-tested universal controller layout is claimed here. Check the controller guide for the existing compatibility boundary, and include your remaps when reporting a mismatch.
Next steps and evidence
This guide summarizes the official announcement, not a completed in-game test. Use the source cards to inspect the developer’s wording and keep your own tested build attached to any conflicting observation.