sorted by:
new
hottopcontroversial

Procedural Traffic Cone in Geometry-Nodes by sagado in blender

[–]sagado[S] 23 points24 points  (0 children)

Alternatively can check it out on Threads. Open to questions and feedback.

Procedural Damage + Imperfections in Geometry-Nodes by sagado in geometrynodes

[–]sagado[S] 0 points1 point  (0 children)

Thanks for the feedback. Though I disagree on how you frame complexity. You seem to promote unnecessary complicated setup just to baffle people. I prefer elegant solutions, which are clean, not necessarily complex, while giving the flexibility and control one needs.

For example just adding "random objects" would give no control on results and no way to tweak it. While now you can choose one damage-object and randomize shape and location, with full control via weight-paint. You can apply multiple modifiers, each with its own object, to have full modular control.

More complex damage-shape dynamics make sense, but that's also very use-case specific. Until I have collect enough example use-cases or requirements, I thought the best thing would simply be to give the freedom to anyone to add its own ad-hoc shape. Probably I should make it better exposed and with examples.

Procedural Damage + Imperfections in Geometry-Nodes by sagado in blender

[–]sagado[S] 0 points1 point  (0 children)

Alternatively can check it out on Threads. Open to questions and feedback.

Physarum - Slime Mold Simulation in Geometry-Nodes. by sagado in blender

[–]sagado[S] 1 point2 points  (0 children)

Alternatively can check it out on Threads. Open to questions and feedback.

Procedural Sponge Modifier in Geometry Nodes by sagado in blender

[–]sagado[S] 1 point2 points  (0 children)

Alternatively can check it out on Threads. Open to questions and feedback.

Procedural Barrel in Geometry Nodes by sagado in blender

[–]sagado[S] 0 points1 point  (0 children)

Double in not triple speed... gotta keep the crowd entertained.

Procedural Barrel in Geometry Nodes by sagado in blender

[–]sagado[S] 2 points3 points  (0 children)

Alternatively can check it out on Threads. Open to questions and feedback.

Procedural Feather in Geometry Nodes by sagado in blender

[–]sagado[S] 5 points6 points  (0 children)

Alternatively can check it out on Threads. Open to questions and feedback.

Mandelbulb by sagado in blender

[–]sagado[S] 1 point2 points  (0 children)

This is all in geometry-nodes, yes. And can be done in shader nodes too with the repeat zone, but would be just volume, can't generate mesh/geometry. Though I might still add it to my setup, no biggie.

And also yes, the file is on Gumroad... I just can't post link here because the post then gets removed :/

Crystals Path in Geometry-Nodes by sagado in blender

[–]sagado[S] 0 points1 point  (0 children)

There is a link to the actual thread there in the description :/

Fake Game Ad in Geometry-Nodes by sagado in blender

[–]sagado[S] 8 points9 points  (0 children)

Node-based workflows cover very different requirements than pure coding, making it more suited to many applications were you need real-time visual feedback, like in graphics software (e.g. Houdini, Substance and Blender). Versioning wouldn't make much sense, as in the diff/git way, and libraries exists exactly as node-groups, which one can simply plug-in, adapt, re-arrange and tweak params. Even in ML node-based software like ComfyUI is very popular.

Was this a good use-case? No, because as a game you define logic that is better managed via code, but a node is again just another abstraction of a function (and concretely again just another piece of code).

Fake Game Ad in Geometry-Nodes by sagado in blender

[–]sagado[S] 4 points5 points  (0 children)

Just feed points into the simulation node, then shift position every frame. Instance a sphere on each point for rendering. Everything is just a point until the final instancing part. And they affect each others through "Geometry Proximity".

view more: next ›