After updating Quest3 to version 2.4.1034 today, all Unity projects that use Environment Depth over Quest Link (V201) stopped working. The same projects were working correctly last night before the update.
I reproduced the issue not only in my own projects but also in the official Unity-DepthAPI sample scenes and even the standard Meta XR Building Blocks occlusion setup. All four depth-related example scenes now fail over Quest Link, including Depth image preview, depth meter/estimation readings, occlusion, and depth-based raycast behaviour. I also tried rolling back Meta Quest Link to v85, but the issue persisted.
I think there is some conflict between the depth API and the latest Horizon OS 2.4.1034.
Update Quest3 to OS 2.4.1034.
Open the official Unity-DepthAPI sample project.
Run the DepthAPI example scenes over Quest Link with Spatial Data over Link enabled.
All depth-related features fail:
DepthMapped preview shows invalid/all-foreground depth.
Depth meter / estimated distance readings are invalid (all 0.06 everywhere).
Occlusion does not work.
Depth raycast behaviour fails.
This also happens in my own Unity projects using EnvironmentDepthManager, EnvironmentRaycastManager, and Building Blocks occlusion. Everything worked before today’s quest update.
Here is my self-written Diagnostics log:
[LinkDepthDiagnostics] Frame
EnvironmentDepthManager present=True, enabled=True, supported=True, available=True
EnvironmentRaycastManager present=True, enabled=True, supported=True
depthTexture=RenderTexture 320x320, dimension=Tex2DArray, format=None/D16_UNorm, updateCount=0, nativePtr=0x288C6C86ED0
raycasts=RayOccluded:5; (0.50, 0.50): ok=False, status=RayOccluded, dist=1.146, point=(0.000, 0.000, 0.000), nconf=0.00 | (0.35, 0.50): ok=False, status=RayOccluded, dist=1.146, point=(0.000, 0.000, 0.000), nconf=0.00 | (0.65, 0.50): ok=False, status=RayOccluded, dist=1.146, point=(0.000, 0.000, 0.000), nconf=0.00 | (0.50, 0.35): ok=False, status=RayOccluded, dist=1.146, point=(0.000, 0.000, 0.000), nconf=0.00 | (0.50, 0.65): ok=False, status=RayOccluded, dist=1.146, point=(0.000, 0.000, 0.000), nconf=0.00
UnityEngine.Debug:Log (object)
Unity version
6000.4.1
Where does the issue occur?
Description
After updating Quest3 to version 2.4.1034 today, all Unity projects that use Environment Depth over Quest Link (V201) stopped working. The same projects were working correctly last night before the update.
I reproduced the issue not only in my own projects but also in the official Unity-DepthAPI sample scenes and even the standard Meta XR Building Blocks occlusion setup. All four depth-related example scenes now fail over Quest Link, including Depth image preview, depth meter/estimation readings, occlusion, and depth-based raycast behaviour. I also tried rolling back Meta Quest Link to v85, but the issue persisted.
I think there is some conflict between the depth API and the latest Horizon OS 2.4.1034.
Steps to reproduce
Update Quest3 to OS 2.4.1034.
Open the official Unity-DepthAPI sample project.
Run the DepthAPI example scenes over Quest Link with Spatial Data over Link enabled.
All depth-related features fail:
DepthMapped preview shows invalid/all-foreground depth.
Depth meter / estimated distance readings are invalid (all 0.06 everywhere).
Occlusion does not work.
Depth raycast behaviour fails.
This also happens in my own Unity projects using EnvironmentDepthManager, EnvironmentRaycastManager, and Building Blocks occlusion. Everything worked before today’s quest update.
Logs
Additional info
No response