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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Add comment