Bug with joints to components that have changed from single component to assembly component

[khokeson]

Bug is a bit hard to describe but these are the steps:

1 - make a multi-body single component, as in not an assembly component, I'll call it Component_A
2 - put Component_A into an assembly
3 - create a joint with Component_A
4 - update Component_A, creating new components from the bodies, so now Component_A is an assembly
4.5 [not sure if this affects it] rigid group the components in Component_A
5 - in the higher level assembly, update the reference so it is referring to latest version of Component_A. The joint will still work, but if you edit the joint, it will show a missing reference, but you can't edit or repair this missing reference, and the joint does not show as broken. Also, depending on what you're doing with APIs, this breaks joint origins. The only fix is to delete and remake the joint.

[g-andresen]

Hi,

please share the file for reply

File > export > save as f3d on local drive > attach to post

günther

[jeff_strater]

This is expected (if admittedly undesirable) behavior.  References to components include the "path" through the component hierarchy.  So, when you convert the bodies to components, you have changed that path, so the reference will fail.  Will it ever be changed?  Perhaps someday, but it is currently not very high priority.  Sorry not to have a better answer.

[khokeson]

It breaking the joint is just fine. It would be cool if it went yellow and
you could repair the joint but this one took a few hours to catch and was
causing downstream issues with a script.