Just something I came across that seemed worth sharing.

      • Gamma@beehaw.org
        link
        fedilink
        English
        arrow-up
        11
        ·
        1 year ago

        Which is what the maintainers said made more sense, since it would allow more frequent updates and could be done better (than what they had) as a community effort

      • Sethayy@sh.itjust.works
        link
        fedilink
        arrow-up
        2
        ·
        1 year ago

        and when they removed it they almost requested the community does something like this, if there’s enough interest

  • Gamma@beehaw.org
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    1 year ago

    👀 This looks nice, I like that it has some abstraction and isn’t just coding with blocks

    • Vahera@kbin.social
      link
      fedilink
      arrow-up
      4
      ·
      1 year ago

      Hi! Great question. No, the Orchestrator does not generate scripts you can attach to nodes but instead generates a resource you can run using the Orchestrator autoload. We are looking into adding an OrchestrationPlayer node that will allow you to directly call the orchestration without needing to write boilerplate code to do so.

  • crittecol@lemmy.world
    link
    fedilink
    arrow-up
    3
    ·
    1 year ago

    Super cool! Might be nice to have a helper node you could add to scenes that just lets you trigger orchestrations from pure signals or more easily from animation players, so you could stay out of the script editor completely for the really simple stuff.

    • Vahera@kbin.social
      link
      fedilink
      arrow-up
      3
      ·
      1 year ago

      Thank you for your suggestion and enthusiasm for Orchestrator. Most definitely, we’ll look at adding an OrchestrationPlayer node that can be pre-configured with the orchestration reference. We’ll add the ability to start the orchestration directly via the player node and look into how we can couple starting via signals.