Yeah Mike, this is the same thing. I tried for a long time to get physical spacing to work like we need it with _FlowAlongSrf, but it’s difficult on single curved and impossible on double curved surfaces.
_Flow neatly solves the spacing issue (curve length or _Stretch for domain) and orientation (curve direction), but you can’t make your stones face up .
There’s still the array and scaling issue, but that’s a separate thing.
Hi Mike - brep faces can have a normal shown by say Dir that points one way, but the underlyting surface’s ‘natural’ normal as determined by the U and V directions (right hand rule) may be the opposite. It looks like right now we’re using the natural normal. When surfaces are joined, the resulting object needs to have a consistent normal direction, and where this contradicts the underlying surfaces’ natural normals, Rhino adds a ‘flip’ flag so that a face is treated as having that required normal for most operations (like Booleans for example) . It looks to me like Flow is only using the natural normals… I hope that makes sense…
@pascal my problem was on a natural normal, but I couldn’t flip the targetsrf without breaking history. I know you can flip the input curves, but that causes side affects, too. A lot of times our targetsrf will be defined by one parent crv that’s offset and lofted. Flipping the one parent curve flips the offset direction.
Right, I saw that. I think using the flip flag will at least be better, I’ll ask if we can do that or add an option. A flip option inside Flow is (probably) less likely in the short term at least, I would say.