AnyPS5 games and compatibility reports

Animal Well has a Windows gameplay and audio report, PAC-MAN WORLD Re-PAC reaches a level on main, and the DOOM homebrew has gameplay plus a separate patched audio/save result. Larger games range from title screens to short scene tests, often with additional patches and unresolved graphics or loading problems.

The reports on this page show where each AnyPS5 run gets to, its configuration and what the author tried next. For a lookup by game, host system and reported GPU, use the AnyPS5 game checker.

Reading stages for AnyPS5 games

A stage is a quick way to locate a result: startup, menu, a playable scene or a longer session. Read the note beside it for the actual route into that scene and the point where the run stopped.

Audio, input, saves, stability and full completion are separate checks. An author's “playable” label describes their reported experience; the individual observations show which of those checks they discussed. “Not reported” leaves an item open.

Notable results for AnyPS5 games

Animal Well: gameplay with music and ambience

The Windows report describes ingame play with no blocker found in that session, including music and ambience. It is a useful starting point for readers looking beyond title-screen demonstrations. See the configuration in the report list and the original Animal Well discussion.

PAC-MAN WORLD Re-PAC: a level on main

The selected follow-up reaches menus, loads existing save data and plays a level with audio without the earlier local patch stack. The previously reported level-complete crash remains a transition to check. Its extra module-directory arguments are part of the setup, so keep the command with the result. Read the PAC-MAN discussion and follow-ups.

DOOM homebrew: two useful Windows runs

One run checks E1M1 movement, firing, pickups and automap with keyboard and mouse. A separate patched run reaches E1M3, checks audio and reloads a save on a later launch. The list keeps these configurations separate. This is lowbit's classic DOOM homebrew, rather than a retail PS5 DOOM release. Follow the DOOM discussion for the test sequence.

Larger games: the launch route matters

Astro Bot has a short Crash Site test with movement, camera control and jumping through a private integration and direct level argument. Gran Turismo 7 has menus, a garage and Music Rally work on another branch, including AutoDrive, with corruption and crashes still reported. Those are useful scenes for development work; their configuration notes explain what is needed to reach them. See the Astro Bot report and Gran Turismo 7 report.

Compare a report with your setup

Before trying a reported configuration, check these details in order:

1. Game identity: title ID, edition and content version. A Preview build or regional edition may differ from your copy.
2. Project revision: release tag or commit, including required pull requests and local changes. Check whether an integration tree is available to build.
3. Host environment: OS, execution method, GPU, driver and any memory conditions stated by the author.
4. Launch route: ordinary New Game, an existing save, a selected scene or a debug argument.
5. Your next test: the first unresolved transition or feature, such as loading a level, saving and reloading, or using a controller.

Use frame rates to understand the reported scene on that machine. They are less useful as a comparison between different games, patch stacks and test routes. For the project's implementation counters, read AnyPS5 progress.

Find and contribute reports

Search the Game bring-up discussions by game and title ID, including replies after the opening post. The community blocker map helps locate related issues and pull requests; our AnyPS5 Reddit guide covers selected showcases.

For an attempt of your own, check AnyPS5 requirements, follow AnyPS5 setup, and use AnyPS5 troubleshooting to record the first failure. For corrections or updated results, contact us.