Search Issue Tracker
By Design
By Design in 6000.5.X
Votes
0
Found in
6000.0.65f1
6000.3.3f1
6000.4.0b3
6000.5.0a4
Issue ID
UUM-131572
Regression
No
Playmode tint color is not overlaid, but instead replaces the original Editor color
How to reproduce:
1. Create and open a new project
2. Open Edit -> Preferences -> Colors
3. Open the Color Picker for "Playmode tint"
4. Change the alpha value from 1 to 0
5. Enter Play Mode
6. Observe the Editor
Actual result: The Editor colors change to pure black (in general, the tint replaces the original Editor color and is not overlaid)
Expected result: The tint is transparent and therefore not applied, and the original Editor color scheme is shown instead (in general, the tint is overlaid over the Editor and does not replace the original Editor color)
Reproducible in: 2023.1.0a1, 6000.0.65f1, 6000.3.3f1, 6000.4.0b3, 6000.5.0a4
Reproduced on: Windows 11 Pro (25H2)
Not reproduced on: No other environment tested
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
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
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.5.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.