Search Issue Tracker
Fixed in 2021.1.X
Votes
0
Found in
2019.3
2019.3.7f1
2019.4
2020.1
2020.2.0a1
Issue ID
1261567
Regression
No
[Android][Vulkan] Frame Debugger on Android shows up as a white background with incorrect texture information
Reproduction steps:
1. Open the "SampleScene" Scene in the attached "1261567.zip" project
2. Switch the build platform to Android
3. Build and Run to an Android Device
4. Enable Frame Debugger and set the target platform to debug from to Android Player
5. Inspect the frames on the device
Expected result: the Frame Debugger lets you step through in great detail how the Scene is constructed from its graphical elements
Actual result: the Frame Debugger shows only a white background with slight gray image textures throughout debugging
Reproduces on: 2019.3.16f1, 2019.4.5f1, 2020.1.0f1, 2020.2.0a1
Not reproducible on: 2020.2.0a2
Could not test with: 2018.4.25f1 (Multithreaded rendering is on, however, the console error shows up saying that it is disabled when enabling the Frame Debugger, tested on an LWRP Template since URP was not introduced in 2018.4)
Reproducible on:
VLNQA00320, Xiaomi - (Redmi Note 8 Pro), Android 9, CPU: MediaTek Helios G90T MT6785T, GPU: Mali-G76 MC4
Note: Reproducible on Vulkan only
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.1):
fixed in: 2020.2.0a1