Search Issue Tracker
Fixed in 2020.1.X
Duplicate in 2019.4.X
Votes
0
Found in
2019.4
2019.4.26f1
Issue ID
1357758
Regression
No
Application crashes when relaunching it on a monitor with different DPI
Reproduction steps:
1. Open the attached "DPICrash.zip" project
2. Build the project
3. Open the built application on primary, lower resolution monitor
4. Use the UI to set FullScreenMode to 'Windowed'
5. Move the application to the primary, higher resolution & DPI monitor
6. Use the UI to select the primary monitor's resolution and set FullScreenMode to 'FullScreenWindow'
7. Click the 'Apply Resolution Settings' then 'Exit' buttons
8. Relaunch the application
Expected result: application opens on secondary monitor with selected resolution
Actual result: crash window immediately opens and closes within a second
Reproducible with: 2019.4.29f1
Not reproducible with: 2020.1.0a1, 2020.3.16f1, 2021.1.16f1, 2021.2.0b6, 2022.1.0a5
Notes:
1. Tested with 1920x1080 (primary, 100% DPI) and 2560x1440 (secondary, 150% DPI) monitors
2. If unable to set resolution to higher than primary monitor's, use the button on the right side as a workaround. (edit ChangeRes.cs script if not using 2560x1440)
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
- Test Runner’s vertical scrollbar overlaps with the up and down arrows and upper toolbar tabs when the window is minimized
- The Input Field view is not updated when deleting lines of text
- The scrollbar does not respect empty lines in the Input Field
- “Texture Atlas Viewer“ button text overlaps another button when the UI Toolkit Debugger is narrowed
- Thresholds are no longer automatically calculated after deleting Motion fields in Blendtrees
Resolution Note (fix version 2020.1):
Fixed in: 2020.1.0a1