Search Issue Tracker
Not Reproducible
Votes
0
Found in [Package]
8.0.1
Issue ID
1232472
Regression
No
[Shadergraph] Shadergraph softlocks when reloading shadergraph with updated subgraph Texture2D output
Bug reproduces on Master (commit 33cd9986fd tested)
Bug reproduces on 8.0.1 release
Bug does not reproduce on 7.3.1, likely due to lack of implementation on shadergraph reloading on subgraph changes.
Repro steps:
1. Open attached project
2. Open softlock.shadergraph and softlock.subgraph
3. in softlock.shadergraph, drag out the edge from the subgraph's texture2d output to a sample texture 2D node. Do not save the graph.
4. Switch to softlock.subgraph. Change the texture2D output slot to a vector1 output slot. Save the subgraph.
5. Switch to softlock.shadergraph. When it asks to reload, choose yes. Do not save the graph.
6. Switch back to softlock.subgraph. Change the second vector1 output slot (the one you changed from earlier) back to a texture2d slot. Save the subgraph.
7. Switch back to softlock.shadergraph. When it asks to reload, choose yes. Do not save the graph.
8. Drag the edge out from the subgraph's texture2d output to a sample texure 2D node again.
Expected result: no error is thrown, graph is not softlocked
Actual result: graph softlocks, error thrown
Note: this is worth looking into, as even though these are the only steps I found to make this bug happen, there may be alternate steps that will trigger the same bug.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] The Player freezes when disabling Bluetooth while connected to the headphones
- Addressable bundles are not retrieved from the cache when a WebGL Player is refreshed
- Sprites are incorrectly occluded by Sprite Physics Shape culling when behind in sorting order
- CPU usage is increased when the Editor is idle with the ProBuilder Package installed
- Unstable lighting when additional light sources are added in Shader Graph nodes
Add comment