- Top Pick: ASUS Prime GeForce RTX 5070 Ti 16GB
- Runner-up: ASUS Prime GeForce RTX 5060 Ti 16GB
- Also consider: Sapphire PULSE Radeon RX 9070 XT 16GB
Ray tracing is the feature Linux gamers ask about most and get the vaguest answers on. The settings menu in a Windows game running through Proton will happily offer ray-traced reflections or global illumination, and sometimes it even works well. Whether it works, and how much it costs you, depends less on the game than on which company’s GPU is in your machine and which driver stack drives it.
This article is a status map, not a benchmark chart. It walks the path a ray tracing call takes on Linux, then goes vendor by vendor — NVIDIA’s proprietary driver, AMD’s RADV driver inside Mesa, and Intel’s ANV driver — using only what those projects document about their own support. Where support is experimental or partial, the map says so plainly.
As an Amazon Associate, we earn from qualifying purchases.
Quick answer
Yes, ray tracing works on Linux today. Windows games send their DirectX ray tracing calls through VKD3D-Proton, which translates them to Vulkan ray tracing extensions that all three vendors’ drivers now expose. NVIDIA’s proprietary driver is the most complete path, AMD’s RADV is fully functional on RDNA 2 and newer with the widest maturity gap behind it, and Intel’s ANV covers Arc cards with current Mesa.
How a ray-traced frame travels on Linux
Almost no ray-traced game you play on Linux was written for Linux. The game issues DirectX 12 ray tracing calls, known as DXR, expecting a Windows driver. VKD3D-Proton, the translation layer inside Proton, converts those calls into Vulkan ray tracing operations — building acceleration structures, dispatching ray queries and pipelines — and hands them to your Vulkan driver. The driver then talks to the RT hardware on the card: RT cores on NVIDIA, ray accelerators on AMD, and the ray tracing units on Intel Arc.
Two consequences follow. First, the Vulkan extensions are the contract: a driver that exposes the standard ray tracing and ray query extensions gets working DXR games, and a driver that does not, does not. Second, every layer can add its own quirks. A game can be fine on one vendor’s driver and broken on another’s with the same Proton build, because the translation is shared but the driver underneath is not. That is why per-vendor status, not a single yes or no, is the honest answer.
The status map, vendor by vendor
NVIDIA: the proprietary driver is the reference path
NVIDIA’s proprietary driver carries full Vulkan ray tracing support, and has done across several driver generations, from the RTX 20 series onward. In practice it is the path against which VKD3D-Proton’s DXR support is developed and tested most heavily, and it is the only Linux route to NVIDIA’s wider feature set: DLSS upscaling and ray reconstruction both work through Proton on the proprietary driver, which matters because ray reconstruction is built specifically to clean up ray-traced images.
The open-source alternative, NVK inside Mesa, is not yet a substitute. NVK has only recently begun exposing ray tracing support in Mesa and it remains experimental; the project’s own positioning is that gaming workloads belong on the proprietary driver for now. If ray tracing is a reason you are buying a card, the NVIDIA entry in this map reads: supported, mature, and tied to the closed driver.
AMD: RADV is functional, younger, and still closing gaps
AMD’s Vulkan driver for gaming on Linux is RADV, developed inside Mesa. RADV exposes Vulkan ray tracing on RDNA 2 and newer hardware; support was switched on by default in Mesa 23.2, and every Mesa release since has carried documented ray tracing fixes and performance work. RDNA 4 cards arrived with substantially stronger ray tracing hardware than earlier Radeon generations, with RADV support in current Mesa from their launch window.
The honest caveats are about maturity rather than existence. RADV’s ray tracing implementation is younger than NVIDIA’s, individual titles occasionally need per-game workarounds tracked on ProtonDB, and the open AMDVLK driver that once offered an alternative path has been discontinued by AMD in favour of the Mesa stack — so RADV is the only AMD route. For hybrid ray tracing in mainstream titles, the documented state is: works, improves every Mesa cycle, and rewards staying on a current release.
Intel: ANV covers Arc, with the smallest library of titles behind it
Intel’s ANV Vulkan driver in Mesa exposes ray tracing for Arc discrete cards, covering both the Alchemist generation and the newer Battlemage generation in current Mesa releases. The plumbing is genuinely there: the same Vulkan extensions, the same VKD3D-Proton translation, the same settings menus lighting up.
What Intel lacks is not support but mileage. Fewer ray-traced titles have been shaken down on ANV than on the other two stacks, and Intel’s own documentation frames Arc on Linux as a moving target that improves driver release by driver release. Treat Arc ray tracing as functional and improving, and check your specific game’s reports before counting on it.
Driver versions: what actually changed
Three version facts explain most forum-thread confusion. The first is Mesa 23.2, which turned RADV ray tracing on by default instead of hiding it behind an environment variable; anything older makes AMD ray tracing look broken, and pre-23.2 advice still circulates. The second is that NVIDIA’s support predates the Vulkan extensions becoming standard — its driver shipped ray tracing early and kept it, so NVIDIA threads rarely mention versions. The third is that current Mesa matters most for AMD and Intel owners: ray tracing fixes land in Mesa point releases, and a distribution that freezes Mesa for a year freezes your ray tracing with it. Rolling distributions and gaming images that track Mesa closely are the friendly choice on the open stacks.
Hybrid ray tracing versus path tracing: setting expectations
Most ray tracing in real games is hybrid: a conventionally rendered frame with ray-traced reflections, shadows, ambient occlusion, or global illumination layered onto parts of it. That is the workload all three vendors’ Linux stacks are built and tested around, and on a mid-range or better RT-capable card it is reasonable to enable on Linux today.
Path tracing is a different animal. A small number of flagship titles offer a fully path-traced mode that replaces most of the lighting pipeline with rays, and it is punishing on every platform, Windows included. On Linux it additionally sits at the sharp end of driver maturity. The realistic reading: hybrid ray tracing is a normal feature to use, path tracing is a showcase mode for top-tier NVIDIA hardware, and on AMD and Intel cards it belongs in the try-it-and-see category regardless of operating system.
The cards behind this map
ASUS Prime GeForce RTX 5070 Ti 16GB
The upper-tier NVIDIA option: Blackwell RT hardware with the full proprietary-driver feature set, including ray reconstruction through Proton, and memory headroom for path-traced modes at high resolutions.
- GPU: NVIDIA GeForce RTX 5070 Ti (Blackwell)
- Memory: 16GB GDDR7, 256-bit
- Interface: PCIe 5.0
- Model: PRIME-RTX5070TI-16G
ASUS Prime GeForce RTX 5060 Ti 16GB
The mainstream NVIDIA entry: the same driver story and DLSS support as the tier above, aimed at hybrid ray tracing at 1080p and 1440p rather than showcase modes.
- GPU: NVIDIA GeForce RTX 5060 Ti (Blackwell)
- Memory: 16GB GDDR7, 128-bit
- Interface: PCIe 5.0
- Model: PRIME-RTX5060TI-16G
Sapphire PULSE Radeon RX 9070 XT 16GB
The AMD flagship of this map: RDNA 4 brought AMD’s strongest ray tracing hardware yet, and paired with a current Mesa it is the Radeon to judge RADV by.
- GPU: AMD Radeon RX 9070 XT (RDNA 4)
- Memory: 16GB GDDR6, 256-bit
- Interface: PCIe 5.0
- Model: 11348-03-20G
XFX Swift Radeon RX 9060 XT 16GB
The mid-range RDNA 4 card: the same RADV ray tracing support as the XT above in a smaller package, with the full 16GB memory configuration ray-traced titles appreciate.
- GPU: AMD Radeon RX 9060 XT (RDNA 4)
- Memory: 16GB GDDR6, 128-bit
- Interface: PCIe 5.0
- Model: RX-96TS316B7
Intel Arc B580 Limited Edition
The budget door into ray tracing: Battlemage hardware with real RT units and ANV support in current Mesa, best matched to modest settings and resolutions.
- GPU: Intel Arc B580 (Battlemage)
- Memory: 12GB GDDR6, 192-bit
- Interface: PCIe 4.0
- Model: Intel Limited Edition reference design
How to choose: GPU class by ray tracing ambition
Match the card to the mode, not the marketing. If you want to tick the ray tracing box in mainstream games at 1080p or 1440p, every card on this page clears the bar on its vendor’s current driver, and the deciding factors become the rest of your Linux experience — driver maintenance style, upscaling support, and how current your distribution keeps Mesa. If you want high-refresh ray tracing or the path-traced showcase modes, the map narrows fast: top-tier NVIDIA hardware on the proprietary driver is the only combination whose Linux support story is both complete and battle-tested, and DLSS with ray reconstruction is a practical part of that, not a bonus. Buying AMD or Intel for other reasons — the open stack, the value — argue for the newest generation you can, since RT hardware and its Mesa support both improve generation over generation.
Who should skip this
Skip ray tracing entirely if your card predates RT hardware — GTX-era NVIDIA cards, pre-RDNA 2 Radeons, and integrated graphics have no path here, and no driver update changes that. Skip it if you play competitive titles where you would turn the settings off anyway. And skip the question if your library is older or indie games: most never issue a single DXR call, and your driver stack’s ray tracing state will never come up.
FAQ
Does ray tracing work in Proton games, or only native Linux titles?
Proton games are the main case. VKD3D-Proton translates DXR calls into Vulkan ray tracing, so Windows titles are where Linux ray tracing actually gets used; the small number of native Vulkan titles with ray tracing use the same driver extensions directly.
Why does the same game ray-trace fine on NVIDIA but struggle on my Radeon?
Because the translation layer is shared but the drivers are not. NVIDIA’s proprietary driver has the longest Vulkan ray tracing history, while RADV’s implementation is younger and still receives per-title fixes in new Mesa releases. Updating Mesa is the first move; checking the game’s ProtonDB reports for RADV-specific notes is the second.
Do I need a special Proton version for ray tracing?
No separate build is required: current Proton releases carry the VKD3D-Proton support. What matters is that your driver exposes the Vulkan ray tracing extensions — a current NVIDIA proprietary driver, or current Mesa for AMD and Intel.
Is the Steam Deck a ray tracing machine?
Technically the hardware supports it through RADV, and a few lightweight titles expose the settings. Practically, a handheld power budget and ray tracing are poor partners; treat it as a curiosity rather than a feature to plan around.
Final verdict
Ray tracing on Linux is real, shipped, and usable — with a vendor-shaped asterisk. NVIDIA’s proprietary driver offers the complete, mature version today. AMD’s RADV offers the genuinely functional open-stack version, best on RDNA 4 and current Mesa, still sanding down per-game rough edges. Intel’s ANV offers the promising newcomer version on Arc. Choose by which of those sentences you are happiest living with, keep your drivers current, and the settings menu will mostly take care of itself.











