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
- InspectorElement and AnimationMode memory leak when selecting different GameObjects in the Hierarchy with the Inspector tab open
- Previous model to world matrix is not correctly set for ASW
- More calls are made to GC.Alloc in an HDRP Sample Template when compared to the 2022.3 stream
- Generating Light Probe lighting returns inconsistent results on a specific mesh
- Two Warnings appear for every Soft Delete Operation when Deleting Sub Assets in the Project Browser
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.