Search Issue Tracker
Fixed in 2017.1.X
Votes
0
Found in
5.6.0b3
Issue ID
875849
Regression
No
Screen.SetResolution works incorrectly when DPI scaling is set to anything else than 100% in windowed mode.
Workaround: divide 96 by logical DPI and then multiply that with the width and height of the resolution before calling Screen.SetResolution:
var width = 1920;
var height = 1080;
var dpiMultiplier = 96.0 / logicalDPI;
Screen.SetResolution((int)(width * dpiMultiplier), (int)(height * dpiMultiplier), false);
This bug does not manifest when setting resolution for fullscreen mode (when the last argument is true).
You can obtain logical DPI using this windows API:
https://msdn.microsoft.com/en-us/library/windows.graphics.display.displayinformation.logicaldpi.aspx?f=255&MSPPError=-2147217396
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "IndexOutOfRangeException" and "NullReferenceException" are thrown and Element disappears from UI Builder when undoing rename of element in "Open Instance in Context" menu
- Select Scriptable Object window freezes and becomes unresponsive when currently opened UXML Template is selected for binding's Data Source
- [Linux] “ReleaseButton expects buttonId >= 0” error is thrown when importing Assets via drag and drop
- Asset gets unselected and added Subgraphs list item is not undone when performing Undo in Heatmap with Default Values asset Inspector
- Black square “shadow” artifacts visible when using Screen Space Reflections without maximum smoothing
Add comment