Thread data directory - where is it nowadays?

[Anonymous]

It used to be (for Windows):

%localappdata%\Autodesk\webdeploy\Production\<version ID>\Fusion\Server\Fusion\Configuration\ThreadData

as per:

https://knowledge.autodesk.com/support/fusion-360/troubleshooting/caas/sfdcarticles/sfdcarticles/Cus...

and it has worked OK, even if I had to re-do it every time Fusion got updated, but...

When I tried to do it again on my Win10 machine it now looks as below:

%localappdata%\Autodesk\webdeploy\Production\<version ID>Api>Python>packages>adsk>defs>adsk>_init_.py

Something appears to have changed since last time I did this ...

Help, please

ps I have also asked this question here:

https://forums.autodesk.com/t5/fusion-360-design-validate/ba-british-association-screw-thread-xml-da...

but since it is four years old thread, I thought I ask in a new with better title?

[MRWakefield]

Nothing seems to have changed here! I've just performed the latest update and my thread data files are here:

%localappdata%\Autodesk\webdeploy\production\<version ID>\Fusion\Server\Fusion\Configuration\ThreadData

[Anonymous]

thanks,

it's a total mystery....

never had this problem before, hopefully someone can offer some suggestion?

[MRWakefield]

From what I can tell on my system: whenever Fusion is updated it can create more than one folder at the <version ID> level. For instance: I have two new folders at this level with the same date but one has a time 10 minutes later (this is the api one you're referencing in your post). Open up the 'production' folder and sort by date, I expect you'll find the two most recent folders have the same date. Open up the slightly older one and see whether you can navigate down to your thread data folder.

[Anonymous · Accepted solution]

All of them were the same, going all the way back to last year,

however... I have a solution 😁

un-install Fusion client and re-install again

and all is back to normal

What is weird, is that App data folder must have been corrupted for a log time, yet Fusion seemed un-affected, until I tried to do this thread business...