<div dir="ltr">Hi Brecht,<br><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, May 1, 2013 at 11:12 PM, Brecht Van Lommel <span dir="ltr"><<a href="mailto:brechtvanlommel@pandora.be" target="_blank">brechtvanlommel@pandora.be</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Rafael,<br>
<div class="im"><br>
On Thu, May 2, 2013 at 3:23 AM, Rafael Campos <<a href="mailto:rafaelcdn@gmail.com">rafaelcdn@gmail.com</a>> wrote:<br>
> Of all ideas, I'm going with OpenVDB integration, and adding Voxel Data<br>
> texture to Cycles.<br>
> I feel that leaving Point Density texture out of the proposal is a bit of a<br>
> shame since the texturing part of volume rendering will be only partially<br>
> satisfied, but I'm all worked up with OpenVDB now, and there is a lot to be<br>
> gained in the future by supporting it.<br>
<br>
</div>Ok, sounds good.<br>
<div class="im"><br>
> True. Since there isn't much time before the submission deadline, I'll come<br>
> up with ideas for the design and interaction of these new nodes so we can<br>
> discuss, but probably after submitting the proposal. Is creating a page on<br>
> the wiki for the proposal a good idea or is it better to wait ?<br>
<br>
</div>The main thing is to get the proposal submitted with about a paragraph<br>
of explanation for each part you plan to implement, then wait to see<br>
if it is accepted. The specific design can still be worked out<br>
afterwards.<br>
<br></blockquote><div><br></div><div style>Ok, that's good to hear. I was under the impression I had to have most things worked out beforehand. </div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
If you want to create a wiki page with more ideas that's fine but not<br>
strictly necessary.<br>
<div class="im"><br>
> I'm thinking import/export operations for the OpenVDB format, and using the<br>
> data structure during rendering. Did I miss something or is that it?<br>
<br>
</div>Ideally there would be some integration with the smoke system, so<br>
smoke can be exported to OpenVDB and then render from those files, not<br>
sure if you would cover that under import/export. Currently we do not<br>
have anything like a volume object type in Blender, so it's not<br>
obvious to me what you mean by import, how that would work.<br></blockquote><div><br></div><div style>Right. By export, I meant the smoke data to the OpenVDB structure.</div><div style>However, I'm thinking we would also use OpenVDB for other sources of volume data, such as sequences of images or even raw formats, as supported by the current Voxel Data texture on Blender Internal, no?</div>
<div style><br></div><div style>Thanks again,</div><div style>Rafael.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5"><br>
Brecht.<br>
_______________________________________________<br>
Bf-cycles mailing list<br>
<a href="mailto:Bf-cycles@blender.org">Bf-cycles@blender.org</a><br>
<a href="http://lists.blender.org/mailman/listinfo/bf-cycles" target="_blank">http://lists.blender.org/mailman/listinfo/bf-cycles</a><br>
</div></div></blockquote></div><br></div></div>