Search Issue Tracker
By Design
Votes
0
Found in
2018.3.9f1
Issue ID
1139232
Regression
No
Android Vulkan corrupted rendering when there is no camera in the scene
Steps to reproduce:
1. Open attached project
2. Build for Android
-Rendering is incorrect(see image)
Reproduced on: 2018.3.10f1, 2019.1.0b8, 2019.2.0a9
Note: Development build has a 100% reproduction rate while non-development build reproduces this behaviour 1 in 10 times
Devices under test:
Reproduced with:
VLNQA00015, Samsung Galaxy Note8 (SM-N950W), 8.0.0, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00218, Samsung (SM-N960U), 8.1.0, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
VLNQA00257, Sony Xperia XZ Premium (G8141), 8.0.0, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
N/A, Xiaomi (POCOPHONE F1), 9, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note:
If there is no camera in the scene, the backbuffer is not cleared. This is undefined behaviour, and results in noise on Adreno GPUs.