Can't use occlusion/Depth-API with Unity Play Mode

[Aethoen]

When I activate play mode on v72, the Unity Editor hangs and needs to be killed with task manager.

It stays on this loading screen indefinitely (waited for ~10 mins), with no errors in the console. This issue did not happen before v72 (as of ~3 weeks ago). I am also unable to build to a Windows program and run, as it crashes immediately with the Quest 3 plugged in.

This issue ONLY occurs with the EnviromentDepthManager enabled or when the DepthAPI is enabled within a custom script. Regular passthrough without occlusion/DepthAPI features works as normal.

I have made no changes to the project since it last worked on v71, but I did update drivers for Meta Quest Link as it requested. I have already tried a fresh project and factory reset my headset, and tried on two different computers. Unity Version: 6000.0.30f1

Edit: the DepthAPI works fine when running on an Android build, but still crashes when run on Windows with Unity Editor. This is with the same build of the game.

[TudorJude]

Hello,

We've been made aware recently of the issues regarding link and depth. A team is actively looking into providing a fix as soon as possible.

[Aethoen]

Do you have an ETA for when this will be fixed? Thanks.

[alfiolocastro]

Oh! I have the same issue!

[TudorJude]

Hello,

Sorry for not getting back to this issue earlier, but as of yet there's no news and we can't give an ETA for the fix. The issue seems to be more complex than initially thought and I'm actively following the issue. The moment I get news, I will update this thread.

We apologize for this inconvenience, we're aware of the frustration this is causing everyone.

[alfiolocastro]

Thank you for the follow up.
Is there any workaround for this? (eg. rolling back modules, installing older versions of Quest Link an so on)

[TudorJude]

Issue seems to be in the Link client and I don't know of any way of reverting it, unfortunately.

[hansvana]

I have nothing to add but say I'm having the same issue, in the hopes more voices will make it go higher on someone's to do list.

[octavr]

The issue seems to be related to the Environment Depth Manager script. I have tried to use in another project and Unity also hangs in play mode with Link.

[TudorJude]

Yes, the problem is with the Link client when we enable depth in the scene. This problem is specifically related to Depth API. Scenes that do not have the EnvironmentDepthManager will not enable depth and thus will not crash Link. The problem has been recently identified and a fix will be part of a future update.

In the meantime, to not hinder development times, I can recommend the XRSimulator package. It's a very handy tool and can be a good alternative to Link while we're working on the fix.

[Leerael]

Fix would be great, running into the same issues running in Link and XR Simulator.

[peacake]

Thank you for the follow up. Is there any workaround for this? (eg. rolling back modules, installing older versions of Quest Link an so on)

I had success getting it to work on Unity 6000.0.40f1 if I start the application with passthrough and the EnvironmentDepthManager component disabled, then enabling both at the same time with a CoRoutine called on Start() - hope that also helps you as a workaround until the fix.

[berkcetinsaya]

Hi @peacake ,

I tried what you suggested. I have two GameObjects in my scene (Passthorugh, EnvironmentDepthManager). They have their components disabled. I have a script that takes these Gameobjects as a variable, then in the
Start(){
StartCoroutine(EnablePassthrough());
StartCoroutine(EnableOcclusion());
}
private IEnumerator EnablePassthrough()
{
passthrough.GetComponent<OVRPassthroughLayer>().enabled = true;
yield return null;
}

private IEnumerator EnableOcclusion()
{
occlusion.GetComponent<EnvironmentDepthManager>().enabled = true;
yield return null;
}
Still no chance. It got stuck in the loading. I use v0.43f1. Did I misunderstand what you implemented?

[peacake]

Hi @berkcetinsaya ,

I enable both in the same CoRoutine. This is the code that works for me:

void Start()
    {
        StartCoroutine(EnableEnvironmentalDepth());
    }

public IEnumerator EnableEnvironmentalDepth()
    {
        _ovrManager.isInsightPassthroughEnabled = true;

        if (!EnvironmentDepthManager.IsSupported)
            yield break;

         // enable depth with soft occlusions
        _environmentDepthManager.enabled = true;
        _environmentDepthManager.OcclusionShadersMode = OcclusionShadersMode.SoftOcclusion;

        _environmentDepthManager.RemoveHands = true;

        // wait until the depth texture becomes available
        while (!_environmentDepthManager.IsDepthAvailable)
            yield return null;
    }

Insight passthrough needs to be unchecked in the OVRManager. Unity will give you a recommended fix to enable it - ignore this. I start with the OVRPassthroughLayer component enabled, and the EnvironmentalDepthManager disabled.

[berkcetinsaya]

Hi @peacake ,

Thanks for the quick response. I just wanted to confirm that your workaround works well. I tested it with Meta SDK 74.0.2, Unity v6.0.43f1, OpenXR Plugin (OVRCameraRig in the scene), and Quest 3 connected to the PC with Link. Until it is fixed in the SDK, this is the solution.

Additionally, I had a toggle to enable/disable the occlusion at runtime in the scene, which just disables the environment depth manager component. The solution above works at the start. But it still crashes when I try to toggle it at runtime with Link. It is not required for me to disable/enable runtime in the Editor. Because it still works on the headset without any issue. However, in case you have another solution for this toggle in the Editor without disabling the passthrough, I would be happy to hear it.

Thanks again.