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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
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.