Real Intel XeSS super resolution and XeSS frame generation inside Proton games, running on the GPU's XMX (matrix) units instead of the DP4a fallback that stock Wine/Proton gets. No Windows driver, no change to Proton or vkd3d-proton:
igdext64.dll, a shim built on Intel's open source dxvk-igdext, answers XeSS' driver queries like an Intel driver and hands every C-for-Metal (CM) kernel XeSS submits over as a placeholder;- a patched Mesa ANV Vulkan driver compiles those kernels with Intel's compiler (IGC) on first use and runs them in place of the placeholders, inside the normal vkd3d-proton queue.
Developed on an ONEXPLAYER 3 (Arc B390, Xe3) with SteamOS, Mesa 26.1.2 / 26.3 and GE-Proton 11-6 / Proton Experimental. Super resolution renders correctly and is temporally stable; frame generation runs at 2x/3x/4x on XMX as well (without the Intel extension, XeSS frame generation is limited to 2x).
Download the release archive, unpack it somewhere it can stay, and run:
./install.sh # once; fetches the compiler bundle (about 230 MB), then reboot or log out and in
./uninstall.sh # reverts everything
Every game started from Steam afterwards uses the patched driver, no launch options needed. In the game, select XeSS
(and XeSS frame generation) on its DX12 renderer. The first launch compiles the game's kernels, a minute or two
once; after that they come from ~/.cache/xess-xmx.
What install.sh does:
- writes
~/.config/environment.d/50-xess-xmx.conf:- the patched driver as the 64-bit Intel Vulkan driver (other GPUs' drivers and the 32-bit Intel driver stay in the list) and the kernel compiler;
VKD3D_DISABLE_EXTENSIONS=VK_EXT_descriptor_buffer, which the kernel binding code needs (it applies to every D3D12 game of the session);force_vk_vendor=0, because Mesa hides the Intel GPU from some games (see docs/debugging.md);
- puts the shim into every Proton that bundles an
igdext64.dlland into every prefix, keeping the original as.stock, and enables a watcher that repeats this after a Proton update and for a new prefix; - enables
xess-xmx-check.service: before every graphical session it checks that the patched driver loads and finds the GPU. If a system update broke it, the other driver of the package takes over; if both are broken, the session uses the stock drivers and XeSS runs as DP4a.~/.cache/xess-xmx/driver-statussays so, andtools/rebuild-driver.shrebuilds a driver for the new Mesa version.
Only the native Steam client is supported (SteamOS, distribution packages), not Flatpak Steam.
Per game instead of system-wide: XMX_APPID=<steam app id> ./enable.sh (or XMX_PREFIX=<prefix> for other
launchers) installs the shim into that prefix and writes the variables to ~/.config/xess-xmx.conf; put
/path/to/package/xmx-launch.sh %command% into the game's launch options. disable.sh undoes it.
The archive carries the patched driver for two Mesa versions; both run the same XeSS kernels:
- Mesa 26.3.0-rc1 (the default): its new shader compiler Jay, the default on Xe2 and Xe3, makes the games' own shaders much faster. Patches by @kas5852 (#19). A release candidate: tested in fewer games so far.
- Mesa 26.1.2: the driver of the earlier releases, the same version as SteamOS' own.
Choose per game in its Steam launch options:
MESA=26.1 %command% # this game uses Mesa 26.1.2
MESA=26.3 %command% # this game uses Mesa 26.3
Games without MESA use the default, which tools/switch-driver.sh lists (*) and changes
(tools/switch-driver.sh 26.1); both take effect at the next game start, no re-login. If the default driver fails the
check before a session (for example after a system update), the other one becomes the default automatically.
INTEL_DEBUG=no-jay %command% runs a game's own shaders on Mesa 26.3 with the old compiler.
- Intel Xe3 (Panther Lake; tested on an Arc B390) or Xe2 (Battlemage; tested by a contributor on an Arc B580, #16) on
the
xeori915kernel driver. Lunar Lake is untested; Xe-HPG (Alchemist) and Xe-LPG are detected but untested. - The drivers in the archive (Mesa 26.1.2 and 26.3.0-rc1 with the patches) replace the system's 64-bit ANV for the user session only. For another Mesa version see docs/building.md.
- vkd3d-proton as in Proton 11 / GE-Proton 11.
See docs/games.md: Wuthering Waves (SR + FG), Forza Horizon 6 (SR; FG through OptiScaler), Cyberpunk 2077 (SR + FG after replacing its older XeSS libraries), notes on OptiScaler and on a game without XeSS.
| Symptom | Cause / fix |
|---|---|
| looks like DP4a, nothing changed | the shim is not in the prefix: re-run install.sh |
| DP4a in one game only, or no XeSS frame generation option | the game sees no Intel GPU (a Mesa game profile, or DXVK with XeSS older than 2.0.2.68): docs/debugging.md |
| noise or black patches in the image | a kernel failed to compile; the next launch retries once and then uses XeSS' generic paths. See ~/.cache/xess-xmx/compile.log; a missing compiler: tools/get-igc.sh |
| XMX gone after a SteamOS update | neither patched driver loads any more: ~/.cache/xess-xmx/driver-status; run tools/rebuild-driver.sh (docs/building.md) |
| a game misbehaves on Mesa 26.3 only | MESA=26.1 %command% in its launch options, and please report it |
| first launch hangs for a minute or two | kernels are being compiled (once) |
The full table, the logs and every switch: docs/debugging.md.
-
Mesa 26.3 (Jay) against 26.1.2, Arc B390, same spot and settings, XeSS super resolution and frame generation on XMX:
Game Mesa 26.1.2 Mesa 26.3.0-rc1 Wuthering Waves 112-119 fps, low 94 120-126 fps, low 113 Cyberpunk 2077 61-62 fps 91-96 fps #19 has a Final Fantasy VII Rebirth comparison (about +15%, half of it from Jay).
-
Not measured yet: XMX against DP4a super resolution alone, image quality, and the cost of disabling
VK_EXT_descriptor_buffer.
- XeLL (Intel's latency reduction, used with frame generation) runs in its cross-vendor mode; its driver mode needs a component of Intel's Windows driver. Details in docs/how-it-works.md.
- The fallback (self-test failed, kernels that did not compile) gives XeSS' generic paths, whose frame generation is limited to 2x: a game set to 3x/4x runs at 2x until the XMX path works again.
- The driver patches are written against Mesa 26.1.2 and 26.3 and rely on vkd3d-proton internals: how it compiles the
placeholder shaders and how it lays out its descriptor heap. If a vkd3d-proton update changes the first, the
self-test turns the XMX path off; if it changes the second, the driver logs
no vkd3d-style descriptor heapand the kernels do nothing.
docs/how-it-works.md: the shim, the placeholders, run-time compilation, which kernel variant
XeSS picks (and why SIMD16Required matters), frame generation, XeLL.
install.sh, uninstall.sh system-wide install / removal
enable.sh, disable.sh per-prefix install / removal; xmx-launch.sh: Steam launch wrapper
patches/ Mesa 26.1.2 ANV: 0001 kernel injection and run-time compilation, 0002 debug tools,
0003 Large GRF Mode for Xe2; patches/mesa-26.3/: the same for Mesa 26.3,
plus 0004, the Jay crash fix for RE Engine games
shim/ igdext64.dll source: dxvk-igdext plus this project's code in src/dll/
tools/cm-compile.sh run-time compiler helper called by the driver
tools/get-igc.sh fetches IGC 2.10.10 + ocloc 25.18 into igc/
tools/rebuild-driver.sh rebuilds the patched driver for the system's Mesa version
tools/switch-driver.sh sets the default among the package's drivers (per game: MESA)
icd/xmx-icd.c lib/libvulkan_intel.so: loads the driver MESA or the default names
tools/session-check.sh the driver check run before each session
tools/cmk_pack.py zebin -> .cmk packer; tools/check-kernels.py validates a kernel folder
tools/gen_dyn_dummies.py placeholder table for run-time kernels; tools/check_dyn_ids.py consistency check
tools/split_patch.py writes patches 0001 / 0002 from the marked source tree
tools/gen_all_dummies.py, s16_map.py, build-kernels.sh, kernel_map_*.txt optional static kernel set
docs/ how it works, building, debugging, games
.github/workflows/build.yml CI: builds the shim, the ICD and both drivers, checks the scripts
The release archive holds the binaries (igdext64.dll, the drivers in lib/mesa-<version>/, the ICD
lib/libvulkan_intel.so) and the scripts. It contains no Intel kernels; they are compiled on your machine from the SPIR-V inside the game's XeSS libraries.
MIT (see LICENSE); the shim is based on dxvk-igdext (MIT), the patches apply to Mesa (MIT). See THIRD_PARTY.md.