Search Issue Tracker
Fixed in 2021.3.29f1
Fixed in 2023.2.0a22
Votes
1
Found in
2021.3.23f1
2022.2.16f1
2023.1.0b13
2023.2.0a11
Issue ID
UUM-33432
Regression
Yes
Simulator view resolution doesn’t match the simulated device resolution when changing the view from “Game” to “Simulator”
How to reproduce:
1. Create a new project
2. Open the Game window
3. In the view dropdown menu, select “Simulator”
4. Observe the view
Expected result: Simulator view resolution is the same as a simulated device
Actual result: Simulator view resolution is not the same as a simulated device
Reproducible with: Built-in (2021.3.13f1, 2021.3.23f1, 2022.2.16f1, 2023.1.0b13, 2023.2.0a11)
Not reproducible with: 3.1.0-preview (2020.3.47f1), Built-in (2021.3.12f1)
Reproduced on: macOS 13.2.1 (Intel)
Notes:
Not reproducible after switching to Game view and back to Simulator view
Not reproducible after switching devices in Simulator
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
- 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
Resolution Note (fix version 2021.3.29f1):
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-30110
Resolution Note (fix version 2023.2.0a22):
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-30110