Fusion 360 notification crash

[jculleton3]

attached is a screencast after a clean install and reboot.

I still have to delete login

[mohammed.aliTDPXK]

Hello @jculleton3 ,

There seems to be no screencast attached here, can you please attach here or post the link ?

Thanks!

[jculleton3]

Sorry here is the sceencast.

Any time I open notifications even with no file open Fusion 360 stops responding.

https://autode.sk/3yAQ3z4 

https://autode.sk/3pRLU5M

I have inserted two separate sceencast links.

[jculleton3]

I actually attached screen casts as links in the above message.

If I do a clean install of Fusion 360 then notifications work fine. 

After I close fusion 360 1 time and then reopen the notification app crashes.

I also don't have access to my add-ons. 

I am really getting fustrated.

[RajkumarIlanchelian]

@jculleton3 I am going to check with our engineering team on this. Meanwhile, if you open Fusion 360 in offline mode (or when ever the notification works), are you able to see notifications in there? If you clear all the notifications and then then go back online (and restart Fusion 360) does that help? 

[mstrater]

Can you also send @RajkumarIlanchelian and I your log files?
https://knowledge.autodesk.com/support/fusion-360/troubleshooting/caas/sfdcarticles/sfdcarticles/How...

[jculleton3]

I discovered the cause of the problem. 

The CPU is an Alienware 17r laptop.

With two external monitors connected via the USB/C port on the laptop.

As long as I open and close Fusion on the monitor designated as Primary (the one with all the desktop icons) it works fine.

If I open Fusion on the main screen, move it to the second, or third(laptop screen) monitors and then attempt to look at notifications it crashes.

Also if Fusion is closed on the second monitor it will not start up again unless I delete the NMachinSpecificOptions and LoginState files and then reboot.

The problem has not re-occured since I stopped moving Fusion to other monitors.

Sincerely JC

[jculleton3]

Attached are the diagnostic logs.

I don't know if they are from after the last re-install in which case they probably don't have any information of use.

I could deliberately connect my second monitor and move fusion hit the notifications button and then restart after deleting the NMachineSpecificOptions and LoginState files and recollect them.

If you think this will help let me know.

[jculleton3]

oops I will send them to your emails instead. 

Once I figure out how.

My bad

JC

[mstrater]

This is extremely helpful! Thanks for figuring that out. I've logged a bug for it and I'll push to fix it soon (FUS-96771). I know exactly where to look based on your information, so I don't think it'll be too hard to fix.

[lance.carocci · Accepted solution]

@jculleton3 could you please try a potential workaround to help us identify the problem?

1. Right-click on My Computer/This PC on the Desktop or in the Start Menu and select “Properties”
2. In the left column of the System window that appears, select “Advanced System Settings”
3. Within the System Properties window that appears, click “Environment Variables” in the bottom right
4. Within Environment Variables, click “New…” under the System Variables section
5. For Variable Name, enter QT_OPENGL
6. For Variable Value, enter angle
   • An alternate option to try for Variable Value is software - edit the aforementioned variable rather than creating a new entry
7. Click OK to save the new variable
8. Launch Fusion 360

Undoing this change is as simple as selecting the variable you've created from the table, and clicking Delete.

If neither value above work, you can delete the variable, and we can try some other approaches.

[jculleton3]

I will attempt that this afternoon. 

I am in the middle of drawing a BattleBot so you know.. Time.

Thanks JC

[jculleton3]

Yes that appears to have worked. 
The screen Starts to open on the main screen (Fusion 360 Splash screen) and the app opens on the second screen.
Once the App has opened it appears to be working properly.
I was able to check notifications, close and re-open the application with no apparent errors.
Moving the App back to the original screen gave the same results.

Thanks for all you help.

JC