Search Issue Tracker
Won't Fix
Votes
4
Found in
2021.3.29f1
2022.3.8f1
2023.1.10f1
2023.2.0b7
2023.3.0a2
6000.0.0b11
7000.0.0a1
Issue ID
UUM-46920
Regression
No
[Mobile] View from the phone’s camera is lagging when changing device orientation if using “WebCamTexture”
How to reproduce:
1. Build And Run the user’s attached “WebCamTexture-Camera-Feed-Bug-Report.zip” project on mobile device
2. Change the device orientation a few times and observe the app
Expected result: View is stable
Actual result: View is not stable
Reproducible with: 2021.3.29f1, 2022.3.8f1, 2023.1.10f1, 2023.2.0b7, 2023.3.0a2
Reproduced on:
VLNQA00494 - iPhone 14 Pro Max, 16.3.1 iOS
VLNQA00358 - iPhone 12, 14.1 iOS
VLNQA00310 - iPad Pro 12.9", 13.4.1 iOS
Samsung Galaxy A71 (user’s info)
Not reproduced on:
VLNQA00392 - iPad (9th generation), 15.0 iOS
Notes:
-reproducible with both Front and Rear cameras (rear occurred fewer times)
-restarting the app might be needed
-not reproducible after opening Control Center
-
makaka-org
Aug 23, 2023 13:01
Reproduced also on:
- Unity 2021.3.21, 2022.3.0, 2022.3.7, Unity 2023.2a17
- Platforms: iOS 16.6 with iPhone XS Max, Samsung Galaxy A71Original bug description and workaround: https://forum.unity.com/threads/camera-feed-on-background-mobile-camera-stream-unity-asset-device-camera.1443007/#post-9244170
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
- Inspector's custom tooltip is displayed incorrectly when the name is truncated in UI toolkit
- Crash on ScriptableRenderLoopDraw when rendering a specific VFX in Play Mode
- The script is not renamed in the Project window when renaming and a compilation Error is present
- Average FPS in Play Mode degradation on a newly created BiRP project when it's upgraded from 2020.3.48f1 to a newer Editor version
- DecoratorDrawer indentation is incorrect when it is called with EditorGUI
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.