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
- Spring Joint shows only one anchor gizmo in Scene view when "Auto Configure Connected Anchor" is enabled
- Crash on _platform_memmove after entering large value in Graphics settings Preloaded Shaders field
- Disproportionally large impact on CPU frame time when writing to a rendering entity's LocalToWorld
- "Constant Force" Component numeric fields drift out of view while entering a really big value in the Inspector
- Scene view camera speed pop-up appears empty or cut off when Scene view is very narrow
Resolution Note (fix version 6000.0.50f1):
Shadergraph: Fixed additional cases where certain Node Reference sample graphs would report unsaved changes on open