You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Linux builds report runtimeVersion 1.6.0 (CMake VERSION is not synced from the tag) #1790
On Linux, xrGetInstanceProperties returns runtimeVersion = 1.6.0 for runtime v2.21.11, both from the installed .deb (displayxr-runtime 2.21.11) and from a local build. The tag only shows up in the name: runtimeName = "DisplayXR Runtime (based on Monado/XRT) 'v2.21.11'".
Why
build-windows.yml has a "Sync CMake VERSION from latest vX.Y.Z tag" step that patches project(VERSION ...) before building. build-linux.yml has no such step. It uses git describe only to name the tarball and the .deb. So the Linux runtime reports the placeholder VERSION 1.6.0 from CMakeLists.txt.
Why it matters
Apps gate on runtimeVersion. DisplayXR/displayxr-unity#348 (the #347 colour fix) turns on _SRGB swapchains only when the runtime is format-honest, and it decides that from runtimeVersion (Vulkan ≥ 2.21.7). On Linux it reads 1.6.0, so the fix never engages, and Unity apps stay washed out on a runtime that logs Color (#1589) [vk_native]: format-honest.
Suggested fix
Add the same version-sync step to the Linux jobs that build the runtime (at least Deb and Package, which ship it), so runtimeVersion matches the tag on every platform.
Found while testing displayxr-unity#348 on a Leia DS1 (Ubuntu 26.04, NVIDIA).
Activity
fix(#347): read the runtime version from runtimeName when runtimeVers…
fix(#347): _SRGB swapchains on format-honest runtimes — colour no lon…