Hi,<br><br>I probably wont be able to be online this sunday meeting.<br>Anyway my SoC plans for this first week are:<br><br>===comming week===<br> *find the bug that makes some black dots.. before I only changed the API but it seems some bugs appeared.. I would like to have those sorted out before continuing. I already spend some time trying. but its kinda hard to debug it.<br>
*plugging the bvh-tree available on blenlib as a tree structure<br> *if time allows add also a raytrace structure to instance-support<br><br>===questions===<br> none<br><br>===schedule===<br> I am still a under school works, but hopefull the advanced I gave before will allow me not to get behind schedule.<br>
<br><br><div class="gmail_quote">2009/5/11 Brecht Van Lommel <span dir="ltr"><<a href="mailto:brecht@blender.org">brecht@blender.org</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi André,<br>
<div class="im"><br>
On Mon, 2009-05-11 at 16:12 +0100, André Pinto wrote:<br>
> Hi all,<br>
><br>
> ==Questions==<br>
> this week I have been coding a more generic raytrace api and I have<br>
> some questions:<br>
><br>
> * In the new files (rayobject.h, rayobject*.c), I copied the GPL<br>
> license block from other files and changed copyright to "2009 Blender<br>
> Foundation". I also set the properties svn:keywords and svn:eol-style.<br>
> Is this all that needs to be done for created files?<br>
> And Is there any sample GPL licence block? i noticed those sligtly<br>
> change between files.<br>
<br>
</div>I don't think we have a policy on svn properties and the license block<br>
details, just do the same as another file in the directory.<br>
<div class="im"><br>
> * The exported functions from render, should all started with RE_ ?<br>
> That means the functions I added should be:<br>
> RE_rayobject_create/raycast/done/add..<br>
<br>
</div>Yes, use the RE_ prefix.<br>
<div class="im"><br>
> * Is it safe to assume that all MEM_callocN are aligned to 4bytes?<br>
<br>
</div>Yes (though obviously make a comment in the raytracing code that you<br>
rely on this).<br>
<div class="im"><br>
> ==API details==<br>
> Details about the ray trace design implementation<br>
> (render/intern/include/rayobject.h):<br>
><br>
> I denoted RayObject as everything where its possible to raycast<br>
> including a single face or a complex data structure.<br>
> Thus allowing to create compound structures (eg.: a bvh of octrees<br>
> (like 1 octree per object)).<br>
><br>
> In order to allow an eficient type-detectation mechanism, all<br>
> RayObjects are aligned to 4bytes, leaving 2bits of adress to determine<br>
> the type, so far 2 types exist:<br>
><br>
> RayFace - struct with coords, object and face.<br>
> RayObject - struct to an abstract raytrace aceleration, with callbacks<br>
> to generic stuff like: add faces, free struct and raycast<br>
><br>
> All callbacks like get coordinates/transform_coords, check_hit, where<br>
> removed for now.. as the functionality of those will be coded as<br>
> needed in a better way.<br>
><br>
> For now only API and Isect structure were modified.<br>
> Daniel Salazar(ZanQdo) reported an 9% improve on his quad core2 :)<br>
> At the moment only shadow rays work/were tested.<br>
<br>
</div>OK, design sounds good, and 9% is a nice start :).<br>
<br>
Brecht.<br>
<br>
<br>
_______________________________________________<br>
Soc-2009-dev mailing list<br>
<a href="mailto:Soc-2009-dev@blender.org">Soc-2009-dev@blender.org</a><br>
<a href="http://lists.blender.org/mailman/listinfo/soc-2009-dev" target="_blank">http://lists.blender.org/mailman/listinfo/soc-2009-dev</a><br>
</blockquote></div><br>