Plane Components Bug

Replies to This Discussion

Permalink Reply by kleerkoat on September 30, 2010 at 11:59am

I think I'm suffering from the same bug in a definition that was working fine yesterday, perhaps the new WIP broke it?

This error is from an Offset component that has a plane component fed into it.

I did close down Rhino, reopened, opened Grasshopper, placed various plane components on the canvas, panned around, tried to delete them and Rhino crashed. I've sent it in through the McNeel error reporter.

Permalink Reply by Stan Carroll on September 30, 2010 at 12:10pm

I am using the September 29 Wip for Rhino 5. I just built the definition today so I am unable to confirm that it worked with previous RH 5 WIP.

Permalink Reply by kleerkoat on September 30, 2010 at 12:23pm

That's why I also tried from scratch, to confirm your bug.

I just tried to open up Grasshopper in V4 and got this error, also the editor never came up.

I don't know if it is related though.

Permalink Reply by Stan Carroll on September 30, 2010 at 12:25pm

I am also having problems with the "Surface Frames" Component in addition to "Plane Components". To test, I opened the drawing in Rhino 4 SR8 to see if these GH components would work, and they worked just fine in the same definition.

Conclusion - it seems that Rhino 5 Sept 29 WIP has issues regarding various GH Plane components.

Stan

Permalink Reply by Stan Carroll on October 5, 2010 at 1:33pm

The problems I was having seem to have been rectified by the new 7.0057 version.

Thanks David for the quick fix.

Stan

Permalink Reply by David Rutten on October 5, 2010 at 2:25pm

Yeah, it was a Rhino SDK break. Since Grasshopper uses the SDK that ships with Rhino5 when it's running under Rhino5, any SDK breakage will usually result in a few days of Grasshopper not working on Rhino4 until everything is updated left and right.

--
David Rutten
david@mcneel.com
Poprad, Slovakia