Grasshopper 0.7.0014 available for download

Dear testers,

Grasshopper 0.7.0014 is available for download.

This release fixes a number of serious bugs with file reading and scripting components. If you've been using an earlier 0.7 beta, please upgrade to this version.

Grasshopper 0.7 undoubtedly still contains many bugs and should not be used for important work/files as it is less reliable than 0.6.X

David Rutten

david@mcneel.com

London, UK

Replies to This Discussion

Permalink Reply by CarloMaria Ciampoli on May 16, 2010 at 2:48pm

thanks David!

Permalink Reply by Daniel Piker on May 16, 2010 at 3:57pm

Thanks David! Awesome stuff

Permalink Reply by raf2205 on May 16, 2010 at 4:04pm

Hi David,
I opened a definition wrote in GH 0.6.0059 in this new release 0.7.0014 you just posted and had the following warning message.
Can you please light me on this ?

thanks

raf

Attachments:

errors.png, 8 KB

Permalink Reply by David Rutten on May 17, 2010 at 1:09am

Hi raf,

can you send me the file?

--
David Rutten
david@mcneel.com
London, UK

Permalink Reply by Tuan N. Tran on May 16, 2010 at 5:34pm

David,

Great release with Galapagos! Can you please post the catenary examples you showed at the AA recently? Thanks.

Permalink Reply by David Rutten on May 17, 2010 at 1:10am

Attached.

--
David Rutten
david@mcneel.com
London, UK

Attachments:

GalapagosExamples.zip, 176 KB

Permalink Reply by Tuan N. Tran on May 16, 2010 at 11:46pm

Hi David

I set up Galapagos to solve for the minimum bounding box. It worked great for the generic test case of a rotated box! Thanks again for the release. However, there's some strangeness going on with the bounding box.

On the left is the original with a GH bounding box. The middle is the bottom half (rhino BooleanSplit) with a GH bbox. The right is bottom half with a rhino bbox. As you can see, the middle and the right bboxes are not the same.

Permalink Reply by David Rutten on May 17, 2010 at 1:12am

Yes I see. I think RhinoCommon too often uses the quick'n'dirty BoundingBox (which operates only on the control-points of geometry) rather than the "tight" BoundingBox which takes trims into account.

I'll see about getting it fixed.

--
David Rutten
david@mcneel.com
London, UK

Permalink Reply by quitronic on May 16, 2010 at 11:58pm