rtcGetGeo...hreadSafe(3)

πŸ“¦ version 3.13.5, in epel 9, fedora 43, fedora 44

✨ rtcGetGeo...hreadSafe(3) ✨

okay bestie, welcome to the Embree Ray Tracing Kernels 3 manual, section 3, page rtcGetGeo...hreadSafe. yes the title is abbreviated with dots because the real name is a whole mouthful β€” it's rtcGetGeometryThreadSafe and we're gonna talk about her. πŸŽ€


πŸ’– NAME πŸ’–

rtcGetGeometryThreadSafe β€” returns the geometry bound to the specified geometry ID


🌸 SYNOPSIS 🌸

#include <embree3/rtcore.h>

RTCGeometry rtcGetGeometryThreadSafe(RTCScene scene, unsigned int geomID);

πŸ¦‹ DESCRIPTION πŸ¦‹

so, rtcGetGeometryThreadSafe hands you back the geometry that's bound to the geometry ID you pass in (that's the geomID argument, queen) inside the scene you specify (the scene argument, obviously πŸ’…). that's the whole gig.

important tho: this function just looks up the handle and does not increment the reference count. it's giving window shopping, not buying. so if you actually want to own that handle β€” like, take custody, be responsible for it β€” you gotta additionally call rtcRetainGeometry. no cap. 🫢

and here's the vibe check: this function is thread safe, but it should NOT get used during rendering. i'm so serious. 😭 if you need a fast non-thread-safe version to use during rendering, please use the [rtcGetGeometry] function instead. that's literally what she's there for.


🌈 EXIT STATUS 🌈

if things go wrong, NULL is returned and an error code gets set β€” you can go query that error code using rtcGetDeviceError. πŸ™ˆ


⭐ SEE ALSO ⭐

  • [rtcAttachGeometry]
  • [rtcAttachGeometryByID]
  • [rtcGetGeometry]

okay that's the whole page, bestie, you ate that reading session πŸ’…βœ¨ this little cutie comes from the Embree Ray Tracing Kernels 3 collection, section 3, and the page signs off as rtcGetGeo...hreadSafe(3) β€” mwah, go call rtcGetGeometry during render like a good main character πŸ‘‘πŸŒΈ

πŸ“¦ where this page comes from