<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><BR><DIV><DIV>On Mar 8, 2007, at 2:20 AM, Stéphane Grabli wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite">Hi,<BR><BR>Freestyle NPR is a procedural renderer that produces<BR>line-drawings from 3D models:<BR><BR><A href="http://freestyle.sourceforge.net/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://freestyle.sourceforge.net </A><BR><BR>Recently, a project aiming at integrating Freestyle <BR>to blender was initiated.<BR>In this context, we are seeking advices from people familiar<BR>with Blender as to how such integration would best happen.<BR>Ideally, since Freestyle only produces contour lines (currently as <BR>2D triangle strips living in image space), its output<BR>would easily be composited (in a way or another) to other<BR>rendered elements such as shadows, objects interiors etc.<BR><BR>In short: How should a contour-line renderer be integrated <BR>to Blender?<BR></BLOCKQUOTE><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Well. I think the compositing node was a really bad idea (like I said on the dev-board). Blender, as it is, is pretty organized. I do stuff in 3d, i render it, it goes to the compositor, from there to the sequencer, compressor etc. As it is (AFAIK), apart from the "defocus" node, the compositor is completely cut off from the 3d environment. ( for example: one problem with the compositing node approach: setting multiple material settings in blender isn't possible, you have to switch renderers to see all the options) Maybe that could change? It probably should. But I think that would be a much larger project than incorporating a renderer.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>What I think should happen? Just integrate freestyle as another renderer. Why?</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>As it is, Blender supports using multiple renderers in the compositor. If I want to use separate renderers in a composite, I have to either use either images, or separate scenes. This works for the most part and can be very useful since seperate scenes can have linked data. It is a bit unwieldy to newcomers and not an obvious option for people to use, but then again, most beginners won't be compositing. Using a linked scene also allows me to set material options etc seperately (override materials) on different "scenes" by switching the material link from "ME" (block) to "OB" (object). I could specify different objects to be rendered, add things etc. The possibilities are far less limited than merely creating a compositing node that dumps all objects on the user with little options to change shading "look".</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Most people think of Layers>Passes, not Scenes(renderer)>Layers>passes, but as it is in Blender, however, it works! and I like it.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>So there's my case. I just didn't want to say that on the dev-board and start a debate.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><BLOCKQUOTE type="cite"><BR>Thanks!<BR><BR>Stephane & Emmanuel<BR><BR><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">_______________________________________________</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Bf-funboard mailing list</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><A href="mailto:Bf-funboard@projects.blender.org">Bf-funboard@projects.blender.org</A></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><A href="http://projects.blender.org/mailman/listinfo/bf-funboard">http://projects.blender.org/mailman/listinfo/bf-funboard</A></DIV> </BLOCKQUOTE></DIV><BR></BODY></HTML>