topic Re: Derived Component Change Causes Unrelated Joint Failures (Position Calculation Initialization Error) in Fusion Support Forum

Derived Component Change Causes Unrelated Joint Failures (Position Calculation Initialization Error)

grenier4 — Sun, 21 Sep 2025 21:44:35 GMT

I have a Design where the first/main component of the Design consists of sub-components derived from another Design (joints are not included with the Derived components). I made a minor change to one of the sub-components in the source Design (added some slot cutouts, circled in red in the screenshot below). After running Get Latest, nearly every joint in the Design has failed giving "Position calculation failed due to initialization error." The failed joints don't have anything to do with the specific sub-component that was changed. I can't determine any reason why the joints are okay up to a certain point in the timeline and then they all fail after that. There is also a derived Parameter file in this Design, to which some new parameters were added for the new slot cutouts... but there were no other parameter changes made.

When I double click on a joint nothing appears to be wrong with it, but it won't resolve. Compute All doesn't help. Rebuilding Occurrences and Dangling Joint Origin commands do not help. This same error has occurred for another Design of similar complexity, meaning I now have nearly 40 failed joints. Is there any potential remedy for this problem besides deleting and remaking every joint? What is causing this problem?

This sort of problem really has me thinking twice about continuing to use Fusion. If a large, complex project can be set back by hours or days by bizarre errors like this, it's just not trustworthy enough to use. Based on current performance, I don't think I would recommend it to someone except for the simplest of projects.

Before the change:

After the change:

Re: Derived Component Change Causes Unrelated Joint Failures (Position Calculation Initialization Error)

grenier4 — Mon, 22 Sep 2025 00:57:02 GMT

Another example of the same issue.

Before making a component change (all joints are fine):

After making a component change (adding the holes indicated in red, which should not interfere with any preexisting joints):

All joints are now broken, giving "Position calculation failed due to initialization error."

Update: If I delete a joint entirely and try to insert a new one, even the new joint fails.

Re: Derived Component Change Causes Unrelated Joint Failures (Position Calculation Initialization Error)

mayank.malukani — Mon, 22 Sep 2025 05:27:33 GMT

Hi @grenier4 , Would it be possible to attach the file with issue. Open the model in Fusion 360, select the File menu, then Export and save as a F3D or F3Z file to your hard drive. Then use the Attachments section, of a forum post, to attach it. If needed, ZIP a F3Z file.

Re: Derived Component Change Causes Unrelated Joint Failures (Position Calculation Initialization Error)

grenier4 — Mon, 22 Sep 2025 14:18:46 GMT

I have no idea why, but this problem seems to have spontaneously fixed itself. After a Fusion restart, Get Latest or Compute All seems to have corrected all the joints. I had previously already tried restarting Fusion... so I don't know what changed. I'm glad this fixed itself, but why did this happen in the first place? Given this has fixed itself, is looking at the file still helpful? I can provide a link to a downloadable file via email to Autodesk, but do not want to publicly post Fusion archives here.

Re: Derived Component Change Causes Unrelated Joint Failures (Position Calculation Initialization Error)

mayank.malukani — Mon, 22 Sep 2025 15:53:21 GMT

@grenier4 Good to know you are not seeing the issue anymore, it would be great if you can share the file so that we can check what went wrong before. If you want to share your file with me privately , please send me a PM.

Re: Derived Component Change Causes Unrelated Joint Failures (Position Calculation Initialization Error)

grenier4 — Sun, 28 Sep 2025 13:08:56 GMT

I sent the archive shown in the first post of this thread.