Search Issue Tracker
Won't Fix
Won't Fix in 2022.3.X
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
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:
The situations described in this bug are known performance trade-offs of Forward+ compared to Forward classic. We will improve the documentation regarding the offering of those renderers and look to improve some of the corner cases in the Forward+.
Resolution Note (2022.3.X):
The situations described in this bug are known performance trade-offs of Forward+ compared to Forward classic. We will improve the documentation regarding the offering of those renderers and look to improve some of the corner cases in the Forward+.