You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now there are two triangle references per triangle: one with a forward sense in its scene (volume) and another for the reverse sense in its scene (another volume).
We may be able to avoid the need to duplicate these references by storing the forward and reverse sense scenes on the GeometryData object -- it should be available to us as part of the intersection arguments. The remaining need is to know what scene the ray is being fired on. This information can be stored on the RTCDRay if needed, but it may also be available as part of the intersection arguments. TBD.
The text was updated successfully, but these errors were encountered:
Right now there are two triangle references per triangle: one with a forward sense in its scene (volume) and another for the reverse sense in its scene (another volume).
We may be able to avoid the need to duplicate these references by storing the forward and reverse sense scenes on the
GeometryData
object -- it should be available to us as part of the intersection arguments. The remaining need is to know what scene the ray is being fired on. This information can be stored on theRTCDRay
if needed, but it may also be available as part of the intersection arguments. TBD.The text was updated successfully, but these errors were encountered: