Search Issue Tracker
By Design
Votes
0
Found in
2020.1.0a2
Issue ID
1179516
Regression
No
[WebCamTexture][Android][Meizu] FPS are not changed to requested value in runtime on Meizu devices
How to reproduce:
1. Open the attached project
2. Build and run a project on Android
3. Click on '03_SetFPS_Test' button to switch the scene
4. Click on 'Scene: 03_SetFPS_Test' toggle at the very top to disable the UI overlay
5. Enter value FPS in the input at the bottom (ex. 1)
6. Check if FPS is changed to the requested value when keyboard os closed
7. One more time change FPS to another value (ex. 15, 30) and observe the differences in image rendering
Expected result: Rendering speed changes with different FPS input
Actual result: No differences
Reproducible: 2018.4.7f1, 2019.2.3f1, 2019.3.0b1, 2020.1.0a2
Reproducible with:
VLNQA00155, Meizu PRO 7 Plus (PRO 7 Plus), Android 7.0, CPU: MediaTek Helio X30 MT6799, GPU: PowerVR Rogue Marlowe
VLNQA00004, Meizu - (MX5), Android 5.0.1, CPU: MediaTek Helio X10 MT6795T, GPU: PowerVR Rogue G6200
VLNQA00286, Meizu - (PRO 5), Android 7.0, CPU: Exynos 7 Octa 7420, GPU: Mali-T760
VLNQA00233, Meizu - (PRO 6 Plus), Android 7.0.0, CPU: Exynos 8 Octa 8890, GPU: Mali-T880
Not reproducible:
VLNQA00013, Samsung Galaxy S6 edge+ (SM-G928F), Android 7.0, CPU: Exynos 7 Octa 7420, GPU: Mali-T760
VLNQA00118, Google Pixel 2 XL (Pixel 2 XL), Android 8.1.0, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00278, Xiaomi - (Redmi Note 7), Android 9, CPU: Snapdragon 660, GPU: Adreno (TM) 512
VLNQA00137, Samsung Galaxy S9+ (SM-G965F), Android 9, CPU: Exynos 9 Series 9810, GPU: Mali-G72
VLNQA00282, Samsung Galaxy S10e (SM-G970U), Android 9, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
VLNQA00021, Samsung Galaxy S7 (SM-G930F), Android 7.0, CPU: Exynos 8 Octa 8890, GPU: Mali-T880
Notes:
- Tested with GLES3 API. Can't test with Vulkan, because of crash: Case 1178553
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (2020.1.X):
We query the supported FPS ranges and adjust requested value based on returned ranges. Hence the the requested fps will be limited by what device reports as supported. See comment below about what device reports on device in question.