Develop
Develop
Select your platform

Occlusions Overview

Updated: Dec 18, 2024

What are occlusions?

The primary function of the Depth API is to enable real-world objects to obscure virtual objects in passthrough. There are two types of occlusion available:
  • Hard occlusion, which is cheaper to compute, but has a jagged edge and more visible temporal instability.
  • Soft occlusion, which is visually more appealing, but requires slightly more GPU.
Occlusions comparison

How do occlusions work?

Depth API provides real-time environment depth textures to your application. These textures can be passed to shaders, which use this information to determine a fragment’s position in relation to the real world. In other words, it determines if a fragment is in front of or behind real world objects.
Occlusions depth map

Limitations

Limitation
Reason
Suggested workaround
Occlusions flicker near surfaces
This is caused by an issue often referred to as “Z-fighting”. In 3D graphics, this usually happens when two virtual objects are rendered at the same depth. Environment depth values are produced within the error margin, so in this case, z-fighting is apparent even when the depth is not precisely the same across frames.
Consult this documentation’s section on Environment Depth Bias. However, it is recommended to offset objects that you place on Scene Model surfaces along the surface normal.
Occlusions aren’t matching the real-world and lag behind during fast motion
Real-time depth sensing has limitations that prevent pixel-perfect occlusions from being achieved at the same frame rate as app rendering.
Soft occlusion shaders reduce visibility issues, but apps must be designed considering this limitation.

Learn more

For more in-depth information, consult the Get Started page.
Did you find this page helpful?
Nav Logo
Virtual reality / Meta Horizon
Virtual reality / Meta Horizon
Virtual reality / Meta Horizon
English (US)
© 2026 Meta