How can you allow this to happen?
also isn’t it conflict of interest to have Meta engineer (Ron Bessems) as chair of open XR working group, if he is allowed to try to make this platform Meta exclusive?
Bump!
Will we get a pronouncement from the Khronos Group about this situation?
Bump, would really like to see this addressed.
As a long time VR enthusiast this would make me recomend to my clients to avoid meta in the future.
The Khronos OpenXR Working Group recognizes the challenges developers have faced with legacy APIs and platform-specific behaviors that limit XR application portability. The Working Group is dedicated to evolving OpenXR by incorporating vendor extensions into the core specification and continues to enhance platform interoperability. Today, three major engines - Unity, Unreal, and Godot - support building OpenXR applications that are compatible with multiple vendors’ OpenXR conformant devices, provided vendor-specific features are avoided.
Application developers retain the choice to target specific runtimes and devices if desired, though this approach may introduce some vendor dependencies. For guidance on building OpenXR PCVR applications on Windows without vendor dependencies, please follow the link below to access PDFs on how to set up cross-device OpenXR on Unity/Unreal/Godot for Windows PCVR: Statement from OpenXR Working Group in Response to Community Discourse on the OVRPlugin from Meta - The Khronos Group Inc