Search Issue Tracker
Fixed
Fixed in 6000.2.7f1
Votes
3
Found in
6000.2.0f1
Issue ID
UUM-113577
Regression
No
Setting World Space UI root element Style to None distorts the elements instead of hiding them
Steps to reproduce:
- Open the attached project
- Open the Sample Scene
- Click the "Hide UI" Button in the World Space Panel
- Observe the Game view
Actual results: World Space UI elements become distorted and remain visible
Expected results: World Space UI UI elements become hidden
Reproducible with versions: 6000.2.0a9, 6000.2.0f1
Not reproducible with versions: 6000.3.0a1, 6000.3.0a4
Can’t test with versions: 6000.2.0a8(World space UI buttons do not trigger when clicked, possibly due to the feature being experimental in those versions)
Tested on (OS): macOS 15.5
Notes:
- Reproduced the issue using Button click events. Setting Style to None inside Awake/Start/Update methods works as intended
- ScreenSpace UI elements function as expected
Comments (3)
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
- [WebGPU] error with compute shader and read-only RWTexture
- Capacity-size memory is copied instead of Length-size when using UnsafeUtility.memCpy()
- Console displays "SerializedObjectNotCreatableException: Object at index 0 is null" error during Unity theme change while "Tile Palette" window is opened
- Details are not shown when Error Message is still selected after changing Log Entry Count in the Console
- Disabling Unity VCS in Project Settings unfocuses the Project Settings Window
freyzorr
Aug 27, 2025 11:25
I have experienced this as well. Setting a root element as display None will still render the elements but the position changed and the elements are distorted and misaligned. Like it's failing to cull the elements and using uninitialized matrices when rendering.
dunebeetle
Aug 24, 2025 11:06
Also forgot to mention that the crashing only happens when Play mode settings are set to "Do not reload Domain or Scene".
dunebeetle
Aug 24, 2025 10:40
I've experienced this. I've also experienced consistent, repeatable hard editor crashing when setting style.display = DisplayStyle.None for root in Awake(), Start(), and Update() in the element's frame 0. Waiting till next frame does not crash.
I believe a workaround for all of the above is to create a sub-root and use that instead of the actual root.