Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.23f1
2022.2.15f1
2023.1.0b12
2023.2.0b4
2023.3.0a1
Issue ID
UUM-33729
Regression
No
[Android] Development Build suffers from an FPS drop when tapping the screen for the first time after relaunching the Build
How to reproduce:
1. Open the attached “IN-28077“ project
2. In the File → Build Settings enable Development Build and Autoconnect Profiler
3. Connect your device and in the Run Device select your connected device
4. Click Build And Run
5. After the build loads on the device check the Profiler to see stable ~60FPS
6. Fully exit the app and relaunch it
7. After the Profiler window pops up tap the screen and observe the Profiler
Expected result: FPS stays stable.
Actual result: FPS drops to 15 for a few seconds.
Reproducible with: 2021.3.23f1, 2022.2.15f1, 2023.1.0b12
Could not test with: 2020.3.47f1 (Errors with customs scripts), 2023.2.0a10 (Vulkan Errors)
Built with: macOS 13.2 (Intel)
Reproducible on devices:
VLNQA00331 - HUAWEI P20 lite (ANE-LX1), CPU: HiSilicon Kirin 659, GPU: Mali-T830, OS: 9
VLNQA00520 - Galaxy S22 USA (SM-S901U), CPU: Snapdragon 8 Gen 1 (SM8450), GPU: Adreno 730, OS: 12
VLNQA00334 - Xiaomi Mi A3 (Mi A3), CPU: Snapdragon 665 SM6125, GPU: Adreno 610, OS: 11
VLNQA00277 - Asus ROG Phone (ASUS_Z01QD), CPU: Snapdragon 845 SDM845, GPU: Adreno 630, OS: 8.1.0
VLNQA00134 - Samsung Galaxy S8 (SM-G950F), CPU: Exynos 9 Octa 8895, GPU: Mali-G71, OS: 9.0.0
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
- Standalone profiler process is hidden in macOS dock
- Shader warnings are being thrown after building Mixed Reality Template
- Error is thrown when entering play mode with build profiles docked and standalone profiler open
- The Player hangs when activating another maximized application
- [XR] Input is not registered and headset view is headlocked after entering Play Mode with Meta XR SDK on 6000.0.0b16 and higher
Resolution Note:
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.