Search Issue Tracker
Fixed in 2020.2.X
Votes
0
Found in
2019.3.9f1
2020.2.0a11
Issue ID
1248638
Regression
Yes
[Screen] Cutout values are not adjusted when device is in Windowed mode on Portrait orientation
Steps to reproduce:
1. Open attached project
2. Open "CheckAreasVisually" scene
3. Build and run on a device with some cutout (Like a notch or camera cutout)
4. Orient the device to Portrait mode
5. Click the button till the status indicates "Windowed" mode and the Navigation bar appears at the bottom
6. Observe the Red area (that indicates the cutout) disappear
Expected: Cutout Rect coordinates should be adjusted to match actual cutout on device once the Navigation bar appears
Actual: Cutout Rect coordinates are not adjusted and since the Navigation bar takes up some extra space, the Rect coordinates end up pointing to just outside the screen space
Reproduced on Unity:
2019.3.9f1 (658902c1d9e3)
2019.3.10f1 (5968d7f82152)
2020.1.0b9 (3f2ec5b3ee51)
2020.2.0a12 (a331b04b65b8)
Not reproduced on:
Version 2019.3.8f1 (4ba98e9386ed)
Tue, 31 Mar 2020 23:50:24 GMT
Branch: 2019.3/release
Devices tested on:
VLNQA00264, Samsung Galaxy S10+ (SM-G975F), Android 10, CPU: NOT FOUND, GPU: Mali-G76
N/A, Lge V40 ThinQ (LM-V405), Android 9, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
Most likely introduced by fix for https://fogbugz.unity3d.com/f/cases/1225672
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