DisplayXR Runtime v2.2.4
Highlights
This release makes every graphics API work on Intel iGPUs of Optimus laptops:
- New
DXR_VK_FORCE_GPU/DXR_D3D_FORCE_GPUadapter overrides to pin the runtime to a specific GPU. - NT-handle DComp bridge — the legacy KMT ring silently shared no pixels on Intel UHD drivers, leaving transparent Vulkan windows invisible.
- LUID-matched bridge devices so the composition path always lives on the same adapter as the app.
Pairs with leia-plugin v2.0.9's capture-adapter fix (#819).
Fixes
- VK/D3D iGPU support: GPU-force env overrides + NT-handle DComp bridge (#821) — 7c77889
- fix(drift-audit): close four blind spots that hid the displayxr-common drift (#820) — e1b07be
- fix(skills): never assign to TMP in the signing paths — it silently unsigns — 6cd6a26
Docs
- docs(#736): purge stale XR_EXT_app_launcher mentions from current-facing docs — 8f7e7e1
- docs(CLAUDE): DXR author ID registered — OpenXR-Docs#201 merged — d0f15b5
Chores
- chore(versions): bump gauss_demo → v1.18.4, earthview_demo → v0.6.4, avatar_demo → v0.9.4
Full Changelog: v2.2.3...v2.2.4