Grasshopper 0.8.0061 available for download

Replies to This Discussion

Permalink Reply by michael sprinzl on November 24, 2011 at 11:21am

cool what was a real fast hotfix  ....

Permalink Reply by Victor Sardenberg on November 24, 2011 at 4:05pm

it was really fast!

i had the multiple curves issue and, at the same time, david posted the update.

Thank you, David!

Permalink Reply by Michael Pryor on November 24, 2011 at 5:01pm

Thanks greatly for the speedy update.

Permalink Reply by Edwin on November 25, 2011 at 10:06pm

Great!

Permalink Reply by Edwin on November 25, 2011 at 10:22pm

I have a problem, i was trying the new ZUI and added a explode tree component to the canvas but as soon as I zoom close enough to show the new controls, rhino chrashed and closed automatically. I was running GH on my macbook pro under parallels with windows xp sp3 and rhino 4 sr9.

Permalink Reply by David Rutten on November 26, 2011 at 2:58am

Hi Edwin,

 

can you post the files so I can try and repeat it here?

 

--

David Rutten

david@mcneel.com

Poprad, Slovakia

Permalink Reply by Edwin on November 26, 2011 at 12:20pm

It was a new file, first i just added a bunch of components and zooming made the program close, then I reopened rhino and gh and just added the explode tree component in a new clean file and when I zoomed it crashed.

Permalink Reply by Edwin on November 26, 2011 at 1:02pm

RhinoCrash.dmp

 

It occurs with any component with the new ZUI.

Permalink Reply by David Rutten on November 26, 2011 at 6:15pm

Hi Edwin,

 

it takes a number of days for crash data to be processed by our system. When you get the crash report dialog, (don't close it) can you have a look on your desktop to see if there's a textfile with dotnet stack trace information? It will be deleted as soon as you close the crash report dialog, so you'll need to copy it manually in order to view it later.

 

I'd like to see the contents of this file.

 

--

David Rutten

david@mcneel.com

Poprad, Slovakia

Permalink Reply by Edwin on November 26, 2011 at 6:31pm

yes, thats the file i posted earlier, here is the link: http://dl.dropbox.com/u/42012027/RhinoCrashDump.dmp 

Permalink Reply by David Rutten on November 27, 2011 at 3:58am

No that's a dmp file, it contains information about the Rhino memory state, there is also usually a textfile with a .NET call stack history, that's the only useful information .NET developers get from a crash.

 

Sometimes when the crash happens deep in Rhino (or if it's an out-of-memory crash) then there will not be a stack history file, but those cases are relatively rare.

 

--

David Rutten

david@mcneel.com

Poprad, Slovakia

 

Permalink Reply by Pieter Segeren on November 27, 2011 at 10:59am

Thank you David :)

• ‹ Previous
• 1
• 2
• 3
• Next ›
• Page