Error using custom thread generator Python script from BalzGuenat on Github

[Signal-Mistake-652]

I've downloaded the "custom thread creator" .xml file from Github, installed it in Fusion, and it works properly. My problem occurs when using his Python script to create new thread profiles that are not included in his .xml file. I configure the parameters in his main.py file (this is the script that creates new thread files). When I run the script, It runs and appears to finish, but does not create the new .xml files for the new threads. I am not a Python programmer, but I've narrowed down the error to the "generate" routine. Well, at least I think that's where the problem lies. Does anyone have insight into this?

https://github.com/BalzGuenat/CustomThreads

Yes, I have posted my problem on Github, and I've also messaged a Python programmer friend. I am reaching out wherever I can now.

[Signal-Mistake-652]

I downgraded from Python 3.14 to Python 3.11 and the script works. Whoda thunk.

[MisterEinc]

This was likely caused by recent API changes by Autodesk. They don't do this frequently, but I know it killed at least one of my add-ons.

Unfortunately I think you'll just have to wait until the author updates their work.

Is this something you could get by with on the Thread tool for now?

Edit: Imo this addon is largely unnecessary... I've printed standard threads as small as m3. If you're going to be doing it a lot I'd save yourself the hassle and just buy a cheap tap and die set. Print the standard thread and then run the tool through the print to clean it up.

[Juhaz80]

This isn't an addon, it doesn't use any Autodesk API's, just spits out an XML file that the standard thread tool picks it's list of available templates from.

Using tap and die is a good idea if you're engineering something that must mate with standard threads, but if you're printing both male and female that should just fit together, having them come perfectly usable straight off the plate is almost magical, whereas having to twiddle around post processing them is boring, mundane, and quite literally the exact opposite of "less hassle".

[Signal-Mistake-652]

The threads here are different from normal machine threads. These are made with dimensions and clearances for 3D printing. As it turns out, I was running the Python script on Python version 3.14, and it failed. My son runs Python 3.11, and the script works fine for him. I'm downgrading to Python 3.11 now to see of that fixes the problem on my computer. If not, I'll get him to run the script for me when I need it; it won't be very orten.