NAME

rtcForwardIntersect4/8/16 - forwards a ray packet to new scene


  from user geometry callback
    

SYNOPSIS

#include <embree4/rtcore.h>
void rtcForwardIntersect4(


  void int* valid,


  const struct RTCIntersectFunctionNArguments* args,


  RTCScene scene,


  struct RTCRay4* ray,


  unsigned int instID
);
void rtcForwardIntersect4(


  void int* valid,


  const struct RTCIntersectFunctionNArguments* args,


  RTCScene scene,


  struct RTCRay4* ray,


  unsigned int instID
);
void rtcForwardIntersect16(


  void int* valid,


  const struct RTCIntersectFunctionNArguments* args,


  RTCScene scene,


  struct RTCRay16* ray,


  unsigned int instID
);
    

DESCRIPTION

The rtcForwardIntersect4/8/16 functions forward the traversal of a transformed ray packet (ray argument) into a scene (scene argument) from a user geometry callback. The function can only get invoked from a user geometry callback for a ray traversal initiated with the rtcIntersect4/8/16 function. The callback arguments structure of the callback invokation has to get passed to the ray forwarding (args argument). The user geometry callback should instantly terminate after invoking the rtcForwardIntersect4/8/16 function.

Only the ray origin and ray direction members of the ray argument are used for forwarding, all additional ray properties are inherited from the initial ray traversal invokation of rtcIntersect4/8/16.

The implementation of the rtcForwardIntersect4/8/16 function recursively continues the ray traversal into the specified scene and pushes the provided instance ID (instID argument) to the instance ID stack. Hit information is updated into the ray hit structure passed to the original rtcIntersect4/8/16 invokation.

This function can get used to implement user defined instancing using user geometries, e.g. by transforming the ray in a special way, and/or selecting between different scenes to instantiate.

When using Embree on the CPU it is possible to recursively invoke rtcIntersect4/8/16 directly from a user geometry callback. However, when SYCL is used, recursively tracing rays is not directly supported, and the rtcForwardIntersect4/8/16 function must be used.

For rtcForwardIntersect4 the ray packet must be aligned to 16 bytes, for rtcForwardIntersect8 the alignment must be 32 bytes, and for rtcForwardIntersect16 the alignment must be 64 bytes.

EXIT STATUS

For performance reasons this function does not do any error checks, thus will not set any error flags on failure.

SEE ALSO

[rtcIntersect4/8/16]