Search Issue Tracker
Fixed
Fixed in 2.4.X
Votes
0
Found in [Package]
2.2.4
Issue ID
XRVOSB-79
Regression
No
Generated Mesh is non-interactable when the Physical Material/Background is of a transparent material
How to reproduce:
1. Open the attached “IN-83398.zip” Project
2. Build and Run on the VisionOS Platform
3. Generate Meshes (Look around the room)
4. Look at a generated Mesh and do a “Pinch” gesture
5. Observe the Mesh
6. Look at different Physical Materials and do a “Pinch” gesture
7. Observe the Mesh
Expected result: A “Sphere” GameObject is spawned on the observed Mesh’s spot
Actual result: Specific Physical Material Meshes inaccurately or don’t even spawn a “Sphere” GameObject
Reproducible with: 2.2.4 (6000.0.49f1, 6000.1.3f1)
Couldn’t test with:
1.3.12 (2022.3.62f1) - Unsupported methods related to RigidBody due to downgrade (Unsupported methods in older versions, feature was not yet present)
2.2.4 (6000.2.0b1) - Unfixable IL2CPP Build errors
Reproducible on:
Apple Vision Pro on VisionOS 2.4.1
Testing environment: macOS 15.4.1 (M3 Pro)
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
- Source Generation with GeneratePropertyBag fails when using reserved keywords as variable names with @ prefix
- Prismatic ArticulationBody moves in opposite direction when using targetVelocity
- Shader Graph skybox material is rendered inccorrectly in builds when "Allow Material Override" or "Cast Shadows" are enabled and the "Deferred" Rendering Path is used
- Object motion is affected by incorrectly added rotation motion when importing animations
- Base class's Context Menu method is called when calling it in the Editor from the child class and the child class overrides this method
Resolution Note (fix version 2.4):
This appears to be fixed in the latest PolySpatial (2.3.1)/visionOS (2.5). It may have had something to do with our fix for asynchronous static ShapeResource creation.