Meta will recommend using Unity and Unreal's built-in OpenXR support, after developers said Meta's Unity and Unreal integrations blocked other PC VR headsets
At Meta, our core philosophy is that a vibrant, multi-platform development community … X: Kent Bye / @kentbye : Public response from Meta about their controversy around OpenXR. Honestly happy to see such a strong statement in support of OpenXR. Curious to hear more developer responses. I'm currently about to land in Austin for SXSW and will be offline for a bit. Fred Emmott / @fredemmott : @MetaHorizonDevs ... As you're committed to OpenXR, do you plan to make more of your many extensions available on PC without developer mode? For example, XR_EXT_hand_tracking is really quite old now, but still unavailable on quest headsets to the average PCVR user David Heaney / @heaney555 : Seems like the issue here stemmed more from a long strategy execution time, typical of a big tech company, rather than some machiavellian scheme to undermine OpenXR. @cixliv : @Heaney555 Ah yes meta never undermines 3rd party devs Forums: r/OculusQuest : Meta reaffirm commitment to OpenXR
Context & Ripple Effects
Meta’s response follows its broader effort to expand Horizon OS beyond its own hardware, including opening the OS to third-party headset makers. At the PCVR tooling layer, it signals that platform expansion must not come at the expense of developers’ ability to target multiple headsets.
The change also lands as VR studios have voiced concerns about the economics of shipping on Quest and Meta’s growing Horizon Worlds focus in recent studio interviews. Reducing integration friction addresses a concrete developer-distribution concern without resolving those wider commercial questions.
First-order effects
- Unity and Unreal developers targeting PCVR are now directed to the engines’ built-in OpenXR paths rather than Meta-specific integrations that developers said prevented use with other headsets.
- Meta publicly repositions its PCVR tooling around OpenXR interoperability; the unresolved availability of extensions such as hand tracking without developer mode remains a practical constraint.
Second-order effects
- Studios can reduce the risk of maintaining headset-specific PCVR integration paths, making multi-headset releases easier to justify when using Unity or Unreal.
- Meta’s tooling teams face pressure to ensure its extensions and runtime behavior work cleanly with the standard path; otherwise the recommendation will not remove the compatibility issues developers raised.
Third-order effects
- If Meta follows through by exposing more capabilities through standard PCVR routes, OpenXR can become a stronger control point for VR distribution and feature access rather than merely a compatibility layer.
- The episode illustrates a durable platform trade-off: as Meta seeks a wider hardware ecosystem, developer trust increasingly depends on interoperable tools instead of integration advantages tied to one headset.
The trend: VR platforms are shifting from device-specific developer stacks toward interoperability as a prerequisite for attracting multi-platform content.