Kangaroo component

by Daniel Piker

Mar 28, 2010

The definition for the latest video I posted showing how simple it is to set up basic force interactions with the Kangaroo component. That huge set of inputs might seem daunting at first, but they nearly all have default settings that you don't have to change unless you want to.

Load Previous Comments

  • Daniel Piker

    Ben - Yeah it's a bit complex looking I know.
    One way forward would be to make it a direct Rhino plugin instead, and set properties for objects (like spring stiffness etc) through that, just like you do with a renderer. Though I'm finding that having all the inputs Grasshopper controlled gives a lot of flexibility.

    As I said, most of those settings you won't need to touch most of the time. One solution might be if there was an option to hide or dock some of the inputs when they are not needed.
    I am also looking at a way of consolidating all the Power Law and Spring settings into a single string input (that would also allow users to use custom expressions for force laws).
    And yes, a good help document would be good and helpful!

    Mar 28, 2010

  • Mårten Nettelbladt

    That looks very nice Daniel! Can't wait to try it out!
    Just one minor thing:
    Some of the short words in the left column end up a long way from their grips, which may cause confusion, especially in such a long list. Is it possible to try to align them with the left side of the component? I know the standard components in GH use a centred column so it may not be an option.
    Thanks!

    Mar 28, 2010

  • taz

    You could extract groups of input parameters as separate components, just like David added [Loft Options] for tweaking [Loft].

    Just my $0.02

    Mar 28, 2010