Search Issue Tracker
By Design
Votes
0
Found in
2017.4
2020.1
2020.1.0a19
Issue ID
1213749
Regression
No
Shader properties are ignored when SetReplacementShader method is invoked
How to reproduce:
1. Open the attached '1213749.zip' project
2. Open 'SampleScene' Scene
3. Enter Play Mode
4. Notice that 'Cube' GameObject is red
5. Open 'Unlit_Modified.shader' shader
6. In 44 line, change fixed4 data type's red value from '1.0' to 'RedVal'
7. Enter Play Mode
Expected result: 'Cube' GameObject is red
Actual result: 'Cube' GameObject is black
Reproducible with: 2017.4.36f1, 2018.4.17f1, 2019.2.20f1, 2019.3.1f1, 2020.1.0a22
Notes:
1. Project and video of reproduction is attached in Edit
2. Reproducible on macOS
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
- IndexOutOfRangeException occurs when entering "<a></a>" tags in a TextMeshPro UI field
- Numeric property drag cursor gets enabled in the Inspector Preview window when the window is above numeric properties
- UI elements become unusable due to Object and Text Fields being set to empty/"0" when clicking "Reset" on their Components
- Scene Asset is not attached to a Lighting Data Asset for a URP Package Sample Scene
- Gizmos are not rendered for the Base Camera when using Camera Stacking
Resolution Note:
The script is missing Shader.SetGlobalFloat("RedVal",1.0f);
Add this so that RedVal has the value.