topic Re: Ghost joint that won't delete in Fusion Support Forum

Ghost joint that won't delete

lkokkone — Tue, 15 Mar 2022 18:16:18 GMT

Hi all, here I have (again) an isolated file that has a bug. In this file, there is a joint "Rigid64" that won't go away with delete or hide. This joint makes the part impossible to use in an assembly. The joint can only be removed by disabling and then enabling design history. This is clearly a bug and prevents me from continuing my work. I hope that this can be fixed as soon as possible.

Betreff: Ghost joint that won't delete

g-andresen — Tue, 15 Mar 2022 21:59:12 GMT

Hi,

@lkokkone schrieb:
This joint makes the part impossible to use in an assembly.

There is nothing in this file that can be used in an assembly.

What is the meaning of an orphaned joint?

günther

Betreff: Ghost joint that won't delete

lkokkone — Wed, 16 Mar 2022 05:20:25 GMT

Exactly. But there is a joint that won't go away.

Re: Ghost joint that won't delete

lkokkone — Fri, 18 Mar 2022 09:30:48 GMT

I'm sorry guenther andresen but you didn't solve the case. Here's a screenshot from the joint on an EMPTY document with everything deleted. WHY do we have a joint in a file that is empty? Please take a better look at the case because this bug is preventing my project to go forward.

Re: Ghost joint that won't delete

jeff_strater — Fri, 18 Mar 2022 13:49:35 GMT

yes, this is a bug. Do you have a way to reproduce it? What steps did you take that resulted in this orphaned joint? We would very much like to fix it, but need to be able to reproduce it before we can do that.

Re: Ghost joint that won't delete

lkokkone — Mon, 21 Mar 2022 09:49:12 GMT

I don't know how it came to be. I narrowed the problem down to saved files between versions 51 and 52. The latest version I have is 340, and I became aware of this bug just now. I guess some latest updates made the assembly not accept this orphan joint. Unfortunately, there is nothing I can do to replicate the issue. When I look at the files, version 51 has one joint that is named "Rigid64", and version 52 has two joints where "Rigid85" identifies the same joint on the timeline that was on the previous file "Rigid64." However, if I delete everything on the timeline of V52, the orphan joint gets deleted, unlike the original file I sent. Neverthelöess, I can not delete the orphan joint without deleting everything on the timeline.

Unfortunately, this design is confidential, so I may not share the original design files with everything in it.

Re: Ghost joint that won't delete

lkokkone — Sun, 05 Jan 2025 15:38:06 GMT

This issue still exists. Is there any news on this.

Re: Ghost joint that won't delete

andrewUTFY6 — Tue, 20 Jan 2026 19:08:00 GMT

I've also been fighting this issue. I believe it happens after removing/deleting a component that has a configured joint. In my case, it was specific to the rigid joint on a robot's tool output flange while rigging an end of arm tool for a simulation. When I swapped the EOAT for a revised model, Fusion didn't clean up the rigid joint correctly. These orphans still exist somewhere in the configuration but no longer show up in the component browser. Add-ins like URDF Exporter will discover these orphans and fail -- I added debug statements to the add-in code and confirmed this behavior. No, I won't share my project or code.

My workaround is the same as yours. Delete the parametric history.

Re: Ghost joint that won't delete

gautham_kattethota — Tue, 20 Jan 2026 22:43:24 GMT

@andrewUTFY6

Did you configure the rigid joint for suppression? Can you check if the joint exists in the browser when you switch to other configurations? I will try to get someone more familiar with joints to help you out with some text commands to detect orphaned joints, if it exists.

Regards

Gautham

Re: Ghost joint that won't delete

lauri_barnhart — Mon, 26 Jan 2026 22:05:28 GMT

Hello, @andrewUTFY6,

Did the information provided by @gautham_kattethota help you and answer your question?

If yes, please click on the "Accept Solution" button on the post(s) that solved your problem. This will assist other community users in finding and benefiting from this information.

If not, please do not hesitate to give an update in this thread so all community members receive an update on the progression of your question, and can suggest next steps that may be helpful for you to achieve what you're looking for.

All the best,

Lauri | Community Manager