Search Issue Tracker
Fixed in 10.x.x
Votes
0
Found in [Package]
master (9f5e9796ac)
Issue ID
1261419
Regression
No
[Shadergraph] Virtual Texture: deleting a layer and then plugging in extra output of Sample Virtual Texture softlocks graph
Needs to be fixed for 9.x.x as well as 10.x.x
Repro steps:
1. Open a shadergraph
2. Create a Virtual Texture property
3. Drag out the output and create a Sample Virtual Texture node
4. Add a layer to the property
5. Unplug and re-plug the virtual texture property into the Sample Virtual Texture node so the outputs update
6. Delete a layer on the property
7. Plug the last output of the Sample Virtual Texture Node into any input on the master stack
Expected result: the number of outputs update when the property updates, or at least the graph doesn't softlock
Actual result: the graph softlocks
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- 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
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment