Search Issue Tracker
Duplicate
Under Consideration for 5.1.X
Votes
0
Found in [Package]
5.1.0-pre.10
Issue ID
ARFB-336
Regression
No
[ARFoundation] Canvases are lagging when using “Screen Space - Camera” Render Mode with “TrackedPoseDriver” on iOS devices
How to reproduce:
1. Build And Run the user’s attached “CameraSpaceCanvasBug.zip” project on iOS device
2. Move the phone quickly from left to right or enable the “Portrait Orientation Lock” setting put the device on the table and lift the right side of the device toward you so the screen faces you
3. Observe the result
Expected result: Both white images stay aligned horizontally together without any space between them
Actual result: The right image does not stay aligned horizontally next to the left image
Reproducible with: 4.2.8 (2021.3.30f1), 5.0.7 (2022.3.9f1), 5.0.7 (2023.1.13f1), 5.1.0-pre.10 (2023.2.0b9), 5.1.0-pre.10 (2023.3.0a5)
Reproduced on:
VLNQA00358 - iPhone 12, 14.1 iOS
iPhone 12 mini 16.6 iOS (user’s info)
iPhone 12 Pro 16.4.1 iOS (user’s info)
Not reproduced on:
VLNQA00494 - iPhone 14 Pro Max, 16.3.1 iOS
VLNQA00392 - iPad (9th generation), 15.0 iOS (images we’re not moving horizontally nor vertically)
VLNQA00310 - iPad Pro 12.9", 13.4.1 iOS (images we’re not moving horizontally nor vertically)
N/A, Samsung S21- (SM-G991U), Android 12, CPU: Snapdragon 888, GPU: Adreno (TM) 660
N/A, Xiaomi - (Redmi Note 8 Pro), Android 9, CPU: MediaTek Helios G90T MT6785T, GPU: Mali-G76 MC4
Note: On the device, the lag is caused by the ARCameraBackground component, not the TrackedPoseDriver or ARPoseDriver. Disabling the ARCameraBackground, or creating a second camera as a child of the ARCamera and using that to render the Screen Space - Camera canvas, removes the visible lag
-
Resolution Note:
Was fixed.
Duplicate of https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-41235
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
- Rendering locks up when not looking at a transparent material on Meta Quest 2
- Volumetrics break when using a Custom Pass to create a Thickness Buffer for Alpha Clipping
- All tests are run instead of only the failed ones when the "Rerun Failed" button is pressed
- GameObject is not masked when the "Render PostProcessing Effects" pass executes with a resolved non-MSAA Color target and MSAA DepthStencil target
- [Android] Gfx.WaitForGfxCommandsFromMainThread high performance usage and inconsistency when built Player scene has Canvas GameObject on a specific Project
This is a duplicate of issue #UUM-41235