4 ms·
Honestly I'm a bit disappointed with their geometry nodes project. I went into it expecting a generic visual scripting language aimed at generate geometry. That
by serverholic 5y ago
Honestly I'm a bit disappointed with their geometry nodes project. I went into it expecting a generic visual scripting language aimed at generate geometry. That IS what it is to an extent, but the design decisions are strange and limiting to say the least.
The main issue is that data is only stored in the geometry itself, per-vertex. So if you just want a single variable you're out of luck. Math operations operate on vertices so you can't just multiply two numbers, you have to store a number in each vertex, then multiply all vertices by the same value. It's like every node is for-loop that loops over vertices.
This limited design is useful for certain things like scattering rocks over terrain but not much else.
- hrnnnnnn 5y agoCheck out the Nodevember geometry nodes entries this year. You can accomplish quite a lot with it as it is. Also, the implementation in 3.0 is very different from the one in 2.93. https://twitter.com/search?q=%23nodevember2021%23geometrynodes https://twitter.com/search?q=%23nodevember2021%23geometrynod...
- deleted 5y ago[deleted]
- pmichaud 5y agoI think what you wrote here is just straightforwardly not correct, eg. you can absolutely set a variable and multiply arbitrary numbers in addition to working with vertex data. There are also a lot of other ways to store and interact with data, eg. textures (either procedural or painted). Maybe you should have another look.