Hi Actually that's the not the current state anymore, for Cycles hair rendering access to child particles was added. Cycles is implemented in C++ but goes through the same API as python exporters. Here's example python code: http://www.pasteall.org/39292/python
The API is not the easiest to use but it works this way because child particles paths are computed on the fly. Brecht. On Wed, Jan 30, 2013 at 9:02 AM, Maurice Raybaud <[email protected]> wrote: > > Hi, > > This may be my first post on this list, so I'm certainly mistaken about a few > things :) but still: > > The following bug report describes the current state of particle Python API > and more specifically in my case hair: > https://projects.blender.org/tracker/index.php?func=detail&aid=33287&group_id=9&atid=498 > > The > best thing for me would be to have ChildParticle.hair_keys to get the > trajectory steps of each child like for parent particles > > I have > heard this is a lot of work to implement, but just want to add one more > request to the rest for it: I implemented basic hair support for POV-Ray > exporter and tried to find other Python exporter that did things > better, to find out that Vray exporter, using more hardcoded approach > was the only other one along cycles to get acces to children hair. > > Could this C code be given access from Python? or is it just not possible? > > Thanks for reading > _______________________________________________ > Bf-committers mailing list > [email protected] > http://lists.blender.org/mailman/listinfo/bf-committers _______________________________________________ Bf-committers mailing list [email protected] http://lists.blender.org/mailman/listinfo/bf-committers
