HoopSnake 0.6.0 out

At last, the new release is out! Download it at Volatile Prototypes or Food4Rhino.

The download file contains some new examples of multiple components working together in various configurations.

Changes:

- Major rewrite, allows for serial and recursive connection of multiple components.

- Added context menu with all basic commands. Hoopsnake can be controlled without opening the main panel.

- Control Panel has been simplified.

Replies to This Discussion

Permalink Reply by Manuel on September 14, 2011 at 12:00am

Thanks!!!

Permalink Reply by Yoann Mescam (Systemiq) on September 14, 2011 at 6:41am

Great !

Trying to make some useful definition to demonstrate it (thinking about packing) but I noticed the L output doesnt seem to reset. At the moment, the only way to fully reset is unloading the definition and reloading it.

Permalink Reply by Manuel on September 14, 2011 at 1:45pm

posible bug: after a loop, rhinoceros viewport doesnt update (show new geometry) until I select the component in grasshopper...

to the wish list:

1. input for number of iterations (ill be much simpler if i just connect a slider to the component).

2. add again the step icon to the control panel :D

Permalink Reply by Yannis on September 14, 2011 at 4:14pm

Thanks a lot for the replies guys!

Systemiq: Thanks for taking the time to make the definition..The L output is set to not reset for the total period of a loop due to sync issues (if it resets serially linked components take precedence and we don't want that). However, the reset function should normally do it..i'll investigate..;)

Manuel: Thanks for the viewport thing I'll look into it. Also, what do you mean exactly by number of iterations? Step button will indeed make it's return I found it also myself useful.

Again, thanks and look out for 0.6.1!

Permalink Reply by Manuel on September 15, 2011 at 9:20am

Hi,

I mean something like this pic and eliminate the "smaller than" thing:

I show the component to some students and they were like "why i cant connect directly the slider with the number of max iterations that i want?" XD

Maybe is the same B input, so if its a number do the number of iterations and if its a boolean do the boolean thing?

well just an idea, thanks.

Permalink Reply by Yannis on September 17, 2011 at 2:42pm

Hi Manuel,

Unfortunately it is impossible to completely change the functionality of the B* input; this is because in this generic form it can receive also stop conditions not based on number of steps, e.g. in an iterative optimization you may have a threshold value (just like I have at the square root approximation example), and therefore not a fixed number of steps.

Now, adding max iterations functionality *on top* of that is a different deal and may be doable. I'll look into it and let you know.

Thanks,
Yiannis

RSS