Search Issue Tracker
In Progress
Fixed in 3.3.0
Fix In Review for 3.2.2
Votes
6
Found in [Package]
3.2.1
3.3.0-pre.1
Issue ID
XRIT-334
Regression
No
[XRI] Object Continues to Move After Pinch Release in Hand-Tracked Interactions
Steps to reproduce:
1. Open the attached user's project "MR core.zip"
2. Open the "Assets/Scenes/SampleScene.unity" Scene
3. Switch to Android and build to a Quest 3/3S headset
4. Make sure to have configured "Space Setup" in the headset settings and enabled Hands
5. Open the built application with only the Hands and spawn a "Floating Torus"
6. Try to pinch and move parts of the object
7. Observe the object moving slightly back after a pinch
Expected result: object stops moving after a pinch release in Hand-Tracked interactions
Actual result: object continues to move after pinch release in Hand-Tracked interactions
Reproducible with: XR Hands 1.5.0 - 1.7.0-pre.2 (6000.0.54f1, 6000.2.0f1, 6000.3.0a5)
Could not test below XR Hands 1.5.0 due to compilation errors appearing after downgrading
Could not test on 2022.3.65f1 due to project errors after downgrading
Reproducible with these devices:
VLNQA00644 - Oculus Quest 3S (Quest 3S), CPU: Google Tensor G2, GPU: Adreno 740, OS: 14
VLNQA00609 - Oculus Quest 3 (Quest 3), CPU: Snapdragon XR2 Gen 2 (SM8550), GPU: Adreno 740, OS: 12
Environment tested: Windows 11 24H2
Notes:
-Customer initially reported the issue with AndroidXR, however after further testing issue can be reproduced with a Quest 3
-Issue only reproduces when using Hands, controllers do not exhibit the issue
Comments (1)
-
VRDave_Unity
Sep 04, 2025 21:42
The easiest solution/workaround if you are using the Hand Interaction Profile is to adjust the Press Threshold and Release Threshold on the XR Origin > Camera Offset > Left/Right Hand > Near-Far Interactor > Select Input > Release Threshold Button Reader.
I discovered that setting the Press Threshold to 1 and the Release Threshold to 0.9 will create a very solid interaction when using pinch to grab without moving the object as much upon release, but has enough wiggle-room that the object is not accidentally dropped.
We will adjust these default values in a patch release, but for now you can adjust those settings without needed to modify the code.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
- VFX Graph font size change does not adjust Sticky Note size when smaller font size is selected
- Rendering Debugger has a “Go to Section” burger button even when the section is already opened and does nothing when pressed
Resolution Note (fix version 3.3.0):
Fixed an issue where pinching with the Hand Interaction Profile caused the Interactables to stick to the thumb longer than desired, moving the object after a pinch was released. The `ReleaseThresholdButtonReader` sample component was updated with new default values to ensure tighter press and release when pinching.
Resolution Note (fix version 3.2.2):
Fixed an issue where pinching with the Hand Interaction Profile caused the Interactables to stick to the thumb longer than desired, moving the object after a pinch was released. The `ReleaseThresholdButtonReader` sample component was updated with new default values to ensure tighter press and release when pinching.