Sub-assembly joints not used in upper assembly

[gil.wery]

Hello,

After yesterday's update, I noticed that some joints in a sub-assembly were not used in its parent assembly. It's something I never had before so I thought it might be useful to ask for a bit of help.

I made a short video with some test assemblies to show you this weird behavior.

This video is showing the sub-assembly first, I show the movement that was intended (a simple swing arm with the shock following [the spring is floating]). And then I insert this assembly in an upper assembly and after grounding the proper parts, I try to animate it but the shock is not following the movement anymore. It seems that the cylindrical joint that was used on the lower shock axis is not considered anymore. Are you aware of this bug? Or did I do anything bad?

Thanks in advance!

Gil

[g-andresen]

Hi,

please share a sample file

günther

[gil.wery]

Hi Günther,

Thank you for taking some time, here it is : https://a360.co/3uQifvs

[gil.wery]

No one else has seen those kind of bugs/glitches after the update?

Do I need to redo all the assembly?

Gil

[jeff_strater · Accepted solution]

the mystery to me is not why this doesn't work when inserted into a higher-level assembly, but why it does work in the subassembly.  There is one cylindrical joint which appears to be missing, even in the subassembly:

Cyl5 does not appear in the browser at all.  My guess is that is why it fails when inserted - it is not really there.  I have no idea how it disappeared - would be interested to see whether you can reproduce it, or if it is OK in older versions.  The rest of the joints seem to be fine.  To fix it, I just rolled to that point, created a new cylindrical joint, and deleted the old one.  The subassembly and top-level assembly were fine.

We have not heard any instances of other problems in this area, due to the update or in general.  Not to say that there is not a problem, we have just not heard any other reports of it yet

[gil.wery]

Indeed I did that for other missing joints (and it solved the problem as well) but I was still interested to have the feedback of the experts to know if I did something wrong or if it was just a glitch. At this time, it is the only assembly where I encountered such behavior so if I see that again I'll post this here. Meanwhile, I'll consider this "as solved" but will reopen if needed.

Thank you for your time and your quick answer!

Best regards,

Gil