Use normal work versus a repeated hang, then compare your transition with the original reports.
Separate preparation from the failing transition
The first launch prepares the game image. Later launches can still be affected by shader work; the corner Loading shader cache indicator describes saved shaders loading in the background. Startup time depends on the cache, driver and CPU, so the checked documentation supplies no single minute threshold that distinguishes every normal load from a fault.
Record whether this is the first launch, an initial level load or a later transition from a reproducible save. Note the last completed scene and whether the process exits. An explicit prepare error belongs to launch diagnostics, not an instruction to keep waiting indefinitely.
Sources: Project README · Download and play · Project README · What works · Project README · Troubleshooting
Two specific hangs with moving indicators
Those are original reporters’ logs and procedures, not this site’s gameplay tests. 2.4.0 still lists both transitions as endless-loading issues, and 2.4.1 inherits its known issues. The reports do not prove every loading hang has the same internal cause.
The high-FPS workaround for a blocked path or QTE is not a confirmed fix for #345: its reporter already tried all three engine rates. Likewise, a restart that happens to reach the next area once is not proof of a universal save-recovery method.
Original loading reports and the limits of their observations
On a narrow screen, scroll the table horizontally to read every column.
| Transition | Original setup and observed result |
|---|---|
| After defeating Hades and allowing HADESDEATH to play | Issue #345: 2.2.0, RTX 4060 Laptop 8 GB, i7-12700H. Frame stats continued while Hds690 loading never completed; 60/120/240 engine settings and video-skip variations gave the same result |
| Entering the Forge after the statue fight | Issue #428: 2.2.0/2.3.0, GTX 1060 3 GB, i7-3770. Spinner continued while Hds500 load entries lacked a later completion line |
Sources: Original issue #345 · Loading after Hades · Original issue #428 · Entering the Forge · 2.4.0 release · 16 October 2026 UTC
Keep progress intact while checking the branch
The backup/import guide explains the actual data boundaries. Do not delete the original progress, import a PS3 save or clear the shader cache as a generic way to skip a stalled area. Cache clearing changes later preparation work and cannot establish that an async area load has been repaired.
Preserve the original data
Close the game before copying saves. Keep a separate copy of the selected Saves folder and the failed run’s log; do not overwrite the only pre-transition slot.
Record a controlled reproduction
Write down the runtime tag, game title/build, transition, last successful checkpoint, resolution and engine setting. If you retry, use a copy of the same pre-transition save and compare one condition.
Use the matching issue information
If the same transition still hangs, retain the result and report the log and pre-transition save to the matching project issue. No proven recovery for these hangs is supplied by the checked release notes.
Sources: Project README · Importing shadPS4 saves · Project README · Troubleshooting · Original issue #345 · Loading after Hades · Original issue #428 · Entering the Forge
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 · What worksMaintainer feature descriptions, not this site’s gameplay tests.
- Project README · TroubleshootingDocumented checks and qualified workarounds.
- Original issue #345 · Loading after HadesReporter: 2.2.0, RTX 4060 Laptop 8 GB, i7-12700H; tested 60/120/240 engine rates without recovery.
- Original issue #428 · Entering the ForgeReporter: 2.2.0/2.3.0, GTX 1060 3 GB, i7-3770; moving loading icon while area load fails.
- 2.4.0 release · 16 October 2026 UTCBuilt-in aspect ratios, fast screen effects, validation hardware and unresolved issues.
- Project README · Importing shadPS4 savesSame-title-ID Remastered saves only; includes slot metadata and list limits.