Search Issue Tracker
By Design
Votes
3
Found in [Package]
2.0.0
Issue ID
AVPB-818
Regression
No
Inconsistent GameObject behavior that are using XRGrabInteractable when moving the GameObject forwards or backwards
How to reproduce:
1. Open the attached “IN-81062.zip” Project
2. Build and Run on VisionOS
3. In the Player pinch-hold the Cube GameObject and move it around
4. Observe the Cube GameObjects behavior when moved forwards, backwards and side-to-side
Expected result: The Cube GameObject follows the hand movement
Actual result: The Cube GameObject moves further away when moved forwards or backwards
Reproducible with: 1.3.12 (2022.3.62f1), 2.1.2, 2.2.4 (6000.0.48f1, 6000.1.2f1)
Couldn’t test with: 2.2.4 (6000.2.0a10) - Builds fail due to il2cpp, error is not specified
Reproducible on: Apple Vision Pro 2.3.1
Testing environment: macOS Sequoia 15.3 (M3 Pro)
Notes:
- Downgrading the Project caused 2022.3 to fail builds with IL2CPP, re-extracting the project and opening with 2022.3 fixed it, downgrading caused the issue
- User also created a custom Script that replicates the movement behavior but it does not reproduce the bug (Teal GameObject labeled “Sample Manipulation Code” in the Scene)
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- 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
Resolution Note:
In my previous message I conveyed how the indirect touch behavior reported matches that of native Apple apps and gave guidance on how they can use direct touch to maintain a one to one relationship with objects that get picked up in XR.