Search Issue Tracker
Fixed in 6000.2.0a9
Fixed in 6000.0.50f1, 6000.1.5f1, 6000.2.X, future release
Votes
0
Found in
2021.3.40f1
2022.3.38f1
6000.0.11f1
6000.1.0a7
6000.2.0a1
Issue ID
UUM-76080
Regression
No
Shader Graph Node Reference samples become dirty on opening
How to reproduce:
1. Open the "ShaderGraphET" project
2. Go to Assets -> Samples -> Shader Graph -> 17.0.3 -> Node Reference
3. Open any folder and open any Shader Graph in it
4. Observe the name of the opened Shader Graph
Expected results: There is no "" near the name
Actual results: There is a "" near the name and the Shader Graph needs saving
Reproducible with: 2021.3.40f1, 2022.3.38f1, 6000.0.11f1
Reproducible on: macOS 14.5 Sonoma (M1)
Not reproducible on: No other environment tested
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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Resolution Note (fix version 6000.0.50f1):
Shadergraph: Fixed additional cases where certain Node Reference sample graphs would report unsaved changes on open