Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.32f1
2022.3.12f1
2023.1.19f1
2023.2.0b16
2023.3.0a12
Issue ID
UUM-55082
Regression
No
Menus and buttons in the Toolbar do not change colour together with the "Playmode tint" setting when it is changed during Play mode
Steps to reproduce:
1. Create a new project
2. Enter Play mode
3. Go to Edit > Preferences… > Colors and change the “Playmode tint” under the “General” category
4. Observe the colour of the menus and buttons in the Toolbar
Expected result: The Toolbar menus and buttons are affected by the new “Playmode tint” colour immediately like the rest of the Editor’s UI
Actual result: The Toolbar menus and buttons do not update until the user hovers over them or Play mode is restarted
Reproducible with: 2021.3.32f1, 2022.3.12f1, 2023.1.19f1, 2023.2.0b16, 2023.3.0a12
Reproduced on: Windows 11 Pro (22H2)
Not reproduced on: No other environment tested
Note: When entering Play mode, the Toolbar menus and buttons update their colour later than the rest of the Editor’s UI regardless if the “Playmode tint” was changed before or not
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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Resolution Note:
Thank you for bringing this issue to our attention. After careful consideration we will not be addressing your issue at this time, as we are currently committed to resolving other higher-priority issues. Our priority levels are determined by factors such as the severity and frequency of an issue and the number of users affected by it. We know each case is different, so do please continue to log any issues you find, as well as provide general feedback.