KYTYPS5 / GAME COMPATIBILITY

Grand Theft Auto V (PlayStation®5)

PPSA03420 · 3 platform reports

Check the result for your operating system, then compare your build and game version with the test.

Windows

In game

Tested 6 Oct 2026
Read the Windows report

Linux

In game

Tested 24 Sept 2026
Read the Linux report

macOS

Doesn’t boot

Tested 7 Oct 2026
Read the macOS report

Imported from the project’s published compatibility database on . Report dates, builds and hardware remain those of the original community tests.

LINUX TEST

Grand Theft Auto V (PlayStation®5) on Linux

In game
Tested build
KytyPS5-2026-09-24-2aaf0c9
Test date
Tested title ID
PPSA04264
Game version
Not recorded
Test hardware
AMD Ryzen 5 5600 / AMD Radeon RX 9070 XT, Mesa 26.2.2 (RADV GFX1201), Vulkan 1.4.354 / 16GB DDR4 RAM / 16GB VRAM

Community report notes

Replaces #229 (@DistantMyth, as requested). It also collects the earlier GTA V reports, listed at the bottom.

The game has three graphics modes (Settings, Display, Graphics mode). Results on Linux, a few minutes of play per mode:

ModeResult
PerformanceStarts and is playable. Visuals look correct apart from the glyph problem below, audio is fine, but the game is pretty laggy.
Performance RTStarts and is playable, with visual glitches: characters are drawn as black silhouettes and lights shimmer. Audio is fine, and the game is pretty laggy.
FidelityStory mode does not load. Some dialog is audible until it crashes (details below).

Fidelity mode: story mode does not load. Every crashing run I did was in Fidelity mode. The maintainers said on #315 that Fidelity mode uses ray tracing, which is not supported (comment). The two builds fail differently:

Latest release (2026-09-24-2aaf0c9): the log shows the game reading the prologue audio (PROLOGUE.rpf), then the emulator exits with: TextureCache: invalid depth upload (textureCache.cpp:1081) That check rejects a depth image that is multisampled, has zero layers or a size that is not a multiple of its layer count, or whose format size does not match; the release message does not say which. I did not see the descriptor error below on this build. The full _kyty.txt is attached.

Official 2026-09-20 release (ba55ba5) and local builds:

  1. On the official 2026-09-20 release, starting story mode plays the intro dialog and the "Ludendorff, North Yankton, nine years ago" text on a black screen, then exits with:

shader resource tracking: hash=0x6a53456e7ef5d1b0 stage=compute pc=0x0000086c GetBufferResource dword 0 is not a valid runtime value Same class as #507 and #548 (their hash is 0x5e3e42fe237d3e16). With a diagnostic build I traced the descriptor's base address to Ballot -> CompositeExtractU32x4 -> ... -> ReadFirstLane -> ReadConstBuffer, i.e. a per-lane value that cannot be resolved on the CPU.

  1. With #690 (dynamic buffer descriptors) merged on top, that error is gone. The next failure was a missing DS opcode (0xa0, DS_WRITE_B8_D16_HI), now upstream through #794.
  2. After that, the run ends in a GPU hang: vkQueueSubmit failed: ErrorDeviceLost, kernel ring gfx_0.0.0 timeout, no page fault. RADV_DEBUG=hang,syncshaders pins it on a single compute dispatch: shader hash 0xa016c19e423c6efb (64-thread groups, 27x1x1 or 3x1x1). It reproduces with the GPU at stock clocks (I reset an undervolt and memory overclock to rule that out), and the shader's SPIR-V matches the emulator's. The kernel looks like tree/BVH traversal (atomics, wave-wide prefix sums, data-dependent loops), which fits a ray-tracing acceleration-structure path.
  3. In Performance mode neither of those two shaders is dispatched: on a local build with #690 and #794, a session of about 3 minutes ran 226,925 compute dispatches across 34 compute shaders with no errors or hangs. I did not capture a log for Performance RT.

Glyph problem (all modes). The game has a glyph problem: the controller-button icons in on-screen hints are drawn as plain boxes (the second screenshot, the first-person camera hint). It looks like the same class of problem as the missing letters reported in #166 and #729, and the boot-time text glyph loss PR #449 tried to fix.

Steps to reproduce

  1. Start the KytyPS5 launcher and add the folder that contains the game (PPSA04264) under the global settings' game folders. Select Grand Theft Auto V in the game list and run it.
  2. At the game's main menu, open Settings, Display, Graphics mode, and choose the mode to test: Fidelity, Performance RT or Performance.
  3. Start Story Mode.
  4. Result:
  • Performance and Performance RT reach the prologue and are playable (Performance RT with black characters and shimmering lights).
  • Fidelity exits during the story-mode load with the errors described in Result details.

To capture a log, set "Printf output" to File in the launcher's global settings before starting the game.

Expected behavior

  • Performance: Story mode loads and plays without heavy lag, and on-screen button icons render as icons (currently the game is pretty laggy and the icons are plain boxes).
  • Performance RT: characters and lighting render like in Performance mode (currently characters are black silhouettes and lights shimmer).
  • Fidelity: Story mode loads and reaches the prologue like the other modes. Ray tracing is not supported yet (see #315), so this may need that work first.

Extra notes

Settings used: 1280x720, Mailbox present mode, vblank 60, shader optimization Performance, shader validation on, GPU Auto, AMD CPU patch off, tessellation off. The game is pretty laggy at 1280x720 on this hardware; I did not measure frame rates.

Related issues and pull requests (GTA V):

  • Reports: #166 (closed, older story-mode crash), #229 (replaced by this issue), #507 (descriptor-tracking design, documents the same GTA V chain), #548 (same descriptor error, EUR release PPSA04263 v01.010.002), #729 (Windows/NVIDIA: missing text glyphs, prologue cutscene crash when frames drop)
  • Fixes for the Fidelity path or shared code: #690 (open, dynamic buffer descriptors, clears the descriptor error on the 2026-09-20 release), #794 (merged, DS_WRITE_B8_D16_HI), #795 (open, GPU tiler shaders: avoids a uvec4 specialization-constant select that RADV evaluates wrongly, found while testing this)

Earlier GTA V bring-up PRs (merged / open / closed)

  • Merged: #315 (Standard64KB colour-target arrays), #404 (V_PK_FMAC_F16 high half), #428 (fast clear from a read-modify-write dispatch), #436 (R32_SFLOAT packed colour clears), #437 (DualSense HIDAPI / light bar), #511 (refresh imports after dynamic module loads), #645 (Nix flake)
  • Open: #431 (border colours from the guest table), #532 (finalize bindings after every range-changing operation)
  • Closed without merging: #401 (HTile fast clears), #419, #422, #433, #435, #534 (streaming-time page-fault retries), #434 and #557 (save metadata / timestamps), #440 (DCC clears before sampled access), #449 (boot-time text glyph loss), #464 (vertex buffer size)

Not resolved by anything above: missing text glyphs (#166, #729), the streaming-time fault race, and the prologue cutscene crash (#729).

KytyPS5 issue #810 · Original community test.

MACOS TEST

Grand Theft Auto V (PlayStation®5) on macOS

Doesn’t boot
Tested build
KytyPS5-2026-10-07-bb98f26-macOS-x86_64
Test date
Tested title ID
PPSA04263
Game version
Not recorded
Test hardware
Apple Silicon M4 / Apple Silicon M4 / Unified 16GB

Community report notes

Using kyty_emulator : Initialized: Config Initialized: Log Initialized: Timer Initialized: Pthread Initialized: Profiler Initialized: Network Initialized: Memory Initialized: FileSystem Initialized: Controller Initialized: Audio [mvk-info] MoltenVK version 1.4.2, supporting Vulkan version 1.4.357. The following 154 Vulkan extensions are supported: VK_KHR_16bit_storage v1 VK_KHR_8bit_storage v1 VK_KHR_bind_memory2 v1 VK_KHR_buffer_device_address v1 VK_KHR_calibrated_timestamps v1 VK_KHR_copy_commands2 v1 VK_KHR_create_renderpass2 v1 VK_KHR_dedicated_allocation v3 VK_KHR_deferred_host_operations v4 VK_KHR_depth_stencil_resolve v1 VK_KHR_descriptor_update_template v1 VK_KHR_device_group v4 VK_KHR_device_group_creation v1 VK_KHR_driver_properties v1 VK_KHR_dynamic_rendering v1 VK_KHR_dynamic_rendering_local_read v1 VK_KHR_external_fence v1 VK_KHR_external_fence_capabilities v1 VK_KHR_external_memory v1 VK_KHR_external_memory_capabilities v1 VK_KHR_external_semaphore v1 VK_KHR_external_semaphore_capabilities v1 VK_KHR_format_feature_flags2 v2 VK_KHR_fragment_shader_barycentric v1 VK_KHR_get_memory_requirements2 v1 VK_KHR_get_physical_device_properties2 v2 VK_KHR_get_surface_capabilities2 v1 VK_KHR_global_priority v1 VK_KHR_image_format_list v1 VK_KHR_imageless_framebuffer v1 VK_KHR_incremental_present v2 VK_KHR_index_type_uint8 v1 VK_KHR_line_rasterization v1 VK_KHR_load_store_op_none v1 VK_KHR_maintenance1 v2 VK_KHR_maintenance2 v1 VK_KHR_maintenance3 v1 VK_KHR_maintenance4 v2 VK_KHR_maintenance5 v1 VK_KHR_maintenance6 v1 VK_KHR_maintenance7 v1 VK_KHR_maintenance8 v1 VK_KHR_maintenance9 v1 VK_KHR_map_memory2 v1 VK_KHR_multiview v1 VK_KHR_portability_subset v1 VK_KHR_present_id v1 VK_KHR_present_id2 v1 VK_KHR_present_wait v1 VK_KHR_present_wait2 v1 VK_KHR_push_descriptor v2 VK_KHR_relaxed_block_layout v1 VK_KHR_robustness2 v1 VK_KHR_sampler_mirror_clamp_to_edge v3 VK_KHR_sampler_ycbcr_conversion v14 VK_KHR_separate_depth_stencil_layouts v1 VK_KHR_shader_draw_parameters v1 VK_KHR_shader_expect_assume v1 VK_KHR_shader_float_controls v4 VK_KHR_shader_float_controls2 v1 VK_KHR_shader_float16_int8 v1 VK_KHR_shader_fma v1 VK_KHR_shader_integer_dot_product v1 VK_KHR_shader_maximal_reconvergence v1 VK_KHR_shader_non_semantic_info v1 VK_KHR_shader_quad_control v1 VK_KHR_shader_relaxed_extended_instruction v1 VK_KHR_shader_subgroup_extended_types v1 VK_KHR_shader_subgroup_rotate v2 VK_KHR_shader_subgroup_uniform_control_flow v1 VK_KHR_shader_terminate_invocation v1 VK_KHR_spirv_1_4 v1 VK_KHR_storage_buffer_storage_class v1 VK_KHR_surface v25 VK_KHR_surface_maintenance1 v1 VK_KHR_surface_protected_capabilities v1 VK_KHR_swapchain v70 VK_KHR_swapchain_maintenance1 v1 VK_KHR_swapchain_mutable_format v1 VK_KHR_synchronization2 v1 VK_KHR_timeline_semaphore v2 VK_KHR_uniform_buffer_standard_layout v1 VK_KHR_variable_pointers v1 VK_KHR_vertex_attribute_divisor v1 VK_KHR_vulkan_memory_model v3 VK_KHR_zero_initialize_workgroup_memory v1 VK_EXT_4444_formats v1 VK_EXT_buffer_device_address v2 VK_EXT_calibrated_timestamps v2 VK_EXT_debug_marker v4 VK_EXT_debug_report v10 VK_EXT_debug_utils v2 VK_EXT_depth_clip_control v1 VK_EXT_descriptor_indexing v2 VK_EXT_extended_dynamic_state v1 VK_EXT_extended_dynamic_state2 v1 VK_EXT_extended_dynamic_state3 v2 VK_EXT_external_memory_host v1 VK_EXT_external_memory_metal v1 VK_EXT_fragment_shader_interlock v1 VK_EXT_global_priority v2 VK_EXT_global_priority_query v1 VK_EXT_hdr_metadata v3 VK_EXT_headless_surface v1 VK_EXT_host_image_copy v1 VK_EXT_host_query_reset v1 VK_EXT_image_2d_view_of_3d v1 VK_EXT_image_robustness v1 VK_EXT_index_type_uint8 v1 VK_EXT_inline_uniform_block v1 VK_EXT_layer_settings v2 VK_EXT_legacy_dithering v2 VK_EXT_line_rasterization v1 VK_EXT_load_store_op_none v1 VK_EXT_memory_budget v1 VK_EXT_metal_objects v2 VK_EXT_metal_surface v1 VK_EXT_non_seamless_cube_map v1 VK_EXT_p

Steps to reproduce

  1. Open KytyPS5
  2. Boot the game

Alternative:

  1. launch the game via kyty_emulator with any argument

Expected behavior

Game booting into menu (at least) was expected

Last working build / first broken build

Never Worked

KytyPS5 issue #1133 · Original community test.

WINDOWS TEST

Grand Theft Auto V (PlayStation®5) on Windows

In game
Tested build
KytyPS5-2026-10-06-6ef4065-Windows-x64
Test date
Tested title ID
PPSA04264
Game version
Not recorded
Test hardware
Intel Core i5-13600K / Intel Arc B580 / 32 GB DDR4 RAM/ 12 GB GDDR6

Community report notes

The game runs and enters gameplay successfully, with generally good performance after initial shader stutter, but some cutscenes cause Kyty to crash.

Kyty reports:

Vulkan depth feedback support: false

Crash:

depth attachment feedback loop is not supported by the host

in D:\a\KytyPS5\KytyPS5\src\graphics\host_gpu\renderer\renderDraw.cpp:536

  • Performance mode allows the game to reach gameplay.
  • Gameplay can run smoothly before the crash.
  • The crash is reproducible during certain cutscenes.
  • The game dump was re-downloaded after an earlier corrupted archive issue, and the current copy successfully boots and reaches gameplay.
  • Latest Arc driver is installed
  • This appears to be related to depth attachment feedback loop support on Intel Arc B580 rather than general game compatibility.

Steps to reproduce

  1. Launch GTA V in KytyPS5.
  2. Set the in-game graphics mode to Performance.
  3. Start Story Mode.
  4. Play through the North Yankton prologue.
  5. Continue until a cutscene triggers the crash.

Expected behavior

The cutscene should render normally and gameplay should continue.

KytyPS5 issue #1123 · Original community test.

Compare another title.

Search all 333 games, or browse reports for your operating system.

Browse all games