Search Issue Tracker
Fixed in 2017.1.X
Votes
4
Found in
5.5.0p3
Issue ID
870209
Regression
No
Screen.dpi returns primary displays dpi when application is on secondary display
Steps to reproduce:
1. Prepare a two monitor setup each with different DPI
2. Open attached project "870209.zip"
3. Build standalone
4. Launch standalone in windowed mode on your Primary display and observe screen dpi
5. Move application to secondary display and observe screen dpi
Result: screen dpi didn't change
6. Close application
7. Launch standalone in windowed mode on your Secondary display and observe screen dpi
Result: Screen.dpi returns Primary screen dpi
Expected result: Screen.dpi returns current displays dpi
Tested on Windows machine (primary screen full HD, secondary - 4k)
Reproducible with: 5.3.6f1, 5.4.4p1, 5.5.0p4, 5.6.0b4
Also reproducible in Editor, Windows standalone, WSA
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Add comment