dfelinto at gmail.com
Wed May 4 11:52:23 CEST 2011
a short (sort of) related question:
For engines that are not doing realtime rendering, will the API allow for
custom glsl code to be hooked up in the material system for pre-visualize
Or this is outside the scope of cycles/render api?
2011/5/4 Brecht Van Lommel <brecht at blender.org>
> That's indeed the intention. I need some time still to work out plans,
> but I think design discussion can start soon. There's quite a few
> things to cover: preview and viewport rendering, data synchronization,
> pluggable node system, texturing workflow and faster data access
> through C/C++, and other things you may come up with. It's probably
> best do discuss these one by one, with me writing up a proposal, and
> then we can discuss it further.
> There's already this wiki page for render API feedback from a while
> ago, a similar list from Yafaray integration developers would be
> Anyway, I'll do a proper announcement later on.
> On Wed, May 4, 2011 at 1:08 AM, Alvaro Luna Bautista
> <alvarolunab at yahoo.es> wrote:
> > Hi there,
> > I have read in the blender artist forum that the idea is to have external
> render engine developers in touch with blender devs (brecht?) as much as
> possible to make integration better for everybody.
> > If you are really interested in our input we are up for meetings or any
> kind of coordination work you would like to have regarding the render API.
> Name it and we will participate. I hope you are able to appreciate this
> > Looking forward to your answer. Regards.
> > Alvaro Luna Bautista
> > YafaRay project team member
> > _______________________________________________
> > Bf-cycles mailing list
> > Bf-cycles at blender.org
> > http://lists.blender.org/mailman/listinfo/bf-cycles
> Bf-cycles mailing list
> Bf-cycles at blender.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Bf-cycles