Search Issue Tracker
Fixed
Votes
0
Found in
2019.4
2021.1
Issue ID
1347884
Regression
No
[Android] The object drawn with RenderLoopNewBatcher.Draw isn't captured by Frame Debug
Reproduction steps:
1. Open The attached project "New Unity Project.zip"
2. Open the Scene "test"
3. Build and Run
4. Run installed app.
5. In the Command Promt enter this command: "adb forward tcp:34999 localabstract:Unity-com.test.framedebug"
6. Open FrameDebug Window on Unity Editor and choose the connected mobile phone.
7. Click Enable button on FrameDebug Window.
Expected result: Both towers appear on the RenderLoopNewBatcher.Draw frame
Actual result: One tower appears on the Draw.Mesh frame
Reproducible with: 2019.4.13f1, 2021.1.0a1
Not reproducible with: 2019.4.29f1, 2021.1.0a2
Reproducible with:
VLNQA00277, Asus ROG Phone, Android: 8.1.0, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
VLNQA00030, Lge LG G2, Android: 4.4.2, CPU: Snapdragon 800 MSM8974, GPU: Adreno (TM) 330
VLNQA00006, Samsung Galaxy S7, Android: 8.0.0, CPU: Exynos 8 Octa 8890, GPU: Mali-T880
VLNQA00121, Samsung Galaxy S9, Android: 9, CPU: Exynos 9 Series 9810, GPU: Mali-G72
Not reproducible with:
Editor and Player on Windows 10
Notes:
- ADB has to be installed for the 5th step to work
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
- A shader error is thrown when building a project containing a material using "Bent normal map"
- Texture generator reference image fails despite valid size
- Agent mode can enter infinite execution loop
- AI Gateway responses contain duplicated sentences
- Texture 2D asset is created when promoting a generated Cubemap to a new asset
Resolution Note:
Fixed in 2021.1.0a2