Context
DisplayXR currently ships a 64-bit runtime only (DisplayXR_win64.json + DisplayXRClient.dll x64). There is no win32 runtime DLL or manifest.
Historically the 32-bit OpenXR active-runtime key on Windows
(HKLM\Software\WOW6432Node\Khronos\OpenXR\1\ActiveRuntime) was pointed
at Leia's Monado-based SRMonado runtime as a stopgap for 32-bit OpenXR
clients. SRMonado is now deprecated and has been removed, and the 32-bit
key has been cleared. As a result, 32-bit OpenXR applications currently
have no active runtime on a DisplayXR-only machine.
Ask
If/when we decide to support 32-bit OpenXR clients, we need to:
Priority
Low / future. Modern OpenXR apps (game engines, demos) are predominantly
64-bit; tracking this so the gap is explicit rather than silently broken.
Context
DisplayXR currently ships a 64-bit runtime only (
DisplayXR_win64.json+DisplayXRClient.dllx64). There is nowin32runtime DLL or manifest.Historically the 32-bit OpenXR active-runtime key on Windows
(
HKLM\Software\WOW6432Node\Khronos\OpenXR\1\ActiveRuntime) was pointedat Leia's Monado-based SRMonado runtime as a stopgap for 32-bit OpenXR
clients. SRMonado is now deprecated and has been removed, and the 32-bit
key has been cleared. As a result, 32-bit OpenXR applications currently
have no active runtime on a DisplayXR-only machine.
Ask
If/when we decide to support 32-bit OpenXR clients, we need to:
win32)DisplayXRClient.dll+ dependenciesDisplayXR_win32.jsonruntime manifestHKLM\Software\WOW6432Node\Khronos\OpenXR\1\ActiveRuntimein the installerPriority
Low / future. Modern OpenXR apps (game engines, demos) are predominantly
64-bit; tracking this so the gap is explicit rather than silently broken.