<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Aug 21, 2013 at 8:37 AM, Matt Ebb <span dir="ltr"><<a href="mailto:matt@mke3.net" target="_blank">matt@mke3.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div> Might also want to consider what sort of bottlenecks or restrictions might be imposed on Cycles by the scene description format (i.e. can you parse or read files or included files in parallel? Do you need to read ).<br>
</div></div></blockquote><div><br></div><div style>Sorry, left out the end of that - "Do you need to read the entire scene description file in order to get started rendering or building geometry internally? Or can you start doing things incrementally as the file is being read?" As far as I understand RIB can have some interesting internal dependencies in some cases that can make it difficult to know what geometry is exactly where, without processing the entire structure of the RIB..</div>
</div></div></div>