Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.24f1
2023.2.0a16
2023.3.0a3
6000.0.0b11
Issue ID
UUM-40217
Regression
No
[Chrome OS] No visible difference between various "SetFPS" settings of the Camera FPS
Chrome OS specific.
Using project: "WebCamTexture-TestProject"
1. Build the mentioned project for Chrome OS device and run it
2. In the app select "SetFPS_Test"
3. Uncheck "Scene: 03_SetFPS_Test" to get better camera visibility
4. Move device around to make sure that camera works as expected (test starts at default camera FPS)
5. Use "Enter Target FPS" to change default FPS to custom (e.g. 15) and confirm with "OK"
6. Move device around to see if FPS change has any effect.
{}Expected result{}: There should be noticeable FPS decrease that can be observed visually. Camera should lag/stutter a bit as a response on FPS decrease.
{}Actual result{}: No visual difference.
{}Reproduced on the following Chrome OS devices{}: Samsung Galaxy Chromebook - OS Android 13/Android 11; Google grunt - OS Android 9.
{}Not reproduced on Android device{}: Google Pixel 7 - OS Android 13
Logs:
[^com.testproject.webcamtexture-SamsungAndroid13.txt]
[^com.testproject.webcamtexture-SamsungAndroid11.txt]
[^com.testproject.webcamtexture-HPgruntAndroid9.txt]
[^com.testproject.webcamtexture-Pixel7Android13.txt]
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
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
Resolution Note:
ChromeOS is no longer supported.