Grasshopper 0.8.0062 available for download

Grasshopper 0.8.0062 is now available for download from the usual location.

Changes and fixes since 0.8.0061:

● Added Content Filter section to the Preferences (Interface section).
● All users will be asked to specify the level of content filtering in the Grasshopper GUI.
● Added Geometry Pipeline object for live object updates (Params.Geometry panel).
● Added Circle Tan Tan component (Curve.Primitive dropdown).
● Added Circle Tan Tan Tan component (Curve.Primitive dropdown).
● Components which have been superceded by newer versions are now marked "Old".
● Added "Show Full Name" item to View menu.
● Coordinate Masks now support all possible permutations of x, y & z.
● Coordinate masks can now be created from text.
● The Stream Filter component now shows which index is streaming.
● Decompose Point component now has a Plane input.
● Point XYZ component now has a Plane input.
● Message Balloons are now drawn in screen space.
● Added an "Upgrade Legacy Components" item to the Solution menu.
● Added auto-upgrade behaviour to VB component.
● Added auto-upgrade behaviour to C# component.
● Added auto-upgrade behaviour to Sort component.
● Added auto-upgrade behaviour to Clean Tree component.
● Added auto-upgrade behaviour to Simplify Tree component.
● Added auto-upgrade behaviour to Flatten Tree component.
● Added auto-upgrade behaviour to Explode Tree component.
● Added auto-upgrade behaviour to Weave component.
● Added auto-upgrade behaviour to Null Item component.
● Added auto-upgrade behaviour to Curve Closed component.
● Added auto-upgrade behaviour to Polygon Center component.
● Isocurve component now limits isocurves to the trimmed region.
○ Internalise wouldn't work on Point parameters, this is fixed.
○ Large strings in tooltips would not display in a useful fashion, this is fixed.
○ The Canvas Radial menu would pop up if space was pressed while inside a nested textbox, this is fixed.
○ Internalise data would fail to disassociate references in certain cases, this is fixed.

The Circle Tangency components won't work in Rhino5 until the next beta goes out.

David Rutten

david@mcneel.com

Poprad, Slovakia

Replies to This Discussion

Permalink Reply by Anders Holden Deleuran on December 16, 2011 at 7:30am

Nice update David,

I noticed that there seems to be a problem with the MeshRay intersection component in the latest build. It appears to return the intersection points offset by about half the ray distance. I can confirm that this is also the case if one uses the same Rhino common function via Python. So I guess it is actually the latest Rhino 5 beta (5.0 (5.1.2011.1214, 14/12/2011)) which is the issue?

In this example (which worked yesterday, before updating today) the blue points are the ray start points and pink are the returned intersection points (the mesh surface being the intersection mesh):

Permalink Reply by Anders Holden Deleuran on December 16, 2011 at 7:53am

Update: Just tried to run the definition with Rhino 4. Same result. So I guess both Rhino 5 and the latest Grasshopper have this bug. Anyhow, hope you guys can fix it. Mesh ray intersections are wicked useful and rather great in general :)

Permalink Reply by David Rutten on December 17, 2011 at 3:38am

Yep, it got broke in the Rhino SDK. The next Grasshopper release will make it work again on Rhino4 and the next Rhino5 Beta will make it work again on Rhino5.

David Rutten

david@mcneel.com

Poprad, Slovakia

Permalink Reply by BLANC Aurélien on December 16, 2011 at 9:29am

i try to use circle Tan Tan Tan and it ask a circle center guide point??

what is it?, i try to indicate a point on the curve, near the center but of course we don't know exactly the center before...

is it a region?

thanks

Permalink Reply by David Rutten on December 17, 2011 at 4:15am

Hi Aurelien,

sometimes there are multiple answers possible. I need you to supply a point somewhere near where you expect the circle to be. I know this is not ideal, but the fitting algorithm in Rhino requires this input.

David Rutten

david@mcneel.com

Poprad, Slovakia

Permalink Reply by BLANC Aurélien on December 17, 2011 at 5:28am

I try to find a point near ... see file attached rhino V5

but still error

thanks

Attachments:

Detail Opt Montant.3dm, 124 KB
Test ArcTTT.gh, 11 KB

Permalink Reply by David Rutten on December 17, 2011 at 6:37am

Does it work in Rhino4? I had to add the circle finder to the SDK so unless you have a Rhino5 that went out after I added the function it won't work at all there.

David Rutten

david@mcneel.com

Poprad, Slovakia

Permalink Reply by David Rutten on December 17, 2011 at 6:41am

I just tested in my Rhino5 and it works there, so I think once you upgrade it will work for you as well.

David Rutten

david@mcneel.com

Poprad, Slovakia

Permalink Reply by Martin Dembski on December 16, 2011 at 7:12pm

Hi David,

I don't know if anybody already noticed it, but there is again the same bug than in some previous version. Pipes have a negative volume and because of this I think also the Solid Union doesn't work for intersecting pipes.

Hope this can be fixed quiet easy.

Best,

Martin.

Permalink Reply by David Rutten on December 17, 2011 at 4:33am

I'm not entirely sure but I think I removed the offending Flip instruction. Let's see how the next version behaves in your case.

David Rutten

david@mcneel.com

Poprad, Slovakia

Permalink Reply by Martin Dembski on December 17, 2011 at 4:40am

Thanks, I'm looking forward to it.

Would it be possible / useful to add a brep flip component besides the surface flip component for those cases, or a flip option to the pipe component?

Permalink Reply by David Rutten on December 17, 2011 at 4:55am

It should not be possible to have an inside-out closed brep. It might however be useful to be able to flip an open brep. I'll add the component.

David Rutten

david@mcneel.com

Poprad, Slovakia