CRASH: Internalising Data in GH (Rhino v5 64-Bit)

Hi David,

Crash report is winging its way to you but in the mean time here is the dotNET crash report

It was a all bit odd because I basically had the same definition open in two separate Rhino Documents. I then realised I wanted to compare the two side by side so I internalised the referenced geometry so that I could paste the components into the other instance.

Nothings seemed wrong during the internalising step but when I drop the components onto the canvas in a new location. One of the Curve Params did not materialise but the wire which would have connected to it was originating at its counterpart in the current definition. I went back to the copied from definition to try and connect a different param with the referenced geometry but It crashed at this point.

-Danny

Attachments:

InternalisedCrash.txt, 4 KB

Replies to This Discussion

Permalink Reply by Danny Boyes on July 4, 2012 at 5:17am

Different DotNet Crash Report this time but it occurred during/after an internalising of Data. Rhino 5 64-bit

Attachments:

InternalisingCrashRhino5.txt, 2 KB

Permalink Reply by David Rutten on July 4, 2012 at 5:55am

Ah, this second one is in my code, I can fix that. Thanks.

David Rutten

david@mcneel.com

Poprad, Slovakia

Permalink Reply by Arie-Willem de Jongh on July 31, 2012 at 4:02pm

Maybe a bit late, but same here. Tried to copy a component (curve with data internalised) from one canvas to another and it crashed (tried it 7 times and all 7 times it crashed). Also when I tried to save my definition one component with internalised data after reopening the file was missing. Whatever i tried i couldnt get it to be 'saved'.

Permalink Reply by David Rutten on July 31, 2012 at 4:22pm

If it is the same error, then I fixed it, but obviously it will keep on crashing until the fix is released.

David Rutten

david@mcneel.com

Poprad, Slovakia

RSS