Search Issue Tracker
Feature Request
Feature Request in 2023.2.X
Votes
0
Found in
2020.3.43f1
2021.3.16f1
2022.2.2f1
2023.1.0a24
2023.2.0a1
Issue ID
UUM-21974
Regression
No
Unity OpenGLCore build crashes on UnityDisplayManager_SetDisplayParam when using Display.SetParams(...)
How to reproduce:
- Open the attached project “bug-openglcore-display.zip”
- Build And Run the project
Reproducible with: 2020.3.43f1, 2021.3.16f1, 2022.2.2f1, 2023.1.0a24
Reproducible on: Windows 10
Not reproducible on: macOS 13.0.1
First few lines of stacktrace:
(UnityPlayer) UnityDisplayManager_SetDisplayParam
(UnityPlayer) Display_CUSTOM_SetParamsImpl
(Mono JIT Code) (wrapper managed-to-native) UnityEngine.Display:SetParamsImpl (intptr,int,int,int,int)
(Mono JIT Code) UnityEngine.Display:SetParams (int,int,int,int)
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
- Icon section shows incomplete message and unusable check box in Build Profiles and Player Settings window instead of “Not applicable for this platform” for Dedicated Server Platform
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
Resolution Note:
Multi-display is only supported for DirectX graphics APIs. Converting this to a feature request for support on other graphics APIs (e.g. OpenGL , Vulkan)
Resolution Note (2023.2.X):
Multi-display is only supported for DirectX graphics APIs. Converting this to a feature request for support on other graphics APIs (e.g. OpenGL , Vulkan)