Use the full mapping table for shoulder buttons, stick clicks and the separate I/K/J/L D-pad.
Default keyboard-to-PlayStation mapping
The table maps keys to game-controller inputs. It does not assert that a key always performs one named combat move in every game state. Follow the action shown by the actual contextual prompt. Arrow keys control the camera stick; the D-pad is the separate I/K/J/L group.
Complete default key rows in the checked README
On a narrow screen, scroll the table horizontally to read every column.
| Keyboard key | Mapped input / purpose |
|---|---|
| W / A / S / D | Left stick |
| Arrow keys | Right stick (camera) |
| Space | Cross |
| Left Shift | Circle |
| E | Square |
| Q | Triangle |
| 1 / 3 | L1 / R1 |
| R / F | L2 / R2 |
| Z / C | L3 / R3 |
| I / K / J / L | D-pad |
| Enter | Options |
| Tab | Left touchpad click (photo mode) |
| Backspace | Right touchpad click (pause menu) |
| Insert | Open/close the port menu (controller: R3 + L2) |
Source: Project README · Keyboard and controller controls
Change a mapping and confirm the saved profile
The launcher preferences and game settings are separate files, described in the save/settings location table. Editing a guessed INI key is unnecessary when the launcher already exposes the mapping.
Inspect the active profile
Open launcher Game → Controls and compare its current mapping with the defaults above. A saved custom binding can be the reason an old key behaves differently.
Change and save the intended binding
Use the binding controls, change the intended input and click Save for pending launcher changes. Keep a note of the previous mapping so you can restore it.
Check in the relevant game state
Launch with the saved settings and test the affected menu or prompt. Compare one remapping layer at a time; restore the previous binding if it does not produce the expected input.
Sources: Project README · Keyboard and controller controls · Project README · Download and play · Project README · Settings
What this table does not say about the mouse
The checked primary controls documentation describes keyboard and controller mappings, not a native mouse-look control scheme. Do not convert that absence into either a promise of mouse-camera support or a blanket claim that no mouse behavior exists. The 2.3.0 launcher’s mouse-wheel and pointer fixes concern the launcher UI, not gameplay camera input.
For a controller-specific prompt, glyph or vibration issue, use the controller guide. A high-engine-rate QTE blocker can remain even when the expected key is correctly mapped.
Sources: Project README · Keyboard and controller controls · 2.3.0 release · 15 October 2026 UTC
Sources and method
Prepared by GOW III · PC Field Guide from the linked maintainer documentation, release records and attributed original reports, with AI assistance in research, writing and implementation. We have not played or independently benchmarked the game. Source checks describe the records read, not our own gameplay results.
- Project README · Keyboard and controller controlsDefault mappings; saved custom mappings can differ.
- 2.3.0 release · 15 October 2026 UTCHistorical texture/RADV/hybrid-GPU fixes, screenshot and vibration validation, and known issues.
- Project README · Download and playMaintainer instructions at the 2.4.1 release commit.
- Project README · SettingsSettings, memory allocation and multisampling behavior.