You can try LeadInOut. Find it under the menu: Path -> Path Dressup -> LeadInOut. In the Comboview, highlight the operation you wish to apply the dress up to and click on the menu item LeadInOut

One thing I really struggle with on the Surface Wb is the the error message that the Boundary edges must be added in a consecutive order. Sometimes I'm lucky and I choose the right order, most of the time however, I don't. What does consecutive order mean? Does it mean how they are arranged? Do I se...

@drmacro Thanks a lot for this! Is the use of SplitCurve in order to have end points so that the redrawn spline that runs through the cross sections can be attached to those points?

Thank you, I tried using the surface WB, but didn't get it to work. I'll have to study what's going on here. Thanks a lot!

I'm trying to create surfaces on this model so that the surface is constrained not only to the 4 curves but also to the straight lines? I've tried lofting, but then there's always a gap between the edge of the surface and the straight line construction. Any ideas how best to achieve this? Surface.PN...

@freman It's in the latest windows dev: 0.22.0dev.36082 (Git)

Edit: I see now this was already discussed earlier, sorry, I'm still getting my head around all the terminology and intricacies of the Path WB. It would be really cool if this could be fixed. :) Can it be that 3d surface is being calculated twice? On the attached model, I changed linear deflection i...

When I did my last 3d project, I had a lot of opportunities to observe CPU utilization. Moreover, I could determine by the load character whether Path creation will be completed successfully or not. So, if we see only one core loaded = no, there will be no success. But if we see periodic bursts of ...

That is expected , as I explained above. The bottleneck is not in the python code. Thanks freman, I understood that, I only mentioned it because earlier in the thread Dimitrious2 said: There is a way to become rock solid but, it will be heavy and I tried to minimize looping through code as much as ...

At the other hand, when I press the apply button on 3D surface Op, starts by only using one thread at the beginning, my GPU jumps to 31-34% and somewhere in the middle, all of the threads are maxed out to 99.9-100% till the end. On the small model attached to this thread I've found exactly the same...