Search Issue Tracker
Won't Fix
Won't Fix in 2023.1.X
Votes
0
Found in
2020.3.44f1
2021.3.17f1
2022.2.3f1
2023.1.0a26
Issue ID
UUM-25483
Regression
No
Project Settings window is black when changing Color Space from Gamma on Vulkan
Reproduction steps:
1. Open project “RefProbe-RGBM-URP”
2. Make sure “Edit\Project Settings\Player\Other Settings\Graphics APIs for Windows” is set to Vulkan
3. While “Edit\Project Settings\Player\Other Settings\Color Space” is set to Gamma, select the dropdown to see other options
Expected result: The Project Settings window is not black
Actual result: The Project Settings window is black (may also crash)
Reproducible with: 2020.3.44f1, 2021.3.17f1, 2022.2.3f1, 2023.1.0a26
Reproducible on: Windows 11
Not Reproducible on: macOS Catalina 10.15.7 (Intel)
Note: not reproducible when using Direct3D11 Graphics API
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:
We understand that this is an issue but have decided to not fix it. Our decision is based on a combination of factors:
1. Limited Resources: Our development team is currently fully engaged in high-priority projects, and we don't have the resources to allocate to this issue.
2. Low User Impact: This bug's impact on users appears to be minimal, and it hasn't caused widespread issues or dissatisfaction.
3. Higher Priorities: We must focus our resources on projects critical to our product's growth and success.
Resolution Note (2023.1.X):
We understand that this is an issue but have decided to not fix it. Our decision is based on a combination of factors:
1. Limited Resources: Our development team is currently fully engaged in high-priority projects, and we don't have the resources to allocate to this issue.
2. Low User Impact: This bug's impact on users appears to be minimal, and it hasn't caused widespread issues or dissatisfaction.
3. Higher Priorities: We must focus our resources on projects critical to our product's growth and success.