Search Issue Tracker
By Design
By Design in 6000.4.X
Votes
0
Found in
6000.3.5f1
6000.4.0b5
Issue ID
UUM-132724
Regression
No
Visible color change delay in Scene view when changing Scene view Overlays color in Preferences window
Steps to reproduce:
1. Create new Unity project
2. Open Scene view window
3. Open Preferences window
4. Select “Overlays” section
5. Find “Scene view”
6. Click on color field
7. When color picker window opens, change colors
8. Observe Overlays in Scene view window
Actual results: When changing Overlays color, there is a delay in Scene view
Expected results: No delay in Scene view when chaning Overlays color
Reproducible with versions: 6000.3.5f1, 6000.4.0b5, 6000.5.0a4
Not reproducible with versions: 6000.5.0a5
Can’t test with versions: 6000.0.66f1 (No such functionality)
Tested on (OS): Windows 11, macOS Silicon Tahoe 26.2 (M1)
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
- Shader Graph Node information is briefly displayed in Graph Inspector when clicking on Category in the Blackboard
- Module installation fails with "Download failed: Validation Failed" errors when using beta.2 Hub version
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
- Shader Graph Category dropdown cannot be expanded/collapsed when clicking on the text
- Different text alignment in the column header in Entities "System" window
Resolution Note:
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.
Resolution Note (6000.4.X):
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.