LeonidaPC.wiki Status Board

Leonida System Requirements

Leonida has no official minimum or recommended specs. The game does not boot yet, so nobody has measured what it needs to play. What is known is what the build needs, and how the project plans to make the console's graphics work on PC cards from AMD, NVIDIA and Intel.

This page separates the two: facts you can rely on today, and the parts that are still open.

Official specsNone published
Graphics APIVulkan
Disk for a buildAbout 350 GB
Frame rate dataNone exists
Illustration of an open desktop PC tower with a graphics card next to a monitor showing code
The graphics card is the hard part
Advertisement

Graphics Card Check

Pick your family of card to see how the build handles it. Everything shown comes from the project's own notes.

This only tells you how the build treats that family of cards. It cannot detect your hardware and it is not a performance estimate. Nobody has frame rates, because the game does not run.

How the 64-wide shaders are handled

Can run the console's 64-wide shaders natively when the driver reports 64-wide subgroups. The project's own check ran on a Radeon 880M that does.

Extra fallback switches

None expected on a card with mesh shaders and barycentrics.

What has actually been checked

Automatic mode only switches emulation off when every GPU in the PC reports 64-wide subgroups, and when the card can run both compute and mesh shaders that way.

Taken from the project README and design notes on November 22, 2026.

What the Build Needs Today

PartWhat the project asks for
Operating systemWindows 10 or 11, 64-bit. The scripts also run on Linux
DiskAbout 350 GB free for work files, on any drive
GraphicsA card with a Vulkan driver. Recent features help, older cards use fallbacks
ProcessorNo number given. Shader translation uses half your threads by default
MemoryNo number given
ToolsPython 3.12, .NET 8 SDK, Vulkan SDK, LLVM 21 with the AMDGPU target, Visual Studio 2022
The gameYour own copy of the Xbox Series package, version 1.0.2.1

From the README on November 22, 2026. The step by step version is on the build page.

What Nobody Knows Yet

  • Frame rates. The game has not started, so there is nothing to measure.
  • Memory use. No figure has been published for system or graphics memory.
  • Which cards will be fast enough. Being able to create a shader is not the same as running the game well.
  • Ray tracing. The project notes that some ray tracing shaders took minutes each just to compile.

If a site lists "GTA 6 PC requirements for Leonida" with exact cards and frame rates, it is guessing.

From Console Shaders to Vulkan

On a PC, a game normally ships its shaders in a portable form and your driver compiles them for your card. A console game does not need to. The Xbox Series has one graphics chip, an AMD design from the RDNA 2 family, so the game ships shaders already compiled into that chip's machine code.

That is the core problem for a PC port. A GeForce or Intel card cannot run AMD machine code, and even a Radeon card on PC does not accept it directly. Leonida's answer is a translator:

  1. Carve. Pull each compiled shader out of the game's shader archive.
  2. Disassemble. Turn the machine code back into readable instructions with LLVM.
  3. Translate. Rewrite those instructions as SPIR-V, the format Vulkan drivers accept.
  4. Validate and build. Check every result, then create it once on your card and save a cache.

All 26,503 shaders in the game go through this: 12,101 pixel shaders, 9,282 mesh shaders, 2,689 compute shaders, 2,236 vertex shaders and 195 geometry shaders.

Illustration of coloured blocks flowing through a translation pipeline on a laptop screen
Carve, disassemble, translate, validate

Wave64 vs Wave32, in Plain Words

A graphics chip runs a shader on many pixels or vertices at once. Each one is a lane, and a group of lanes that run together is a wave. The console's chip can run waves of 64 lanes. NVIDIA and Intel cards work with groups of 32.

For most shaders the width does not matter. It matters when lanes in the same wave share information: one lane reads a value from another, or the whole wave votes on which branch to take. Many of the game's compute and mesh shaders do this and assume 64 lanes.

On a 32-wide card, one console wave is split across two groups that cannot see each other. Leonida's wave64 emulation fixes that by passing the shared values through a small buffer and running the shader in rounds, so both halves stay in step.

How Each Card Family Is Handled

CardsGroup width64-wide shaders
AMD Radeon reporting 64-wide groups64Run as they are
NVIDIA GeForce32Emulation, switched on automatically
Intel32Emulation, switched on automatically
Cards without mesh shadersVariesMesh shaders are run as compute instead

The default setting asks your Vulkan driver what it supports and decides for you. It chooses emulation whenever it cannot be sure.

The project checked emulation on a GeForce RTX 5070 Laptop (32-wide) and a Radeon 880M (64-wide) and got the same results on both.

Advertisement

Vulkan Features the Shaders Ask For

FeatureIf your card lacks it
Mesh shadersA switch runs them as compute shaders
Fragment shader barycentricsA switch feeds the same values through an ordinary input
The maintenance8 extensionA switch folds texture offsets into the coordinates
A float precision guarantee some shaders declareA switch drops the declaration

The design notes give the GeForce GTX 10 series as an example of cards that lack mesh shaders and barycentrics. A fallback means the shaders can be created. It says nothing about speed.

The One Full Run We Can Quote

The project built the entire shader set into real Vulkan pipelines on a GeForce RTX 4060 Ti. All 26,503 were accepted by the driver with no failures.

  • Wall time: about 2.8 hours on four threads.
  • Slowest group: compute shaders, with some ray tracing shaders taking 2 to 19 minutes each.
  • Resulting cache: about 3.8 GB, reused on later runs so they start fast.

This proves the driver accepts the translated shaders. It does not prove they draw the right picture, and the project says so itself.

From the design notes, November 22, 2026. See the status page for what else is done.

Hardware That Helps With Big Builds

Disclosure: As an Amazon Associate we earn from qualifying purchases made through the hardware links on this page at no extra cost to you.

Internal NVMe SSDs, 1 TB and Up

The build asks for about 350 GB of free space for work files alone. A spare fast drive keeps it off your system disk.

See NVMe SSDs on Amazon

Graphics Cards With Mesh Shaders

The game's shaders lean on mesh shaders and other recent Vulkan features. The project's own full shader build ran on a GeForce RTX 4060 Ti.

See graphics cards on Amazon

PC Game Controllers

The runtime reads controllers through SDL3, which covers most modern pads. Useful for the PC games you can play today.

See PC controllers on Amazon

Leonida Requirements: Common Questions

What are the Leonida system requirements?

There are no official minimum or recommended specs, because the game does not run yet. What the project does publish is what the build needs: Windows 10 or 11 64-bit, about 350 GB of free disk space, a set of developer tools, and a graphics card with a Vulkan driver.

Will Leonida work on an NVIDIA graphics card?

The shader side is being built for it. NVIDIA cards process shader lanes in groups of 32, while many of the console's compute and mesh shaders expect 64. The build has an emulation mode for that and turns it on automatically. The project created all 26,503 translated shaders as pipelines on an RTX 4060 Ti with no failures.

What is wave64 and why does it matter?

The console's AMD graphics chip can run a shader across 64 lanes at once, called a wave. Some of the game's shaders rely on lanes talking to each other inside that wave. A card that works 32 lanes at a time needs those shaders rewritten so the two halves still agree, which is what wave64 emulation does.

Do I need an AMD card to run Leonida?

No. An AMD card whose driver reports 64-wide subgroups can run those shaders without emulation, but the build supports 32-wide cards from NVIDIA and Intel through emulation. Nobody can compare speed yet.

How much disk space and time does the shader step take?

The README asks for about 350 GB of free space for work files. In the project's own run on an RTX 4060 Ti, creating every shader pipeline took about 2.8 hours on four threads and produced a cache of about 3.8 GB.

What frame rate will GTA 6 get on PC through Leonida?

Nobody knows. The game has not booted, so there are no measurements. Any chart or video showing frame rates for a specific card is made up.