God of War III on Windows: Unofficial PC Port Setup, Requirements and 240 FPS Caveats

What "native" means here​

The project's own description says the CPU side is native. The game's original executable runs directly on the PC's processor, because the PS4 uses the same x86-64 architecture. A runtime written for this game replaces the PS4 system libraries, so there is no emulator.

The graphics side is a different story. The graphics are translated. They run on the shadPS4 video core, which converts PS4 GPU commands and shaders to Vulkan, with God of War III rendering fixes from cuesta4's branch.

The README also admits that running game code directly on the CPU is how shadPS4 already works. What this project changes is the system layer and the game-specific work: patches, a background shader cache, a launcher and an in-game menu.

So "no emulator" is fair for the CPU path, but the GPU path still involves translation. It is a one-game port built on emulator-derived graphics technology. It is not a rebuild of the game from source, and it is not an official Sony release.

The project is a fork of Supermedo's Windows port of deadinside28's bloodborne_pc. Wccftech notes that its scope is similar to the unofficial Bloodborne PC port released last week. The release credits also name patch authors kvicken and cuesta4, and say Felipe Prado adapted the 240 fps patch.

Frame rates and resolution​

The headline numbers are developer-reported, not independent benchmarks. The developer says that on a Radeon RX 6700 XT, Ryzen 5 5600X and 32 GB of RAM, the game averages 144 fps at 1080p with the 240 fps engine frame rate. The range is 55 to 240 fps. At 4K with FSR 1 it averages 108 fps.

That range matters. A 240 fps ceiling does not mean 240 fps on your PC.

• Engine options: the launcher offers render resolution from 480p to 4K and an engine frame rate of 60, 120 or 240 fps.
• Long session: the 2.1 release notes describe about four hours of gameplay on an RX 6700 XT averaging 118 fps with no crash. That is a different test from the 144 fps figure, and the developer adds that performance varies by hardware and scene.
• Resolution caveat: at render resolutions other than native 1080p, some textures look broken. 4K is selectable, but it is not a clean 4K experience yet. Native 1080p remains the recommended setting.
• Texture glitches at 1080p: the 2.1.2 notes say yellow or corrupted textures can appear in some areas, including at native 1080p. The developer lists this as under investigation. New areas and effects can also cause temporary stutters while shaders are prepared.

Keyboard and mouse input​

The 2.0 release notes say the game has sound, controller and keyboard input, and saves. The launcher includes controls with PlayStation or Xbox button icons. That supports keyboard input and a configurable controls page.

The headline's "customizable mouse and keyboard controls" is not something I could confirm in detail. I found no documented mouse scheme or complete remapping description in the sources I reviewed.

What you need to run it​

The documented requirements are:

• Windows 10 (1903 or newer) or Windows 11, 64-bit.
• A graphics card with Vulkan 1.3 and an up-to-date driver.
• Your own copy of the game (CUSA01623, version 01.02), meaning the folder with eboot.bin, sce_module and sce_sys.
• For persistent shader caching, GPU and driver support for VK_KHR_pipeline_binary.

The project says no game files are included, and you need a dump from your own PS4. It also states it is not affiliated with Sony Interactive Entertainment or Santa Monica Studio.

Destructoid says the project "does not allow pirates" to use it. That overstates what the repository shows. The project distributes no game files and requires your own dump. Whether dumping or using game files is lawful depends on where you live, and I can't settle that here.

Setup steps from the release notes​

1. Download gow3-windows.zip and extract it to a folder. The 2.0 notes say not to run it from inside the zip.
2. Open God of War III.exe. The program is not digitally signed, so Windows may show "Windows protected your PC". The project's instruction is to click More info, then Run anyway.
3. Click Choose the game folder, then Browse next to Game folder, and select the folder containing eboot.bin.
4. Click PLAY. The first start takes longer while the game image is prepared, and previously unseen shader pipelines also need preparation.
5. On later runs, the Play button in God of War III.exe starts the game straight away.

Running an unsigned executable from a hobbyist project means you are trusting the author and the download. Get it only from the project's own release page, and consider whether you're comfortable with that on your main machine.

Known issues and fixes​

The project has shipped several releases in about two days. Details matter if you're troubleshooting.

• Startup crash on Nvidia (2.1.3): the notes say that disabling "Use pipeline binary cache (A/B test)" in Performance → Shaders now takes effect during Vulkan device initialization. If the game closes immediately at startup on an Nvidia card, turn that option off manually and relaunch. The notes say Nvidia confirmation is still pending. AMD users can normally leave caching on, though only the RX 6700 XT was tested. Intel is untested.
• Cost of turning caching off: longer loading and temporary stutters.
• Game speed fix (2.1.4): the 120/240 fps patch only applies to the executable build it was checked against. On other builds, such as a different 01.02 build or the EU version, the engine stays at 60 fps. Before 2.1.4, the frame limit could exceed that, so the game ran too fast. The fix caps the frame limit at the applied engine rate. The launcher now shows "patches not available for this game build" when this applies.
• Executable compatibility: patches and cheats still apply to only one executable build. Support for the other 01.02 build is in progress.
• Non-Latin titles (2.1.2): a startup failure caused by non-Latin characters in the game's metadata, such as a Japanese, Korean or Russian title, is fixed.

An open pull request claims a large jump on an Nvidia laptop, from 35 to 129 fps median. That is an unmerged third-party claim, so treat it as a lead and not a result.

Why Windows users should care​

Destructoid frames this as a sign that AAA publishers are endangered by AI-assisted coding. The evidence is thinner than that. The developer reportedly used Claude Opus 5.5 as a coding assistant, as noted by the Brazilian outlet Gameplays Cassi. But the port stands on years of shadPS4 renderer work, an earlier Bloodborne port and community patches. AI assistance may have sped up the integration. It did not create the foundation.

The claim that Vulkan makes AMD the best and most stable option is also unproven. The developer's testing is mostly on an RX 6700 XT, and the early startup problems were reported on Nvidia. That is a gap in testing, not evidence of a vendor ranking.

For PC enthusiasts, the lasting interest is technical. It shows how far the shared x86-64 architecture of modern consoles, plus Vulkan, can carry a single-title port. The practical cautions are just as clear. This is an unofficial, evolving project that needs a specific game build, and it has known texture bugs. It also asks you to run unsigned software.