Grasshopper 0.8.0066 available for download

Important. You need recent Microsoft C++ runtimes in order to run this version of Grasshopper. You can download them here.

A new release is available for download from the usual location. This release mainly features a set of bug fixes. Not all reported bugs in 0.8.0065 and earlier have been fixed. OffsetCurveOnSurface and Brep internalisation is still buggy.

List of features and fixes:

VB and C# script components now have 'Destroy Caches' menu item that erases all recorded compiler data.
VB and C# script components now also cache compiler errors and warnings.
VB and C# script component code editor now caches the 10 most recent source codes.
Mesh Volume computation was broken on Rhino4, this is fixed.
VB and C# scripts would not update on parameter addition or removal, this is fixed.
Similarity component did not work well with negative numbers, this is fixed.
Display adjustment for curves was not working, this is fixed.
VB/C# script code changes were delayed until after autosave, this is fixed.
VB/C# scripts would not be re-evaluated after certain breaking changes, this is fixed.
VB/C# script editor would not save the code when the target object has been modified, this is fixed.
Rail Revolution component did not work, this is fixed.
Changing expressions on output parameters did not result in an update, this is fixed.
Changing Normalise flags on curve output parameters did not result in an update, this is fixed.
Changing Normalise flags on surface output parameters did not result in an update, this is fixed.
Changing Unitize flags on vector output parameters did not result in an update, this is fixed.
Changing Invert flags on boolean output parameters did not result in an update, this is fixed.
Undo/Redo events that affect output parameter post processes would not cause updates, this is fixed.
Script components in User Objects and Clusters were not deserializing correctly, this is hopefully fixed.
GH/GHX document ids were not deserialized, this is fixed.
User Objects with an unset subcategory caused a failure in the Ribbon, this is fixed.
Radial Grids would omit the row of points along the boundary of the grid, this is fixed.

David Rutten

david@mcneel.com

Poprad, Slovakia

Tags: 0.8.0066

▶ Reply to This

Replies to This Discussion

Permalink Reply by Sameer Kumar on January 22, 2012 at 10:02am

David,

The file at the download page is still the 20120112(2nd) version. I cannot find the 0.8.0066 version.

▶ Reply

Permalink Reply by David Rutten on January 22, 2012 at 10:24am

Sorry, my bad. Url is correct now.

David Rutten

david@mcneel.com

Poprad, Slovakia

▶ Reply

Permalink Reply by Enrico Casetta on January 22, 2012 at 11:40am

Interesting but what is this?

▶ Reply

Permalink Reply by Andrew Heumann on January 22, 2012 at 12:12pm

I'm pretty sure it's not working yet. (at least it isn't for me) See this discussion: http://www.grasshopper3d.com/forum/topics/component-request-rotatio...

▶ Reply

Permalink Reply by David Rutten on January 22, 2012 at 12:43pm

Yeah, sorry, it's not operational yet. I wanted to release because of the important fixes.

David Rutten

david@mcneel.com

Poprad, Slovakia

▶ Reply

Permalink Reply by Andrew Heumann on January 22, 2012 at 8:02pm

Thanks for all the fixes - you must be the hardest working man in parametric modeling!

I'm running into a couple issues, one somewhat serious and one minor:

1. I am still running into trouble with the new C# script component. In certain cases clicking "OK" doesn't seem to do anything; I am not able to commit my changes at all. I can exit the script without committing by closing the window perfectly well. This is happening at the same time as "Enter" and "Escape" are failing in Rhino. At the same time, Rhino refuses to quit - I can run commands like "Save," but cannot exit without force quitting. This appears to be the same issue I was running into before as noted here.

Please let me know if there's anything I can do to monitor my system in order to give you more useful information about when + why this occurs.

2. This is more of a minor annoyance than a bug, but it seems that the new shortcut logic for quick-creating sliders is overriding all other component aliases when the component name or alias begins with a number (such as 4Point Surface) - where typing "4pt" used to be sufficient, now entering this only offers the option of a slider.

▶ Reply

Permalink Reply by Victor Leung on January 26, 2012 at 9:34am

Yea, Cannot use 2p for Vec2Pt now.

▶ Reply

Permalink Reply by Nathan Miller on January 23, 2012 at 12:39am

Great work as always. Cheers!

-Nathan

▶ Reply

Permalink Reply by michael sprinzl on January 23, 2012 at 1:16am

Hi David,

I have a propsal for three functions with in c# component.

First....link code to external code... because when it would be possible to edit the code within mono or visualstudio... ( lambdaexpressions in the current codeeditor is pain...) and then put it to a database...maybe with an eventhandler to see if the code got changed...

second... a extra function to define input and outputs within the code.(not the execution code)

third ... customdisplay as ref into the execution code to use it as preview for debugging.

I do not know if this is alot of work, but it may help to reuse the codes and debug them.