Why Intel GPUs need their own Proton pass
A Godot Windows export that runs clean on NVIDIA or AMD can still fail on Intel integrated graphics and Arc. The reasons are practical, not mysterious. Intel iGPUs use shared system memory, smaller render caches, and tighter power limits. Arc cards have their own D3D12 driver quirks on Windows. When you run that same Windows build on Linux through Proton, you add a second translation layer.
For Godot 4, that layer matters a lot. Compatibility rendering uses Direct3D 11, which Proton translates with DXVK. Forward Plus and Mobile rendering can use Direct3D 12, which Proton translates with VKD3D-Proton to Vulkan. On Intel Linux systems the Vulkan driver is ANV, part of Mesa. ANV has improved quickly, but it has historically lagged behind RADV and NVIDIA in game specific workarounds.
That is where DXVK-IGDEXT comes in. It refers to ongoing community and driver work around Intel graphics driver extensions under DXVK, with the goal of better Godot Windows export behavior on Intel GPUs through Proton. It is not a stability switch you can turn on today in stable Proton. Treat it as a reason to build a repeatable Intel test pass now, so you can retest the same scenes and logs when Mesa, Proton, and DXVK move forward.
Build a reproducible Windows test export
Do not test with a random ZIP from your downloads folder. Make a build you can trace back to a commit.
- Duplicate your Windows Desktop preset and name it
Windows-Intel-Test. - Pick one renderer per build. Test Compatibility first if you promise Intel iGPU support, then test Forward Plus separately if you ship it.
- Export a debug build for the first pass, plus one release build for performance checks. Debug builds give you better stack traces when D3D initialization fails.
- Include a small test scene list: main menu, heaviest 3D level, particle heavy scene, UI only scene, and a save and load round trip.
- Zip the export with the Godot version and preset name in the file name, for example
mygame-4-4-compat-windows-intel-test.zip.
If you ship for other unusual targets, the Steam Frame export checklist shows a useful way to structure that export matrix without mixing results together.
If you use Godot MCP Studio to drive playthroughs, keep Proton log collection manual and use the agent only to list scenes to cover and grab screenshots for each run.
Set up an Intel Proton test bench on Linux
You need real Intel hardware for this. A VM with virtualized Vulkan or an NVIDIA machine with Intel emulation will not reproduce the same failures.
Test on at least one of each class if you can:
- Older UHD Graphics, for example UHD 620 or UHD 730, for low shared memory behavior
- Iris Xe integrated graphics, for the most common laptop player setup
- Arc A380, A750, or A770 if you claim discrete GPU support
Update Mesa before you blame the game. On Fedora, Arch, or Ubuntu LTS with a hardware enablement stack, you want a recent stable Mesa with ANV Vulkan support. Then confirm the system sees Intel Vulkan:
lspci | grep -i vga
vulkaninfo --summary
glxinfo -BUse Steam with forced compatibility for repeatability. Proton Experimental is useful for latest fixes, while a pinned GE-Proton build is better when you need every tester on the same version. Install the Windows export as a non-Steam game, open Properties, Compatibility, then force a specific Proton version. Do not mix Proton versions inside one test round.
Run your Godot Windows export under Proton and collect logs
Start simple, then add logging once the game launches or fails the same way twice.
- Launch once with no extra flags and note the result: boots, black screen, crash to desktop, or stable with glitches.
- Add a Proton log through Steam launch options:
PROTON_LOG=1 DXVK_HUD=compiler %command%- For a D3D11 Compatibility build, expand DXVK logging on the next run:
PROTON_LOG=1 DXVK_HUD=fps,compiler DXVK_LOG_LEVEL=info %command%- For a D3D12 Forward Plus build, log the VKD3D-Proton side instead:
PROTON_LOG=1 VKD3D_DEBUG=warn DXVK_HUD=fps %command%Logs land in your home directory by default as steam-APPID.log. Copy each log next to the build ZIP right away and rename it with GPU, Proton version, and renderer, for example iris-xe-ge-protron-compat-run02.log. Proton logs are overwritten on every launch, so a missed copy means a lost repro.
What to save for every Intel run
- Proton log and DXVK or VKD3D log section
vulkaninfo --summaryoutput and Mesa version- Exact GPU model, Proton version, and desktop session, X11 or Wayland
- Renderer used in Godot, Compatibility or Forward Plus
- Screenshot or short clip of the failure, plus steps from a cold boot
Read the logs like an Intel bug report
Intel Proton failures fall into a few repeatable patterns. Use this table to separate a game bug from a translation or driver gap.
| Symptom | Likely area | What to check first |
|---|---|---|
| Crash before window appears, DXGI error in Proton log | D3D12 feature level or swapchain init | Retest same build as D3D11 Compatibility export |
| Black 3D view but UI and audio work | Shader or render target translation | Look for DXVK compiler errors, test Low versus High glow and MSAA off |
| Long freeze on first load, then smooth | Shader cache building on shared memory | Retest second launch, check DXVK_HUD=compiler activity |
| Flickering textures or missing probes | Memory pressure or reflection probe path | Lower texture memory, test one level with probes disabled |
| Out of memory on 8 GB iGPU laptop | Shared memory budget | Monitor system RAM, reduce texture size, avoid 4K backbuffer |
| Stable on AMD but not Intel, same Proton | ANV or DXVK Intel path | Search Mesa and DXVK issues for GPU ID before changing game code |
When you file an issue, include the minimal bundle from the previous section. A report that says crashes on Intel is not actionable. A report that says Iris Xe, Mesa 25.1, GE-Proton build, Compatibility export, crash in dxgi after window creation, with log attached, can be fixed.
Proton is not a way around platform limits. Server side checks and kernel level anti-cheat still apply, as explained in the Linux anti-cheat guide. Test gameplay under Proton, but keep account and anti-cheat expectations separate.
Set compatibility expectations while DXVK-IGDEXT work lands
Do not promise Intel fixes tied to a future DXVK or Mesa release. Promise a tested configuration instead.
Use wording players can act on:
Tested on Windows with Iris Xe and Arc A750 at 1080p, Compatibility renderer. Proton on Linux with Intel graphics is playable but not officially supported until Intel DXVK driver extension work reaches stable Proton. If you play on Linux on Intel, please include your Mesa version and Proton log with bug reports.
Practical policy for now:
- List Intel iGPUs as supported only for your Compatibility preset, with resolution and quality caps you actually tested.
- List Arc separately from iGPUs. They fail in different places.
- Offer a native Linux export if your netcode and middleware allow it, rather than telling every Linux player to use Proton.
- Track engine regressions the same way you would for a beta, using the checklist in the Godot 4.8 test guide.
Retest on a schedule, not on hope. Pin one Intel machine, one Proton version, and one test scene list. When a new Proton Experimental or Mesa stable lands, rerun the same five scenes, compare new logs to old logs, and update your store page only when the results change. That gives Intel players honest guidance today and lets you adopt DXVK-IGDEXT improvements the week they actually help.