{"slug": "witcher-3-linux-ray-tracing-fix-md", "title": "witcher-3-linux-ray-tracing-fix.md", "summary": "A developer documented a fix for ray tracing, path tracing, DLSS and frame generation in The Witcher 3: Wild Hunt version 5.0 under Proton on Linux, tracing the failures to a deliberate Wine-detection check in the game plus two vkd3d-proton bugs. One bug, tight 256-byte buffer alignment, was fixed in vkd3d-proton PR #3308, while a second bug that under-reported acceleration structure sizes on NVIDIA by up to about 5× and caused GPU hangs (Xid 109, VK_ERROR_DEVICE_LOST) was fixed in PR #3332. The workaround requires GE-Proton, vkd3d-proton built from master, and a protonfixes local fix that hides Wine from the game.", "body_md": "*Authored by: Claude Opus 5.5*\n\nThis guide makes ray tracing work in *The Witcher 3: Wild Hunt* under Proton. It also brings back path tracing, DLSS, and frame generation. It covers version 5.0 of the game, the \"Remastered\" update released on 2026-09-29. It was written on 2026-09-30. I tested the fixes on NixOS with an NVIDIA RTX 3080 Ti, using my own build of the same vkd3d-proton commit. The Debian commands below follow the same steps, but I have not run them as written.\n\nThe steps assume a common distribution, such as Debian or Ubuntu, with Steam installed from the distribution's package. Paths for the Flatpak version of Steam differ, and I have not tested it.\n\nIn version 5.0, ray tracing does not work on Linux, whatever the GPU or driver:\n\n- You can switch ray tracing on in the graphics menu, and the game accepts it.\n- Nothing changes on screen.\n- When you open the menu again, ray tracing is back to off.\n- Path tracing, DLSS, and frame generation are missing or greyed out too. Geralt's hair may render wrong, because HairWorks uses the same path.\n\nVersion 4.0, the \"next-gen\" update from 2022, failed differently. The game froze the moment you switched ray tracing on. It stopped responding to input, and only `kill` could end it.\n\nTwo separate faults are at work. Both hit every Linux setup.\n\nAt start, version 5.0 looks up the function `wine_get_version` in `ntdll.dll`. Only Wine has that function, so finding it means \"running under Wine\". The game then does five things:\n\n- it marks ray tracing and DXR 1.1 as unsupported, whatever the GPU reports;\n- it skips the path tracing shaders;\n- it skips NVIDIA Streamline, so DLSS, Ray Reconstruction, DLSS Frame Generation, and Reflex become unavailable;\n- it marks FSR frame generation as unsupported;\n- it skips a request for 256-byte buffer alignment.\n\nThis is a deliberate check in the game. It is not a driver or hardware limit. It explains why the menu setting goes back to off. The same check also fires on Steam hardware, such as the Steam Deck.\n\ngabrielmaialva33 found this by static analysis of the game's executable, and confirmed it with a local test. The details are in [Proton issue #607](https://github.com/ValveSoftware/Proton/issues/607), in a comment from 2026-09-29.\n\nvkd3d-proton is the part of Proton that translates DirectX 12 to Vulkan. It had two bugs that this game hits:\n\n- **Tight buffer alignment.** With Wine hidden, the game asks for 256-byte buffer alignment. Older vkd3d-proton does not handle that, and the game crashes at start with`Invalid alignment 256 for buffer resource` .[PR #3308](https://github.com/HansKristian-Work/vkd3d-proton/pull/3308) fixed it, merged on 2026-09-21.\n- **Wrong acceleration structure sizes.** The game queries acceleration structure sizes without a required flag. vkd3d-proton has a workaround for that, but on NVIDIA it under-reported the sizes by up to about 5×. The game's builds then overflowed into nearby memory, and the GPU hung (`Xid 109` ,`VK_ERROR_DEVICE_LOST` ) within about a minute.[PR #3332](https://github.com/HansKristian-Work/vkd3d-proton/pull/3332) by Stanni97 fixed it, merged on 2026-09-30. The tracking issue is[vkd3d-proton #3226](https://github.com/HansKristian-Work/vkd3d-proton/issues/3226) .\n\nThe second bug is behind the freeze in version 4.0. It also explains why hiding Wine alone is not enough: the game then crashes or hangs.\n\nBoth fixes are in vkd3d-proton master. As of 2026-09-30, no vkd3d-proton release and no Proton release includes them.\n\nYou need three things:\n\n1. GE-Proton, because it can hide Wine and Valve's Proton cannot.\n2. vkd3d-proton from master, placed inside a copy of GE-Proton.\n3. A protonfixes local fix that hides Wine from this one game.\n\nThe copy of GE-Proton gets its own name. Only The Witcher 3 uses it, so your other games keep stock GE-Proton.\n\nDownload [`GE-Proton11-7-x86_64.tar.gz`](https://github.com/GloriousEggroll/proton-ge-custom/releases/download/GE-Proton11-7/GE-Proton11-7-x86_64.tar.gz) from the GE-Proton releases page. Then unpack it under a new name, and rename the tool inside its description file:\n\n```\nmkdir -p ~/.steam/steam/compatibilitytools.d\ncd ~/.steam/steam/compatibilitytools.d\nmkdir unpack\ntar -C unpack -xf ~/Downloads/GE-Proton11-7-x86_64.tar.gz\nmv unpack/* GE-Proton11-7-witcher3\nrmdir unpack\nsed -i 's/GE-Proton11-7[^\"]*/GE-Proton11-7-witcher3/g' GE-Proton11-7-witcher3/compatibilitytool.vdf\n```\n\nThe rename matters. Steam identifies each tool by the name in `compatibilitytool.vdf`. Without the rename, Steam treats this copy and a stock GE-Proton11-7 as the same tool.\n\nvkd3d-proton's own CI builds every commit. The build of commit [`44cf7c20`](https://github.com/HansKristian-Work/vkd3d-proton/commit/44cf7c2042168f3b8ee37249f0a53ac091e48fd9) has both fixes, plus a follow-up to #3332.\n\n1. \nOpen the [CI run for that commit](https://github.com/HansKristian-Work/vkd3d-proton/actions/runs/36730655724) . You need to be signed in to GitHub to download.\n2. \nDownload the artifact `vkd3d-proton-master-44cf7c2042168f3b8ee37249f0a53ac091e48fd9` . GitHub deletes it on 2026-12-29.\n3. \nUnpack it into `~/Downloads` , and copy the two 64-bit DLLs into the copy of GE-Proton:\n\n```\ncd ~/Downloads/vkd3d-proton-master-44cf7c2042168f3b8ee37249f0a53ac091e48fd9\ncp x64/d3d12.dll x64/d3d12core.dll \\\n  ~/.steam/steam/compatibilitytools.d/GE-Proton11-7-witcher3/files/lib/wine/vkd3d-proton/x86_64-windows/\n```\n\nThe game is 64-bit only, so the 32-bit DLLs can stay as they are.\n\nIf the artifact has expired, build vkd3d-proton yourself. Its [README](https://github.com/HansKristian-Work/vkd3d-proton#building-vkd3d-proton) lists the tools needed and has a one-line build script.\n\nGE-Proton runs [protonfixes](https://github.com/Open-Wine-Components/umu-protonfixes) before each launch. protonfixes also runs any \"local fix\" it finds in `~/.config/protonfixes/localfixes/`, named after the game's Steam app ID. The Witcher 3's ID is 292030.\n\nCreate the local fix:\n\n```\nmkdir -p ~/.config/protonfixes/localfixes\ncat > ~/.config/protonfixes/localfixes/292030.py <<'EOF'\nr\"\"\"Game fix for The Witcher 3: Wild Hunt.\n\nHides Wine from the game, which otherwise turns off ray tracing,\npath tracing, DLSS, and frame generation.\n\"\"\"\n\nfrom protonfixes import util\n\ndef main() -> None:\n    \"\"\"Turn on HideWineExports in the game's prefix.\"\"\"\n    util.protontricks(\"hidewineexports=enable\")\nEOF\n```\n\nThe fix runs winetricks, which sets `HKCU\\Software\\Wine\\HideWineExports` to `Y` in the game's prefix. That is a wine-staging setting, and GE-Proton includes wine-staging. winetricks records that it ran, so later launches skip it.\n\n1. Restart Steam.\n2. Open the game's Properties, then Compatibility.\n3. Tick \"Force the use of a specific Steam Play compatibility tool\", and pick `GE-Proton11-7-witcher3` .\n4. Start the game while online. protonfixes skips winetricks when it finds no internet connection.\n5. Switch ray tracing on, leave the menu, and open it again. The setting should stay on.\n\nTo check that the fix ran, set the game's launch options to `PROTON_LOG=1 %command%`. Proton then writes `~/steam-292030.log`. On the first launch, it should hold the line `Using winetricks verb \"hidewineexports=enable\"`. Remove the launch option afterwards.\n\nTo check that the game uses the new vkd3d-proton, compare the DLL in the game's prefix with the one in the tool. After one launch, run:\n\n```\ncmp ~/.steam/steam/steamapps/compatdata/292030/pfx/drive_c/windows/system32/d3d12core.dll \\\n  ~/.steam/steam/compatibilitytools.d/GE-Proton11-7-witcher3/files/lib/wine/vkd3d-proton/x86_64-windows/d3d12core.dll\n```\n\nNo output means the files match. If the game is installed in another Steam library, use that library's `steamapps` folder.\n\n- **AMD GPUs:** with ray tracing on, RADV has crashed while it creates the ray tracing pipelines ([Mesa #16450](https://gitlab.freedesktop.org/mesa/mesa/-/issues/16450) ). This guide was tested on NVIDIA only.\n- **Steam Deck:** the game's check also asks Steam whether it runs on Steam hardware. Hiding Wine does not change that answer, so the check may still fire on a Steam Deck. gabrielmaialva33's[patch script](https://gist.github.com/gabrielmaialva33/33ebb2542f0513d55100b22aa2149ff5) patches the check out of the executable instead. Steam's \"Verify integrity\" and every game update undo that patch.\n- **Game updates:** a new version of the game may move or change its checks.\n\nOnce a GE-Proton release ships vkd3d-proton from 2026-09-30 or later, you no longer need steps 1 and 2. GE-Proton release notes usually say which vkd3d-proton each release ships. Then:\n\n1. Install that GE-Proton release the normal way.\n2. Select it for The Witcher 3 in place of `GE-Proton11-7-witcher3` .\n3. Delete `~/.steam/steam/compatibilitytools.d/GE-Proton11-7-witcher3` .\n4. Keep step 3, the local fix. It stays needed until one of the following happens:\n  - the game stops checking for Wine;\n  - protonfixes adds a fix for app 292030 itself. Other games' fixes there already use `hidewineexports=enable` ;\n  - Proton hides Wine from this game by itself.\n\nValve's own Proton will not do this soon. Valve's [vkd3d-proton PR #3333](https://github.com/HansKristian-Work/vkd3d-proton/pull/3333), still open, would hide Wine from this game but report no ray tracing support. With it, DLSS would work under Valve's Proton, but ray tracing would stay off.", "url": "https://wpnews.pro/news/witcher-3-linux-ray-tracing-fix-md", "canonical_source": "https://gist.github.com/larry0x/72815ee92019f05146cc8cf0f032cf0b", "published_at": "2026-09-30 18:39:46+00:00", "updated_at": "2026-10-03 10:36:43.352497+00:00", "lang": "en", "topics": ["ai-tools"], "entities": ["The Witcher 3: Wild Hunt", "Proton", "vkd3d-proton", "NVIDIA", "Valve", "GE-Proton", "NixOS", "Steam Deck"], "also_reported_by": [], "takeaway": "Hiding Wine via GE-Proton plus vkd3d-proton master (PR #3308 for 256-byte buffer alignment and PR #3332 for acceleration structure sizes under-reported by up to 5× on NVIDIA) restores ray tracing, path tracing, DLSS and frame generation in The Witcher 3 v5.0 on Linux.", "recommendation": null, "alternates": {"html": "https://wpnews.pro/news/witcher-3-linux-ray-tracing-fix-md", "markdown": "https://wpnews.pro/news/witcher-3-linux-ray-tracing-fix-md.md", "text": "https://wpnews.pro/news/witcher-3-linux-ray-tracing-fix-md.txt", "jsonld": "https://wpnews.pro/news/witcher-3-linux-ray-tracing-fix-md.jsonld"}}