"An error has occurred during stock calculation"

[ltomuta]

I opened and old design, made some slight changes to it and tried to simulate the CAM. I get two instant errors about stock calculation. Once dismissed the simulation continues but no stock is actually removed. 

And then, when I stopped the simulation, Fusion crashed and report 310336059 was uploaded. 

[ltomuta]

The same error, minus the crash, happens on the unmodified version of the design so the error is not due to my current edits. Something must have been introduced in Fusion after end of January when this design was last modified.

[seth.madore]

Could you share your file?

[ltomuta]

I will send it to you in a PM

[seth.madore]

If you prefer email, that works as well: seth dot madore at autodesk dot com

[seth.madore]

Well.....hmm. I'm not getting any Simulation alarms, using your file "as is".

Are you on Mac or PC? If on PC, what flavor of Windows are you running?

[ltomuta]

Windows 10 Pro, up to date*
I will try later at home but I have Windows 11 running there so that may be even more unstable.

* Some patches awaiting installation as I'm just back from my vacation.

[ltomuta]

Yep, I can reproduce it instantly on my home PC as well. As soon as the tool touches the would be stock the error is triggered (in duplicate). See https://autode.sk/3iPb96o

Sometime I can dismiss it and simulation continues and some other times Fusion hangs. This time the crash data was sent to MSFT not to ADSK.

[jdholbrook33]

I opened a file I made back in June and had the same experience. "Error calculating stock" or something like that. If I clicked through the error it would crash Fusion.

I tried a few things such as checking "Stop on collision", tried to adjust the accuracy of the stock (which crashed Fusion instantly).

I was finally able to get it to process normally by going to my tools and just changing the length by a tiny amount.

This cured the error so I went back in and changed the tool lengths back to original.

It seems to have cured it as I've tried multiple things to cause it to error out again and it hasn't.

worth a try.