Ideas for Geometry Nodes
IDEAS FOR GEOMETRY NODES
We can think geometry nodes likes an oriented graph, and we can read the entire process from left to right. We can start with the actual problem and idea for solving that:
-
Put primitive objects inside geometry nodes .
- If we want to use with asset browser, we will put a primitive object inside the graph. When we import a g.n. asset we don't know the right primitive objects.
- We need to add another primitive inside(edit mode style) the graph for the same reasons
- With this, we create real standalone geometry node assets.
-
Use Geometry Nodes interface for all modifiers .
- For a standalone result, we must not use modifiers or move all modifiers inside g.n. interface
-
Add basic control structures nodes for greater customization .
- For loop, we can create two nodes(start loop, end loop)
- For the test, we can do the same things
- Using attributes such as variables
-
Create a node to add a custom python script
- Use that for particular requirements considering the objects selected in object mode.
Per aspera ad astra.
5 Comments
Yes, these should be standard features.
Also, these posts should only contain one idea. Makes it much easier to track when they're finished, etc.
* @h.goudey * No reason for spam. better remove this pls.
* @Zawardo * I can't remove posts here
Most of these are planned. Since geometry nodes is in active development, the current feature-set isn't really representative of the "final" result. It's just a matter of time!