RTCRayHitN(3)

RTCRayHitN 💖

okay bestie, welcome to the Embree Ray Tracing Kernels 3 corner of the manual, where we're talking about RTCRayHitN — the combined ray/hit packet of runtime size. yes, runtime. the size is a whole mystery until you actually run the thing. main character energy tbh ✨

✨ NAME ✨

RTCRayHitN — combined ray/hit packet of runtime size 🎀

🌸 SYNOPSIS 🌸

#include <embree3/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 tea 🍓: sometimes you don't know the packet size of a ray/hit structure at compile time. like, at all. the classic example is when Embree hands you back a ray/hit packet inside the RTCIntersectFunctionN callback function — at that point the size is just... whatever it is, and you find out when you find out. when that happens, Embree uses the RTCRayHitN type for ray packets. it's giving flexible. it's giving runtime. 🦋

⚠️ heads up though: these ray/hit packets can only have sizes of 1, 4, 8, or 16. that's it. no other packet size will be used. periodt. 👑

so what's a girl to do? you've got two paths, and both are valid, pick your fighter 💖:

1. implement different special code paths for each of those possible packet sizes, and cast the ray/hit to the appropriate ray/hit packet type — very bespoke, very tailored, very 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 — honestly iconic, lowkey the move 🫶

either way you're getting at the ray bits and the hit bits. no cap. 💯

👑 EXIT STATUS 👑

(nothing here bestie, the original left it blank — we move in silence 🤫)

🌈 SEE ALSO 🌈

• [RTCHitN]

okay that's the whole page, you ate it up fr fr 💜 this was RTCRayHitN(3) from Embree Ray Tracing Kernels 3 — go forth and packet-ify responsibly, bestie 🧚✨