<div dir="ltr">Hi,<br><div><br></div><div>I've been checking the sources another day. Was mainly looking into traversal parts of the code.</div><div><br></div><div>There's interesting to see stackless traversal implemented, however from a quick investigation it only supports AABB nodes (unless i've missed something?) and the ray-triangle intersection does not seem to be implementing any of robust intersection checks. There is also no instancing support.</div><div><br></div><div>I hoped to see some vectorization happening in QBVH traversal, but there's no such a thing, all the children are traversed one by one.</div><div><br></div><div>Main advantage f those kernels would be from bucketed ray-to-scene intersectons. It might be better performance, but we do something really similar in the split kernel (we use stack there tho). Would be interesting to see how the FireRays kernels will behave after OBB/MoBlur/Hair support added tho.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, May 18, 2016 at 7:15 PM, Mohamed Sakr <span dir="ltr"><<a href="mailto:3dsakr@gmail.com" target="_blank">3dsakr@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi,<div><br></div><div>looks interesting!</div><div>I wonder if there is a method to use this into Cycles and test if it will improve "I expect Cycles BVH has many areas to improve".</div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, May 18, 2016 at 7:05 PM, Stefan Werner <span dir="ltr"><<a href="mailto:swerner@smithmicro.com" target="_blank">swerner@smithmicro.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
AMD published the source code for their OpenCL ray tracing kernel and sample renderer:<br>
<a href="https://github.com/GPUOpen-LibrariesAndSDKs/FireRays_SDK" rel="noreferrer" target="_blank">https://github.com/GPUOpen-LibrariesAndSDKs/FireRays_SDK</a><br>
<br>
>From skimming the source code, they have embree 2.9 built-in as a fallback for CPU rendering. Haven’t dug deeply into it yet, I haven’t seen any references to motion blur or hair yet though.<br>
<br>
-Stefan<br>
<br>
_______________________________________________<br>
Bf-cycles mailing list<br>
<a href="mailto:Bf-cycles@blender.org" target="_blank">Bf-cycles@blender.org</a><br>
<a href="https://lists.blender.org/mailman/listinfo/bf-cycles" rel="noreferrer" target="_blank">https://lists.blender.org/mailman/listinfo/bf-cycles</a><br>
</blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
Bf-cycles mailing list<br>
<a href="mailto:Bf-cycles@blender.org">Bf-cycles@blender.org</a><br>
<a href="https://lists.blender.org/mailman/listinfo/bf-cycles" rel="noreferrer" target="_blank">https://lists.blender.org/mailman/listinfo/bf-cycles</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div><span style="color:rgb(102,102,102)">With best regards, Sergey Sharybin</span></div></div>
</div>