Search Issue Tracker
Fixed in 2021.2.X
Fixed in 2021.1.X
Votes
0
Found in
2020.1.17f1
2021.2.0a10
Issue ID
1322862
Regression
No
[Device Simulator] When render outside safe area is disabled, rendered part in Device Simulator doesn't match real devices
How to reproduce:
1. Create a new project
2. Switch game view to Device Simulator
3. Select a device which has a notch, like Samsung S10e
4. Go to Player Settings > Android > Resolution and Presentation
5. Disable "Render outside safe area"
6. Keep "Start in fullscreen mode" enabled
7. Play the scene
Actual result: everything is rendered
Expected result: the area where is notch shouldn't be rendered
8. Disable "Start in fullscreen mode"
9. Play the scene
Actual result: after rendering around notch is fixed when running in windowed mode, notch area is rendered
Expected result: the area where is notch shouldn't be rendered (navigation bar is not rendered and that works correctly)
Reproducible: 2020.1.17f1.4949, 2020.2.7f1.4104, 2021.1.0f1.2163, 2021.2.0a10.1508
Tested using Device Simulator package 2.2.4-preview and Device Simulator whic is in coreh
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment