Scott Mudge

More updates: 1. It happens **only** for gears with > 24 teeth (i.e., 25 or more teeth). 2. It happens **only** for non-zero beta value. 2. Other parameters appear not...

Okay, one more update. So the error being thrown in `ComplexGeoData::setElementName()` looks like it's being triggered by an arbitrarily set max iteration threshold:  I think I know what is...

A while back it looks like it was set to a `while(1)` loop, so it looks like this threshold was put in place as sort of a sanity check to...

Increasing `if (++i == 100)` to `if (++i == 4096)` fixed the issue, but I'm not sure if it is the ideal solution or not. I stress-tested it by creating...

Added this issue to FreeCAD project, as it will likely need some fixes there as well. But perhaps there is a way to refactor `helicalextrusion()` to avoid having to use...

Line 1573 in features.py for me was: ``` shell = Part.makeShell(shell_faces) ``` in `def helicalextrusion(face, height, angle, double_helix=False)`. `makeShell()` presumably produces a call stack leading to `ComplexGeoData::setElementName()`. I am using...

I do use that approach for aligning objects, but I'm actually creating a lofted transition between two gears of different teeth count, so using face binders (or referenced faces) is...

Yep, this is fixed now, with leaving `if (++i==100)` in place. Thanks!

I'm sorry, I had a "brain fart". When I rebuilt and tested with your latest commits @realthunder, I went back to double check, and unfortunately I did not actually revert...

Interesting, I don't see anything that sticks out as being invalid. Is it just this file, or all interactions with ArcWelder and MP? It appears to run find with both...