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
- Build fails when building a project containing an 18+ dimension array with IL2CPP
- [Android][Sentis] Human poses are not detected when using the BlazePose model
- Sprite Editor Outline Tool Overlay is not displayed when no Sprite is selected
- “No method with RuntimeInitializeOnLoadMethod attribute” warning from ReadmeEditor.cs is thrown after installing Project Auditor Rules
- Projection matrix is altered when using RasterCommandBuffer.ClearRenderTarget on DX12 and Metal
Add comment