RTCRayHitN(3)

✨ RTCRayHitN(3) ✨

okay bestie, welcome to the <strong>Embree Ray Tracing Kernels 4</strong> manual — this one's about RTCRayHitN, the ray/hit packet that's lowkey runtime-sized and honestly iconic for it 💅

---

🌸 NAME 🌸

RTCRayHitN — combined ray/hit packet of runtime size. it's giving "ray AND hit, together, and you don't know how many until runtime" 🦋

---

✨ SYNOPSIS ✨

#include <embree4/rtcore_ray.h>

struct RTCRayHitN;

struct RTCRayN* RTCRayHitN_RayN(struct RTCRayHitN* rayhit, unsigned int N);
struct RTCHitN* RTCRayHitN_HitN(struct RTCRayHitN* rayhit, unsigned int N);

---

💖 DESCRIPTION 💖

so here's the situation, bestie. when the packet size of a ray/hit structure is not known at compile time — like, for example, when Embree hands you back a ray/hit packet inside the RTCIntersectFunctionN callback function — Embree uses the RTCRayHitN type for ray packets. no cap, that's literally the whole point of it 🫶

the tea: these ray/hit packets can only have sizes of 1, 4, 8, or 16. no other packet size will be used. periodt. 💀

so you've got two vibes to pick from, and both are valid:

1. implement different special code paths for each of these possible packet sizes and cast the ray/hit to the appropriate ray/hit packet type — very "I did the homework" of you 👑
2. extract the RTCRayN and RTCHitN components using the rtcGetRayN and rtcGetHitN helper functions, then use the RTCRayN_XXX and RTCHitN_XXX functions to access the ray and hit parts of the structure — very "work smarter not harder" energy ✨

either way, you get at the ray bits and the hit bits. slay. 🌈

---

🎀 EXIT STATUS 🎀

crickets — nothing here, bestie, this section is empty. not every page gets an exit status and that's okay 🦋

---

🌟 SEE ALSO 🌟

• RTCHitN — the hit half of the duo, iykyk 💜

---

okay that's the whole page!! mwah 🫶 this was <strong>RTCRayHitN(3)</strong> from the <strong>Embree Ray Tracing Kernels 4</strong> manual, and honestly? iconic. go forth and cast your packets responsibly, bestie 💅✨🌸