Search Issue Tracker

By Design

Votes

0

Found in

2021.3.8f1

2022.1.14f1

2022.2.0b6

2023.1.0a8

Issue ID

UUM-13067

Regression

No

Framerate drops on some Android devices when using a custom shader

-

Reproduction steps:
1. Open the user's attached "AndroidShaderPerformanceIssue-2021.3.zip" project
2. Build and Run for Android
3. Observe the "FPS" and "GPU" counters displayed in the Scene

Expected result: FPS: >=30, GPU: <=30
Actual result: FPS: 7-15, GPU: 80-160

Reproducible with: 2021.3.9f1, 2022.1.15f1, 2022.2.0b7, 2023.1.0a9
Couldn’t test with: 2020.3.39f1 (pink textures after downgrade)

Reproducible with these devices:
Huawei - (ELS-NX9), Android 10, CPU: HiSilicon Kirin 990 5G, GPU: Mali-G76
Samsung Galaxy S10+ (SM-G975F), Android 10, CPU: NOT FOUND, GPU: Mali-G76
Samsung Galaxy S9 (SM-G960F), Android 10, CPU: NOT FOUND, GPU: Mali-G72

Not reproducible with these devices:
Samsung Galaxy S22 (SM-S901B), Android 12, CPU: Exynos 2200, GPU: Ltd.
Samsung Galaxy Z Flip3 5G (SM-F711B), Android 12, CPU: Snapdragon 888, GPU: Adreno (TM) 660
iPhone 13 (iOS 15.0) - 30FPS; 26ms GPU

Not reproducible with: Windows Standalone

Reproducible with: Vulkan and OpenGLES3 Graphics APIs

Tested with: Windows 10

Note: Going to Assets/Game/Art/Shaders/CustomIncludes/CustomLitInput.hlsl and commenting 1099-1107 lines fixes the issue

  1. Resolution Note:

    The performance and scalability of custom shaders is responsibility of user.

Log in to vote on this issue

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.

Latest issues

See all new issues