Search Issue Tracker
Duplicate
Votes
0
Found in [Package]
Issue ID
1226430
Regression
Yes
[Graphview] Contents of Input fields to Matrix nodes disappear when moused over in complex shadergraphs or VFX graph
Reproduced in Version 2019.3.5f1 (d691e07d38ef)
Does not reproduce in Version 2019.2.6f1 (fe82a0e88406)
Reproduces in Version: 2020.2.0a2.295
Repro steps:
1. Download the attached shadergraph (bug works with any shadergraph with enough nodes)
2. Create a matrix3x3 node
3. Save the shadergraph
4. Close the shadergraph
5. Reopen the shadergraph
6. Mouse over all the fields on the matrix3x3 node
Expected results: the fields display normally
Actual result: they disappear or get mostly cut off, and stay that way until you change zoom levels
Note: switching to another shadergraph or the scene tab will make this bug stop reproducing. Pressing play and switching back to your shadergraph, or closing and reopening the shadergraph will make it reproduce again.
Also reproduces in VFX graph (see attached VFX graph file). If it doesn't reproduce in VFX graph make sure to zoom out before closing it and reopening it then zoom back in.
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
- UI Toolkit meshes are fully rendered and rasterized when opacity is 0
- Light rendering artefacts appear in the Editor when assigning unsupported 3D Custom Render Texture in Camera’s Output Texture, unclearable errors and warnings spammed
- Memory leak when running a test with "GfxThreadingMode" set to "SplitJobs"
- Loading Unloaded unsaved Scene throws “ArgumentException” error in the Console
- Crash on std::__1::__tree_const_iterator when opening the Build Profiles window in a specific project
This is a duplicate of issue #1222517