AnyPS5 Progress and Game Test Milestones
A reviewed snapshot of the upstream project and selected game reports. Documentation coverage is not game compatibility.
Upstream implementation coverage
| Measure | Reported snapshot | Meaning |
|---|---|---|
| Library functions | 3,292 / 3,706 · 88.83% | Implementation coverage, not a playable-games rate. |
| Shader instructions | 1,166 / 1,166 · 100% | Recorded instruction coverage, not full rendering correctness. |
Selected game milestones
Ghost of Yōtei · Separate Linux/RDNA4 run records an OOM stop.
Original evidence ↗Gran Turismo 7 · Separate RTX 4090 stock-main failure report posted.
Original evidence ↗Demon’s Souls · Linux/RADV follow-up reaches character creation with visible artifacts.
Original evidence ↗Ghost of Yōtei · Windows experimental runs reach the opening scene and setup screens.
Original evidence ↗Demon’s Souls · Source update distinguishes stock-main loading failure from the patched tutorial result.
Original evidence ↗Gran Turismo 7 · Music Rally and later performance updates retain the local-branch scope.
Original evidence ↗Gran Turismo 7 · Bring-up thread opened with the local integration environment.
Original evidence ↗God of War: Sons of Sparta · Upstream-based title-screen report explains filesystem and plugin fixes.
Original evidence ↗God of War: Sons of Sparta · A follow-up reports repeated crashes during a two-hour session.
Original evidence ↗Grand Theft Auto V · Opening report updated with 27–28 FPS prologue observations and a separate main comparison.
Original evidence ↗God of War: Sons of Sparta · Opening gameplay report posted; exact test date is not stated.
Original evidence ↗Grand Theft Auto V · Per-title bring-up thread opened.
Original evidence ↗
A merged PR or a higher implementation percentage does not establish a game’s status. Read the exact test report.
What the AnyPS5 progress snapshot establishes
AnyPS5 progress combines dated engineering work with separate per-game observations. A higher implementation counter does not mean the same percentage of games is playable.
Read AnyPS5 progress beside the original source date and build. A merged change may fix one path while another scene still needs an unimplemented function. Keep release notes separate from experimental results.
For a practical next step, choose a game report rather than treating AnyPS5 progress as a system-requirements calculator. Preserve the platform, patches and limitations that belong to that observation.