Search Issue Tracker
Fixed
Votes
0
Found in
6000.0.15f1
6000.0.28f1
6000.1.0a5
Issue ID
UUM-87798
Regression
Yes
Constant console errors when using Min/Max Slider in PlayMode
Steps to reproduce:
- Open a Unity Project
- Create a UI Document Asset via Assets > Create > UI Toolkit > UI Document
- Create a Panel Settings Asset via Assets > Create > UI Toolkit > Panel Settings Asset
- Open the created UI Document Object
- Add a Min/Max Slider to the document by dragging it from the Library to the Hierarchy
- Save and then close UI Builder
- Create an empty GameObject in your scene via GameObject > Create Empty
- Add a UI Document Component to this GameObject
- Assign your created Panel Settings Asset and UI Document Asset to the component
- Enter PlayMode
- Change the values of the Min/Max Slider
Actual results: There are constant 'Layout update is struggling to process current layout' errors logged to the console while using the Min/Max Slider
!image-2024-11-19-13-31-58-077.png|width=1261,height=107!
Expected results: There are no errors when using the Min/Max Slider in PlayMode
Reproducible with versions: 7000.0.0a8, 6000.1.0a5, 6000.0.28f1, 6000.0.15f1
Not reproducible with versions: 6000.0.14f1, 2022.3.53f1, 2021.3.45f1
Can’t test with versions: -
Tested on (OS): MacOS Sonoma 14.6.1
Notes: -
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
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
Resolution Note:
Fixed by another internal issue: UUM-84683: MinMaxSlider seems to cause "Layout update is struggling to process current layout"