New Blackjack PR/Release brings in gizmos to make editing your procedural models more fun
github.com/setzer22/blackjack/pull/62Posted Nov 6, 2022, 7:09 PM UTC
Posted Nov 6, 2022, 7:09 PM UTC
Hello, I just found your app you are developing, and have a question for you, if you don't mind.
One of the drawbacks with node-based histories is that they become complex and unwieldy as the history grows. In the 3ds max and blender, the history is stack-based, where history is only recorded when the user adds modifiers.
Is it possible to add an "edit poly" node that erases all direct modeling operations (every extrude, bevel, cut, etc), but simply is a placeholder for the model's end state after all of those operations have been performed? Sort of like a "bookmark." Then, you add several "edit poly" nodes on top of one another, and you have a series of snapshots, or bookmarks, of your model you can go back to, instead of having to deal with hundreds of operations (every single extrude, bevel, cut, etc).
Is it possible to add this ability, while retaining normal node functionality? That way, the user would have the best of both worlds; the speed and efficiency of stack-based history, and the power and flexibility of node-based workflows.
Hey, thanks for asking! 😄 This is something I've had considered for a while. The main pieces are almost there: We have gizmos, and there will be a way to pick faces / edges / vertices from the viewport soon.
So I've been envisioning some kind of meta-node that codifies a "streak of modelling operations". It could encode a sequence of operations like: "Translate vertex 3 by this amount", "Bevel edges 1 and 2 by this amount", "Scale face 5 by this amount"... one after the other. The idea is that the node would record operations as they happen on the viewport, via the gizmos, but nothing would be destructive: You'd still have the operation logged as a series of atomic steps internally, only visually collapsed into a single node.
This is something Houdini already supports to some extent. The "Edit" SOP already can store multiple primitives being translated, rotated or scaled at the same time. I have a more lightweight version of this in Blackjack's "Edit Geometry" node, but currently you have to add multiple nodes to perform multiple sequential edits which I agree can be a bit cumbersome in some workflows. Ideally, each node in your graph is a semantically meaningful action that stands on its own, and there should be ways to collapse multiple sequential edits that perform a single logical operation.
One issue with this approach is that you loose some of the procedurality. When I say "Bevel edges 1 and 2 by this amount", the structure of the input mesh is kind of locked, if I change its topology. This is something users would need to learn to live with. But other than that I don't see any major blockers to implement this :) It's just something that may take a while since I'm currently focusing on more foundational things.
Oh cool, that sounds exactly what I was getting at. A "meta-node" is a good way to characterize it; that is essentially what the edit poly modifier is in 3ds max, but it doesn't give you the ability go back and edit each individual modeling operation.
You could have nodes for each modeling operation (bevel, extrude, cut, etc) for users that need that power, at the expense of efficiency. Then you could have a "mesh snapshot" node that has destructive versions of those operations (but are still present in the undo stack so you can revert a change within the snapshot node) for users that want to minimize node wrangling in exchange for speed. When a user adds the mesh snapshot node to his model and it is active, all hotkeys could be mapped to the direct operations within that node for a fast and seamless workflow.
The limitation in your last paragraph is in 3ds max as well; you can't go back and make topological changes to a previous edit poly modifier if there is another stacked on top of it. But users don't mind; the limitation is worth it for the efficiency it provides.
If your app could do both, that would make it VERY powerful and unique among all the 3d modellers. You'd essentially have the functionality of houdini and 3ds max in one app.
From the README:
Blackjack is a procedural modelling application, following the steps of great tools like Houdini or Blender's geometry nodes project. At its core, Blackjack is a simple node-driven interface where you can compose operations to create a 3d mesh in a non-destructive way.