Extrusion Bug? Surface from extrusion cannot be referenced in GH

Replies to This Discussion

Permalink Reply by Hannes Löschke on March 30, 2012 at 4:33am

Are you creating light extrusions the new Rhino5 way? Those are not surfaces as they used to be. You can still set the extrusion preferences to create classic surfaces.

Does this error happen with converted extrusions, too?

Permalink Reply by Jon Mirtschin on March 30, 2012 at 4:44am

David will know better, but in his absence here's my understanding.

Grasshopper still targets Rhino v4 (it will change when v5 ships I'm sure, but when will that be??) which has no knowledge of extrusions.  Therefore it's will not know how to cast this new object.

If you convert to a brep/surface as Hannes has suggested it should work well.  

Permalink Reply by Danny Boyes on March 30, 2012 at 5:27am

it will change when v5 ships I'm sure

He's openly said that from that day all support for Rhino 4 will be dropped faster than Cheryl Cole from X Factor.

Permalink Reply by Rajaa Issa on March 30, 2012 at 8:35am

Thank you all.  

I understand this is a V5 only issue and converting light extrusions to breps will solve it, but I thought it can be supported still.  We'll wait until David comes back and probably he can enlighten us about it.

Permalink Reply by Jon Mirtschin on March 30, 2012 at 8:42am

I do support some v5 rhino common functionality in my addons (unrolling etc), you can compile against a v5 rhino common assembly and then wrap all functionality inside a function with no parameters referring to objects not in the grasshopper rhino common library, but I don't think David has used this (at least yet).