SpartanPort

English | Português (Brasil) | Español

SpartanPort is an unofficial PC port of God of War III Remastered (PlayStation 4) for Windows 10/11 and Linux (experimental AppImage).

No game files are included. You need a dump from your own PS4 (tested: CUSA01623 and CUSA01715, versions 01.00 and 01.02). This project is not affiliated with or endorsed by Sony Interactive Entertainment or Santa Monica Studio. God of War is a trademark of Sony Interactive Entertainment.

Formerly gow3_pc. Updating from 2.5.0 through the launcher keeps your saves and settings: on the first start, the game settings (gow3.ini), the launcher settings and, on Linux, the data folder (~/.local/share/gow3) are copied to their new names. The old files stay where they were, and existing shortcuts keep working. On Linux, the AppImage is now spartanport-x86_64.AppImage: update Steam launch options that use the old file name.

Contents

• SpartanPort
  • Contents
  • Download and play
  • Linux (AppImage, experimental)
  • What works
  • Feature availability
  • Settings
  • Keyboard controls
  • Importing shadPS4 saves
  • Third-party overlays (Windows)
  • Troubleshooting
  • Performance and compatibility
  • Building from source
    • Windows
    • Linux (Ubuntu 24.04)
    • Linux (Arch Linux)
  • Tests
    • Python
    • Windows C++ tests (MSYS2 CLANG64)
    • Linux C/C++ tests
    • Checks using a prepared game
  • How it works
  • Credits
  • License

Download and play

• Windows 10 (1903 or newer) or Windows 11, 64-bit.
• A 64-bit processor with AVX: Intel Sandy Bridge (2011) or newer, AMD FX or newer. On CPUs without MOVBE, BMI1 or LZCNT (Sandy/Ivy Bridge, AMD FX) the loader rewrites the game's instructions that use them to emulated stubs and logs an ISA: line; performance on those CPUs has not been measured yet. Older CPUs stop at start with a STOP: this CPU lacks line in the log.
• A graphics card with Vulkan 1.3 and a current driver.
• Your copy of the game (the folder with eboot.bin, sce_module and sce_sys). Tested: CUSA01623 and CUSA01715, versions 01.00 and 01.02.

Steps

1. Download spartanport-windows.zip from the Releases page.
2. Extract it to a folder of your choice, for example C:\Games\spartanport-windows. Do not run it from inside the zip.
3. Open SpartanPort.exe. If Windows shows "Windows protected your PC", click More info, then Run anyway: the program is not digitally signed.
4. Click Choose the game folder. It takes you to the Game page. Next to Game folder, click Browse… and select the folder with eboot.bin.
5. Back on Home, the cover art and "CUSA01623 · version 01.02" appear. Adjust Quick settings if you like: display mode, frame rate limit, render resolution and engine frame rate.
6. Click Save to keep pending changes, then PLAY. The first start prepares the game image; shader compilation can also affect startup and performance on later launches.

Patches and fixes are included and applied automatically: texture fix, skip videos with X and 120 FPS are on by default. Change the resolution and frame rate on Home or Performance. The startup black-screen fix is always requested, even with an older saved patch selection; patches apply only where their signatures match. A resolution patch replaces the texture fix.

While playing

• Insert on the keyboard, or R3 + L2 on the controller, opens the port's menu: cheats, multipliers, image, performance and the performance overlay.
• Saved shaders load in the background. A small "Loading shader cache" note in the corner shows the progress.

Next time

• Play SpartanPort.exe starts the game straight away with your saved settings. You can make a desktop shortcut to it, or add it to Steam with Add a Non-Steam Game.
• Your saves, shader cache and log are in the user folder next to SpartanPort.exe. Keep that folder when you update.
• Advanced → Check for updates downloads and installs a new version. Your saves and settings are kept.

Linux (AppImage, experimental)

The Linux build runs the same native runtime and the same launcher. It was tested on Arch Linux with a Radeon RX 7800 XT (RADV) in a Wayland session.

You need: x86-64 Linux with glibc 2.39 or newer, an AVX-capable CPU, a Vulkan 1.3 driver and your own game dump. Launcher startup is checked on Ubuntu 24.04, Debian 13, Fedora 42, Arch and openSUSE Tumbleweed; this does not establish gameplay compatibility on every GPU.

Download and run

1. Download spartanport-x86_64.AppImage from the Releases page.
2. In its folder, run:

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

3. Choose your game folder, save the settings and press PLAY.

If an older download reports GLIBC_2.44 not found, download the rebuilt AppImage again. The AppImage updates itself: Advanced → Check for updates (or the notice when the launcher opens) downloads the newer AppImage from the release, checks its SHA-256 and replaces the file. It needs a writable folder; otherwise it opens the releases page. Steam Deck/RADV rendering corruption is a known issue in the published 2.2.0 AppImage.

• Files: saves, settings, shader cache and the log are in ~/.local/share/spartanport; the launcher's own settings in ~/.config/spartanport-launcher.
• Update folder: if the update was dumped apart from the game, choose it under Game → Update folder. It is laid over the game folder without changing either.
• Advanced → Linux: window system (automatic, Wayland or X11), GameMode and MangoHud. Only the tools installed on the system can be turned on.
• Steam: Advanced → Add to Steam adds "SpartanPort" as a non-Steam game, with the icon, the vertical and horizontal capsules, the library background and the logo made from the dump's pictures. Close Steam first (it rewrites its shortcuts when it exits). The button is also in the Windows launcher (not tested there yet).
• Steam Deck / SteamOS (Gaming Mode): if Steam tries to launch the AppImage with Proton, open the shortcut's Properties → Compatibility and select Steam Linux Runtime instead of Proton. The AppImage is a native Linux application. If it fails to launch using Steam Linux Runtime, open the shortcut’s Properties → Compatibility and select Default to use the host libraries instead.
• Menu entry: the AppImage writes ~/.local/share/applications/spartanport.desktop when it starts, so the launcher and the game window show their icon in the dock; Advanced → Linux turns it off and removes the entry. When another tool (Gear Lever, AppImageLauncher…) already made an entry that starts the same file, it makes none and removes its own, so there are no duplicates.

What works

• Opening, menus, video cutscenes (H.264) and gameplay.
• Audio: music, voices and effects (ATRAC9 and MP3).
• Controller (DualSense, Xbox and others, through SDL3) and keyboard at the same time, both remappable.
• In-game button icons (opt-in, off by default): the PlayStation button icons in the game can show your controller's, Xbox or Nintendo ones, or the keyboard keys you play with (Game page, Controls).
• Saving and loading: the save list is shown on screen, as on the PS4. Autosave works too. The launcher backs the saves up before every start.
• Patches: render resolution of 480p, 720p, 900p, 1440p, 1800p or 4K, corrupted texture fix and skip videos with the X button (community); engine frame rate of 120 FPS (kvicken), 100 FPS (for 100 Hz displays), 144 FPS (for 144 Hz displays) or 240 FPS (adapted by Felipe Prado).
• Ultrawide (beta): 21:9, 32:9 and 16:10 render resolutions (3440x1440 tested) with a wider field of view instead of a zoomed-in picture, built in: choose one in Render resolution, where every size shows its exact resolution and aspect ratio. Cutscenes keep their 16:9 borders (see docs/ultrawide.md). Mods can also carry game patches; the Ultrawide mod is the same sizes for older versions. How to install a mod: put its .zip (do not unzip it) in the mods folder next to SpartanPort.exe; the game unpacks it by itself. The Ultrawide mod and a one-click installer for 2.2.0 are explained in extras/mods/Ultrawide.
• Background shader compilation: saved pipelines load and compile in the background while you play. Stutters, missing effects during compilation and temporary FPS drops can still occur; startup time depends on the cache, graphics driver and CPU.
• Launcher in the game's colors, with selectable languages and English fallback: five pages (Home, Graphics, Performance, Game, Advanced) and a Save button for pending changes; quick settings on the home page, graphics, performance, game folder and save backups, patches, mods (order, presets and conflicts), controls with PlayStation or Xbox button icons, updates and diagnostics.
• In-game menu (Insert on the keyboard, R3+L2 on the controller), with four tabs:
  • Game: cheats (infinite health, magic, item meter, Rage of Sparta, max red orbs, automatic QTE: button and stick-rotation prompts answer themselves); multipliers from 0.1x to 100x for red, green (health), blue (magic) and gold (Rage of Sparta) orbs and for damage dealt and taken; an enemy health bar.
  • Image: display mode (windowed, borderless, fullscreen), VSync and RCAS sharpening.
  • Performance: frame rate limit (30 to unlimited), frames queued, background shader compiling; render resolution, engine frame rate and GPU readback options apply with one "Apply and restart" button.
  • Overlay: a performance overlay with FPS, frametime, upscaler, GPU (name and use), CPU, RAM and VRAM, each optional, with font size, corner, background opacity and layout. The numbers are the game's own use, not the whole system's.

Feature availability

Availability checked against release 2.2.0 and the source on October 14, 2026.

Feature	Published 2.2.0 packages	Current source
Windows ZIP / experimental Linux AppImage	Available	Build scripts available
Startup black-screen patch / controller button icons	Included	Included
Discord Rich Presence	Not included	Optional under Advanced, off by default; game name and elapsed time
RADV sparse-queue fix	Not included	Merged into main
FSR 1, FSR 3.1, FSR 4, TAA, DLSS	Disabled	Disabled in the launcher/game settings path
RCAS sharpening	Available	Available

The Linux AppImage was rebuilt on October 14 for glibc 2.39 or newer. The Windows and Linux packages can use different source revisions. Check the release notes for changes to later downloads.

Settings

Settings are kept in spartanport.ini (the game and the in-game menu) and in settings.json (the launcher), in the port folder. Saves, the shader cache and last_run.log go to the project's user folder.

GUI Scale: choose Auto, 1x or 2x under Advanced → Launcher, then click Save. Text, controls and layout resize together, without changing game resolution. Auto follows the desktop scale the window system reports to the Rust launcher (Windows display scaling; the Wayland or X11 scale on Linux). On macOS, Retina scaling stays with the operating system. Manual 1x/2x sets the launcher's logical size, including text, icons, controls, scrollbars and spacing. Screen resolution alone does not select a scale. The choice is saved in settings.json.

On Performance → GPU data → Stream buffer memory, choose System RAM (cached, default), System RAM (uncached) or GPU memory (previous behavior). System RAM can improve frame rates on NVIDIA laptops. The choice is saved and applies on the next game launch, including when using Play SpartanPort.exe or --play. Choose GPU memory to restore the previous allocation behavior. For direct launches without the launcher, SPARTAN_STREAM_MEMORY accepts cached, host or device; the launcher's saved choice takes precedence when using it.

On Performance → GPU data → Game multisampling, Automatic lets the game decide by the graphics card it runs on: it creates the game's multisampled images with a single sample on AMD's and Intel's Windows drivers, where reading the 2-sample depth buffer as a texture produced black lines in the lighting (Radeon RX 6600 family, Arc), and keeps them multisampled elsewhere (NVIDIA). The label names the card and the decision, for example "Automatic (Intel(R) Arc(TM) A750 Graphics: off)", and follows the Graphics card choice. The rule covers every GPU on those two drivers, integrated ones included; the game's log line GPU: guest multisampling off or on is what was applied. Choose Off if the lines appear on another card and On to keep multisampling anyway. Off and On set SPARTAN_NO_MSAA=1 or 0; Automatic passes an inherited SPARTAN_NO_MSAA through. Applies on the next game launch.

Chinese interface

Select 简体中文 under Advanced → Launcher language for the launcher and the Insert / R3+L2 menu. This does not change the game's text or voice language. Direct launches without the launcher can set SPARTAN_UI_LANGUAGE=zh.

The launcher prefers an installed CJK font (Microsoft YaHei UI on Windows, Noto Sans CJK SC or another available CJK family elsewhere). The in-game menu merges an installed Chinese font with its embedded font: Windows YaHei/SimHei, common Linux Noto/WenQuanYi locations, or macOS PingFang. No additional font is distributed. If no usable CJK font is found, the in-game menu keeps English and logs the reason instead of displaying missing-glyph boxes.

The headless chinese-ui-test CMake target checks translation fallback, printf arguments, font merging and Chinese glyphs without a game dump or Vulkan device. Its real glyph checks are skipped, with a message, on systems without an installed CJK font.

Keyboard controls

Defaults; change them on the launcher's Controls page, under Keyboard & Mouse Mapping.

Key	Button
WASD	left stick
Arrows	right stick (camera)
Space	Cross
Left Shift	Circle
Left click	Square
Right click	Triangle
Q and E	L1 and R1
R and the mouse's forward button	L2 and R2
Z and X	L3 and R3
F	Rage of Sparta (L3 + R3)
C	Grab (L1 + Circle)
The mouse's back button	Dodge
1, 2, 3, 4	d-pad up, right, down, left (weapons)
Mouse wheel up and down	next and previous weapon (cycles the d-pad weapons); in the game's menus (title, pause and Power Up) it moves the selection up and down, and goes back to the weapons once you walk or dodge
Tab	Options
P	left touchpad click (photo mode)
Esc	right touchpad click (pause menu)
Insert	the port's menu (R3+L2 on the controller)

Rage of Sparta on one input (on by default) leaves Z and X unused. Joystick prompts answer the stick-rotation quick-time events without a stick: type the turn (half turns D S A, A S D, A W D or D W A; full turns D S A W or A S D W) or, with Adaptive mouse, draw it. While you play, the mouse stays in the game window; the in-game menu, the pause key (Esc) and other windows get it back, and Esc again or a click in the window takes it back. With L2 held (R), the mouse aims with the right stick, for the Head of Helios or the Bow of Apollo: Relative follows the movement, Absolute points from where the mouse was when L2 was pressed, and Right stick sensitivity sets how much mouse it takes. Without the launcher the game keeps its own keys: E and Q for Square and Triangle, 1 and 3 for L1 and R1, F for R2, C for R3, I, K, J, L for the d-pad, Enter for Options, Tab and Backspace for the touchpad.

On a controller without a touchpad (Xbox and others), View opens the pause menu (the right touchpad click) and L1 + View opens photo mode (the left click). On a DualSense the touchpad works as on the PS4, and Share/Create works like View.

In-game button icons (off by default) are chosen on the launcher's Controls page, under In-game button icons: Match my controller, Xbox, Nintendo or Keyboard. They replace the PlayStation icons in the tutorial, move-list and quick-time prompts and, for the controller styles, on the Muses' lyre in the Chamber of the Flame; the pause-menu controller drawing stays a DualShock 4. Keyboard shows the key that presses each button, following your keyboard mapping (a changed key shows on the next start); Match my controller shows the keys too when no gamepad is connected. The launcher writes a patched copy of up to three game files (about 410 MB) into the port's data folder and never changes your game folder. A new controller is picked up after a restart. Without the launcher, set SPARTAN_GLYPH_STYLE to auto, xbox, nintendo or keyboard before starting run.sh.

In the menu: L1/R1 or Q/E switch tabs. In the save list: arrows or the d-pad choose, Enter or Cross confirm, Esc or Circle cancel.

Importing shadPS4 saves

Only shadPS4 saves of this game are compatible. RPCS3 saves are from the PS3 game and will not work. Use the same title ID (this example uses CUSA01623).

1. Close the game and shadPS4. Back up both save folders.
2. Find the source in shadPS4's data folder: user\savedata\1\CUSA01623\ in older versions, or home\<user-id>\savedata\CUSA01623\ in newer versions.
3. The destination is user\savedata\1\CUSA01623\ next to SpartanPort.exe. Example: C:\Games\spartanport-windows\user\savedata\1\CUSA01623\. With a custom Saves folder in the launcher, use <custom folder>\savedata\1\CUSA01623\.
4. Copy each slot folder there, keeping its name and game files. Do not nest another CUSA01623 folder. Exclude the slot's internal sce_sys folder from the game data.
5. Beside each slot, create <slot name>.sce_sys if it does not exist. You can copy shadPS4's sce_sys\icon0.png there. Do not rename param.sfo to param.bin: the formats differ. Preserve any existing port param.bin. Without one, the slot appears by folder name; saving again in the port writes its metadata and refreshes the displayed information.
6. Start the port and select Load Game. Completed saves can be imported too.

The port's save dialog displays at most 32 entries. If the imported slot is missing from a long list, test it with a separate Saves folder containing just that slot under savedata\1\CUSA01623\, with its sibling metadata folder. Keep the original saves and restore the previous Saves folder setting after testing.

Third-party overlays (Windows)

The game process is bin\spartanport-probe.exe, not SpartanPort.exe (source builds use out\spartanport-probe.exe). Add that executable to RTSS and enable Afterburner's on-screen display. In the ReShade installer, select that same executable and the Vulkan API.

If the overlay still does not appear, report the port and overlay versions, the last working port version, and attach user\last_run.log. These checks do not confirm a fix for every overlay configuration.

Generic USB controllers

Generic USB controllers: in Controls → Set up a controller, select the joystick, then choose Configure next to any button, D-pad direction or stick axis. Joysticks without an existing SDL gamepad mapping are listed too. Each detected input is saved immediately; you can start with any row and correct just one control later. Existing bindings are shown when reopening the editor. Clear removes only that row, and Cancel capture leaves the pending edit unchanged while keeping previous saves. The live preview lets you check the result at any time. Close the window when finished.

Profiles are saved per SDL device GUID and operating system in gamecontrollerdb.txt in the port's data folder. They load on the next game start, including --play, shortcuts and direct run.py launches. Explicit SDL_GAMECONTROLLERCONFIG and SDL_GAMECONTROLLERCONFIG_FILE mappings retain priority. The existing game button remapping still applies; use Reset to defaults if you want the buttons to match the guided setup. SDL must be able to read the joystick; the mapper does not install device drivers.

Troubleshooting

• Executable format errors: source builds accept plaintext PS4 SELF containers and unpacked little-endian x86-64 ELF executables and modules. A valid unpacked ELF was previously rejected with prepare failed: expected PS4 SELF. Files in another format and encrypted/compressed SELF segments still need a correctly prepared game dump.
• Black screen at start: use the latest release, which includes the startup deadlock patch. If it persists, report your GPU, driver, game build and Advanced → Log output. Clearing the shader cache is not a general fix and requires rebuilding it on the next launch.
• The game closes with "cannot create ... guest memory (error 1450)": Windows ran out of virtual memory to allocate the guest pool. Increase the page file: press Win + R, type SystemPropertiesAdvanced, go to Performance Settings → Advanced → Virtual memory Change, uncheck automatic management, select drive C:, set a custom size (e.g. 16384 MB initial, 24576 MB maximum), click Set, OK, and restart your PC.
• Game language in the launcher has no effect: it is only used on the game's first start. After that the game restores its own text and speech languages from its settings save, so change them in the game: Options → Game Settings → Game Text and Options → Audio → Speech (for example, Polish text with English voices).
• The game does not open: check Advanced → Log, or send user\last_run.log with your report. With a custom Saves folder, last_run.log is in that folder instead.
• Yellow/orange/white textures or wrong lighting: try disabling Performance → GPU data → Deferred GPU readbacks, then restart. This workaround can cause stutters.
• GPU-specific rendering failures, crashes, audio problems and progress blockers remain under investigation. Check the release notes and issues before reporting; include a save from before the problem when relevant.

Performance and compatibility

Previous testing on an AMD Radeon RX 6700 XT, Ryzen 5 5600X and 32 GB recorded 144 FPS on average (55 to 240) at 1080p with the 240 FPS engine frame rate. These are reference results, not a benchmark of every release or a guarantee for other systems.

Tested and playable from start to finish at native 1080p with the 240 FPS engine frame rate on the test system. Texture corruption, crashes and progress blockers have also been reported on other setups, including at 1080p. See the known issues in the release notes.

Building from source

Windows

Install rustup (stable) and the Visual Studio Build Tools with the "Desktop development with C++" workload; the launcher is built with cargo and needs no Python. The build commands below use MSYS2 CLANG64; launcher commands marked PowerShell run on Windows.

Development happens on the spartanport branch; main receives tested merges.

1. Install MSYS2 (winget install MSYS2.MSYS2) and, in the MSYS2 CLANG64 shell, the packages listed in packaging/windows/README.md.

2. Clone the repository with its submodules and build:

   git clone --recursive https://github.com/FelipePrado0/SpartanPort
   cd SpartanPort
   git checkout spartanport   # development branch; omit to build main
   bash build.sh

3. Start the launcher (in PowerShell, in the project folder):

   cd launcher-rust
   cargo run --release

4. On Game, choose the game folder and patches. Adjust Graphics and Performance, click Save for pending changes, then PLAY.

To play with the saved settings without opening the launcher's window (for a shortcut or Steam):

cd launcher-rust
cargo build --release
.\target\release\spartanport-launcher.exe --play

Or without the launcher's settings, from a Git Bash or MSYS2 shell:

SPARTAN_GAME_DIR='D:\path\CUSA01623' bash run.sh

Linux (Ubuntu 24.04)

For a fresh checkout, run the following in a Linux shell. The dependency script installs system packages using sudo and selects GCC 14 as the default compiler. The launcher also needs rustup (stable). It is intended for Ubuntu 24.04; adapt dependencies for other distributions. If already cloned, start in the repository and skip the first two commands.

git clone --recursive https://github.com/FelipePrado0/SpartanPort
cd SpartanPort
bash packaging/linux/ci-deps.sh
bash build.sh
cd launcher-rust
cargo run --release

To package an AppImage after the build:

bash packaging/linux/build.sh
./dist/spartanport-x86_64.AppImage

packaging/linux/build.sh builds the Rust launcher itself. Building on a newer distribution can require a newer glibc; public release builds use Ubuntu 24.04. From the repository, use bash run.sh for a direct start (it builds what is missing and runs the launcher's exe with --run), with SPARTAN_GAME_DIR=/path/to/CUSA01623 to name the game folder. For the saved launcher settings without the window, run launcher-rust/target/release/spartanport-launcher --play.

Rust launcher

The launcher is written in Rust (launcher-rust/, iced) and is the only launcher the packages ship. It builds with rustup (stable). On Windows, install the Visual Studio Build Tools with the "Desktop development with C++" workload; on Ubuntu, sudo apt-get install build-essential pkg-config libwayland-dev libxkbcommon-dev.

cd launcher-rust
cargo run --release

Started from a checkout, it finds the tools in out/ on its own; SPARTAN_PORT_DIR points it at a packaged port instead (its bin/). PLAY starts the launcher's own exe with --run, so nothing needs Python.

Linux (Arch Linux)

The PKGBUILD is provided here.

Build and install (using yay for the AUR build dependency):

sudo pacman -S --needed base-devel git curl robin-map
yay -S --needed vulkan-memory-allocator
mkdir -p ~/spartanport-build && cd ~/spartanport-build
curl -fLO https://raw.githubusercontent.com/FelipePrado0/SpartanPort/main/packaging/linux/PKGBUILD
makepkg -si

Run the launcher under Games in your application menu or with spartanport from terminal.

Optional packages (use an AUR helper such as yay for python-iced-x86):

sudo pacman -S --needed gamemode mangohud
yay -S --needed python-iced-x86

Tests

Run these from the repository root after the build. The first C++ checks below do not need a game dump.

Python

The launcher and runner Python code is frozen: it is not packaged and not run by the port. It stays in the repository as the parity reference for the Rust launcher. Its tests still run, with Python 3.10 or newer (on Windows, in PowerShell):

python -m unittest discover -s tests -p "test_*.py"

Rust launcher

cd launcher-rust
cargo test

The page snapshots under launcher-rust/snapshots/ are compared pixel by pixel on Windows only. python -m unittest discover -s tests -p "test_launcher_parity_doc.py" checks that every Python launcher test has its row in docs/specs/2026-10-21-rust-launcher-parity.md. tools/runner_fixtures.py generates launcher-rust/fixtures/runner/, the inputs and the files the Python runner's modules write over them, for the Rust runner's parity tests.

Windows C++ tests (MSYS2 CLANG64)

source ./msys2-env.sh
ninja -C out/gpu perf-overlay-test warmup-inbox-test graphics-settings-test
out/gpu/perf-overlay-test.exe
out/gpu/warmup-inbox-test.exe
out/gpu/graphics-settings-test.exe

Linux C/C++ tests

bash build.sh --test
ninja -C out/gpu perf-overlay-test warmup-inbox-test graphics-settings-test
out/gpu/perf-overlay-test
out/gpu/warmup-inbox-test
out/gpu/graphics-settings-test

bash build.sh --test runs the additional C runtime tests on Linux only. On Windows the build exits before that block; use the Ninja targets above.

Checks using a prepared game

After preparing your own dump, out/eboot.elf and out/boot-linked.bin are needed for the following checks. In MSYS2 CLANG64 on Windows, replace the example game path with yours:

ninja -C out/gpu stat-multipliers-test
out/gpu/stat-multipliers-test.exe out/eboot.elf
out/spartanport-probe.exe out/boot-linked.bin --app0 "D:/Games/CUSA01623" --check-imports

On Linux, use out/gpu/stat-multipliers-test and out/spartanport-probe without .exe, and a Linux game path. --check-imports checks system imports and exits without starting gameplay. More test targets are listed in gpu/CMakeLists.txt.

How it works

The CPU side is native: the game's original executable runs directly on the PC's processor (the PS4 uses the same x86-64 architecture), and a runtime written for this game replaces the PS4 system libraries, without CPU emulation. The graphics are translated: they run on the shadPS4 video core, which converts the PS4 GPU commands and shaders to Vulkan, with the game's rendering fixes from cuesta4's eltutz branch. Running the game code directly on the CPU is also how shadPS4 works; what this project changes is the system layer and the game-specific work (patches, background shader cache, launcher and in-game menu). It is a fork of Supermedo's Windows port of deadinside28's bloodborne_pc (see Credits).

• The patches and the in-game hooks (cheats, multipliers, health bar) find their sites by signature: the original bytes around each one, wherever a release placed that code (tools/make_signatures.py). A site that is not found leaves only that patch or hook off; the game starts without it, and the log and the menu say why.

Part	Where	What it does
Preparation	launcher-rust/src/core, launcher-rust/src/runner	Reads eboot.bin, applies its relocations and links the game's own libc and libSceFios2 into one image
Loader	src/probe.c	Loads the image, installs the validated hooks (cheats, multipliers, health bar) and starts the game's original code
Runtime	src/runtime_*.c	Reimplements the PS4 system functions: memory, threads, files, audio, video, controller, saves and services
GPU	gpu/shadps4/	The shadPS4 video core, translating the PS4 GPU commands and shaders to Vulkan, with cuesta4's fixes for this game (eltutz branch) and this port's speed work (background shader cache, deferred readbacks)
In-game menu	gpu/shim/spartanport_overlay.cpp	The Dear ImGui menu and performance overlay; settings in gpu/shim/spartanport_settings.cpp
Patches	patches/CUSA01623.xml, launcher-rust/src/core	Applied in memory at start, without changing the game files
Launcher	launcher-rust/src/ui	Settings, patches, mods, controls and the play button

The Python in scripts/ and launcher/ is kept as the frozen reference the Rust code was ported from; it no longer ships.

More documentation: mods, patches, frame map and historical upscaler research and parallel GPU work.

Credits

This project is a fork of Supermedo's Windows port, which builds on deadinside28's original:

• deadinside28: bloodborne_pc, the original native port.
• Supermedo (Mohammed Albarghouthi): bloodborne_pc for Windows, the fork this project comes from.
• cuesta4: shadPS4 fork focused on this game (branch eltutz). The game's rendering in this port depends on its fixes: the GNM blend rewrite, depth/stencil state and image aliasing. cuesta4 is also a co-author of the resolution, texture fix, 120 FPS and skip videos patches (below). If you play on shadPS4, this is the build to use for this game.
• shadPS4 team: the shadPS4 video core, which does all the GPU and shader translation to Vulkan in this port.
• WilkPrintes: designed and built the SpartanPort website. Special thanks for giving the project its home.

Patches: kvicken and cuesta4 (resolution, texture fix, 120 FPS and skip videos, building on the PS3 patches by illusion0001), published for shadPS4 in shadps4-emu/ps4_cheats#145 and adapted to this executable. The 144 and 240 FPS patches were adapted by Felipe Prado from the 120 FPS patch; the 100 FPS one is the same patch with 100. Cheats: adapted from Celogamez's GoldHEN cheats.

Also used: LibAtrac9, FFmpeg, SDL3, Dear ImGui, sirit, magic_enum, miniz, xbyak, Vulkan Memory Allocator, FSR-Vulkan and the AMD FidelityFX SDK, MSYS2, LLVM and Pillow.

License

GNU GPL v2 or later (LICENSE). Third-party components keep their own licenses.