Search Issue Tracker
Fixed
Fixed in 1.1.6
Votes
0
Found in [Package]
1.1.6
Issue ID
AVPB-450
Regression
No
[VisionOS] PolySpatial Object node always outputs (0,0,0) when using the visionOS Player
Reproduction steps:
1. Open the attached "PROJECTFILE" project
2. Build And Run the project (File > Build And Run)
3. Observe the Simulator
Expected result: GameObjects appear with different colors
Actual result: GameObjects appear black
Reproducible with: Repro: 1.1.6 (2022.3.20f1)
Couldn't test with: 1.0.3 (Console errors)
Reproducible on: macOS Sonoma 14.3.1 (M1 Max)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 1.1.6):
This is fixed for the next version.