Grasshopper

algorithmic modeling for Rhino

GH keeps crashing irretrievably when wrong components are connected

hello,

i don't want to moan, for GH is a free tool (which makes it so popular), but it is obvious it's yet not stable.

It crashes every time two wrong components are connected leaving the only solution of shutting the entire Rhino session for it immediately jams all of CPU.

This is totally annoying when happening unexpected thus the definitions and rhino project weren't saved in the latest status.

So it would be immensely helpful if in the next GH release component slots would only eccept wires from components which transmit the correct kind of values/information/data/dimension etc.., and reject all others, along with a more useful hint and advise in the slot info-tag.



Please take a look at this for it would be a huge progress, maybe the most important.

Also: please make the selection status and info-tags of all the buttons and menu options less nervous and remain longer.

Those are my improvements suggestions,

thanks.


-

Views: 251

Replies to This Discussion

I think the next release has an autosave feature that creates a copy of the definition just before you do something that might hang the computer.
I'm not sure why you have that problem. Whenever i connect to an input a data type that it can't read, i just get a red component with an error, the computer doesen't hang. The most common way of making Grasshopper hang is by accidentally connected a flat list of data and a grafted list of data (that should have been flattened out) on the same component. Are you sure you are not doing that?
Well, could be, i'm not sure, for i don't understand the term "flattened" und "grafted" in GH yet.
So i don't want to deny that.

And usually i recieve a red componet too, your right, but as described, not seldomly i have to start all over again.

-
This is where 'draw fancy wires' comes in handy. I think it should be a default enable. And essentially when you hook up a tree to a flat list, you get your GH repeating a task an unimaginable number of times.

Perhaps there could be an Autocad style safety switch there asking 'are you sure you want to do this' (used to be a common phenomenon on acad 2006 and below for large hatch areas.. dont know if it still exists)?

And yes, I'd say if you don't know something well enough, you can make anything crash.. but once you start getting the hang of it, you know what not to do. So Tim, perhaps a little more time and you'll be in more familiar waters, causing less agony.

GH is not an unstable software, its just a matter of how you use it. Almost all software deal with these issues with safety switches and warnings... which is just a matter of writing more and more error trapping code, and a sh*t load of if loops.

RSS

About

Translate

Search

Videos

  • Add Videos
  • View All

© 2024   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service