Search Issue Tracker
Fixed in 2018.2.X
Votes
0
Found in
5.6.1f1
Issue ID
913963
Regression
No
Screen.dpi is not consistent in the Editor when using monitors of different dpi scalings
Steps to reproduce:
1. Make sure you have monitors of different DPI scalings (e.g 4k and 1080p)
2. Download and open the attached project
3. Enter Play mode
4. Click between different windows in different monitors
5. Observe console
Expected result: dpi reports consistently depending on a single factor( last (or first) created game window)
Actual result: dpi is based on where game windows are created, when and where scene windows are created, and when and where input is captured
Only reproducible on 5.6.1f1 due to Case 920841
Comments (1)
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
- PlayerPrefs get corrupted when a minimized fullscreen Player is closed through the Taskbar
- "To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations." warning is printed when JobTempMemoryLeakValidation switch is enabled
- Main Thread stalling when loading Audio Source asset asynchronously while preloading another Audio Source asset
- Material artifacts occur in the Material Preview window when baked lighting is applied to scenes
- “ArgumentOutOfRangeException” after saving, reseting and re-add Default Tile Palette Tools to the list in Preferences window
andrewsinn
Jan 27, 2025 18:07
The discussion about inconsistent DPI scaling in multi-monitor setups highlights a critical challenge for developers working with diverse hardware. It’s a reminder of how nuanced technical issues can impact user experience. For those navigating similar complexities in health, this detailed guide on HRT and weight management is an excellent resource: . It offers clear insights and actionable advice, helping individuals better understand their health journey.