Search Issue Tracker
Third Party Issue
Votes
0
Found in
2019.3
2019.3.3f1
2020.1
2020.2
Issue ID
1228623
Regression
No
Extra LoadAction in final FrameBuffer when using a SkinMeshRenderer
Steps to reproduce:
1. Download Snapdragon Profiler (Installers attached)
2. Open User-supplied project ("SkinnedMeshRender.zip")
3. Enable SkinMeshRenderer ( ASS_SCE_COM_ELFBRIDGE01_10080241_RoadC_MESH ) in the Main scene
4. Build and Run on an Android device.
5. Open the Snapdragon profiler and follow the steps attached by QA either in the image or the video.
6. Notice the GMEM sections at the bottom of the snapshot
Expected: they should be called once
Actual: they're called twice
Reproduced in: 2019.3.9f1, 2020.1.0b5, 2020.2.0a7
Reproducible with: OpenGLES3
Not reproducible with: OpenGLES2
Could not test with: Vulkan (Application keeps crashing)
Note:
There might be more tools to verify on other phones, but QA are not aware of them.
Reproduced on:
VLNQA00321, Xiaomi MI 9 (MI 9), Android 9, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
No repro on:
VLNQA00277, Asus ROG Phone (ASUS_Z01QD), Android 8.1.0, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630, iPhone SE 2, macOS
Can't test on
VLNQA00121, Samsung Galaxy S9 (SM-G960F), Android 9, CPU: Exynos 9 Series 9810, GPU: Mali-G72
VLNQA00288, Samsung Galaxy J7 (SM-J730F), Android 8.1.0, CPU: Exynos 7 Octa 7870, GPU: Mali-T830
VLNQA00021, Samsung Galaxy S7 (SM-G930F), Android 8.0.0, CPU: Exynos 8 Octa 8890, GPU: Mali-T880
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note (2020.2.X):
GPU drivers issue, caused by use of compute skinning. Reported to manufacturer.