Search Issue Tracker
Fixed in 5.3.1
Votes
0
Found in [Package]
3.0.0
Issue ID
1141821
Regression
No
ShaderGraph throws Compilation error when an input value Vector1 is in Slider mode and its Min/Max values are set to floats
Reproduction steps:
1. Open the attached project named "Case_1141821"
2. Open the "TestShader"
3. Observe the console window
Expected result: No errors are thrown and the shader is functional
Actual result: Compilation error is thrown and the shader is broken
Reproducible with: 2017.4.25f1, 2018.3.13f1, 2019.1.0f2, 2019.2.0a11
Notes:
1. The bug is fixed in ShaderGraph version 5.3.1 or newer
2. Tested with package versions 3.0.0, 3.3.0, 4.0.0, 5.0.0, 5.2.3, 5.3.1, 5.10.0
Full error message:
Compilation error in graph at line 5 (on ):
Parse error: syntax error, unexpected ',', expecting ')'
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment