<div dir="ltr">Additionally, I discussed the current results in the wiki, here: <a href="http://wiki.blender.org/index.php/User:Jehuty/GSoC_2013/Results/Rendering_VDB_Volumes">http://wiki.blender.org/index.php/User:Jehuty/GSoC_2013/Results/Rendering_VDB_Volumes</a><div>
<br></div><div style>Rafael.</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Sep 25, 2013 at 10:12 AM, Rafael Campos <span dir="ltr"><<a href="mailto:rafaelcdn@gmail.com" target="_blank">rafaelcdn@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"><div>Apologies for the (ultra) late report.</div><div><br></div>=== This week ===<div><br></div><div>In the last two weeks, 3D texture sampling was finished, with support for either nearest neighbor, trilinear or quadratic interpolation mechanisms.</div>
<div><br></div><div>I had some trouble with different behaviors on the viewport when sampling using the OpenVDB library versus looking up values myself, for each voxel, without a cache - differences were expected, such as being slower and everything, but the resulting image was significantly different, past the difference of interpolation techniques. </div>
<div><br></div><div>Then Brecht came to the rescue and uncovered a bug on OpenVDB! :-D</div><div><br></div><div><br></div><div>=== Next week ===</div><div><br></div><div>I had already agreed with Brecht I'd continue working regardless of the SoC timeline. For one, I'd really like to get the library working on Blender fully-featured. Moreover, I intend to use the work done in lieu of an internship, for college.</div>
<div><br></div><div><br></div><div>=== Questions ===</div><div><br></div><div>None.</div></div>
</blockquote></div><br></div>