Fusion 360 Crashes when generating toolpaths

alex5Q7M5
Explorer Explorer
929 Views
8 Replies
Message 1 of 9

Fusion 360 Crashes when generating toolpaths

alex5Q7M5
Explorer
Explorer

I'm having a pretty major issue with Fusion 360 that I can't quite find a solution to. I'm working on the CAM for a 3+2 axis part, and every time I go to generate a certain toolpath, it generates most of the way and then stops. Becoming stuck at whatever percentage it decided to stop at, Fusion just completely wrecks. My RAM usage jumps up to about 99.5% (regardless of the amount of RAM I have, I added more to the PC and tried again) and if I don't terminate Fusion in task manager soon enough the computer becomes unusable until I do a hard reboot. I should also mention that it isn't just one toolpath, this has happened multiple times with different operations. Is anyone else having this problem, and what can I do to solve it?

2 Likes
930 Views
8 Replies
Replies (8)
Message 2 of 9

kate.raskauskas
Alumni
Alumni

Hi @alex5Q7M5,

 

Can you please share an f3d of one of the files this is happening in?

Kate Raskauskas

Product Support Specialist



My Screencasts | Fusion 360 Webinars | Tip and Best Practices | Troubleshooting
0 Likes
Message 3 of 9

Anonymous
Not applicable

I am also having this problem when milling a basic 3-axis part.  It happens when I am in the 3D Rough operation and have the Stay-Down level on anything other than "Least".  My computer has 48GB RAM and it pegs it out within one minute of starting the computation.  It does it regardless of whether I use "Rest Machining".

0 Likes
Message 4 of 9

Anonymous
Not applicable

I have been having this problem for ages now! has a solution been found? 

0 Likes
Message 5 of 9

Anonymous
Not applicable
I stopped using fusion because of it. It wasn't fixed when I left it behind a little while back.
0 Likes
Message 6 of 9

revtmyers
Observer
Observer

I occasionally have an issue that does that as well. I noticed though mine has been based on previous tool paths. So for instance I have one now where after my initial rough in the second pass would consistently calculate 64.1% of the path then stop. I tweaked on thing on the rough cut and then redid the second path with no changes to it and it would do 100% then. If I changed the rough cut back to the initial one then it would hang up again so it was definitely something path related causing it because as soon as I tweaked it again everything worked again. Just thought this may help someone in the future. BTW the "issue" was on the rough cut I wanted to try leaving .4mm of stock, which this cause an issue one the second pass setup for some reason. As soon as I changed it to leaving .5mm of stock the second pass would also run just fine. Weird I know but I could recreate it.

0 Likes
Message 7 of 9

Tgauer86
Participant
Participant

Was this ever resolved, I’m experiencing the same issues.

0 Likes
Message 8 of 9

seth.madore
Community Manager
Community Manager

@Tgauer86 this thread is quite old by software standards, it's not extremely likely that what the OP was running into is the same thing you are encountering. Nonetheless, could you share some more info as to your steps and what Fusion is doing? If you could share the file, that would be helpful as well.

File > Export > Save to local folder, return to thread and attach the .f3d file in your reply


Seth Madore
Customer Advocacy Manager - Manufacturing


0 Likes
Message 9 of 9

TimKeij
Enthusiast
Enthusiast

I experienced a similar issue where my toolpath generation was stuck at 80%. Following the advice above, I re-examined my other toolpaths and discovered a mistake. Some components had shifted during the arrange function, causing the contours to fall outside the designated setup area.

 

Fusion didn't display an error message, it just remained stuck at a certain percentage during the process. After correcting the problematic contours, the toolpath generated successfully. This suggests that if the toolpath generation process becomes stuck at a percentage, it could indicate an error elsewhere in the design.

 

0 Likes