Search Issue Tracker
By Design
Votes
0
Found in
2017.4.0f1
2018.3.0a1
2019.1.0a1
2019.2.0a1
2019.2.7f2
2019.3.0a1
2020.1.0a1
Issue ID
1189653
Regression
No
Shader [Gamma] attribute is ignored when MaterialPropertyBlock.SetFloat() is called
How to reproduce:
1. Open the Sample Scene of the attached project "1189653.zip"
2. Enter Play mode
3. Investigate the 2 Cubes in the Scene
Expected result: Colors of both cubes match
Actual result: Colors of cubes are different
Reproducible with: 2017.4.33f1, 2018.4.11f1, 2019.1.14f1, 2019.2.9f1, 2019.3.0b7, 2020.1.0a8
Notes:
Calling Mathf.GammaToLinearSpace() for the MaterialPropertyBlock.SetFloat()'s value parameter will work as a workaround.
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
- The Up, Down and other Buttons in a Style Sheet's Inspector unselect items when they are clicked while they are disabled
- Virtual Player remains active and still launches when removed from Additional Editor Instances from a custom Play Mode Scenario
- UI Toolkit Editor Window Creator becomes not interactable and greyed out when a long name is entered
- [Web][iOS] Web Player keeps restarting on launch when Native C/C++ Multithreading is enabled
- "Add Scene to Scenes in Build" pop-up reappears after Scene has already been added and another Multiplayer Editor Instance is loaded
Resolution Note:
This is by design. The [gamma] attribute will only affect the value that is altered on the material inspector, that means the script will not be limited by it.