Joints not working properly when changing configurations since the January update

[AncientCowboy]

After installing the January 2025 update last night, I'm having an issue with joints not reorienting when switching configurations. When I switch configurations, the jointed parts are not where they belong. If I open the joint and close it, the joint repairs itself. The attached video shows the issue. The assembly file is also attached.

Edit:  I have recreated this assembly from scratch and the problem persists.  

[karina.harper]

Hi @AncientCowboy 

I still have the December build on one of my machines, can you share an earlier version of the design so I can try it there? We made some changes to how Joint works recently, and I'd like to see if we can narrow it down to those changes.

You can export an earlier version like this:

1. In the data panel, select the "v123" (or whatever version you're on)
2. In that dropdown, hover over an earlier version of the design (saved before Jan 25th)
3. Click the 3 dots
4. Click Open
5. When the design opens, go to File - Export (just make sure you don't save/ save as).

The exported design should be in the December schema so I can try opening it.

Cheers,
Karina

[AncientCowboy]

Hi Karina,  The attached assembly was saved prior to the update.  Also, I wasn't sure if I'd get a quick reply in the forum (thank you for that) so I opened a ticket under my commercial license (info@palemoonranch.com).  Ticket # 23823694

[karina.harper]

Hi @AncientCowboy 

I just spoke with @brent.tanner who is working your case as well - we logged a ticket so the team can take a look at this ASAP: FUS-187331.

Unfortunately, the design you exported is still in the January schema and can't be opened on an earlier build. We might be able to get a version with an earlier schema from Fusion Team - can you try this method?

Here's a quick vid to show how to export from FT:

Cheers,

Karina

[AncientCowboy]

Here is a much earlier version of this assembly.  Hopefully, this one will work for you.  It does exhibit the behavior.

[AncientCowboy]

I am also having another issue since I updated and I don't know if it is related to the other.  When I update a component the assembly isn't recognizing that it has changed.  For example, the Pile component is currently on version 22 but the configuration of that in the assembly is version 15 and it isn't giving me the option to update it.  It is also saying that I have one reference out of date but when I tell it to get latest it does nothing and the warning remains. See attached video.

[AncientCowboy]

The last couple of days have presented a number of problems.  Here is another one. In this same assembly when I try to activate certain configurations I get this error message... Cannot switch configuration. Make sure Fusion is online, then try again.  I am, of course, online.  See attached video.

Also, I accidentally replied to myself a couple of times below with another, older, version of the assembly and another issue I am having since the update.  Hopefully you can see those.  

A note on the one problem... This morning I was able to make a change on the XBrace component and it did update in the assembly which it wasn't doing yesterday.  So not sure wht was going on yesterday.  I also didin't realize that the version numbers on the configurations don't match the version number on the component so that was confusing me.  Anyway, there doesn't seem to be an issue there at the moment.

[karina.harper]

Hi @AncientCowboy 

So the current issue (aside from the joints problem) is that switching to certain configurations fails? It could be related to the Get All Latest (GAL) failure you saw previously, I see there is still an out of date reference in the video you shared. 

That can be caused by a lost reference to another Configuration. A couple things you can do:

1. There is probably a Configuration referenced in the table for the row that is failing. Navigate to the Configured Design that holds that configuration. Toggle the root component, and save again. Then try and GAL again in the top assembly.
2. If GAL fails again, you can isolate where the problem design is by running the text command "linkmgr.list"
   1. That will output a list of references and will also say if the reference is latest or out of date, and if the reference is healthy. 
3. You can also try running the text command configreplacementrefs.counts /fix
   1. If there is a problem with the number of references (fusion thinks there's a reference, when there isn't), this will fix it. 

If none of that works, please share diagnostic log files and I can dig further.

Cheers,

Karina

[AncientCowboy]

Well, I tried the things you suggested and had no luck.  So, what I did is I exported the assembly and then uploaded it into another folder.  When I did this I could clear the unresolved component that was refusing to update.  However, other problems arose when trying to update components.  So, I had my other team member try uploading the exported component, and on his computer the other problem where components could not be switched also corrected itself. At this point my assesment was that my update became corrupted. So I uninstalled Fusion and re-installed it.   I then went to the assemblies that included this assembly and replaced them with the uploaded one.  I had to do a number of repairs to joints and sketches that broke but I have the model back together.  All seems to be working at this time.

[AncientCowboy]

Morning update...

I thought everything was working ok using compute all (ctrl-b).  However, when I bring one assembly into another assembly it seems that compute all is not working.  I've attached a video showing the result I am getting.

[karina.harper]

Hey @AncientCowboy 

Sorry you had to do all that to get it working. If you are still having issues, capture logs and we can also get on a call and look together.

Regarding the insert issue, I can see why that would happen. When you insert we are generating the design in the background (essentially computing it as-is) and insert the result. So if we are computing a bad result in the CD, it would insert similarly. The only workaround I can think of: open the design, activate that row, compute all, toggle the root component (or make some change to that row only to only prompt a GAL for that configuration), then GAL in the assembly.

We are working on the joints issue on priority, we have narrowed it down and are looking for a fix.

Cheers,

Karina

[karina.harper]

@AncientCowboy  @dsgn_sole_s_a_ 

We have pushed a fix for this issue into Production, please give it a try and let us know if you still see problems.

Cheers,

Karina

[AncientCowboy]

I installed it and all seems to be working. Thank you for all your help.

Jerry