RTCTRAVERSABLEFORWARDOCCLUDED1(3)

💖 rtcTraversableForwardOccluded1/Ex — Embree Ray Tracing Kernels 4, section 3 💖

okay bestie so this is page rtcTraver...cluded1/Ex(3) from the Embree Ray Tracing Kernels 4 manuals, and yes the title is truncated like that, it's giving cryptic but we move 💅

---

✨ NAME ✨

rtcTraversableForwardOccluded1/Ex — forwards a single ray to a new scene from a user geometry callback 🦋

---

✨ SYNOPSIS ✨

#include <embree4/rtcore.h>

void rtcTraversableForwardOccluded1(
  const struct RTCOccludedFunctionNArguments* args,
  RTCTraversable traversable,
  struct RTCRay* ray,
  unsigned int instID
);

void rtcTraversableForwardOccluded1Ex(
  const struct RTCOccludedFunctionNArguments* args,
  RTCTraversable traversable,
  struct RTCRay* ray,
  unsigned int instID,
  unsigned int instPrimID,
);

(and yes, that last comma in the Ex version is literally just… there. it's canon, we keep it 🎀)

---

✨ DESCRIPTION ✨

okay so the way this works, bestie: rtcTraversalbeForwardOccluded1 and rtcTraversableForwardOccluded1Ex are equivalent to rtcForwardOccluded1 and rtcForwardOccluded1Ex respectively — literally same energy — except they take a traversable object (that's the traversable argument) instead of a scene object. that's the whole plot twist 🫶

for the full deets, go read the documentation of rtcForwardOccluded1/Ex, because that's where all the real lore lives 💀

ngl, rtcTraversalbeForwardOccluded1 is spelled exactly like that in this page and I'm not touching it, that's not my business, iykyk 🙈

---

✨ EXIT STATUS ✨

bestie there is no error checking in here, and I mean none, for performance reasons — so on failure it will not set any error flags. it's giving "not my problem" energy, no cap 😭

---

✨ SEE ALSO ✨

• [rtcForwardOccluded1]
• [rtcGetSceneTraversable]

---

mwah 💜 that's the whole page, go forth and occlude responsibly. this was page rtcTraver...cluded1/Ex(3) from Embree Ray Tracing Kernels 4 — no date on this one, she's timeless like that ⭐🌸🦋