Search Issue Tracker
Fixed in 7.2.X
Votes
0
Found in [Package]
7.1.7
Issue ID
1215494
Regression
Yes
[Shadergraph] Subgraphs break when copied from one project into another (GUId error)
Several subgraphs break when copied from one Unity Project into another. The error reported has to do with GUID.
This is a serious problem because it means collections of subgraphs can't be distributed as shareable libraries.
For instance from project
https://github.com/mmikk/Surfgrad-Framework-Unity-Shadergraph.git
Repro step:
1. Copy Assets\Subgraphs from this project into the new project.
2. Create a new shader graph.
3. Add the subgraph: Triplanar to surfgrad.
The project was made with unity 2019.3.0b4 and Package 7.1.7. They assets have to come from 7.1.7, otherwise this doesn't reproduce.
In this instance the new project was created on a different computer (still windows) and with 2019.3.0f5 but still Package 7.1.7.
Several of the subgraphs are breaking. An instance of Triplanar to surfgrad is just one example. Essentially any subgraph which uses other subgraph(s) in its graph breaks from what I can tell.
Note: Importing and exporting subgraph collections using .unitypackage file formats will maintain guid references between projects. Please use .unitypackage files to move subgraphs from one project to another until we can resolve this issue.
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
- “Cache Management” text is misaligned in Preferences > Package Manager
- [macOS] network permission shows the name of previously closed app when different app requests network access
- Delta value returned by mouse movementsMonitor is different when changing Screen Resolution
- The Radius Scale option is removed from the Visual Effect Graph Output Particle when Lod is disabled in Particles Options
- Visual artifacts appear when the HD Dynamic Resolution Component changes the resolution scale
Resolution Note (fix version 7.2):
Resolved as Fixed seeing as the issue doesn't repro from 7.2 onwards.