God of War 3 PC Port on Steam Deck and Linux

Current Steam Deck support and limits

The project publishes an experimental Linux AppImage. Release 2.3.0 includes a fix for the RADV sparse-queue problem associated with block corruption on Steam Deck. Pull request #252 identifies a native Linux test on a Steam Deck OLED where the artifacts disappeared.

That is more specific than “Steam Deck support works.” It demonstrates a rendering correction on the identified test, not a sustained-FPS guarantee, a full-game test on every Deck revision or validation of every new setting.

Issue #8 is an earlier request. Use its date and follow-up context; an old answer should not override the newer release package.

Select and run the Linux AppImage

Use Desktop Mode on Deck for file selection and the initial launch. From the project’s release assets, obtain gow3-x86_64.AppImage, not the Windows ZIP. Place it in a normal folder and open a terminal there:

chmod +x gow3-x86_64.AppImage
./gow3-x86_64.AppImage

The documented runtime conditions include x86-64 Linux, an AVX-capable CPU, a Vulkan 1.3 driver and glibc 2.39 or newer. Check the package notes against your actual SteamOS or Linux version. A desktop Linux test is not automatically a Steam Deck test.

If an old package reports a newer glibc dependency such as GLIBC_2.44 not found, compare its release date with the rebuilt package rather than replacing system libraries by hand.

Choose your compatible game folder in the launcher, select a separate update folder only if applicable, save settings and press PLAY. Your own PS4 Remastered files are still required; the AppImage does not contain the game.

Add the launcher to Steam

The project documents Advanced → Add to Steam. Close Steam first because it rewrites shortcut data when it exits, then use the launcher action and reopen Steam to inspect the entry.

The Linux AppImage is the native Linux route; adding it to Steam does not by itself make it a Windows program or establish a need for Proton. If you choose a different execution route, state that clearly when reporting results.

After making a shortcut, test that its working setup still points to the same game and configuration. A launcher opening from a shortcut is only the first milestone; verify that PLAY reaches a scene and that input behaves as expected.

Controls, saves and rendering issues

Item	Documented location or next check
Runtime data	~/.local/share/gow3
Launcher settings	~/.config/gow3-launcher
Button mappings and prompt styles	Keyboard/controller guide
Updating the Linux program	Obtain a newer AppImage; preserve runtime data first
Block corruption on an older AppImage	Check that the package includes the 2.3.0 RADV fix

Before an update, keep a separate copy of your data. Do not confuse application files with your game or save data. For other yellow/white surfaces or resolution-specific failures, use texture troubleshooting; the RADV fix does not establish that every graphics symptom is gone.

What a useful Deck performance report includes

This website has not tested gameplay on a Steam Deck. There is no claimed battery life, power draw or stable frame-rate target here.

For a useful report, identify LCD/OLED model, SteamOS version, project package, game build, render resolution, engine rate, power settings, cache state and the game section. Distinguish a short scene from a longer session. Include whether the run starts through Desktop Mode or a Steam shortcut.

The 2.3.0 notes explicitly leave some new options unverified in-game on Linux. Keep those limits attached to the feature instead of copying a Windows result into a Deck recommendation.