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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
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.