Search Issue Tracker
Won't Fix
Votes
1
Found in [Package]
2019.4
2020.1.17f1
2020.2
2021.1
2021.2
Issue ID
1316351
Regression
No
Missing reference error when moving a ShaderGraph with Sub Graphs to a project that has the same Sub Graphs under different GUID
How to reproduce:
1. Open the attached project (case_1316351-SubGraphReference)
2. Add the attached file SHADER_GRAPH.shadergraph to the assets
3. Open SHADER_GRAPH
4. Observe Could Not Find Sub Graph Asset with GUID error
Expected result: SHARED_GRAPH retains the reference or it's possible to seamlessly replace the lost Sub Graph with the new one
Actual result: The reference to the Sub Graph is lost and there's no way to replace it
Reproducible with: 7.5.3 (2019.4.21f1), 10.3.1 (2020.2.6f1), 11.0.0 (2021.1.0b8), 12.0.0 (2021.2.0a6)
Could not test with: 4.1.0-preview (2018.4.32f1) (shader graphs do not open)
Notes:
1. In 2019.4 the error appears in the ShaderGraph itself, in later versions the error only appears in the console
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
- Too little validation messages in the "WebAssembly Language Features" Memory settings
- Project Settings Search Highlights are misaligned when using the Bitmap Text Rendering Mode
- "GetControlID at event ValidateCommand returns a controlID different from the one in Layout event" Warning is thrown when undoing the deletion of Sprite Shape Profile
- Memory related fields in the "WebAssembly Language Features" can be set to the negative numbers
- "WebAssembly Language Features" Header in the Player Settings has a smaller indentation
Resolution Note:
Nice catch, thanks for bringing it to our attention. We've added a feature request for the ability to re-attach subgraphs to our backlog and will address it in a future update.