The trick is when one of the 2 cuvres has a more pronounced curvature, more points will be required. Easy to solve with one curve, by dividing it with the fit curve component.
But further on, the difficulty comes with the relationship to the other curve which have sometimes also pronounced curvature and need more points. Therefore for final usage, we can’t use the curve closest point nor a perp frame component…
Any Idea on this puzzle ?
In the past @Jakinta, came up with a clever solution, but only for a specific part of the curve, and it was kinda "manual. Still pretty clever tho.
This appears to be a DUPLICATE THREAD. I didn’t read now all of the two threads you linked to, nor should anyone be required to do so. But I see enough there to know you’ve had plenty of good advice. The code you posted in this THIRD THREAD is useless without a plugin.
P.S. Your curves are obviously corrupt, not fair. GIGO
Hello @Joseph_Oster ! Glad to hear from you again, in this THIRD THREAD.
If you’ve had red carefully, I’m posting this to try to go further down that road. I definitly didn’t find any convenient solution yet and I’m still searching. If some are willing to help or have briliant ideas since then, well I’ll be very interested to hear about. Don’t butter with this post if not interested to answer in this to help, as far as I know you’re not a moderator here.
Never the less, what you propose was a good idea but still cause issues at some places.
Connect_2_curves_4.2.gh (34.1 KB) the file with the 2 curves to work on. Data internalized this time.
@Benjamin_TAN1 thanks for the try out, unfortunatly, with my 2 tests curvs, its not accurate enough. See in LtBlue your GHdefinition, then in black, the output lines that are close to what I’m after.
And curves arn’t same lenght so it might be difficult to divide them by the same amount of points. It depends in the end of the number of pronounced sub-curves in a curve VS the other one.
Indeed this highly depends on the number of sub-curves in each curve. The most problematic part is to detect them reliably first and then manipulate the data trees carefully to get the correct lines.
I did try a 2nd approach, don’t know if that’s satisfying enough but it’s definitely closer to the lines you drew!
Do you know what GIGO means?
