46
I might have gone a bit over the board with these nodes (lemmy.ml)
submitted 1 month ago by to c/blender@lemmy.world
28 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] [S] 7 points 1 month ago* (13 children)

believe it or not, it does reuse many nodes. sim/repeat won't be of much help here, there're no repetitions. I'm testing an addon I've been creating which converts regular Python logic into geometry nodes. this is like ~500 lines of Python code converted into nodes. It's making a procedural full-quad wall with crenellations from an edge. unsurprisingly, most of the nodes are to correctly treat edge cases/self intersections, removing stray edges/faces etc.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 13 child comments
    •
  • [–] 2 points 1 month ago* (7 children)

    I've built a DSL for generating geometry nodes setups from a high-level Python-like script. It is still undergoing major architectural improvements, but you can already try it out. Let me know what you think. ✌️

    https://github.com/denikryt/NodeForge

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 7 child comments
    •
  • [–] [S] 1 point 1 month ago (5 children)

    looks nice! i wanted something more code friendly, so mine actually parses math expressions, if statements, lambda functions, loops etc and decides internally what nodes it needs to put together (hence the horrible looking node sausage). so you literally write a python logic, which it then transpiles and compiles into a node tree. in other words, you never actually have to think in nodes.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] 2 points 1 month ago* (4 children)

    My goal was to think about nodes as functions and operations that could be described with simple Pythonic syntax. Every node is a function with positional arguments as socket inputs and a return value as a socket output. The mathematical operation nodes could be described as simple operators like + - // etc. The links between nodes are described as simple variable assignments and passing variables into functions and so on.

    Basically, the idea it to think about Geometry Nodes setup as a script and reduce the Blender API Geometry Nodes boilerplate, while keeping it possible to address a specific node when needed.

    I also put a bunch of work into the Extension API, which makes it possible to extend the functionality of the DSL with additional third-party libraries with its own defined methods and logic and use them in a familiar way.

    I'd be happy if you tried it out! 🌽

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] [S] 1 point 1 month ago (3 children)

    yep, that's the same idea! i'm happy to share the code once i clean it up a bit, and you should feel free to transfer any of the functionality. there are few features i added which i really like, such as a support for LSP and type hints in an external IDE, plus an ability to write the code outside, while the add-on auto-regenerates the node-group if a file is changed. another cool thing is you can inline functions, i.e.:

    # these two are automatically inlined (i.e., nodes added to the active group)
@inline
def foo(x: float, y: bool):
  return x**2 if y else x**3

foo = lambda x, y: x**2 if y else x**3

# while this becomes a reusable node group
def foo(x: float, y: bool):
  return x**2 if y else x**3
  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 1 point 1 month ago (2 children)

    Interesting, I'm looking forward to seeing your project! I'll note the features you've mentioned, the LSP should be a really handy one : )
    The declaring of inline functions i.e. creating nodes in the root node group is something I feel is lacking in my project right now. Would you make a post about the addon somewhere?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 1 month ago (1 child)

    Wow. That's really cool. And, one hell of a time-saver for big models.

    Does it follow terrain? How does texture input work? How would you handle a big battle scene where a section of wall gets destroyed by a siege engine?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] [S] 2 points 1 month ago

    :D thanks! i actually already added support for towers and will add other adjacent buildings soon too. the plan is to also have a gatehouse and generative arcs. I'm currently trying to work out the general topology with all the edge cases and then will add decorative elements.

    it follows a custom edge which doesn't necessarily lie in a single plane, so it's trivial to add a shrinkwrap or another node to make it follow a terrain. texture input is a good question. uv of this thing might be totally messed up, but a generative material should work ok.

    for the battle scene - it does produce a well treated topo, so you could chain another destruct modifier. )

    will be happy to share once it's more mature.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 2 points 1 month ago (1 child)

    This hurts my brain imagining how I would go about recreating something similar.

    What I tried to convey is that...
    duplicating nodes = more nodes, shorter noodles, fewer reroutes
    reusing nodes = fewer nodes, longer noodles, more reroutes
    and I try to find a good middle point where it is not confusing mess XD.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] [S] 2 points 1 month ago

    agree, the whole advantage of writing this python library is that debugging a code is much easier than a noodle of nodes (especially when doing conditionals, math etc). it also supports factorization into functions. and since it produces ultimately a geometry node group, it's as fast and customizable as if it was made by hands. i'll post the add-on as soon as it's ready if people are interested (free ofc).

  • permalink
  • fedilink
  • source
  • parent