Search Issue Tracker
Won't Fix
Won't Fix in 2023.1.X
Votes
0
Found in
2021.3.17f1
2022.2.3f1
2023.1.0a26
Issue ID
UUM-26313
Regression
No
GameObject color in Scene window is different than in Color preview window
Reproduction steps:
1. Open the attached “RectangleBliss.zip“ project
2. Open “SampleScene” scene
3. Enter Play mode and press “esc” keyboard button
4. Click “Load” and “This will replace canvas with a save are you sure?” buttons and select “Colorbug.canvas” file
5. Go to Scene window and select black rectangle (refer to the reproduction video)
6. Open its Color preview window and observe it
Expected result: Black rectangle color in Color preview window and Scene window is the same
Actual result: Black rectangle color in Color preview window is green but in Scene view it shows up as black
Reproducible with: 2021.3.17f1, 2022.2.3f1, 2023.1.0a26
Could not test with: 2020.3.44f1 (Due to errors in the Console window)
Reproduced on: macOS Monterey 12.6 (Intel)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Thank you for bringing this issue to our attention. After careful consideration, we have determined that this issue is not aligned with our current development priorities and focus areas. As such, we have decided not to invest time and resources into addressing it. We appreciate your input and understanding, and please let us know if you have any other concerns or issues you would like to report in the future.
Resolution Note (2023.1.X):
Thank you for bringing this issue to our attention. After careful consideration, we have determined that this issue is not aligned with our current development priorities and focus areas. As such, we have decided not to invest time and resources into addressing it. We appreciate your input and understanding, and please let us know if you have any other concerns or issues you would like to report in the future.