[BUG] explicit joint origin does not derive with the component

[BUG] explicit joint origin does not derive with the component

TrippyLighting
Consultant Consultant
898 Views
7 Replies
Message 1 of 8

[BUG] explicit joint origin does not derive with the component

TrippyLighting
Consultant
Consultant

When adding an explicit joint origin to a component and then deriving that component into a new design, this joint origin is not part of that component in the new design.


EESignature

899 Views
7 Replies
Replies (7)
Message 2 of 8

karina.harper
Autodesk Support
Autodesk Support

Logged as FUS-47955

 

0 Likes
Message 3 of 8

lure23
Collaborator
Collaborator

Good. 

 

This bite me again, today. I'll place some pictures here, but just wanting to get a knowledge that is being worked on (it's been in the oven for 8 months, now).

 

Inner projectInner project

 

joint_origin_missing.png

 

I find this bug and the delay fixing it hard to understand. The Joint Origins are intended to make connecting components easier. The Derive feature is intended to make distribution of components easier. Surely these two should play together?

 

Workaround: I make a sketch in the inner project (since sketches do survive the Derive) and either create the Joint Origins in the parent side (whoa! bad modularisation!) or join directly to the sketch.

 

As to Jeff's description elsewhere, this sounds like a "one liner" to have the code also pick up Joint Origins. Is there something more complex involved?

Asko Kauppi

IT guy into Cleantech.
0 Likes
Message 4 of 8

karina.harper
Autodesk Support
Autodesk Support

Hi @lure23 

 

I have added your notes to the internal comments of the ticket. I can't speak to what progress has been made on it, but bear in mind there are thousands of feature requests and changes people want in Fusion. Your feedback is appreciated that this is something people really want.

 

Cheers,

 

Karina

 

Message 5 of 8

lure23
Collaborator
Collaborator

Thanks Karina. Hearing that the number is "thousands" (and considering the throughput times we can see) maybe there is a need for serious reduction of backlog. I feel bad for the developers who need to struggle with such never-ending work pile. Have been there.

Asko Kauppi

IT guy into Cleantech.
0 Likes
Message 6 of 8

TrippyLighting
Consultant
Consultant

@lure23 are you fully aware of the difference between Derived components and linked components ?

It might just be that you are better off using linked components.


EESignature

0 Likes
Message 7 of 8

hpekristiansen
Advocate
Advocate

Are there any news about derived joint origins?

I wish that small things like this would take priority over large new functions.

0 Likes
Message 8 of 8

CreativeEngineer
Explorer
Explorer

Please add my vote! I would also like to be able to select individual joint origins when not grabbing the whole design at root level. I'm using this to create simplified representations of complex assemblies with lots of fasteners. I pick just the bodies I want, and would also like to grab a couple joint origins that control how the assembly connects to other things.

0 Likes