Search Issue Tracker
Fixed in 5.1.0
Votes
1
Found in [Package]
4.10.0-preview
Issue ID
1130502
Regression
No
Game Object goes magenta when using 'Slider' or 'Sampling Gradient' Nodes in HDRP template project
How to reproduce:
1. Open the attached project
2. Open the 'LitGraph_GradientTest', 'LitGraph_SliderTest' shaders and observe them
3. Observe the Scene
Expected result: Objects are rendered without magenta
Actual result: Objects rendered in magenta
Reproducible: 2018.3.10f1
Not reproducible: 2019.1.0b6, 2019.2.0a1, 2019.2.0a9
Can't reproduce:
- 2019.1.0a1, 2019.1.0b7, 2019.1.0b8, because all scene is rendered in magenta
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
- Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- Crash on dynamixel_sdk.dynamixel:groupSyncReadTxRxPacket when entering Play Mode after updating path to Dynamixel SDK in script
- NullReferenceException is thrown when changing the Inspector preview selection
Egil-Sandfeld
Aug 17, 2019 10:43
Can reproduce this in 2019.2.0f1 with a Gradient that:
- have more than 2 color points in the gradient
- have 2 color points in the gradient, but the points are not at the extremes
Balikk
Aug 01, 2019 16:48
Maybe it's not where the problem is, but when we use gradient and look at the error, we have the line :
g.colors[0] = float4(0, 0, 0, 0,002944991);
The last number should be with a point and not a coma, which result to give a float5 at this time
Fernando-Ferreira
Jul 07, 2019 22:06
Same on 2019.3.0a7
Shader Graph is not production ready
Yanka33
May 24, 2019 08:39
After further tests, it appears that this gradient bug sometimes does not occurs when the Gradient used as input for the Sample Gradient node is composed by 2 points located at the boundaries of the gradient
Yanka33
May 24, 2019 08:10
I can reproduce this same bug in a Lightweight Render Pipeline project with Unity 2019.1.3f1, LWRP 5.7.2 and ShaderGraph 5.7.2.
My shader use a Gradient input node linked to a Sample Gradient.
On shader compilation, the Editor show the errors:
- ArgumentException: GUILayout: Mismatched LayoutGroup.repaint
- Shader error in 'Shader Graphs/Fire Shader': incorrect number of arguments to numeric-type constructor at line 130 (on d3d11)
- Shader error in 'Shader Graphs/Fire Shader': incorrect number of arguments to numeric-type constructor at line 428 (on d3d11)
If I remove the Sample Gradient node, I have no more error.