Grasshopper

algorithmic modeling for Rhino

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

Views: 3683

Replies to This Discussion

David,

My apologies. I was confused about which mesh comps were native in comparison to Mesh Edit by UTO. I did recreate the sequence for a mesh using native comps and received no error or crash (everything working smoothly). Must be an issue with UTO tools??

Still, this does not seem to explain (at least not for me) why I was receiving an error on GH version 0.9.0014. Never had an issue with it before. Maybe there is some incompatibility with my specific computer??

Thank again,

Ron

It could be that UTO tools are creating naughty meshes. Perhaps they have unused vertices or degenerate faces. I do not know. But even if they are doing that, it is our fault when that results in a crash.

--

David Rutten

david@mcneel.com

Poprad, Slovakia

It's probably a bug. We just need to figure out how to pin-point the problem and step #1 is always finding a way to recreate the problem. One way to get the same file but without UTOs tools would be to internalise the meshes once they come out of UTOs tools. You have the data but no longer need the components.

--

David Rutten

david@mcneel.com

Poprad, Slovakia

Can you tell me what build specifically, rather than 'the latest'?

--

David Rutten

david@mcneel.com

Poprad, Slovakia

Can you please locate the log for this failed install? It will be in:

%appdata%\McNeel\Rhinoceros\5.0\logs

and it will be called grasshopper_0.9.54.0 (somenumbers-somenumbers).log

Either attach it here or mail it to me personally.

--

David Rutten

david@mcneel.com

Poprad, Slovakia

Oh, I'm so sorry... just found out I wasn't running SR 3... 
It's all up ad running now.

Best,

Charles

Hi david,I come again.Below are some bugs and My suggestion about gh!

bugs:

1, Points in gh cann't display properly in Rhino in some GH commponents!

2, The Panel can't update the Stream Destination file immediately after I select the "Stream Contents" menu. It's can update just when I put the Recompute button! It's very dangerous for us to export data to files.Test it for csv file exporting you will see it!  It's different from before versions--

3,Maybe this problem  stay long before "Item Index" commponent! It couldn't act properly! See the picture, Same type,Same data,Same path, It just cann't find it's index.

4,The principal doesn't do the right thing about Merge commponent I think! Do you think so?

Suggestions:

1,I want a batch code comment button  and a batch uncomment button in VB commponent editor!

2,I want a assemblies Remove button!

3,I want select the wirelines, When I select one wireline,It can hightlight or be bold,So that I can see it's parameter!

Waiting for your reply,Thank you very much.

1. Points in gh cann't display properly in Rhino in some GH commponents

I don't understand. What is wrong with the display?

--

David Rutten

david@mcneel.com

Poprad, Slovakia

3,Maybe this problem  stay long before "Item Index" commponent! It couldn't act properly! See the picture, Same type,Same data,Same path, It just cann't find it's index.

[Item Index] doesn't find similar values in a list, it finds the same values in a list. I.e. values that are actually in the same memory. I think you want to use [Member Index] instead.

--

David Rutten

david@mcneel.com

Poprad, Slovakia

Have a read of this thread for a better understanding of [List Index]

Thank you. I understand it now.But it seems not fit to normal user who does use code to understand.

I strong recommand to change this commponent to What we understand at first sight! 

4,The principal doesn't do the right thing about Merge commponent I think! Do you think so?

There's definitely something weird with the principal parameter logic. I'm looking into it to see if I can fix it for 0.9.0055.

--

David Rutten

david@mcneel.com

Poprad, Slovakia

RSS

About

Translate

Search

© 2024   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service