Search Issue Tracker
Active
Votes
1
Found in
2022.3.0f1
Issue ID
UUM-40387
Regression
No
[Forward+] GPU Frame Time is bad on Android Vulkan, when object covers a lot of screen pixels
Peter is aware of this issue and he says he will look into this after vacation.
*Steps:*
# Open attached project (ForwadPlusAndroidPerf2.zip)
# Switch to Android platform
# Open Repro scene
# Depends on what you want to test, enable the light / camera objects
# Make player build on Android Vulkan
# Open profiler and observe *GPU Frame Time* module number (If you don't have this profiler module, add it on the Settings of Profiler Modules)
Attached pics shows devices Forward+ GPU timing is >> Forward, when the cube covers most of screen pixels.
*GPU Frame Time:*
* S7 Edge Mali-T880 Android 8
** Forward+ {color:#de350b}50.85{color}ms VS Forward 33.39ms
* OnePlus 8T Adreno 650 Android 13
*
** Forward+ {color:#de350b}16.60{color}ms VS Forward 8.52ms
*Reproducible:*
2023.2.0a20.3021.2930
2022.3.0f1
*Tested on:*
S7 Edge Mali-T880 Android 8
S10+ Adreno 640 Android 10
OnePlus 8T Adreno 650 Android 13
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [URP] Invalid update of shader stripping settings
- [HDRP] Errors on Shader stripper that do not stripp shaders.
- Usage of Adaptive Probe Volumes throws a lot of IndexOutOfRangeException and Assertion Failed errors
- Prefab overrides don't recover missing managed references
- Trail Renderer visual doesn't match the positions of vertices when they have been offset
Add comment