Search Issue Tracker
Fixed in 2023.1.0a1
Fixed in 2022.2.0b3
Votes
0
Found in
2022.2.0a16
Issue ID
UUM-3649
Regression
Yes
[Win7] Getting "Failed to determine current display mode" errors when opening Build Settings window
To reproduce:
1. Create a new project
2. Open the Build Settings window
3. Make sure that the window is undocked
4. Observe the console
Reproduced on:
2022.2.0a16
Not reproducible on:
2022.2.0a15
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
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- 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
Resolution Note (fix version 2023.1.0a1):
Fixed by another internal issue: UUM-3700: "Failed to determine current display mode, falling back to main display mode." message is spammed when the editor is headless
Resolution Note (fix version 2022.2.0b3):
Fixed by another internal issue: UUM-3700: "Failed to determine current display mode, falling back to main display mode." message is spammed when the editor is headless