0.9 issues: maintaining references...

Couple of issues I am struggling with here using 0.9.

1) It doesn't seem like a geometry parameter maintains it's reference to a BRep after closing and reopening the files. So I create some geometry, reference it from a grasshopper geometry param, save both, reopen... they are no longer ref'd. Used to work... do I need to do something different?

2) I tried instantiating a geometry pipeline instead and ran into a slightly different problem... if I create a "box" in Rhino 5 it creates an extrusion instead of a brep as in Rhino 4. And the geometry pipeline doesn't seem to pick it up. I can assign it to a geometry parameter (in which case I believe it is converted into a brep) and that's fine (other than issue #1 :^)) . I can also explode and join the Rhino object in order to convert it into a brep and then the pipeline picks it up fine. But noooo extrusions for you today!

Attached are the (trivial) files.

- B -

Replies to This Discussion

Permalink Reply by David Rutten on September 2, 2012 at 1:15pm

I finally fixed [1]. Though old files will still not read in correctly.

David Rutten

david@mcneel.com

Poprad, Slovakia

Permalink Reply by David Rutten on September 3, 2012 at 11:10am

While Grasshopper needs to run on both Rhino4 and Rhino5 I'm not even going to contemplate doing anything special for Extrusions. As soon as Rhino5 goes out officially, I'll switch over to the new SDK and I can start adding all these cool new R5 only features, which will include Extrusions.

So, yes, no extrusions for you today... Or tomorrow, but hopefully not too long.

David Rutten

david@mcneel.com

Poprad, Slovakia

Permalink Reply by Alan on March 27, 2017 at 11:50am

Hi David,

It seems I am having similar error, but I am using a newer version of Grasshopper (August-27, 2014, Build 0.9.0076) from the date you fixed this bug. Please see image attached. If I save and close the Rhino file, next time I open it, my data tree will have a different order than previously. Is there a way to avoid this? Thanks.

Attachments:

floating names.gh, 19 KB
170327 Dry-Run Test.3dm, 2.5 MB

Permalink Reply by David Rutten on March 31, 2017 at 2:26am

The order of objects in the Rhino 3dm file is not meaningful and not persistent. You simply cannot rely on Rhino returning objects the same way each time you do a search. It'll return the same ones, but not necessarily in the same order.

Permalink Reply by Alan on April 6, 2017 at 10:00am

Thanks David!

Its interesting knowing this, I will then sort the sets alphabetically (Tsort) before exploding the tree (Bang).

Cheers!

RSS