Two days ago I wrote about the difficulties I was having with Path Finder.
So, as @martinsiegrist recommended, I went back to reading the forums on this and have studied it.
I understood the content perfectly and thought I could solve my problem.
But the zigzag problem keeps happening.
I think the problem is caused by scale.
I do my all works in mm, so the numbers are big.
But people who had discussed about this script in the forums before, the numbers are all small probably because they were using m units.
If I run the script by @DanielPiker as it is, it works fine, but if I scale up the geometries 1000x, I immediately get the zigzag problem…
To solve this problem, I first increased the min/max edge of the mesh by 1000x(it makes sense),
and I thought I should also increase the divide value, I think this was a bad idea, as it will only create more zigzags. So I decided to leave it as it is.
Please let me know why this problem happening and what values I need to adjust to fix it.
Working with landscape scale geometry in mm is likely to cause other tolerance issues.
However, in this case, what you need to change is just making the bending strength a few orders of magnitude higher (since it depends on the area of the cross section, but we are not setting cross section explicitly).
Then you can make the path smoother: A. Path Finder.gh (101.5 KB)
Thank you, you saved my me
The new script you created works perfect!
It seems that when the scale changes, the Bending Strength needs to change as well.
This is what I wasn’t expecting, as the physical force doesn’t change even if scale changes in real world
Onmesh Strength UP : Increase the area reach follow natural ridges more closely.
length UP : Smoothing the slope (most important)
Bending Strength DOWN : make turning platform narrow (not to make big cutbank)
I’ve thought value’s fuctions like this
I’ve been stabilizing the corners of every switchback by reducing the bending strength at the end
However, I thought that such a high value would make the factor slider useless, but it work same as well!!
And you set the divisions to 100 in script, but larger values would give better results. 300 division seems to work best
Once again, thank you for further troubleshooting @DanielPiker
Hello
I looked at your problem and wanted to use my tool that flows along a vector field in Nautilus. As I haven’t the good tool to make a vector on a specific slope, I made one. It will be on a future release of Nautilus.
Here my tool follow the slope at a specified angle or max Slope if this one is less than the specified one.
As it is not the same as the tool you use, it turn around the mountain. You can choose the orientation
