Hi everyone. I’m trying to create a sort of a duct that will connect to a wall. When I try to use sweep2 with the given profiles and rails, I get a surface as seen in the image. All of these curves come from a grasshopper script and I baked them to show the problem. I’m new to using rhino and grasshopper and I don’t know what I’m missing here. Would really appreciate some help.
Without seeing some sketches or mock-up photos, it’s hard to know the exact form you’re after, but if you build your rails as proper degree 3 or 5 curves with a reasonable CV layout, and your two cross-sections with degree 3/8 span curves, Sweep2 works all right.
Thanks for your response. I’m trying to create a feature where I can control the lips at the inlet and profiles of the curves. Afterwards, I will be studying the effects of these parameters on how well this features sucks in air. I tried to provide a bit more detail in the image below. Due to the curved nature of this channel, it is very hard to be able to control the profiles of the lips while creating a satisfactory geometry. Would you have suggestions for modelling?
I also looked at the .3dm file you provided. It seems that making the rail parallel with the inlet profile in their connection point causes the problem with the sweep. Can there be a workaround for this issue?
yep - something is strange with the start condition of the sweep2.
if you select the rails with only one profile - you get a fully planar tail …
quite strange.
i tried to design a minimal sample that shows the same behaviour but i failed.
do a minimal (maybe less then 1 degree is ok) - nonplanar setting for the start condition (move the 2nd cvs of from the plane)
check if changedegree → 3 improves the result
and then do 2 x sweep2 - one for each side (grey and violett)
also if i set the CV of the rail curve to same x and world 0 for y,z
bad CV from original curve
Point at (-36.53523940,0.00000010,-0.00000000)
-------------------------------^
CV of new curve still creating a nice surface
Point at (-36.53523940,0.00000000,0.00000000)
-------------------------------^
but now setting all 3 coordinates to the bad target CV i get this strange Sweep2
Thanks for taking a look at this. I didn’t realise that it could be bug and thought I might be doing somethings wrong. Thanks for that clarification.
I don’t know if I mentioned it or not but the curves were actually created using grasshopper. Could there be an issue on that side where it generates noisy position data. That might be a better place to look for issues. Also would there be a way to workaround this issue in grasshopper? Didn’t choose grasshopper in the topic, but I now suspect that the issue might be stemming from there.