Match the stage and process state before changing settings.
Identify what continues behind the black screen
Note whether sound continues, the process remains present, and the last visible screen. Sound or a live FPS counter helps describe the state but does not prove that the next area is loading. Keep the failed run’s log before another launch replaces it.
Use the stage to choose the next check
On a narrow screen, scroll the table horizontally to read every column.
| What you observe | Relevant branch |
|---|---|
| The program exits or shows an error | Use the crash log branches |
| The window stays black after the Santa Monica logo | Match the startup issue to release and GPU; preserve the log |
| Menus work, but 3D is black/blue | Check the GPU-specific known limitations |
| Black screen at a repeatable area transition | Use loading-hang evidence |
| Only textures, lighting or screen placement are wrong | Use graphics symptoms |
Sources: Project README · Download and play · Project README · Troubleshooting · 2.4.0 release · 16 October 2026 UTC · Original issue #345 · Loading after Hades
Check the startup patch and the selected GPU
The README says the startup black-screen patch is always requested, including with an older saved patch selection, and applied where its signature matches. Use a published package that contains it rather than assuming an old saved checkbox prevents the request. If the problem persists on 2.4.1, its existence alone is not proof that your fault has been fixed.
2.3.0 addresses AMD-integrated/NVIDIA hybrid laptops where the AMD switchable-graphics Vulkan layer hid the NVIDIA GPU. Start with that release or later, inspect the selected Graphics card and compare the GPU named in the log. This change is specific to that detection problem; it is not a general driver replacement procedure.
Intel HD 630 black/blue 3D remains in the 2.4.0 known-issue list. Treat it as a matched compatibility report rather than repeatedly toggling unrelated display settings. A current Vulkan driver meets a requirement but cannot by itself prove correct rendering.
Sources: Project README · Download and play · 2.3.0 release · 15 October 2026 UTC · 2.4.0 release · 16 October 2026 UTC
Preserve useful evidence and stop broad resets
Open Advanced → Log. On Windows the default file is user\last_run.log beside the program; a custom Saves folder moves the log there. Record the tag shown by the launcher, OS, CPU, GPU/driver, PS4 title ID/build, last visible stage and exact final log messages.
If the log names guest-memory error 1450, a missing/invalid game file or an overlay DLL, follow that specific launch-error branch. Do not classify all those failures as the startup deadlock.
The maintainer explicitly rejects cache clearing as a general black-screen cure. It forces cache rebuilding on the next launch. When the current package still fails without a matched remedy, keep the log and report the configuration; do not promise that reinstalling the same files will solve it.
Sources: Project README · Troubleshooting · 2.4.0 release · 16 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 · Download and playMaintainer instructions at the 2.4.1 release commit.
- Project README · TroubleshootingDocumented checks and qualified workarounds.
- 2.4.0 release · 16 October 2026 UTCBuilt-in aspect ratios, fast screen effects, validation hardware and unresolved issues.
- Original issue #345 · Loading after HadesReporter: 2.2.0, RTX 4060 Laptop 8 GB, i7-12700H; tested 60/120/240 engine rates without recovery.
- 2.3.0 release · 15 October 2026 UTCHistorical texture/RADV/hybrid-GPU fixes, screenshot and vibration validation, and known issues.