Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
0
Found in
2019.3.0a12
2020.1.0a1
Issue ID
1178393
Regression
Yes
Duplicate IMGUIContainer element is created for the InspectorElement
How to reproduce:
1. Open the attached project named Case_1178393
2. Double click on the "DemoGraph" located at Assets/Plugins/NodeGraph/Resources
3. Observe the node data fields
Expected result: Nodes don't have duplicate fields
Actual result: Nodes contain duplicate fields
Reproducible with: 2019.3.0a12, 2019.3.0b1, 2020.1.0a1
Not reproducible with: 2019.3.0a8, 2019.3.0a11
Could not test with: 2017.4.32f1, 2018.4.7f1, 2019.2.2f1, 2019.3.0a7 (Some of the referenced API classes were not available)
Notes:
Inspecting nodes UIElements Debugger shows that the InspectorElement has duplicate IMGUI containers.
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