Passthrough Layer is Black on Meta Quest Pro

I tested using Unreal and the passthrough is ok on Quest Pro. So you did something wrong or its a bug from the Unity version

Has anybody been successful trying the passthrough on the Meta Quest Pro using Unity?

I have it working using Unity 2022.1.21, with these settings.

Thanks mreimer, the last screenshot there made me aware that you have to use the Oculus XR plugin pre-release to get the Quest Pro available as a Target Device. Unfortunately that didn't help.

I did discover though that passthrough is completely broken in all contexts on my device (except Quest Link)! I can't even set a new guardian. The button in settings simply doesn't do anything.

So I restored device factory settings and got passthrough working in general again, but my app still fails to start passthrough.

I found this in "Device Logs" in Meta Quest Developer Hub:

07:08:49.870
Unity
Failed to initialize Insight Passthrough. Passthrough will be unavailable. Error Failure_NotInitialized.
07:08:49.870
Unity
UnityEngine.StackTraceUtility:ExtractStackTrace () (at /home/bokken/build/output/unity/unity/Runtime/Export/Scripting/StackTrace.cs:37)
07:08:49.870
Unity
UnityEngine.DebugLogHandler:LogFormat (UnityEngine.LogType,UnityEngine.Object,string,object[])
07:08:49.870
Unity
UnityEngine.Logger:Log (UnityEngine.LogType,object)
07:08:49.870
Unity
UnityEngine.Debug:LogError (object)
07:08:49.870
Unity
OVRManager:InitializeInsightPassthrough () (at C:/Users/Chetic/e/Assets/Oculus/VR/Scripts/OVRManager.cs:2626)
07:08:49.870
Unity
OVRManager:InitOVRManager () (at C:/Users/Chetic/e/Assets/Oculus/VR/Scripts/OVRManager.cs:1800)
07:08:49.870
Unity
OVRManager:Awake () (at C:/Users/Chetic/e/Assets/Oculus/VR/Scripts/OVRManager.cs:1848)

helensloeb, maybe do the same?

I found the solution! https://forums.oculusvr.com/t5/Quest-Development/Passthough-not-working-with-Unity-Editor-build-run-works-fine/td-p/898399

I've been testing using OVR Scene Quick Preview, but apparently this is not supported for security reasons. You have to create a complete build and drag it to your headset in Meta Quest Developer Hub.

Very slow and frustrating way of working in my opinion...

Edit: I take it back. I just discovered I can use "Build And Run" in Unity Build Settings and "ADB over Wi-Fi" in Meta Quest Developer Hub to deploy and test with working passthrough over wifi. I suddenly have an incredibly simple and powerful setup!

The documentation and/or error handling in the SDK could've saved me a lot of wasted time here. Hope someone else can be saved by my comments in the future!

So I had the exact same problem , I followed a tutorial to have a blank scene with passthrough setup, thought I'd done all the settings correctly but when I built and checked on the Quest Pro the feed was always black. I then tried the oculus sample scenes and had the same problem. Turns out some settings have to be updated on the 'passthrough' sample scene provided in the 'SampleFramework/usage' folder. If anyone is still looking for a solution make sure to follow the checklist below... I had this working in 2021.3.3f1 , 2020.3.34f1 and 2022.1.2f1

In Player Settings:
- Colour Space should be Linear

- Require ES3.1 and ES3.1 +AEP and ES3.2 all ticked
- Set the scripting backend to IL2CPP 
- Untick ARMv7 and tick ARMV64

In the Scene on the OVRCameraRig:

- the colour gamit was auto set to 'Rift' , change this to 'Quest'

- double check both passthrough boxes are ticked : 'passthrough capability ' under general and 'enable passthrough' under Insight passthrough
- go to the CentreEyeAnchor and make sure the background is set to 'Solid colour' , and the colour is pure black and alpha is zero

- the passthrough layer should be set to 'underlay'

I also suddenly experienced black pass-through surfaces, which were working previously, and restarting the Quest solved the problem.

Hey all,

after trying the above methods to no avail, I realized that the HDR setting in the Camera game object has to be set to "Off" before getting it to work! 

Hopefully this helps any other unfortunate soul debugging this issue 😕

Cheers

I also had similar issues when trying to set passthrough in Unity. I have pushed a sample project on GitHub with the settings that worked for me: sample project passthrough.