Search Issue Tracker
By Design
Votes
0
Found in
2021.3.42f1
2022.3.42f1
6000.0.15f1
Issue ID
UUM-78031
Regression
No
DisplayInfo.WorkArea x and y values are not set when using 'Screen.GetDisplayLayout'
How to reproduce:
1. Ensure there are at least 2 monitors connected
2. Open the attached “IN-82146“ project
3. Open the "SampleScene" scene
4. Enter Play Mode
5. Observe the work area of each display logged in the Console
Expected result: x or/and y properties are different
Actual result: x and y properties are 0
Reproducible in: 2021.3.42f1, 2022.3.42f1, 6000.0.15f1
Reproduced on: Windows 11 (pro)
Not reproduced on: macOS 14.5 (Intel)
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
- GameObjects change Hierarchy order when undoing adding Component to multiple GameObjects
- [macOS] Editor crashes after entering Play mode with overlapping GameObjects with Cloth Component and Cloth Inter-Collision enabled
- Look Dev constantly regenerates the default Volume Profile when set to "None" instead of using the default one
- Look Dev errors are spammed when opening a new HDRP project when Look Dev was added to the layout in the previous project
- URP Scene Templates are not editable when first opened from the New Scene dialog
Resolution Note:
This API won't show how displays are aligned with respect to each other. The the DisplayInfo.WorkArea results for all displays will always show an x,y of zero as long as the Windows taskbar is aligned to the bottom or right edge. The work area is the area of the display not covered by the taskbar on Windows and Linux or the Dock/menubar on macOS.