Search Issue Tracker
Feature Request
Votes
0
Found in
2022.3.15f1
2023.2.3f1
2023.3.0a17
6000.0.0b11
Issue ID
UUM-58421
Regression
Yes
Materials render incorrect color when using the "require native16bit" pragma directive
How to reproduce:
1. Open the “DXC16BitIssue“ project
2. Open the “SampleScene”
3. Open the Scene view window
4. Observe the “16bit” GameObject
Expected result: The “16bit” GameObject is red
Actual result: The “16bit” GameObject is black
Reproduced with: 2022.2.0a1, 2022.3.15f1, 2023.2.3f1, 2023.3.0a17
Not reproduced with: 2021.3.33f1 2022.1.0a16
Reproduced on: Windows 11
Not reproduced on: No other environment tested
Notes:
1. Also reproducible in Player
2. In the 2023.3 stream the “16bit” GameObject is green
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:
Using 16-bit types in a constant buffer was never supported, so the issue is not a regression. This may be added in the future, however.