Search Issue Tracker
Fixed in 2022.3.13f1
Fixed in 2022.3.X, 2023.3.X, 2023.3.0a12
Votes
5
Found in
2022.3.11f1
2023.3.0a10
Issue ID
UUM-53778
Regression
Yes
Dragging from a node’s output port causes a nullref error and renders the Shader Graph window unusable
Steps to reproduce:
1. Open any URP-enabled Unity project
2. Create a new Shader Graph (Assets>Create>Shader Graph>Lit Shader Graph)
3. Create a Dither node
4. Drag out a connector from the Dither node’s out port and select any node from the node dropdown
5. Observe the console/try moving around in the Shader Graph window
Note: not tested with every node, but consistently reproduces with any tested node
Reproducible with: 2022.3.11f1 (14.0.9), 2023.3.0a10 (17.0.1)
Not reproducible with: 2021.3.31f1 (12.1.12), 2022.3.10f1 (14.0.8), 2023.1.16f1, 2023.2.0b14 (16.0.4), 2023.3.0a9 (17.0.1)
Expected result: a connected node is created
Actual result: an error is thrown and the Shader Graph window becomes unusable
Error:
NullReferenceException: Object reference not set to an instance of an object
UnityEditor.ShaderGraph.Drawing.GraphEditorView.AddEdge (UnityEditor.Graphing.IEdge edge, System.Boolean useVisualNodeMap, System.Boolean updateNodePorts, System.Collections.Generic.Dictionary`2[TKey,TValue] lookupTable) (at ./Library/PackageCache/com.unity.shadergraph@17.0.1/Editor/Drawing/Views/GraphEditorView.cs:1287)
UnityEditor.ShaderGraph.Drawing.GraphEditorView.HandleGraphChanges (System.Boolean wasUndoRedoPerformed) (at ./Library/PackageCache/com.unity.shadergraph@17.0.1/Editor/Drawing/Views/GraphEditorView.cs:854)
UnityEditor.ShaderGraph.Drawing.MaterialGraphEditWindow.Update () (at ./Library/PackageCache/com.unity.shadergraph@17.0.1/Editor/Drawing/MaterialGraphEditWindow.cs:372)
UnityEditor.EditorApplication:Internal_CallUpdateFunctions() (at /Users/bokken/build/output/unity/unity/Editor/Mono/EditorApplication.cs:363)
Comments (6)
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
- Multiple exceptions are thrown after exiting Play mode when Layout Group component is displayed in Debug Inspector and Padding section is expanded
- ScrollView elements are not restored to their original positions after removing a Layout Group with Undo action
- "Assembly with name already exists" errors are thrown when two packages with different technical names resolve to the same namespace
- A Select Scene Entry is added to Undo History when Deleting while a Scene is selected in the Hierarchy
- The Add Component Menu's back arrow accumulates phantom levels when the Menu is repeatedly opened into a Category and closed without selecting
svenssone92
Nov 25, 2023 11:15
Upgrading from 2022.3.11f1 to 2022.3.14f1 solved it
svenssone92
Nov 25, 2023 10:41
I have the same problem on 2022.3.11f1
curkas
Oct 25, 2023 13:00
Can confirm. Specifically happens with connects relating to the Dither node
Technocyde
Oct 20, 2023 18:57
I too am receiving this error. Even on a fresh project it occurs.
LePaithon
Oct 20, 2023 13:43
Got the same issue
Omi
Oct 18, 2023 10:16
I found this page via web search. Can confirm I am getting the same issue on 2022.3.11f1.