Search Issue Tracker
Fixed
Fixed in 1.1.6, 1.2.3
Votes
0
Found in [Package]
1.1.6
Issue ID
AVPB-469
Regression
No
[VisionOS] Mesh collider breaks interactions with XR interaction toolkit
Reproduction steps:d
1. Open the attached “Repro“ projected
2. Open the “Assets/Scenes/HandsDemoScene AVP.unity“ Scene
3. Select the “VirtualTabletop” GameObject (Table > VirtualTabletop) in the Hierarchy
4. Disable the “Box Collider“ Component and enable the “Mesh Collider“ Component in the Inspector
5. Build the project on “visionOS” platform (File > Build Settings > visionOS > Build)
6. Open the project in Xcode and run it on an Apple Vision Pro device or visionOS simulator
7. Try to interact with the 3 cubes on the left side of the tabletop
Expected result: The cubes are consistently interactable
Actual result: Picking up objects is not consistent, picking up from the bottom part of the cube is not possible (using simulator)
Reproducible with: 1.0.3, 1.1.6 (2022.3.27f1)
Reproducible on: MR using visionOS Simulator 1.1 - built using M1 MacOS 14.4.1
Not reproducible on: No other environment tested
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
- Cursor doesn't change to the resizing when using the Rect Tool and the Sprite is too close to the bottom of the Scene View
- InvalidOperationException exception is thrown when Editor Default Text Rendering Mode is set to "Bitmap" and Editor Font is set to "System Font" and an array is expanded in the Inspector Window
- "Sample Gradient" node can be connected to the "Sub Mesh Mask" input and makes the VFX Graph uncompilable
- "LoadFontFace_With_Size_and_FaceIndex_FromFont_Internal can only be called from the main thread." exception is thrown when opening an editable array in the Inspector while Editor Default Text Rendering Mode is set to "Bitmap"
- EditorGUILayout.PropertyField foldout icon inside Vertical Layout Group has an incorrect indent when used with OnInspectorGUI()
Resolution Note (fix version 1.2.3):
This issue should be resolved by the generalized (non-convex) mesh colliders added in 1.2.3