Search Issue Tracker
Fixed in 5.2.0
Votes
0
Found in
4.6.6p4
Issue ID
708877
Regression
No
[WSA] The resolution of the app doesn't take the display settings correctly
Reproducible on 4.6, 5.1 versions;
Attached repro screenshots;
Repro steps:
1. Open project "ResolutionBug.zip";
2. Build to WSA and deploy on Surface 3 tablet;
3. Minimize the app, then go to "Screen resolution" settings of the device;
4. Set the resolution to the lower or lowest and apply the resolution settings; (reproduces with resolution, when you get a warning that some items might not fit on the screen)
6. Go back to the game;
Expected result :
The game is still full screen and the inputs work correctly.
Actual result :
The game is displayed in the top left corner of the screen and the rest of the screen is black, while the inputs are still mapped to the right position in the screen, resulting in inputs not being over the visual of the objects.
Project info:
In project cubes and spheres in the scene are clickable and change color when clicked to demonstrate the offset in the inputs after changing the screen resolution.
Workaround: use recommended screen resolution;
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “EndRenderPass: Not inside a Renderpass” and other Render Graph errors in the Player when Render Graph is enabled and Overlay UI is used
- ScalableBufferManager does not work correctly when MSAA and RenderGraph Compatability are enabled
- Sprite artefacts appear when Sprite Packer is enabled
- Crash on ResizeScriptingList<ScriptingObjectPtr> when passing an undeclared variable to the results parameter for GameObject.FindGameObjectsWithTag
- [Android] "Screen.safeArea.y" always returns values outside of the Safe Area when the device is in Portrait orientation
Add comment