Search Issue Tracker
Fixed in 12
Votes
1
Found in [Package]
11
Issue ID
1296291
Regression
No
[Shadergraph] Shadergraph shader errors in console are not cleared when the graph is fixed
Repro steps (case 1):
1. Create a new shader graph
2. Create a custom function node
3. Give the custom function node a float output
4. Plug the custom function node's output into the "color" output of the graph, observe the errors
5. Unplug the custom function node's output from the "color" output of the graph
Expected result: the error for the main preview is removed from the console
Actual result: the error for the main preview remains
Said error should look something like: "Shader error in 'Master': variable '_CustomFunction_d29bb6f5938242698c96d2462b742c1a_New_0' used without having been completely initialized at line 278 (on d3d11)"
Repro steps (case 2):
1. Create a new shader graph
2. Create a custom function node
3. Give the custom function node a float output, observe the error printed to the console
4. Delete the custom function node
Expected result: the error of the custom function node's preview failing to render is deleted when the custom function node is deleted
Actual result: the error stays
Repro steps (case 3):
1. Create a new shader graph
2. Create a custom function node
3. Give the custom function node a float output, observe the error printed to the console
4. Delete the output to the custom function node you just created
Expected result: the error of the custom function node's preview failing to render is deleted when the custom function node's preview shader changes
Actual result: the error stays
The errors for case 2 and 3 should look something like:
"Shader error in 'hidden/preview/CustomFunction_4d4dda8b932a414c9f04da5492c829d9': variable '_CustomFunction_4d4dda8b932a414c9f04da5492c829d9_New_0' used without having been completely initialized at line 145 (on d3d11)"
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