SpartanPort is an unofficial Windows and experimental Linux port of God of War III Remastered for PC, using a custom runtime and Vulkan graphics. It provides a launcher, in-game settings, and performance options, and requires a game dump from your own PS4.
Project status
- Actively maintained: the latest upstream push was on 2026-11-05, following frequent updates through late October and early November.
- Updates have been arriving in a rapid burst, often several test builds within a day. Many are explicitly experimental and ask users to verify that the build runs.
AI summary generated
Recent updates
linux-v3.1.0-shaders-test1
This experimental Linux build adds first-launch shader and pipeline preparation, which is intended to reduce shader stutter during later play. It also asks testers to play normally, export the recorded-shader ZIP from the launcher, and send it to the SpartanPort team; it is explicitly not a final release.
Featureswindows-v3.1.0-shaders-test1
This non-final Windows test build prepares shaders and pipelines on first launch, which takes about 1 to 2 minutes. The goal is to reduce shader-related stutters during gameplay, and testers can export recorded shaders through the launcher to help the SpartanPort team.
Featureswindows-v3.1.0
SpartanPort 3.1.0 adds experimental free camera, DualSense features, anti-aliasing options, a game-specific TAA implementation, and native-resolution HUD and text support for FSR 3.1. The release also includes controller and launcher improvements, ultrawide and upscaler fixes, stability and audio fixes, and translations; the notes state that settings and saves carry over from 3.0.0.
Featureswindows-v3.1.0-test1
Windows v3.1.0-test1 is a non-final test build adding experimental free-camera control, DualSense features, rendering options, and launcher and input improvements. The code and accompanying documentation also reveal compatibility removals and launcher behavior changes that the release notes do not explain in detail.
BreakingFeatureswindows-v3.0.0-launcher-test1
The release notes announce a non-final Windows test build, with instructions to extract the ZIP, run SpartanPort.exe, and report whether it works. The supplied code diff shows substantial undocumented launcher, graphics-patch, and GPU-emulator changes beyond packaging, including startup recovery behavior and compatibility fixes.
windows-v3.0.0-issue1165-test2
This is a Windows test build based on commit 1177c7e, with release notes asking users to test whether SpartanPort.exe opens and runs. The code changes focus on fixing concurrent SDL audio initialization and broadening the Windows DirectSound fallback conditions; neither change is described in the release notes.
windows-v3.0.0-prs1121-1124-test1
This is a non-final Windows test build; the release notes only ask users to extract the archive, run SpartanPort.exe, and report whether it works. The visible code diff contains substantial undocumented GPU, cache, audio, memory, and Windows behavior changes, but the supplied diff is truncated and shows only 24 of the 49 changed files.
Breakingwindows-v3.0.0-issue1165-test1
This is a test build for PCs where SDL reports no audio driver and Windows has no default audio device: it adds a DirectSound fallback for that case. The supplied diff compares a 2.8.0 build with 3.0.0 and includes substantial changes beyond the audio fix, so it does not isolate which changes belong specifically to this test build versus the underlying 3.0.0 release.
windows-v3.0.0
SpartanPort 3.0.0 replaces the Python launcher with a Rust launcher and adds major graphics, high-FPS, trophy, controls, and stability changes. The release notes describe the Windows and Linux update paths and call out the removal of DLSS. The supplied diff excerpt is truncated, so some implementation details and changes across all 79 files cannot be independently verified here.
BreakingFeatureswindows-v2.8.0-issue1131-test2
This test build combines the documented memory and GPU/cache fixes with opt-in file tracing and a load-stall watchdog intended to diagnose infinite loading screens. The code adds thread-state sampling, including Windows instruction and stack address capture, and also adds a game-installation manifest utility that is not mentioned in the release notes.
Featureswindows-v2.8.0-collision-test1
This test build targets missing scenery and floors with a memory-generation fix intended to prevent late GPU writebacks from overwriting a newer mapping. It also adds opt-in guest-memory tracing for diagnosis. The release notes include cache fixes and other changes from the current main branch, but the supplied diff primarily changes memory handling, tracing, and tests.
Featureswindows-v2.8.0-issue1131-test1
This is a test build intended to diagnose and address infinite loading screens. It includes memory and GPU/cache fixes, optional file tracing and a load watchdog, plus other changes from main; it is explicitly not a final release.
Featureswindows-v2.8.0-launcher-identity-test1
The release notes announce an experimental Windows test build and ask users to report whether it runs; they document no feature, fix, migration, or breaking-change details. The code diff includes substantial unannounced changes to legacy data migration, environment-variable handling, release identification, and update discovery.
Featureswindows-v2.8.0-intel-test4
This is an experimental Windows test build, and the release notes only ask users to try launching it and report whether it runs. The code adds Vulkan GPU checkpoint diagnostics, an opt-in empty fragment shader mode, and batching for oversized texture tiling dispatches, none of which are described in the notes.
BreakingFeatureswindows-v2.8.0-intel-test2
This release has no publisher-provided release notes. No features, fixes, compatibility changes, or upgrade actions can be identified from the available information.
windows-v2.8.0-issue1075-test1
This is a 2.8.0 test build that introduces the native Rust launcher and fixes startup failure with exit code 21 when another process occupies part of the PS4 address range. The diff also contains substantial launcher, controller, build and repository-automation changes that are not described in these focused release notes.
Featureswindows-v2.7.0-issue209-test2
This is a diagnostics build based on 2.7.0, intended to compare shader-cache behavior and collect more complete CPU timing logs. It adds CPU timing output when exiting through the in-game menu and reduces how often shader-cache reporting reads the clock.
windows-v2.7.0
SpartanPort 2.7.0 adds substantial shader-cache and low-thread CPU performance improvements, alongside game-menu, save, trophy, graphics, audio, and launcher updates. It also fixes several crashes and Linux launcher issues. The supplied code diff is truncated, so this analysis covers the changes visible in the excerpt.
Featureswindows-v2.6.0-startup-test1
This is an experimental 2.6.0 test build with candidate fixes and added diagnostics for startup crashes, black screens, and first-level loading failures. Gameplay and affected-hardware validation are still pending, so the release does not confirm that every reported issue is fixed.
Featureswindows-v2.6.0-issue188-test1
This Windows-only 2.6.0 test build proposes serializing file operations that share a guest descriptor and adds automatic read-history and crash diagnostics. The reported I/O regression passes the described native test, but the release notes say the original first-level loading crash remains unconfirmed on affected hardware; the supplied diff also shows several substantial changes unrelated to that issue.
Features