Search Issue Tracker
Active
Under Consideration for 2021.3.X, 2022.3.X
Fixed in 6000.0.14f1
Votes
0
Found in
2021.3.40f1
2022.3.38f1
6000.0.11f1
7000.0.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
- Particle System 'Texture Sheet Animation' does not react to changes when changing textures in HDRP
- Asset instance duplicates when there is no dependency duplication between asset bundles
- The list remains orderable when NonReorderableAttribute is used
- The Physics Debugger displays incorrect Collision Volume when compared to its Collider bounds
- Errors are thrown when using stacking cameras with two different Renderer2DData
Resolution Note (fix version 6000.0.14f1):
Opened and re-saved all of the assets in the Node Reference sample in Unity 6 so they should no longer get marked as dirty when imported.