Search Issue Tracker
Fixed in 10.1.0-preview.3
Votes
0
Found in [Package]
Master (63ab00783d)
Issue ID
1264932
Regression
Yes
[Shadergraph] Setting a Texture2D from a valid texture to none does not propagate to downstream node previews or master preview
Also occurs in 9.x.x
Repro steps:
1. Open a shadergraph
2. Create a Texture2D property
3. Drag it onto the graph
4. Create a Sample Texture 2D node and plug in the property
5. Change the property's texture to a valid texture
6. change the property's texture back to none
Expected result: the sample texture 2D's preview is changed to white
Actual result: the sample texture 2D's preview still has the old texture. Disconnecting and reconnecting the property doesn't fix this. The incorrect preview propagates to downstream node previews and, if plugged into base color, the master preview as well (this does not reproduce on 8.2.0, making this bug unique to 9.x.x and 10.x.x) Saving, closing and reopening the shadergraph fixes the problem.
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