Search Issue Tracker
Won't Fix
Votes
0
Found in
2020.1.0a19
2020.2.0a4
Issue ID
1228944
Regression
Yes
[Android] [Vulkan] Distorted screen when trying to change orientation
Steps to reproduce:
1) Download attached project and open in Unity
2) Make sure Vulkan is the only Graphics API in the list
3) Build and Run project on a device
4) Rotate device (change orientation)
Note: for a second or two screen will be distorted (check attached video)
Reproduced with:
2020.1.0a19, 2020.1.0a20, 2020.1.0b2, 2020.2.0a4
Not reproduced with:
2019.3.6f1, 2020.1.0a12, 2020.1.0a16, 2020.1.0a18
Regression since:
2020.1.0a19
Devices under testing:
Reproduced with:
VLNQA00010, Galaxy S8, CPU Snapdragon 835 MSM8998, GPU: Adreno 540, OS: 7.0.0
Not reproduced with:
VLNQA00217, Razer2, CPU: Snapdragon 845 SDM845, GPU: Adreno630, OS: 9.0.0
VLNQA00268, Galaxy S10+, CPU: Exynos 9 9820, GPU: Mali-G76, OS: 9.0.0
VLNQA00099, Pixel XL, CPU: Snapdragon 821 MSM8996 Pro, GPU: Adreno 530, OS: 9.0.0
VLNQA00006, Galaxy S7, CPU: Exynos 8 Octa (8890), GPU: Mali-T880, OS: 8.0.0
Note: Gles3 works fine
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
- Component Glyphs value is truncated and Ligature Table glyph fields become inaccessible when increasing the Component Glyphs count
- There is no “Overwrite Preset?” popup when saving a Customizable Toolbar preset with a name that already exists
- Customizable Toolbar preset does not switch to the Unity Default Preset when Reverting All Saved Presets or deleting the active Preset
- New Hierarchy visibility and pickability icon behavior differs from documentation
- [Usability] Selected node gets unselected when undoing changes in the Graph Inspector Node Settings tab
Resolution Note (2020.2.X):
This particular case has been investigated thoroughly and we have decided, in the interests of protecting the stability and features of Unity for users that rely upon the affected versions, to not address this fix for the time being. We understand that this will cause problems for some users, and so may address in a future version.