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
- Keywords on Material Variants aren't automatically saved when changed on original Material through Shader Graph
- Light Probes get baked when calling LightProbes.Tetrahedralize
- Shadows flicker and cause visual artifacts when modifying a GameObject's bounds using Swizzle (Y Mask) and Sine Time nodes
- [WebGL] Frame rate drops by 5-20 fps when moving cursor or touch input in the Player
- Light bleeds when using box shaped spotlight with specific Emission Range values
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.