Search Issue Tracker
Fixed in 4.0.3
Votes
0
Found in [Package]
4.0.0-preview.3
Issue ID
1245717
Regression
No
[Android][ARFoundation] AR Session overrides targetFrameRate on first Update despite matchFrameRateEnabled being set to false
Repro steps:
1. Open attached project
2. Build and Run on Android
3. Observe the log
Actual: matchFrameRateEnabled becomes true and the targetFramerate is overridden
Reproducible with: 2019.3.14f1, 2020.1.0b9, 2020.2.0a11
Tested and reproduced on these devices:
VLNQA00294, Oppo Reno Z 中国版 (PCDM10), Android 9, CPU: Mediatek MT6779 Helio P90, GPU: PowerVR Rogue GM9446
VLNQA00128, Samsung Galaxy Note8 (SM-N950F), Android 9, CPU: Exynos 9 Octa 8895, GPU: Mali-G71
Didn't reproduce on:
iPhone 11 (iOS 13.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
- [MacOS] Invalid Code Signing Entitlements errors appear when signing MacOS project for App Store
- Missing UNITY_MATRIX_IT_MV definition in HDRP shaders
- ScrollRect panel not resizing correctly to fit text
- Scroll bar doesn't show full text
- [Linux] AutoLocale: current locale expects 'C' but got error is thrown when starting a project
Resolution Note (fix version 4.0.3):
The fix will be available in the AR Foundation 4.0.3 and the 4.1.0-preview.4 package release. AR Foundation will no longer overwrite user targetFramerate settings on the first frame.