topic Also, if I have multiple in Intel® Embree Ray Tracing Kernels

rtcNewScene, rtcNewGeometry thread safety

Burr__Adam — Tue, 05 Mar 2019 14:54:10 GMT

Are the rtcNewScene and rtcNewGeometry functions thread safe when called concurrently with a shared RTCDevice? I assume not but I don't want to put in redundant locking if it's handled internally.

Also, if I have multiple

Burr__Adam — Tue, 05 Mar 2019 15:02:00 GMT

Also, if I have multiple RTCScene objects sharing a single RTCDevice, is it safe to modify the scenes (eg rtcAttachGeometry, rtcSetNewGeometryBuffer, rtcCommitGeometry, rtcCommitScene, etc) concurrently from multiple threads? Or should I be using multiple RTCDevice objects? Or a single RTCDevice with mutex locking?

All operations that take the

SvenW_Intel — Thu, 07 Mar 2019 06:04:50 GMT

All operations that take the device are thread safe, e.g. you can create scenes for a single device from multiple scenes. Other objects are typically not thread safe, thus you cannot attach geometries from multiple threads to the same scene. However, for different objects that works. thus each thread can work on a different scene. Similar each thread can work on separate geometries, but not on the same.

An exception are functions that only read state and are intended for rendering. E.g. the rtcIntersectXX and rtcInterpolateXX functions can get called from multiple threads (as long as no thread is modifying the underlying objects with some API calls).

In my case different threads

Burr__Adam — Thu, 07 Mar 2019 13:20:53 GMT

In my case different threads will always be working with different scenes and geometry, the only thing shared between threads is the device. I won't be modifying the same scene or geometry concurrently so it sounds like I will be safe. Thanks!