Search Issue Tracker
Won't Fix
Won't Fix in 2023.3.X
Votes
0
Found in
2023.2.0b5
2023.3.0a4
Issue ID
UUM-46768
Regression
Yes
Shader Graph asset icons are shown incorrectly after reimporting the project library
Shader Graph asset icons are shown incorrectly after reimporting the project library.
Or after say, cloning a project from github for example!
Or downloading a repro project from a remote drive...
Generally, the icons appear again, correctly, after you open and save the shader graph asset once.
Repro steps:
- download the attached project [https://drive.google.com/file/d/1u2UPlJULOjRtKe-hwUOeKcOGXwvVUIu4/view?usp=sharing]
- open it with the latest 2023.2 (it was created with 2023.2.0b2)
- notice that the shader graph shaders assets have the regular shader asset icon, not the blue shadergraph one
Expected result: The assets should have the correct asset icon.
Reproducible with 2023.2.0b2 and Shadergraph version 16.0.3
Cannot repro with 2023.1.071 and ShaderGraph version 15.0.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
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
Resolution Note:
We'll keep on eye on this issue, but I think we'll address it as a larger set of changes we're planning to make to our asset handling. As we won't address this as a single issue, I'm closing it out for now.
Resolution Note (2023.3.X):
We'll keep on eye on this issue, but I think we'll address it as a larger set of changes we're planning to make to our asset handling. As we won't address this as a single issue, I'm closing it out for now.