Fusion360 Crashes on Startup on Mac

[Anonymous]

ARE YOU KIDDING ME!?

Fusion360 was recently automatically upgraded and now it doesn't start up! It crashes on my Mac everytime I try to start it. DON'T you guys test your releases before you foist them on everyone and ruin someones workday! I need to access fusion360 today and cannot because it crashes. I was perfectly happy with the previous release that worked.

PLEASE HELP!!!

Sani 

[MikeschTheCat]

Hi @Anonymous,

i have a MAC, too.

My Version runs fine at the Moment.

Which Fusion 360 Version have you at the Moment ?

=> My Version is: 2.0.3034

What do you have for a MAC-Version ?

=> My Version is: Sierra (10.12.4 (16E195))

Which Model do you have ?

=> My Model: Mac Pro (Mid of 2012)

Which Graphic Card ?

=> My GPU: 2* ATI Radeon HD 5770 1024 MB

Have you any Error Messages ?

=> Applications/Console.app

Please give AutoDesk informations, so they can Help you 

Best Regards

Stefan

[Phil.E]

@Anonymous

Sorry to hear of this problem. Let's try to get you back up and running.

First, I want to find out what went wrong with your installation. For this, I need your diagnostic log files. 

• Go to ?Help menu
• Pick "diagnostic log files"
• When these are gathered you will be prompted to their location
• Attach to a response in this thread

I'm looking to see if there is a remedy short of re-installing. Will update this thread shortly.

Thanks,

[Phil.E]

@Anonymous

After you gather your diagnostic files, try this:

Go to Library > Application Support > Autodesk > Neutron Platform > 

Delete NMachineSpecificOptions.xml

Next go into the folder in Neutron Platform that has an alpha numeric name like: K3JND45L

Delete NGlobalOptions.xml

Restart Fusion 360.

If that fails, use these instructions to cleanly remove Fusion and reinstall.

https://knowledge.autodesk.com/support/fusion-360/troubleshooting/caas/sfdcarticles/sfdcarticles/How-to-do-an-automatic-Clean-Uninstall-for-Autodesk-Fusion-360.html

[Anonymous · Accepted solution]

---

@Phil.E wrote:

@Anonymous

After you gather your diagnostic files, try this:

Go to Library > Application Support > Autodesk > Neutron Platform > 

Delete NMachineSpecificOptions.xml

Next go into the folder in Neutron Platform that has an alpha numeric name like: K3JND45L

Delete NGlobalOptions.xml

Restart Fusion 360.

If that fails, use these instructions to cleanly remove Fusion and reinstall.

https://knowledge.autodesk.com/support/fusion-360/troubleshooting/caas/sfdcarticles/sfdcarticles/How-to-do-an-automatic-Clean-Uninstall-for-Autodesk-Fusion-360.html

---

Just want to say thanks to @Phil.E; Fusion 360 update was crashing on my Macbook and Google brought me here.  Deleting the files you specified fixed my issue.

[Phil.E]

Thanks for letting me know. You might notice the advice above was from 2017. It just happens that removing the same files will get past this new bug (which is actually entirely different than the issue in 2017). We are working now to fix the issue and ensure it doesn't happen again. Sorry for the inconvenience.

[alan]

@Phil.E  I am experiencing the same problem (May 2020). Have you been able to come up with a fix for this?

Thanks!
Alan

[Phil.E]

Hi,

I think this should be a new thread. The problem from 2017 is not what we are experiencing today. 

The recent reply was informative, but not helpful to determine anything we can work on. The problem with bugs and crashes is the need to repeat them, and understand how they happen, and then debug the problem in code.

I don't see any CER reports from your email address which makes it impossible to tell what problem you have exactly, and offer advice.

It would help to make a new post and include details like this:

• How often does this happen, does it repeat
• Whether you are blocked from running Fusion entirely
• Did you take any action to change the situation
• Do you see a CER report

Thanks for helping and considering questions like those above. 

Regards,

[alan]

@Phil.E  Hi Phil, thanks for your fast reply. Sorry, you are right. I should have probably started a new thread.

To make a long story short, the problem is now solved. After I uninstalled Fusion 360 and attempted to reinstall, I got a message that Fusion 360 was not compatible with my operating system (which was High Sierra). I upgraded to Catalina and Fusion 360 works fine.

Thanks, Alan

[Phil.E]

Fantastic.  Thanks for the update. Glad it's working for you now.

Best regards,

[ckriesi]

Yeah it's back.

It all worked fine yesterday, today I can't get past the login. I tried:

- regular uninstall / re-install

- uninstall with the cleaner app + re-install

- removing the abovementioned files

- changing the proxy settings.

nothing.

Awesome does not even begin to describe my feelings about this program right now.

Mac OS 10.14.6

newest fusion version

[ckriesi]

Okay somehow I can't edit my reply above either.

Update: I used the cleaner but unchecked the "keep local data", re-installed, and it worked. 

Reason: Somehow the NativeTrackpad Add-In I used (I used the github .zip file yesterday...) causes Fusion360 to crash, unless one installs it through the Fusion App store. Now it all runs again. 

So: keep the "run at startup"-option unchecked for new Add-Ins, it might just make your day a lot worse. 

That being said: Fusion programmers, please pretty please implement what NativeTrackpad does by default! It makes the trackpad experience on mac miles better.  

[Phil.E]

For anyone finding crash on startup on mac:

Please start a new thread in the Fusion 360 support forum page. I'm going to ask that this thread be locked. We are getting several issues mixed up with an old bug that no longer exists.

@ckriesi The crash you are experiencing, as you have noticed, is related only to Native Track Pad from git. You are the only customer who has sent in a crash report for this issue, and thank you for sending in each and every one of those crash reports, it truly helps to send each one.

The author of the add-in has been notified and we are looking to see if any other add-in could also produce the same result. Bottom line - crash on start issues are very high priority, please send in any reports when you see the crash dialog, and/or post in the support forum about it.