Search Issue Tracker
Fixed in 2021.3.24f1
Fixed in 2021.3.X, 2022.2.X, 2023.1.X, 2023.2.X, 2023.2.0a10
Votes
0
Found in
2023.1.0a6
2023.2.0a1
Issue ID
UUM-1589
Regression
No
[Linux] DisplayInfo.WorkArea ignores resolution scaling when working with multiple displays
How to reproduce:
1. Open the attached project named "desktop-move-window-sample-main.zip"
2. Open "SampleScene"
3. Build and Run
4. Press the ESC key
5. Enter Windowed mode
6. Move the Player window to the secondary screen
7. Press the "Snap to bottom right" button
Expected results: Player window snaps to the bottom of the secondary screen regardless of the resolution scaling used
Actual results: Player window does not snap to the bottom of the screen, ignoring the applied resolution scaling
Reproducible with: 2021.2.0a16, 2021.2.0b5, 2022.1.0a4
Couldn't test with versions older versions as MoveWindowAPI was introduced in 2021.2.0a16
Notes:
1. A 4K primary display with 200% resolution scaling and a 1080p secondary display were used for testing
2. Tested on Ubuntu 20.04
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment