AnyPS5 game tracker
Grand Theft Auto V key art
Grand Theft Auto V icon

Grand Theft Auto V on AnyPS5

PPSA04264 · PPSA04263 · last report 10 Oct 2026

In game The opening prologue has been played in game on Windows at around 27 fps, but only on a testing branch; current main still stops during boot.

  1. Nothing
  2. Boots
  3. Menus
  4. In game
  5. Playable

The Story Mode prologue plays on Windows (about 27-28 fps in Performance mode) on a contributor's testing branch built from an older main plus many unmerged pull requests; current main stops at boot.

Running it and it stopped on an error? Check the error against every report and fix for this game.

Screenshots

Posted by testers in the project's threads; the date links to the post. Click to enlarge.

Where it stands

GTA V is the furthest-along big game in the project, but not on the normal main branch. One contributor's testing branch gets from the intro movie and menus through Story Mode loading into the North Yankton prologue. In Performance mode it runs at roughly 27-28 fps inside the bank, with the HUD, reflections, music, speech and sound effects working. Only the prologue has been tried, and the frame rate drops depending on where you are and where you look.

The higher graphics modes (Fidelity and Performance RT) render correctly since 7 October, when a ray tracing bug was fixed, but they run at only a few frames per second. Story Mode also needs an add-on entitlement entry to be listed for the game before Resume Story is available. The first launch after a graphics-code change rebuilds the shader cache and can sit on a black screen for a few minutes.

Current main is a different story. A big change on main in early October made the game stop at boot. On 9 October, plain main aborted a few seconds in. Stacking about seven open pull requests got it to show its first start screens at about 29 fps, then it stopped about two minutes in on a texture table the game reads at run time. Two of those fixes (#2293 and #1836) were merged on 10 October, but others are still open.

A second tester on an RTX 4090, using a separate branch, got into Story Mode but the game stops about 30 seconds after it starts, on every run, because one graphics job reads data that has not been written yet. The project is not an emulator; it converts the PS5 program to run natively, and the game needs your own game dump to try it.

WindowsIn game (prologue) at about 27-28 fps in Performance mode on a testing branch; plain main stops at boot
LinuxNo run reported; one boot fix was prepared on Linux by a contributor
macOSNo test report yet

What is stopping it

  • Current main stops at boot. Several unmerged fixes are still needed to reach even the start screens (heap capacity, shader headers, image mode switches, packed pixel data). Thread
  • On main plus the open fixes, the game stops about two minutes in when it reads a texture from a material table (bindless image tables); the fix is still being reworked. Thread
  • On a second tester's branch, Story Mode stops about 30 seconds in: a job-manager graphics kernel reads descriptors from a memory block that is still blank when it runs. Thread
  • Performance mode is limited by one CPU thread recording draw calls (about 1,800 per frame), capping the frame rate near 27-28 fps. Speedups are still in open pull requests. Thread
  • Fidelity and Performance RT (ray tracing) modes run at only a few fps; the ray tracing passes take most of the GPU time. Thread

How it got here

  1. A contributor gets GTA V (PPSA04263) to its main menu: intro movie with sound, legal and calibration screens, landing page and Settings. It then starts loading Story Mode until it hits a shader the recompiler cannot handle. Source
  2. Another contributor's build takes GTA V (PPSA04264) from the Story Mode load into the prologue, at about 3-4 fps. The lit scene is still far too bright and some textures are garbage. Source
  3. That work is merged with the game running its own bundled system libraries (no skip flags), getting as far as the Story Mode load. Source
  4. The prologue is reported playable at about 10 fps on a testing branch, with music, speech, sound effects, HUD and reflections. Source
  5. A decoding fix merged: music and speech work (they were silent before). Source
  6. A fix for a ray tracing hang is merged; Fidelity and Performance RT modes now render correctly, though at a few fps. Source
  7. Performance mode in the prologue bank reaches about 27-28 fps on the testing branch (23.5 before). Source
  8. Current main is found to stop at boot; with a stack of open fixes it presents its first start screens at about 29 fps, then stops at material tables. Source
  9. Two boot fixes are merged to main (#2293 prim states, #1836 deferred shader preparation). A second tester reports reaching Story Mode on an RTX 4090 before a new stop about 30 seconds in. Source

Tested hardware

PCResult
Windows 11 Pro / Ryzen 5 7600 / GeForce RTX 5080 (driver 32.0.16.1074) / 32 GB DDR5-5600Prologue at about 27-28 fps in Performance mode on the testing branch (about 10 fps on 3 Oct); Fidelity and RT modes only a few fpsReport
Windows 11 Pro / Ryzen 5 7600 / RTX 5080, current main plus open fixesFirst start screens at about 29 fps, then stops about 2 minutes inReport
Windows 11 / Core i9-13900K / RTX 4090, gtav-next branchReaches Story Mode, then stops about 30 seconds in on every runReport