Supported extensions by Meta

Hi,

I noticed that Meta’s OpenXR runtime (the one that comes with the Meta Horizon Link app) doesn’t seem to support some pretty fundamental extensions, such as
XR_EXT_hand_tracking
XR_EXT_hand_joints_motion_range
XR_EXT_hand_interaction
XR_EXT_hand_tracking_data_source
XR_EXT_uuid

and the more recent
XR_EXT_render_model
XR_EXT_interaction_render_model.

I’m using a Quest 3 to develop a PCVR app, and this was a bit shocking to me, given that SteamVR (that I usually use) supports all these without any issues. I mean, Meta’s is the “official” runtime for the headset that I’m using. Why can’t I have simple things?

What’s the reasoning behind this lack of support?
Thanks

Many extensions, including hand tracking are locked behind the developer mode on Link, which requires registering a developer account. Meta hasn’t made any moves to improving the support since Link was released. It seems Meta regards PC support as a legacy or developer feature.

Hmm so even if I register a developer account, I may get access to them, but then potential third parties (friends, customers etc) won’t be able to use such an app since they can’t be forced in any way to have a dev account. Is this correct?

Exactly. This has caused a lot of feature fragmentation on PC, making it hard to support these features at all.

Good lord, what are they thinking…Anyway, very helpful as always, thank you @Rectus .

1 Like