rtcOccluded4/8/16(3)

✨ rtcOccluded4/8/16 — finds any hits for a ray packet ✨

okay bestie, welcome to the Embree Ray Tracing Kernels 4 page for rtcOccluded4/8/16 💖 this is the one where you ask a whole squad of rays at once "hey... did literally anything get in your way?" and you get a yes/no back. no hit data, no tea, just vibes. let's go 🦋

---

🌸 SYNOPSIS 🌸

#include <embree4/rtcore.h>

void rtcOccluded4(
  const int* valid,
  RTCScene scene,
  struct RTCRay4* ray,
  struct RTCOccludedArguments* args = NULL
);

void rtcOccluded8(
  const int* valid,
  RTCScene scene,
  struct RTCRay8* ray,
  struct RTCOccludedArguments* args = NULL
);

void rtcOccluded16(
  const int* valid,
  RTCScene scene,
  struct RTCRay16* ray,
  struct RTCOccludedArguments* args = NULL
);

---

🎀 DESCRIPTION 🎀

So like. The rtcOccluded4/8/16 functions check, for each active ray in a ray packet of size 4, 8, or 16 (that's the ray argument, obvi), whether there is any hit with the scene (the scene argument, duh). It's giving "is the path blocked, yes or no" — that's the whole entire job 💅

The optional arguments struct (the args argument) can be used for advanced use cases — see the section [rtcInitOccludedArguments] for more details. And if you want the full lore on occlusion rays, how to set them up, how to trace them, all of it, go read Section [rtcOccluded1]. iykyk 🧚

A ray valid mask must be provided (the valid argument), and it stores one 32-bit integer per ray in the packet — -1 means valid, 0 means invalid. Only active rays get processed, and the hit data of inactive rays is not changed. like, not touched. left exactly as you gave them. periodt.

Alignment check, bestie, do not skip this one 😭

• For rtcOccluded4 the ray packet must be aligned to 16 bytes.
• For rtcOccluded8 the alignment must be 32 bytes.
• For rtcOccluded16 the alignment must be 64 bytes.

The rtcOccluded4, rtcOccluded8 and rtcOccluded16 functions may change the ray packet size and ray order when calling back into intersect filter functions or user geometry callbacks. yep. they can shuffle your lil rays around 🫠 under some conditions though, the application can assume packets stay intakt, and you can determine that by querying the RTC_DEVICE_PROPERTY_NATIVE_RAY4_SUPPORTED, RTC_DEVICE_PROPERTY_NATIVE_RAY8_SUPPORTED, and RTC_DEVICE_PROPERTY_NATIVE_RAY16_SUPPORTED properties through the rtcGetDeviceProperty function. See [rtcGetDeviceProperty] for more information. go check before you assume, fr fr 👑

---

💀 EXIT STATUS 💀

For performance reasons this function does not do any error checks, thus it will not set any error flags on failure. it's fast because it does not care. iconic behaviour honestly but also pls be careful 🌈

---

👀 SEE ALSO 👀

• [rtcOccluded1]
• [rtcIntersect4/8/16]
• [rtcInitOccludedArguments]

---

and that's the whole page, bestie 🍓 this was rtcOccluded4/8/16 from the Embree Ray Tracing Kernels 4 set — mwah, slay, go trace something gorgeous 💜💅✨