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
- ArgumentOutOfRangeException when manipulating the Project Settings search bar
- [Linux] Touch freezes in Player when any mouse button is clicked
- UnityEngine.Rendering.Volume.OnEnable() is called twice before OnDisable() creating multiple copies of the same volume when a volume is enabled right after Domain Reload when entering Play Mode
- Hinge Joint transforms are reset when toggling the "useMotor" property
- Motion Vector texture reports incorrect Mesh data when Mesh is coming from off-screen
Add comment