Components Have Their Own Timelines?

Components Have Their Own Timelines?

glencandle
Advocate Advocate
1,220 Views
6 Replies
Message 1 of 7

Components Have Their Own Timelines?

glencandle
Advocate
Advocate

According to Autodesk, components "have their own origins and timelines":

 

https://www.autodesk.com/products/fusion-360/blog/5-time-saving-strategies-assembly-design/

 

But in my experience all my components share the same timeline.  What am I missing?

0 Likes
Accepted solutions (1)
1,221 Views
6 Replies
Replies (6)
Message 2 of 7

g-andresen
Consultant
Consultant
Accepted solution

Hi,

The timeline can be limited to the activities of a component.
If this C is then active, only the contained actions are displayed.

 

Screencast

 

günther

0 Likes
Message 3 of 7

glencandle
Advocate
Advocate

Oh this is huge for me, thank you! I did not know about "Hide all inactive features" option.  I feel like that should be turned on by default, not off.  Thanks again, saved me tons of headache.

0 Likes
Message 4 of 7

jeff_strater
Community Manager
Community Manager

@glencandle - while this is, indeed, useful, it is important to understand what this does.  This is just a filter.  The timeline still contains all of the features from all local components, in whatever order they were created.  In particular, be wary of moving the end of design marker while this filter is on, as you could be rolling past lots of features not related to the active component.  Similarly, feature reorder can have unexpected effects in this mode.

 


Jeff Strater
Engineering Director
0 Likes
Message 5 of 7

dave_g_martin
Explorer
Explorer

just came across this thread because of similar problem - so what use is timeline with components if, when "hide inactive" is on,  you can't just step backwards in that component without damaging another component?

 

0 Likes
Message 6 of 7

TheCADWhisperer
Consultant
Consultant

@dave_g_martin wrote:

... you can't just step backwards in that component without damaging another component?


@dave_g_martin 

Part of this statement doesn't make logical sense.

You can't damage another component unless you are tying the history of the two together in some way.

Understanding how to use the history is key to understanding Fusion.

Can you File>Export your *.f3d file that exhibits unexpected/unwanted behavior to your local drive and then Attach it here to a Reply?

One of the experts here can demonstrate how best to use the history "time machine" to your advantage.

0 Likes
Message 7 of 7

dave_g_martin
Explorer
Explorer

Thanks ... only getting up to speed with Fusion; if there's a good resource re history/timeline I'd appreciate someone pointing me at it ...

0 Likes