[Bug] Camera feed extreme lag after 6.0.X to 6.1.0 AR foundation upgrade

[Jocke155]

Unity bug report case number
Will edit Unity bug report case number as soon as it's reported there.

Describe the bug
The camera feed lags severely but occasionally. Restarting the game and starting it again sometimes results in a better framerate. Other times it's not playable. It's just the camera feed that is lagging and have a severe framerate impact.

Happened without any changes other than upgrading from AR Foundation 6.0.X to 6.1.0 (Same issues in 6.2.0-pre4). Works as normal in 6.0.X,

To Reproduce
Steps to reproduce the behavior (hopefully):

1. Setup an AR project in 6.0.X (no occlusion or advanced features).
2. Upgrade to +6.1.0
3. See occasional lag in the camera feed.
4. Restarting the game changes the performance every time.

Expected behavior
An acceptable frame rate from the camera.

Smartphone:

• Device: Samsung A55 5G
• OS: Android 14
• 6000.1.2f1
• ARFoundation version 6.2.0-pre4 or 6.1.X

[andyb-unity]

Please file a formal bug via the Unity Editor: https://unity.com/releases/editor/qa#bug-reporting. Bugs reported to this GitHub repo are unofficial and may not be seen by the development team.

[mike-copley]

Yes Andy's advice is good advice. Please file the bug, and we can link that bug with an internal issue that we are tracking for it. The work-around for now would be to ensure that multithreaded rendering is set to off. If the Vulkan renderer is used, then since it is already inherently multithreaded, there should be no impact there. If the GLES renderer is used, you should no longer also have frame-rate issues with passthrough with single threaded.

[Jocke155]

Yes Andy's advice is good advice. Please file the bug, and we can link that bug with an internal issue that we are tracking for it. The work-around for now would be to ensure that multithreaded rendering is set to off. If the Vulkan renderer is used, then since it is already inherently multithreaded, there should be no impact there. If the GLES renderer is used, you should no longer also have frame-rate issues with passthrough with single threaded.

You're right. It appears to be the combination of OpenGLES3 and multithreaded rendering that causes it, which wasn't an issue before.

[Vaxela]

Hello do we have some new be cause i have the same problem on android mobile : multithreaded rendering was checked with OpenGLES3, my fps drop a lot when launching on android with AR

[mike-copley]

ARCore version 6.2.0 and above no longer have this issue. It is recommended that users move to that version if they are currently on 6.1.X.

[Vaxela]

I have the same issue fps drop on 6.2.0 and 6.3.0 and unity 6000.2.6f2:

• Graphics api : OpenGLES3
• Multithreaded Rendering: true

I change to 6.0.6 no problem anymore on android version 14 on a samsung GALAXY A53 5G

[mike-copley]

Hello Vaxela,

At this point I can only recommend two things that you can do:

1. See if you are getting the same performance problems with our Samples project located here:
   https://github.com/Unity-Technologies/arfoundation-samples
   ... if our samples do not reproduce the performance problem, then analyze what differences there are between your code and the code used in our samples.

2. If our samples do exhibit the problem, or they don't but you have a repro project that does demonstrate the problem, then please file a bug report:
   https://unity.com/releases/editor/qa#bug-reporting

thank you and sorry for your troubles.

[mrcarriere]

We are seeing a similar issue on Unity 6000.0.59f2, and saw the frame drop happening on Android devices when the com.unity.xr.arcore package was updated to any version >6.0.6.

This did seem to resolve itself when we disabled multithread rendering, which we'll use for a workaround for the time being -- but ultimately we'd love to see this resolved where we can re-enable that feature.

We have filed a bug report regarding this issue -- see the issue thread here.

[Jocke155]

I can confirm this problem in 6.2.0.
Disabling multithread rendering is still the same workaround.