4 ms·
> using graphical programming (by connecting nodes) I use Octane Render [0] whose materials editor is based on graphically connecting nodes which might be mate
by KineticLensman 6y ago
> using graphical programming (by connecting nodes)
I use Octane Render [0] whose materials editor is based on graphically connecting nodes which might be materials (diffuse, specular, etc), image files, mappings, colours, procedurals, emitters and many more. Compared with conventional languages the Octane shader language lacks any sort of conditional or iterative constructs, which obviously simplifies the 'programming' required.
I'm happy with graphical node editing for this shader use case. However, I sometimes really miss the ability to do a global textual search and replace across multiple materials, e.g. to change the file name of a normal map that is used in a node in multiple materials. I suspect that there would be similar frustrations when maintaining and updating a complex system configuration using a 'no-code' node-based mechanism.
[0] https://home.otoy.com/render/octane-render/ https://home.otoy.com/render/octane-render/
- otoy 6y agoHave you played around with octane script nodes for the use cases above? They should allow you to do almost anything in the node graph through Lua (or native code via ffi) - Jules
- KineticLensman 6y agoThanks for this great reply, and sorry for lack of response! I should have been more precise - I was actually referring to the Octane plug-in for Daz Studio, where I don't think script nodes are available.