Use the process table, then the disable-and-compare path if adding an overlay changes launch behavior.
Use the actual game process and API
Close the game while changing the installation, note the port and overlay versions, and begin with one overlay so you can identify which change affects the result. The instructions establish executable/API targeting; they do not provide a measured compatibility matrix, a certified preset or a reason to copy a preset for the 2018 God of War executable.
Documented Windows overlay targets
On a narrow screen, scroll the table horizontally to read every column.
| Tool / build | Target or setting |
|---|---|
| RTSS / Afterburner OSD | Add bin\gow3-probe.exe and enable Afterburner’s on-screen display |
| ReShade installer | Select bin\gow3-probe.exe and Vulkan |
| Source build | Use out\gow3-probe.exe instead of the packaged bin path |
| God of War III.exe | Launcher, not the renderer target described by the README |
Source: Project README · Third-party overlays
Separate a missing overlay from a hook-induced failure
If the game still runs but the overlay is absent, first recheck the executable path, selected API and the tool’s own enabled display. The README asks for the port/overlay versions, last working port tag and last_run.log if that is still insufficient. It explicitly does not guarantee a fix for every configuration.
If the process exits only with an added hook, keep the crash log and compare without that integration. Original issue #199 names ow-graphics-hook64.dll; the 2.3.0 notes advise closing Overwolf for that startup crash. This is a specific hook report, not proof that all ReShade or RTSS installs crash.
The port’s own performance overlay is a separate feature, and 2.4.0 lists its input-lag report as unresolved. Disable that overlay for an input-lag comparison before blaming a third-party shader preset. If the log instead reports memory or game-file failure, use launch diagnostics.
Sources: Project README · Third-party overlays · 2.3.0 release · 15 October 2026 UTC · 2.4.0 release · 16 October 2026 UTC · Original issue #199 · Overwolf crash log
Disable the integration and compare without altering game files
The ReShade developer advice concerns the installer’s removal mechanism, not a test of a particular 2.4.1/ReShade pair. Avoid deleting guessed Vulkan files across the system. If you only want sharpening or a local performance readout, first check the port’s built-in image and overlay controls.
Keep the baseline and the failed log
Close the game, record which overlays are enabled and save the failed run’s log. Keep your game files and saves unchanged.
Remove one integration at a time
Close Overwolf for the named Overwolf branch. Disable the relevant RTSS/Afterburner display/profile for its comparison. For ReShade, developer crosire describes using the setup tool again, pointing it at the game where ReShade was installed and choosing uninstall.
Relaunch and compare the same stage
Use the same runtime, game build and scene without that integration. If the crash persists, retain the new log; absence of the overlay is not proof that the underlying game bug is fixed.
Restore only the intended integration
If you choose to re-enable or reinstall, use the recorded executable/API and tool version. Reintroduce one integration at a time so a regression remains attributable.
Sources: Project README · Third-party overlays · ReShade developer · Removing an installation · 2.3.0 release · 15 October 2026 UTC
Sources and method
Prepared by GOW III · PC Field Guide from the linked maintainer documentation, release records and attributed original reports, with AI assistance in research, writing and implementation. We have not played or independently benchmarked the game. Source checks describe the records read, not our own gameplay results.
- Project README · Third-party overlaysWindows process/API targeting; no universal overlay compatibility promise.
- 2.3.0 release · 15 October 2026 UTCHistorical texture/RADV/hybrid-GPU fixes, screenshot and vibration validation, and known issues.
- 2.4.0 release · 16 October 2026 UTCBuilt-in aspect ratios, fast screen effects, validation hardware and unresolved issues.
- Original issue #199 · Overwolf crash logHistorical 2.1.8 log names ow-graphics-hook64.dll; 2.3.0 notes advise closing Overwolf.
- ReShade developer · Removing an installationDeveloper crosire’s setup-tool uninstall advice; not a test of a particular gow3_pc/ReShade pair.