Grasshopper 0.9.0006 available for download

An incremental release is available for download. It fixes 4 bugs in the 0.9.0005 release. To wit:

Local data would not be read from files saved with earlier versions. This is fixed.
Bar Graphs had missing input grips, this is fixed.
Colour Swatched had missing output grips, this is fixed.
Cross Reference component would display an error if no inputs were connected, this is fixed.

David Rutten

david@mcneel.com

Poprad, Slovakia

Replies to This Discussion

Permalink Reply by Chris K. Palmer on August 3, 2012 at 12:12pm

This fixed it for me too. Thanks Danny.

Permalink Reply by Thomas J. Mrokon on August 3, 2012 at 4:58am

here are the results:

and the GHA list has a lot of duplicates....

etc.

I will try to remove those duplicates like Danny and hope this will solve it...

Permalink Reply by Raul Matagringo on August 3, 2012 at 4:03am

Hi,

when i load GH i get this message:

Can someone tell me what im doing wrong?

Tank you.

Permalink Reply by Danny Boyes on August 3, 2012 at 4:06am

Hi Raul,

It is happening to lots of people. If you have a look at David's reply to Thomas just above your post it is related to the same error.

Permalink Reply by Raul Matagringo on August 3, 2012 at 4:15am

Yep, it was my fault. I was a bit too slow. Sorry.

I found something! Because of some restrictions i have under user\AppData\Roaming one "Grasshopper" directory. Inside are Autosave, Libraries, ScriptBackup and UserObjects

Then i have C:\Users\AppData\Roaming\McNeel\Grasshopper_0_9x\Components

I think GH is trying to load the *.gha's from this 2 dir.

I mean data from user\AppData\Roaming\Grasshopper\Libraries and from C:\Users\AppData\Roaming\McNeel\Grasshopper_0_9x\Components

Permalink Reply by phillip on August 3, 2012 at 4:48am

When opening files created in 0.8.0066 Gh is very slow in handeling them. If I just delete an old component (even if its not wired to anything) or add a new one to the canvas, it will freeze for about two seconds. Components - exept clusters - are upgraded.

New definitions behave normal.

Permalink Reply by phillip on August 3, 2012 at 6:19am

Found out, the problem is caused by Geometry Pipeline. In my definition it´s linked to a series of 60 surfaces. Could it be, the pipeline is rechecking the input everytime I add or change components, even if they are not linked to it?

Permalink Reply by David Rutten on August 3, 2012 at 6:32am

Shouldn't be the case. Geometry Pipeline *should* only update when the Rhino geometry changes or when you change the settings of the pipeline.

Can you post the files that show the slowdown so I can run some tests here?

David Rutten

david@mcneel.com

Poprad, Slovakia

Permalink Reply by phillip on August 3, 2012 at 8:30am

Just sent you an email...

Permalink Reply by Gongming Liu on August 3, 2012 at 4:48am

many thanks~

you are the man

Permalink Reply by David Stasiuk on August 3, 2012 at 8:07am

Thanks for this update, David...so useful. I have a question with the new Sift component...was it intended to output null values? It seems odd to have to attach a clean component to each output. For example, if I have a list of 4 items:

and I use a mask of

The "0" list results in

null

And the "1" list results in

null

Permalink Reply by David Rutten on August 3, 2012 at 10:31am

Yes. Sift outputs nulls and Combine puts it all back together again. This allows you to channel some data through some components and the other data through other components. This was of course possible before, but then it was really difficult to put it all back together again in the right order.

David Rutten

david@mcneel.com

Poprad, Slovakia