Why can't Rhino loft deal with sharing and edge?

Hi, it feels like the Loft command should be able to handle this situation easily.

It becomes especially problematic in Grasshopper definitions, where changing a slider can cause two curve edges to coincide unexpectedly, making the loft fail or produce incorrect geometry.

For example, in this case I am lofting two closed curves that share the same lower edge, but the resulting loft is not created correctly.

Is there a reliable way to handle this without manually modifying the curves whenever their edges coincide?

A work-around is delete the shared portions of the curves.

Sure I could also construct each surface with Surface from Points, point by point, one by one. I could also just trash my PC and draw it by hand as if CAD didn’t exist. Or better yet I could travel back in time, discover I can shape stones with friction and force and invent the wheel all over again!

in this situation you have two triangles that on the ends that you could loft and cap and get a perfect polysurface. Those triangles might not be what was generated earlier in a GH script, but they can be derived.

I understand what you’re saying about the limitations of loft. In other situations that aren’t as simple as this, it’s still the wrong tool for the job. Someone else can explain why better than me, but turning on control points will help illustrate what _loft isn’t able to do.

Thanks for the suggestion. The triangles on the sides you mean? Those I don’t have as curves.

The curves I have are these, and I see no topological difference between these:

Literally I could reduce that difference to 0,00001 and loft will work.

Why do I get punished for having a difference of 0,0001 between two edges to the point of breaking a command that works perfectly otherwise?

Seriously, if your whole modelling philosophy is going to be based on curves as construction guides, command should be robust enough to deal with this cases…