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
- Crash on mecanim::SetValueWeight when switching the AnimationMixerPlayable connection with Animator's UpdateMode set to "Animate Physics"
- The "StringComparer.InvariantCultureIgnoreCase.GetHashCode()" returns different Hash Codes for the same word with the only difference being case sensitivity in WebGL
- 2D Light Textures show the lights of any 'blend style' index higher than theirs (if present) when they aren't visible by the Camera using Render Graph
- [SpeedTree] Wireframe mode not rendering correctly ST assets
- Light2D affecting only the Default Sorting Layer will also affect any Custom Lit Sprite not on that Layer when using Render Graph
Add comment