Skip to main content
New Participant
June 1, 2026
Question

Horizon OS v2.4 breaks hand far-interaction in all OpenXR Unity apps

  • June 1, 2026
  • 7 replies
  • 942 views

Posting here to surface a regression that's affecting our production app

on the Meta Horizon Store and appears to be hitting the broader OpenXR

ecosystem on Quest 3.

 

SUMMARY

Since Horizon OS v2.4 rolled out (week of 18 May 2026), the Meta Aim

Hand OpenXR extension (XR_FB_hand_tracking_aim) returns a stuck/invalid

aim pose. Any Unity app reading pose from the MetaAimHand input device

(via com.unity.xr.hands) loses hand far-interaction: the ray is stuck

pointing forward, and the grab interaction range tied to the ray is

also affected. Reproduces in the Unity Hub VR template project as well

as in our production apps

 

WHAT'S RULED OUT

- System-level hand tracking is healthy: works in Quest Home, 2D system

apps, and via XR_EXT_hand_tracking joint data inside the app itself

(near interaction with hands continues to work).

- Our MRTK-based sister app, which derives its hand ray from joints

rather than from the Aim extension, is unaffected — confirming the

breakage is scoped specifically to XR_FB_hand_tracking_aim.

- The latest Meta XR Core SDK / Interaction SDK (v201.0, April 15) and

Unity's com.unity.xr.hands (1.6.0-pre.3) and com.unity.xr.meta-openxr

(2.6.0-pre.1) all predate the v2.4 rollout — no upstream SDK fix

available to update to.

- The Hand Interaction Profile workaround restores a ray but with pinch

detection too sensitive for production use, which makes it unviable

for medical/clinical content.

 

VIABLE MITIGATIONS FOR SHIPPING APPS

Falling back to controllers, or computing a custom aim pose from

XR_EXT_hand_tracking joints directly (bypassing MetaAimHand entirely).

 

ALSO REPORTED

- Unity Discussions: https://discussions.unity.com/t/quest-3-openxr-hand-tracking-no-longer-works-after-2-4-update/1721513

- Filed on Meta Feedback Center (Inputs → Hand Tracking) for engineering

tracking.

 

ASK

Confirmation this is on Meta's radar, ETA on a Horizon OS hotfix or an

SDK-level workaround, and any guidance for affected apps shipping

today. Happy to provide additional repro details or logs (privately) if

useful.

7 replies

Participant
June 1, 2026

Encountered this too: 

Hand tracking no longer works on 2.4 | Meta Community Forums - 1375023

I'm amazed that despite this being on PTC for how long now that nobody ran into this? I'm using the hand interaction profile workaround but it's so awful to use.

New Participant
June 5, 2026

I was able to reproduce the problem on v2.4

Participant
June 9, 2026

The extension still tracks pinches so I'm currently fixing this by:

  • Adding the Hand Interaction Profile
  • Removing the graspFirm and graspValue input actions for each hand
  • Keeping the Meta Hand Tracking Aim feature enabled

This uses meta pinching and the Hand Interaction Profile ray pose which is acceptable for now.

New Participant
June 15, 2026

Been having this issue too.  

New Participant
June 16, 2026

Need a fix for this.

Sandstedt
Inspiring
July 6, 2026

+1 Tried to enable hand-tracking in a project with Unity XR Interaction Toolkit and XR Hands, and also have this issue. The select action works just fine in the editor when running through Meta Quest Link, but as soon as I build, it stops working.

 

Unity 6000.0.59f2

OpenXR Plugin: 1.17.1

XR Interaction Toolkit:3.5.1

XR Hands: 1.8.0

XR Plugin Management: 4.6.0

 

Feature Groups:

Meta Quest

 

Features:

Hand Interaction Poses

Hand Tracking Subsystem

Meta Hand Tracking Aim <-- the broken one

Palm Pose

And some more for mixed reality features (the forum refused to upload my screenshots due to invalid HTML)

Unity XR Developer
Sandstedt
Inspiring
August 16, 2026

This have been solved in a recent OS update.
But I still have problems with the input deactivating itself, so I have to disable and enable the input handler when a device connects. But it might only be user error (project-related code).

Unity XR Developer