Hi everyone,
I stumbled upon this issue that cannnot undestend why it happens.
While when calculated in local the result is correct, at the shapediver platfomr is wrong.
Did anybody encounter this behaviour too?
Please post a minimal definition that can help our team reproduce the issue.
Hi Mathieu, Unfortunatelly i can’t share the definition but here’are two screenshots of the differences,
I t seems Shapediver messes up the creation of the perimetral curve of the shape you see.
This is how it looks in Shapediver:
This is how it’s supposed to be:
There can be multiple causes for this issue. You could start by comparing the Rhino version you use locally versus the one installed on the servers you are using. It might be a backwards compatibility issue between versions.
Otherwise, the problem might come from the method you use to build the curve, possibly by using splitting or joining operations and making assumptions about the order and direction of the resulting objects.
Unfortunately, I won’t be able to help much further without a file I can test with.
Thank you Mathieu. In fact i tried different methods to create the curve, always trying to force the direction based on an existing curve. I use the most up to date of rhino 8 locally and chose backend rhino 8 in shapdiver (sdr8euc1,Rhino 8, Europe, Shared system).
Also I avoid plugins in GH and try to use standard components mostly.
I’ll keep on testing the various segments of the definition hopening to find where’s the problem.