Derived component not bringing across joint origins

[eng]

When creating a derived component, specified from the component browser level or elsewhere, the system is not bringing across joint origins to the new target assy. All the other bits of sketches, joints etc are there. The information for the joint origins is present in the target's parameter table but not in the browser tree.

Hicups aside the new derive workflow looks like a very useful candidate for working with master sketches.

[kgrunawalt · Accepted solution]

Yes Joint Origins are not currently derived. I'll note this post in our backlog of derive todos.

[eng]

Thankyou. Joint origins will provide one more facet to the necessary set of resources to work effectively with master sketches.

The initial tests which we have run for the master sketch workflow for use in large complex hierarchical assemblies have been quite promising. The ability to change visibility in the target assembly on the derived components and geometry without disturbing the original component file is a boon.

The derived functionality is a strong adition to the Fusion system.

[krokocad]

Any updates?

[danQ84DJ]

I would also LOVE to get this, It's essential in setting up preexisting components where they can attach! Like 80-20, I assumed it would bring joint origins about to derived part. Nope, I have to create new origins for each piece. Just creating all the possible joints was crazy, then using the "join" tool to "subtract" pockets, not intuitive at all. Solidworks is way easier than this. I thought this setup would be amazing, you know once I got it going, this lack of essential feature killed it dead in it's tracks. Spent hours making these parts and origins, now... Useless... I think more people get annoyed spending their time setting things up just to find out , again, fusion does not support this feature after extensive searching.

[kgrunawalt]

It is definitely on our radar. Thanks for the feedback!

[punisher]

UGGGHHH!!!

I can't believe I went through all this time deconstructing a large assembly (it just can't handle the load) into sub-group derived components, only to find that the joint origins do not derive. What a waste of time.

The only reason we're using joint origins is because we can't use joints on planes and construction objects.  This is massively frustrating. We are expected to play by Fusion's new rules, but are not given enough tools to complete a project......

Anyway, if we are going to have to rely on joint origins, then PLEASE implement these in the derived components in the near future.

[kgrunawalt]

The latest release supports joint origin derive

[Anugrah.Andisetiawan]

Now I can derive all joints from derived components, how can I delete a particular joints? There's no "delete" command in right click menu from derived joints in derived components.

[TrippyLighting]

You cannot delete joint origins from derived components. That can only be done in the source design, but then obviously deletes the joint origin in all designs derived from that source.