We are investigating migration to Rhino6. In the past, we have released quite number of complex grasshopper definitions which our end-users have used and might want to pick up in the future. Using those unaltered definitions in Rhino6 yields an annoying error that blocks the big part of the definition:
Rhino5 gives a warning with open breps, but provides the center point anyways:
Rhino6 gives an error with open breps and provides no data at all:
There is no way that the end-users are going to dig into the definitions and solve the problem them selves. So I was wondering what else can be done? Maybe a rhino/grasshopper setting that allow old behaviour or something.
Another option could be to submit a change request of the GH volume component for Rhino 6.
Best regards, Wei Pien