Search Issue Tracker
Fixed in 8c97c76
Votes
0
Found in [Package]
12.0.0
Issue ID
1349311
Regression
Yes
[Shadergraph] Erroring unconnected node causes material to become invalid/pink
Does not repro in Version: 2021.1.8f1.2516
Repros in 2021.2.0b3.3078.7
Repro steps:
1. Create a URP Lit shadergraph in a project with URP
2. Open it and add a custom function node
3. Add an output to the custom function node so it errors
4. Don't plug the custom function node in
5. Save the graph
6. Make a material from the graph
Expected result: the material works because the custom function node wasn't connected to anything
Actual result: the material is pink
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