Search Issue Tracker
By Design
Votes
0
Found in
2018.3.0a9
Issue ID
1074362
Regression
No
material.SetFloat(name, value) ignores min/max values of slider property
How to reproduce:
1. Open the "FloatMinMax Repro.zip" project
2. Open the "SampleScene.unity" scene
3. Press Play
4. Check the console for debug log
Actual result: material.SetFloat(name, value) ignores slider's min/max values in shader graph and sets float bigger than the max value.
Expected result: material.SetFloat(name, value) should set the value equal to the max value if the value is higher than the max value.
Reproducible with: 2018.3.0a11, 2018.2.6f1, 2018.1.9f2, 2018.1.0b5.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment