Grasshopper 0.9.0054 available for download

Another incremental update is available for download. This release fixes a few annoying bugs in 0.9.0053.

If you're updating to 0.9.0054 from 0.9.0014 or older, please read these release notes as they contain some important information. "Important information" incidentally is bold and red, hard to miss.

New since 0.9.0053:

Added Project Along component for directional planar projections (Transform.Affine dropdown).
Added Rotate Vector component for rotating geometry from one direction to another (Transform.Euclidean dropdown).
Added default values for absolute and angle tolerance in the Curve To Polyline component.
Added Version option to Quick Image Export.
Pressing Delete while a textbox is active on the canvas would execute the Delete menu item, this is fixed.
The new Pull Point component was much slower than the old one, this is fixed.
Arrow and Delete keys did not work for Slider and Scroller on-canvas edit boxes, this is fixed.
Ctrl+Alt info mode would hide the Rhino window sometimes on exit, this is fixed.
Addition component did not add vectors to points, this is fixed.

Enjoy,

David

David Rutten

david@mcneel.com

Poprad, Slovakia

Replies to This Discussion

Permalink Reply by David Rutten on May 14, 2013 at 1:32am

Since it exports a compound transformation consisting of a projection, a rotation and a non-uniform scale, it would have to be my code. You solution generates a single generic transformation rather than a series of primitive transformations.

David Rutten

david@mcneel.com

Poprad, Slovakia

Permalink Reply by huaxiamengqing on May 14, 2013 at 4:38am

I can't understand the third Scale transform--.

Permalink Reply by Frane Zilic on May 13, 2013 at 10:55pm

Hi David

Thanks again for your updates...

Ctrl+Alt is fixed, it works. But still it's as if Rhino goes momentarily to the windows background and then is called back to the front, because I can see the applications that are behind it for a fraction of a second.

Permalink Reply by David Rutten on May 14, 2013 at 1:33am

I know. It's very strange. I see no reason why closing the overlay windows would affect the z-depth of Rhino, but for some reason Rhino has a lot of problems with maintaining its position within the window-stack.

David Rutten

david@mcneel.com

Poprad, Slovakia

Permalink Reply by Sridevi Koonath on May 14, 2013 at 4:21am

Hi David,

It seems that System.Int, System.String...etc, and their members are missing from intellisense of the script components.

Permalink Reply by David Rutten on May 14, 2013 at 12:30pm

Yep, seems like it. I'm on it.

David Rutten

david@mcneel.com

Poprad, Slovakia

Permalink Reply by David Rutten on May 14, 2013 at 12:46pm

Found the bug and fixed it. I'm going to try and fix some more bugs before releasing 0.9.0055 though.

David Rutten

david@mcneel.com

Poprad, Slovakia

Permalink Reply by rainake on May 14, 2013 at 6:05pm

Hello David

Will you release 0.9.0055 this week?

Permalink Reply by David Rutten on May 15, 2013 at 5:04am

Yes, today or tomorrow.

I'm going to try and fix a compatibility issue with the VisualARQ components first.

David Rutten

david@mcneel.com

Poprad, Slovakia

Permalink Reply by Ron Shvartsman on May 14, 2013 at 11:37am

Hi David,

Thank you for the new update. I came across an error when running 0.9.0052 + 54. Rhino was crashing when working on a simple low res mesh. Tracked the problem down to the mesh.Evaluate component. It works fine with a single mesh face quad, however multiple mesh faces cause rhino to crash. Is this something on my end?

Running, Rhino 5 SR3, Windows 7, GH -- 0.9.0054

I have included an image as well as rhino and associated GH file. Thank again for your great work.

Ron

Attachments:

rhinoFile.3dm, 126 KB
GHfile.gh, 14 KB

Permalink Reply by David Rutten on May 14, 2013 at 12:53pm

I don't have UTO's tools, but reconnecting the wires I can't make it crash:

Could you create a file with only native component which also crashes?

David Rutten

david@mcneel.com

Poprad, Slovakia

Permalink Reply by Ron Shvartsman on May 14, 2013 at 1:38pm

Hi David,

Thanks for your response. I attempted to recreate the file using GH native comps for NURBS instead of meshes (was not sure how to recreate that specific sequence on mesh without UTO tools), and I received no crash or error. Also, I wanted to note that in your version here you are running one mesh through. In mine, I had broken down the mesh into its faces and used those as individual meshes for evaluation. It was upon running the script on multiple meshes where I had the problem.

I uninstalled 0.9.0054 and reverted back to 0.9.0014. I received an error when attempting to evaluate multiple meshes. Error states, "Attempting to write or read to protected memory. This maybe an indication that other memory is damaged". This makes me think it must be on my end. Using a new work computer and discussing the issue with IT.

Am I right in assuming this is on my end? Something tells me you may know more about this then my IT department :)...