Fusion Auto-updates subassemblies

Fusion Auto-updates subassemblies

gabrielle.boutrosFGMS4
Explorer Explorer
627 Views
5 Replies
Message 1 of 6

Fusion Auto-updates subassemblies

gabrielle.boutrosFGMS4
Explorer
Explorer

For the past few months, it appears that every time I open an assembly in Fusion, instead of showing the triangle icon indicating that a part in the assembly has a new version, Fusion has been automatically doing all the "get latest" commands when I open the assembly. I can see this because immediately after opening the assembly, there are several unsaved changes and I can undo lots of "Get Latest" commands. Not only does this happen when I first open the assembly, but every time I navigate away from and then back to an assembly in an open tab. This has massively slowed down my computer and made Fusion360 virtually unusable, as the assembly seems to fully re-compute each time I switch tabs, and can take upwards of 3 minutes to load each time, despite my computer having appropriate specs for Fusion, and having no issues in previous versions of the software. Opening the same files on my colleague's computers does not show this issue, it seems to be only with me. I can't find the option in settings to undo the automatic "Get Latest" commands, does this exist?

0 Likes
Accepted solutions (1)
628 Views
5 Replies
Replies (5)
Message 2 of 6

helfenj
Alumni
Alumni

Hi @gabrielle.boutrosFGMS4,

 

Can you record a video of this and/or tell me more about your scenario, steps, process, etc...? This is clearly not correct and there isn't a setting to control this today.

 

Do you have any 3rd Party plugins or scripts installed?

 

Thanks,

 

John

0 Likes
Message 3 of 6

gabrielle.boutrosFGMS4
Explorer
Explorer

Hi John,

 

I can't screencast due to confidentiality.

 

The only thing I have installed that might affect Fusion is the Altium CoDesigner, but I installed that long before these issues began to happen.

 

In my file structure I have nested levels of individual parts that are each their own file. These parts and subassemblies are then inserted into the overall assembly. When I need to edit an individual part, I prefer to open that part file and version/save my changes there rather than edit in place.

 

Then the process when opening an assembly for the first time after updates to components is as follows:

1. Make edits to or save the individual component that needs to be changed in the assembly

2. Save my work and close the file - it doesn't affect the next result

3. Open the assembly. Wait several minutes for it to load. Once it is open, notice that the updated components, which should appear with the "get new changes" icon, do not have the icon next to them.

4. At the top of the task bar, the undo button shows there are actions that can be undone even though the file has just been open. This is always a series of "get latest version" commands. Undoing this manually gets me back to where the file should have been when I first opened it, with the "get new changes" icon next to any updated parts.

 

There is also this similar but slightly different workflow:

1. Open both the assembly and a component that is part of this assembly

2. Test switching back and forth between tabs. Even if there are no changes to the smaller part or the main assembly, switching back to the assembly causes it to "re-build", it takes as much time as if I had closed the file and opened it again, and I can see the loading bar in the bottom right corner.

3. Edit and save the component, but do not close the tab

4. Switch back to the assembly tab. Since it "re-builds" each time I switch back to the assembly tab, the changes to the component are pulled in automatically, and once again it takes a long time to load.

0 Likes
Message 4 of 6

helfenj
Alumni
Alumni

Hi @gabrielle.boutrosFGMS4,

 

Thanks for the detailed overview.

 

Do other users also have Altium CoDesigner installed? Just want to confirm we have evidence that the two apps aren't conflicting. This feels like an external app is triggering a Get All Latest Action as part of an open call.

 

I completely understand the need for confidentiality. Would it be possible for you to capture some diagnostic logs for our dev teams to review privately?  You can private message me through the forums and I can give you my direct contact info to share the logs.

 

Here are some instructions on gathering the logs. 

https://knowledge.autodesk.com/support/fusion-360/troubleshooting/caas/sfdcarticles/sfdcarticles/How...

 

We can have a look and see if there is anything that jumps out in the logs.

 

Thanks,

 

John

Message 5 of 6

gabrielle.boutrosFGMS4
Explorer
Explorer
Accepted solution

Hi, I disabled the Altium CoDesigner plugin and all the problems immediately resolved, so it must have been an issue with this feature.

I sent you a PM, I can still provide the log files if it would be helpful for the dev team.

 

Thanks,

 

Gabrielle

0 Likes
Message 6 of 6

victor.farautS6FQB
Participant
Participant

Hi, I was running into the same on my side and it was more tricky on my work flow than my performances to be honest. Non the less, have no clue on what was updated and what was not was a big no go for me as I do not want unwanted version in my assemblies. I will test and see if uninstalling the plugin do the trick.

EDIT: it work perfectly. I will report it to the Altium team. A pain as this plugin was useful in my workflow.

0 Likes