where to put joints in the tree?

[rocketmanthree]

When creating joints should they all go in the top level joints folder or can / should they be in the same folder as the parts they are joining. Mine seem to be scattered all over, some in the top level and others in components created to hold sets of similar components. And they keep not working, I locked together lots of parts including a DVD drive with a sliding draw and then at some point in the future I can just drag all the parts again even though the joints still appear to be in the tree. I had to redoo most of the joints which now seem to be doubled up.

I wonderd if they should all be kept in the top level to work properly even though the software seems to create them down in the component folder.

I have added a picture of some of my parts tree.

I am very new to Fusion so it could be me.

[jeff_strater]

Joints will go wherever they need to go, there isn't really any way to control where they go.  For local designs (no external referenced designs), this is the "lowest common parent" component.  So, if you have a design that has this kind of a structure:

    root

        ComponentA:1

              ComponentB:1

              ComponentC:1

        ComponentD:1

               ComponentE:1

               ComponentF:1

If you create a joint between ComponentE and ComponentF, it will go into ComponentD.  If you create a joint between ComponentF and ComponentB, the joint will go into the root of the design.

Hopefully this helps to clear up your question.  Thanks for posting it!

Jeff Strater (Fusion development)

[joel.palioca]

Hello,

The location the joint is created is based on the components and associated geometry that is connected to those components.  What it tries to do is create the joint at the lowest possible component that contains all of the components and associated geoemtry involved in its creation.  If you have a multi level design with components inside of each other many levels deep, depending on how the components are created joints can end up in different locations.

Would you be willing to share your file with me?  This way I can take a look at your design and joint issues and see if I can offer some advice on what might be happening, or if there is a problem we can work to resolve it.

You can share a file by exporting it out as an .f3d or .f3z, or you can add me to your project with my email below.

Cheers,

[rocketmanthree]

Cheers Joe I have sent an invite. Some other probably unrelated observations, sometimes it is not possible to drag and drop parts into other components and then you can, possibly during uploads. Also after a crash possibly due to nvidia driver I had a popup stating the software was now running in compatibility mode and i'm not sure if that is still the case.

[joel.palioca]

Thanks for the invite.  I will take tomorrow to look over the file and see what we can figure out 🙂

Cheers,

[joel.palioca]

Hello,

I have spent some time looking at your file and there is a few things I need to dive deep into with more of the team.  As you mentioned there seem to be some duplicate joints that are in a weird state.  If it is alright with you, I would like to export out your file and work with the team to understand what is happening.  Is this an issue at all?

On another note, most of your practices for creating and using the joints look to be good.  You seem to have a good understanding on when to use the joints and how they work, but obviously we have a hiccup that you have created a work around for.  Outside of the workaround effort to create duplicate joints, are you able to continue working on your project and design?  I want to make sure you are able to be productive while we investigate these other issues, which may require additional time.

Cheers,

[rocketmanthree]

Feel free to export it and play around. I would like to have been able to
tell you when the original joints broke but all I can say is it might have
been after the update. I ended up applying the grouped joint on all the
frame after I found it. I would probably have used that from the start if I
had known about it earlier.