God of War 3 PC Port Keyboard and Controller Controls

Keyboard-to-controller mapping

The project maps keyboard inputs to controller buttons. The following are the defaults documented at the reviewed revision; a saved custom profile can override them. Use the launcher’s Game → Controls section to inspect or change mappings.

Keyboard	Mapped PlayStation input
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	The PC project’s own menu

These are mappings, not an assertion that a given key always performs one in-game move. Context, prompts and game state can change what the mapped button does.

Xbox and PlayStation button prompts

A controller’s face-button position, printed letter and displayed game icon are three things to distinguish. An Xbox X and a PlayStation Cross do not name the same physical face-button position.

PlayStation prompt	Equivalent Xbox face-button position
Cross	A
Circle	B
Square	X
Triangle	Y

The project offers In-game button icons in Game → Controls. It documents options to match the controller or choose Xbox/Nintendo prompts; the feature is opt-in. After changing the setting or controller, restart when required by the project and check a tutorial prompt before judging a QTE.

Changing prompt artwork is not the same as remapping input. If a key sends the wrong button, inspect its mapping. If the action is correct but the drawing is unfamiliar, inspect the prompt option.

Pause menu and in-game menu shortcuts

The game pause menu and the PC project’s overlay menu are different interfaces:

• Backspace is the documented keyboard pause-menu shortcut.
• Insert, or R3 + L2 on a controller, opens the project’s menu.
• Enter maps to Options, so it should not be assumed to duplicate Backspace.
• On a controller without a touchpad, the documentation assigns View to pause and L1 + View to photo mode.

If a shortcut fails, verify that the game window has focus and that your saved profile has not changed the default. Avoid stacking several remapping layers while diagnosing one button: a launcher mapping and a Steam Input mapping can otherwise be difficult to distinguish.

QTE problems and frame-rate limits

First establish which input the prompt requests and confirm the active mapping. If it is a repeated-button prompt that will not advance despite the correct input, the project’s release notes also describe a high-engine-rate issue.

Use the 60 FPS engine-rate workaround for the affected section. State the engine rate, frame cap and controller type if reporting an unresolved case. Do not treat every failed prompt as evidence of controller hardware failure.

Remapping and vibration

Change one mapping at a time, save it and test a low-risk action before entering a difficult sequence. Retain a note of the previous setting so you can revert it.

Release 2.3.0 adds vibration-strength control. Its notes distinguish Windows validation from options not yet checked in-game on Linux. For Deck-specific launch and input context, continue to the Steam Deck/Linux guide.