Search Issue Tracker
By Design
Votes
0
Found in
5.3.1f1
Issue ID
760053
Regression
No
Shader w/ pow function produces different result w/ values from inspector and code
Steps to reproduce:
1. Download and open attached project "ShaderBug.zip"
2. Open scene "Main" and notice, that both, cube and sphere, has white sides and black middle
3. Open "TriWater" shader file and comment out line 38 (_bug = 4;), this removes the forced value for _bug variable and takes one from the inspector
4. After switching focus back to Unity and shader recompile, notice that only one side of the cube and sphere is black now
Expected result: No difference between the way variable has been set
Tested and reproduced on:
Windows 10
Unity 5.1.4f1, 5.2.4p1, 5.3.1p3, 5.4.0b2
Comments (1)
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
- 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
- UI Mask Component does not apply correctly when Canvas Render Mode is set to Screen Space - Camera
scottunity
Mar 22, 2016 03:34
This sounds very similar to a shader bug I'm having. Inspector or script passed value wildly different than same value hard coded.
Unity 5.3.4f1