So, there are various ways this is done, including what you describe, which uses a clutch to drive a tap for internal threading. Generally they are pricey, by hobbyist standards. $500-$1000 range likely. https://static.grainger.com/rp/s/is/image/Grainger/2ZAZ1_AS01?hei=128&wid=128&$adapimg$=...

If this had come up before so many 3d milling features were added, the simple solution would be--as you mentioned--to ensure the selected edges all are in the same plane, but that might not be a good fix at this point...

Hey Brad, I don't think their is anything "new" here, just that I happened to notice it a couple of year in. I get your point about multiple solutions perhaps unaccounted for. In the case of the simple example file I gave where a square is padded downward, are you suggesting at a corner, i...

I found the script code for this function in PathUtils.py, so maybe it will be clearer what is going on? def loopdetect(obj, edge1, edge2): ''' Returns a loop wire that includes the two edges. Useful for detecting boundaries of negative space features ie 'holes' If a unique loop is not found, return...

Pad also fails though.

Nice catch Chris. I should have mentioned in my file the midlayer pad edges fail also.

I wonder if slice succeeds because it returns two objects, and that loop is on top of one, bottom of the other, where pad and Chamfer modify the same object?

I am attaching a really simple file LoopByTwoEdges.png that demonstrates a bug in the 'Complete loop selection from two edges' tool. I ran into the bug because I chamfered the edges of my model in a real job-file, but with this file figured out how to reproduce the issue. The edges that define the t...

elif self.angle > 0.0 and height > 0.0: # cone rad = math.radians(self.angle) tangens = math.tan(rad) dr = height / tangens if dr < r1: # with top r2 = r1 - dr s = height / math.sin(rad) radius = min(r2, s) * math.tan((math.pi - rad)/2) * 0.95 I think the "min" function should be "ma...

I just tried using Dressup-Tag for first time, and note that the calculation appears not to quite correctly compensate for the bit-radius--thus, no remaining tabs if the width field is small relative to the bit radius. Playing with it, I see that changing Width from 5mm to 4mm changes the bottom wid...

And, I noticed CW/CCW seemed wrong while milling yesterday, and so following up on it, I notice that it's inverted if "Use Compensation is deselected".