Grasshopper 0.7.0030 available for download

GH 0.7.0030 (June 18th build) is available for download.

You need at least Rhino4 SR8 to run this build.

This build fixes numerous serious bugs in the previous 0.7 release so it is highly recommended for those of you who have already had the nerve to depart from 0.6.X.

One of the fixes affects Cross Reference Data Matching and although it is only supposed to be a fix, please be on the lookout for any unwanted changes.

A new feature available in this build are User Objects. Basically you can store any individual existing object on the canvas (including all settings) as a new Component. This allows you to create parameters with preset data, or Components with preset inputs, or Sliders with Integer accuracy as default, or ready made Script components.

User Objects can be created from the Grasshopper File menu. They can be deleted from the toolbars (each component on the toolbar now has a rudimentary menu), or they can be managed manually. There is a single User Object folder (accessible via the File menu again), so anything placed in here will be loaded.

This is still a very early attempt at making a customizable toolset. The interface and responsiveness of User Objects will improve.

David Rutten

david@mcneel.com

Poprad, Slovakia

Replies to This Discussion

Permalink Reply by Liam Morrow on July 8, 2010 at 6:24am

I just got this red screen that made the entire definition disappear, whats the deal? (definition +error message enclosed)

Attachments:

red screen of death.jpg, 174 KB
Final Triagulation Panelization Defintion.ghx, 635 KB
errormessage.jpg, 115 KB

Permalink Reply by David Rutten on July 9, 2010 at 11:27am

Hi Liam,

there was an error in the display code. In order to avoid further errors (perhaps more fatal errors), I disable the display to give you a chance to save your work.

When the display is busted, you can switch it back on via the View menu (a new item will be available at the top of the dropdown menu). However, it is of course possible that the same error will happen again, in which case it might be exceedingly difficult to get rid of the problem.

--
David Rutten
david@mcneel.com
Poprad, Slovakia

Permalink Reply by efe gözen on July 9, 2010 at 7:55am

I have a humble wish for the next release.
Is it possible to have a ray component? (or the vector component to have an infinite length option), along with a curve|ray intersection component? (in addition to the brep|ray intersection) I rely on building a plane for the ray|curve intersections I want at the moment, however as the plane extends in both ways, there can be more than one intersection in some cases, which I actually would like to avoid. //or i have to convert the curves to breps, and then test for the brep/ray intersection, which slows down the definition.

Permalink Reply by to] on July 9, 2010 at 8:07am

hi
curve line intersection is infinite and working like a ray
you ca limit it to the first intersection also
-to]

Permalink Reply by efe gözen on July 9, 2010 at 8:27am

thanks, i think i have taken "line" too literally and haven't even tried before.
cheers.

Permalink Reply by AnnaLisa Meyboom on July 13, 2010 at 7:07pm

I used to be able to import an edge of a polysurface in as a curve and with version 0.7.0030 it isn't working - comes up as null. Any clues?

Permalink Reply by David Rutten on July 14, 2010 at 4:35pm

Hi AnnaLisa,

yeah, this is something which I need to add to our new SDK. Edge indexing has been missing so far. I don't think it will make it into the next release, but hopefully we'll have it up and running again in a few days.

--
David Rutten
david@mcneel.com
Poprad, Slovakia

Permalink Reply by Daniel Xiong on July 15, 2010 at 5:49am

Hi David,
Thanks for the great update! However, I find out there may be 2 bugs.
1. CullPattern no longer accepts null boolean input. It used to work in the 0.6 version. It was quite convenient so that I didn't need to use the clean tree constantly. The bug also results in failures opening the 0.6 files.
2. Offset doesn't work like the offset in Rhino. Sometimes it produces broken curves.

I have attached the files below.
Cheers

Attachments:

GH0730-cullpattern-nolonger-accepts-null-boolean.rar, 14 KB
GH0730-offset-bug.rar, 24 KB

Permalink Reply by David Rutten on July 15, 2010 at 5:53am

Thanks Daniel,

I actually just fixed the Cull component 10 minutes ago :)
I'll have a look at Offset.

--
David Rutten
david@mcneel.com
Poprad, Slovakia

Permalink Reply by Daniel Xiong on July 15, 2010 at 6:20am

Thanks David,
I just had an idea about offset. Is it possible to have a input to control the offset direction by offsetting in or out rather than + or -? I know there is no in or out for some curves. Just want to make the component more friendly.

Permalink Reply by David Rutten on July 15, 2010 at 7:01am