Hello everyone,
I have this problem. I had this also on V8. I share it in the “WIP” section hoping that it can be fixed (of course if there is something wrong, maybe I am doing sth wrong).
When I do the sweep 2 the surface is not sitting exactly on the curves (feel free to see the image and take a look at the Rh file). Do you know why and do you know I fix?
WIP - Sweep2 Problem.3dm (2.7 MB)
The attached .3dm file does not include the rail and section curves. Without those curves only speculation is possible.
The most common reason a sweep surface deviations from a rail is one or more section curves do not intersect the rail. The sweep surface goes through the sections, even if that requires deviating from the rails.
The profile and rail curves are included in my local file. There are 2 rail curves and 3 profile curves. I just checked. I upload it once again in case sth went wrong when uploading.
WIP - Sweep2 Problem.3dm (2.7 MB)
The curves are in the file - bit hard to see from the colors. I have created a ticket about this here RH-95502.
What I’m seeing as a temporary workaround is this: select the circle and run _ProjectToCPlane. Even though it is already on the CPlane, it will convert the circle to a nurbs circle (use What before and after to see the differences). After this conversion, Sweep2 will give the expected result. Of course, this needs fixing on the Rhino side so you don’t need to use this workaround, but I hope this helps in the mean time.
Hello Menno,
Thank you for the support.
It worked. Thank you.
Well, I have generated this ‘bug’ first in Grasshopper. In my definition this curve enters the definition as the outcome of the simple ‘Circle’ component, into which we provide a plane and a radius. In the definition it is only ‘reparameterized’ and nothing else is changed. Does this somehow cause it to downgrade from ‘NURBS circle’ to just ‘circle’?
