Search Issue Tracker
Fixed
Fixed in 4.0.3, 5.1.1
Votes
0
Found in [Package]
4.0.2
5.1.1
Issue ID
APB-34
Regression
No
Adaptive Performance Android package reset Application.target framerate to -1
Reproduction steps:
1. Open the attached project “BugRepro”
2. Build and Run on Android
3. Observe the logcat (search for ‘Framerate’)
Expected result: targetFrameRate remains at 50
Actual result: targetFrameRate is set to -1
Reproducible with: 1.2.0, 1.2.1, 1.3.1(2021.3.39f1, 2022.3.34f1, 6000.0.7f1)
Reproducible with these devices:
VLNQA00518 - Google Pixel 4 (Pixel 4), CPU: Snapdragon 855 SM8150, GPU: Adreno 640, OS: 13
VLNQA00591 - Samsung Galaxy S23 (SM-S911B), CPU: Snapdragon 8 Gen 2 (SM8550), GPU: Adreno 740, OS: 14
Not reproducible with these devices:
VLNQA00278 - Xiaomi Redmi Note 7 (Redmi Note 7), CPU: Snapdragon 660, GPU: Adreno 512, OS: 9.0.0
VLNQA00139 - Vivo Xplay6 (vivo Xplay6), CPU: Snapdragon 820 MSM8996, GPU: Adreno 530, OS: 7.1.1
VLNQA00414 - Galaxy Note10+ 5G (SM-N976V), CPU: Snapdragon 855 SM8150, GPU: Adreno 640, OS: 9
Testing environment: Windows 11 23H2 (22631.3007), Windows 11 (10.0.22631) 64bit (user’s)
Not reproducible environment: No other environment tested
Workaround: Removing the Adaptive Performance package fixes the issue.
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
- Incorrect Shader keyword activation for Shadows when no Light is present in URP
- Editor freezes when loading a specific AssetBundle
- WebGPU builds with Multithreading enabled crash on Safari
- Set as Value in UI Builder doesn't work across all properties.
- Calculating time durations in RenderDoc with DX12 causes 'Device Lost error' popup
Resolution Note (fix version 5.1.1):
The issue was that during initialization the Framerate Scaler is activated and deactivated. During that process the targetframerate is overwritten without having the correct targetframerate yet. The targetframerate changes during setup multiple times and the default is wrong. Now it is acquired only when the Framerate Scaler is also actively used.