Find your guide
Download

Independent port guide.

INDEPENDENT PORT GUIDE

How to Install God of War 3 on Linux and Steam Deck

Updated · SpartanPort 2.7.0

Use spartanport-x86_64.AppImage to run SpartanPort natively on Linux or Steam Deck. This experimental AppImage includes the launcher; follow the native launch and Steam runtime choices below.

What should I check before launching on Linux?

Use x86-64 Linux, glibc 2.39 or newer, an AVX-capable CPU and a Vulkan 1.3 driver. Requirements gives system checks; Game version gives the existing game folder layout and supported combinations.

For an installation using the 2.6.0 AppImage, use the manual replacement branch to reach the current package once.

How do I make the AppImage executable and open it?

  1. Download spartanport-x86_64.AppImage from the current release.

  2. Complete the Linux SHA-256 check.

  3. Open a terminal in the folder containing the AppImage.

  4. Make it executable:

    chmod +x spartanport-x86_64.AppImage
    
  5. Start it:

    ./spartanport-x86_64.AppImage
    

The launcher opens. Keep the AppImage in a writable folder if you want its updater to replace it later. If the terminal displays an error instead, use the launch-failure checks.

How do I select the game and start it?

  1. Click Choose the game folder to open Game.
  2. Use Browse… beside Game folder to select the directory containing eboot.bin and the remaining game content.
  3. For a separately stored update, use Update folder (optional) with the same-ID folder rules. Leave it empty for a game directory already containing that update.
  4. Return to Home and check the cover, title ID and version against your game.
  5. Choose Native resolution for an initial desktop launch. Steam Deck's first start selects 1280 × 800; a previously saved resolution wins.
  6. Click Save, then PLAY.

The first start prepares the game image. New shaders can cause stutters as scenes appear. Settings explains disk reuse and background compilation; a persistent black screen needs Troubleshooting.

How do I add the AppImage to Steam?

  1. Close Steam completely; it rewrites its shortcuts when it exits.
  2. In the port launcher, open Advanced and click Add to Steam.
  3. Reopen Steam. The new SpartanPort non-Steam entry includes artwork from the selected game.

Keep the AppImage at that path. If a saved Steam launch option uses the former AppImage name, replace that name with spartanport-x86_64.AppImage at its current location. Update explains the rename.

Should I use Proton in Steam Deck Gaming Mode?

Use the AppImage's native Linux route. If Steam attempts to launch it through Proton, open the shortcut's Properties → Compatibility and select Steam Linux Runtime. If that runtime fails to launch it, choose Default in the same menu to use the host libraries.

On a first Deck start, check the 1280 × 800 rendering size. Use Settings to change a previous saved choice and Controls to set prompts or inputs.

For a Bluetooth external controller that stays inactive after restarting, include its model and connection type with the log in a report.

Where are my data, and how do I update?

The default AppImage data directory is ~/.local/share/spartanport. It holds settings.json, spartanport.ini and mods; the user subdirectory holds saves, caches, backups and last_run.log. Read the launcher's Saves folder field and hint for a custom path, including an XDG_DATA_HOME or SPARTAN_DATA_DIR override.

Keep this data when replacing the AppImage. The current launcher offers Advanced → Check for updates and needs a writable AppImage directory. A 2.6.0 AppImage needs the one-time manual replacement first. Use Update for the complete steps and Saves for backup paths.

What if I get a GLIBC error or the game stays blank?

For GLIBC_2.44 not found from an older package, replace it with the current AppImage. Confirm that the system has glibc 2.39 or newer. For a Steam runtime failure, retry Default as described above.

If the launcher opens but the game closes, hangs or renders incorrectly, keep Advanced → Log, the distribution, GPU driver, title ID and game version. Use the loading and GPU entries to find the matching next step.