Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.0.0-preview.14
Issue ID
1332726
Regression
No
[UI Toolkit] IMGUIContainer flickers when UI is updated in the Build
How to reproduce:
1. Open the user's attached "DragAndDropExample" project
2. Open the Scene "SampleScene"
3. Open the Build Settings (File->Build Settings...)
4. Press the "Add Open Scenes" button
5. Build And Run
6. Drag the "IMGUIContainer contents" box
Expected results: The box doesn't flicker
Actual results: The box flickers
Reproducible with:1.0.0-preview.11, 1.0.0-preview.14 (2020.3.7f1, 2021.1.6f1, 2021.2.0a16)
Could not test with: 2019.4.25f1 and earlier because the UI Toolkit package was not yet available, 1.0.0-preview.9 and earlier because the Build would be empty
Note:
- The issue has been tested and reproduced on Windows
- The issue is present only in the Build
- The flickering happens when the IMGUIContainer is dragged, when mouse is hovered over it, when mouse button is pressed, when any other container is dragged
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
- 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
Resolution Note:
The availability of the IMGUIContainer class in the UnityEngine assembly was needed for backward compatibility reasons. IMGUIContainers can be used inside the editor but usage outside the editor is unfortunately not something we can support.
While it may currently work in some use cases, proper runtime support for IMGUIContainer would need significant investment on our part because of issues like this one. It's unfortunately not something we plan on supporting in the foreseeable future.