Search Issue Tracker
Fixed
Fixed in 2.3.1
Votes
0
Found in [Package]
2.3.1
Issue ID
AVPB-832
Regression
No
Sprite GameObjects show incorrect color when the "Sprites/Default" Shader is used on VisionOS projects
How to reproduce:
1. Open the attached “IN-106361.zip” Project
2. Build and Run on Simulator or Device
3. Observe the Sprite GameObjects in the player
Expected result: Sprites show up with white and red color material
Actual result: Sprites only show up with black color material
Reproducible with: 2.3.1 (6000.0.52f1, 6000.1.10f1, 6000.2.0b8)
Couldn’t test with:
1.3.13 (2022.3.64f1) - Broken shaders, pink materials, impossible to verify if reproducing or not
2.3.1 (6000.3.0a1) - Polyspatial Package errors due to missing Collections arguments
Reproducible on:
Apple Vision Pro on VisionOS 2.5
Testing environment: macOS 15.5 (M3 Pro)
Notes:
- Also reproducible in Simulator
- Creating a new GameObject with a Shader that isn’t Sprite related, shows the correct colors
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 2.3.1):
Will be fixed in the next version of PolySpatial.