- User Since
- Jul 4 2014, 7:47 PM (325 w, 2 d)
Jul 10 2014
I'm right here :) I'm new to the community so I don't know what's the usual method, but a task for this would be nice. I'm working on improving the exporter in github here: https://github.com/fabiosantoscode/cycles-xml-exporter . you can post issues there or pull request, and collaborate like that.
Jul 8 2014
Really nice to know that shaders are somewhat taken care of already :) I'm trying to get Cycles working on the web browser, actually, through the CrowdProcess platform.
Jul 7 2014
I don't understand why these must be written to disk. Textures are loaded into RAM anyway, are they not?
Jul 6 2014
The blender-cycles standalone XML exporter is only capable of exporting meshes, so I'm enhancing it.
Jul 4 2014
I'm currently improving the current blender > cycles standalone XML exporter and I hit a problem which I feel needs solving: the <connect> tag (inside the <shader> tag) currently identifies the nodes involved in the connection in a less-than-optimal way: "nodeName (SPACE character) socketName". This is problematic because node names will not be able to have spaces this way.