Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4.0f1
2018.4.0f1
2019.1.0a1
2019.1.2f1
2019.2.0a1
2019.3.0a1
Issue ID
1155099
Regression
No
Display.SetRenderingResolution does not work
How to reproduce:
1. Open attached project "New Unity Project (2).zip"
2. Build the project
3. Run the build
4. Select any other resolution from the drop-down list
Expected result: Resolution of the second monitor is changed
Actual result: Resolution of the second monitor is not changed
Reproducible with - 2017.4.28f1, 2018.4.1f1, 2019.1.5f1, 2019.2.0b5, 2019.3.0a4
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
- Specular lighting visible in a camera with Path Tracing when Preserve specular lighting is disabled in observed material
- Cinemachine package throws CS1061 errors in the Console when installed in a project that has HDRP and URP installed
- Editor.log file size grows rapidly when a scene exceeds the "Maximum Shadow on Screen" limit setting in the HDRP Asset
- Player build freezes after calling Application.Quit() when the scripting backend is set to IL2CPP
- Texture is not applied on a Custom Render Texture when a Cubemap is selected as the texture
Resolution Note (2019.3.X):
This method is only supported for iOS, Android, and Universal Windows Platform (UWP); it was never implemented for Standalone builds (Windows, MacOS, and Linux).
At this time, there isn't any active development for Multi-Display, and only critical bugs or regressions will be addressed.