Search Issue Tracker
Won't Fix
Won't Fix in 2021.3.X
Votes
0
Found in
2021.3.32f1
Issue ID
UUM-57232
Regression
Yes
Shader Editor throws an ArgumentNullException when trying to open a ".shadergraph" file
Reproduction steps:
1. Open the user-attached "PhantomPeakArcadeMachines" project
2. In the Project window, search "shader"
3. Double-click on "OlympicsBgShader.shadergraph" to open the Shader Editor
4. Observe the outcome
Expected results: Shader Editor opens in Unity Editor without errors
Actual results: Shader Editor throws an ArgumentNullException and asks to "Select an app to open this .shadergraph file"
Reproducible with: 2021.3.32f1, 2022.2.0a8
Not reproducible with: 2022.3.14f1, 2023.2.1f1, 2023.3.0a15
Fixed in: 2022.2.0a9
Reproducible on: Windows 11 Pro
Not reproducible on: No other environments tested
Notes:
- Unable to reproduce the issue on a new project
- The issue happens with any “.shadergraph” file
- Deleting the Library folder fixes the issue
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
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
Resolution Note:
Although it was possible to repro the issue using the project provided, deleting the library folder restored the project to a functional state. It's unclear what the root cause for this issue was, but we've been unable to reproduce this issue otherwise.
Resolution Note (2021.3.X):
Although it was possible to repro the issue using the project provided, deleting the library folder restored the project to a functional state. It's unclear what the root cause for this issue was, but we've been unable to reproduce this issue otherwise.