Fusion is unuseable after todays update (7/16/2024) v 2.019725

[TPrice_71]

This mornings update made Fusion unusable on my pc. There is a 5 to 10 second delay after every command , if it does it at all. The drawing space locks up if I try anything. Is there a way I can roll back the update? Is there someone I can call to discuss this? I need a fast resolution, my entire department is down because of this.

[karina.harper]

Hey @TPrice_71 

If you have a subscription, I suggest you contact support (you can also start a chat with support in the bottom right o Fusion). You'll probably want to send them diagnostic log files as well - feel free to share them here too if you want. Does this happen to everyone in your department? Maybe there's an issue with network/proxy 🤔

Cheers,

Karina

[TPrice_71]

Thanks for the quick reply. I tried the chat support, but it freezes up just like everything else is. I am the only one in my department so we are at a standstill. Here are the log files.

[RajkumarIlanchelian]

@TPrice_71 When you mentioned your entire department is down, how many machines are impacted? Ca you give more details on if this is Windows or Mac and some of the machine specs? What you mention could also be related to graphics drivers. Can you please check to see if the drivers are up-to-date on the machines seeing this problem? 

[karina.harper]

@TPrice_71 

It looks like this is happening to you after every update? Is it more than what you've reported before?

Karina

[TPrice_71]

Yes, I seem to have trouble after each update. but not to this degree. I am running a windows pc - 12th gen Intel i9 2.3ghz 32 gb ram   graphics drivers up to date

[TPrice_71]

Just got off the line with the support team, not sure what they did, but everything is working again so far.

[TPrice_71 · Accepted solution]

Update: I'm using the BOMMER add in for creating bill of materials. You have to update to the latest version of BOMMER to work with the July release of Fusion. This was causing some of the freeze ups.

[RajkumarIlanchelian]

@TPrice_71 glad to know that updating the add-in solved the issue.