Search Issue Tracker
Won't Fix
Won't Fix in 2.0.X
Votes
0
Found in [Package]
2.0.0
Issue ID
AVPB-816
Regression
No
Multiple Skinned Mesh Renderer components are not being rendered when observed in the VisionOS Player
How to reproduce:
1. Open the attached “IN-94959.zip” project
2. Open the “Main” Scene (Assets → Content → Scenes)
3. Enter Play Mode
4. Observe the rendered Character Model in the Game View
5. Exit Play Mode
6. Build and Run the “Main” Scene on Apple Vision Pro
7. Observe the rendered Character Model in the Player
Expected result: The Model is fully rendered same as in Game View
Actual result: Multiple Meshes are not rendered until the whole Model is moved then only a few are rendered
Reproducible with: 2.1.2 (6000.0.44f1), 2.2.4 (6000.1.0b12, 6000.2.0a7)
Couldn’t test with: 1.3.12 (2022.3.60f1) - Compilation errors related to unsupported methods after package downgrade
Reproducible on: Apple Vision Pro 2.3.2
Testing environment: macOS 15.3.2 (M3)
Note: Not reproducible on Standalone Player
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
Bounds issue will be addressed in the next package release. However, some of the skinned meshes will still be invisible/out of bounds and require one of the two listed workarounds to fully work.
Resolution Note (2.0.X):
Bounds issue will be addressed in the next package release. However, some of the skinned meshes will still be invisible/out of bounds and require one of the two listed workarounds to fully work.