Would node-based workflows make AI 3d tools more useful ?
Posted by Lightnig125@reddit | LocalLLaMA | View on Reddit | 4 comments
I’ve been working on Modly, and I recently started experimenting with a node-based extension system.
The idea is to let people build their own workflows using nodes that can be written in python or js/ts, instead of having a fixed pipeline.
Instead of just “generate and export”, you could chain steps like preprocessing, generation, post-processing, etc.
I’m curious if this kind of node-based workflow would actually be useful in practice, or if it just adds complexity.
One interesting thing is that someone already started building an auto-rigging workflow on top of it, which wasn’t something i initially planned for.
Would love to hear how you’d approach this do you prefer fixed pipelines, or more flexible node-based systems ?
If you are interest by the project : https://github.com/lightningpixel/modly
draconisx4@reddit
Node-based workflows can add crucial oversight by letting you insert safety checks at each step, which is key for avoiding errors in AI tools. It's a smart move for building more reliable systems without locking users into rigid setups.
Lightnig125@reddit (OP)
Thanks for your feedback. I actually find this approach more interesting, it makes it possible to create complex things in a visually accessible way
Pitiful_Gene_3648@reddit
Lightnig125@reddit (OP)
It’s still in development; it’s been delayed due to the new extension system