<div dir="ltr">Jacob Merrill <span dir="ltr"><<a href="mailto:blueprintrandom1@gmail.com" target="_blank">blueprintrandom1@gmail.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p>Is there any way to socket the render?</p></blockquote><div>My first instinct is that there will be one "best" renderer for any specific system. So swapping out renderers at runtime or between runs doesn't make sense. Plus that would be a *nightmare* to code up! There will most likely be platform-specific code though, and options to enable or disable at build time.</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<p>Can data be independent of the render?</p></blockquote><div>For the most part yes. It gets interesting for materials & shaders-as-content -- some might be specific to the renderer or targeted game engine. This is still very much open for design.<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<p>So you could later update/change render features without effecting the rest of blender?</p></blockquote><div> From one release to the next you mean? Please clarify.</div><div><br></div><div>-- Mike</div></div></div></div>