Timeline impact

Timeline impact

mac_ito
Collaborator Collaborator
1,870 Views
18 Replies
Message 1 of 19

Timeline impact

mac_ito
Collaborator
Collaborator

Hello, it's painful the behavior of the timeline when you want to make adjustments

 

(view in My Videos)

0 Likes
1,871 Views
18 Replies
Replies (18)
Message 2 of 19

TrippyLighting
Consultant
Consultant

I don't exactly see what you feel is so painful. Care top explain ?


EESignature

0 Likes
Message 3 of 19

mac_ito
Collaborator
Collaborator

I don't know the distance to apply and therefore I would like to be able to adjust the position of the lock according to the position of the dark gray component, but as we go back in time because of the time lime, it's impossible, it's boring.

0 Likes
Message 4 of 19

davebYYPCU
Consultant
Consultant

I don't know the distance to apply....

 

Measure it, Copy distance to clipboard, Edit Joint

Paste value in to the Dialogue.

 

Might help.....

0 Likes
Message 5 of 19

mac_ito
Collaborator
Collaborator

thank you @davebYYPCU  that's a good idea..

0 Likes
Message 6 of 19

mac_ito
Collaborator
Collaborator

Beyond confirming that the "measure" function exists what I want to highlight with this example is how the timeline works. As it is done today, in my opinion, it is more a developer's delirium than a user request. Indeed, the notion of returning to time T when you want to make a modification to an element related to another element of the future is more time-consuming than productive. Solidworks, onshape even inventor doesn't work like that, why fusion made this choice? That it helps the software for the tuning history, but in my opinion it does not bring anything concrete and productive to the user. For example, Onshape is just as effective on the version history but does not use this timeline. I would be interested to have the opinion and especially the arguments of a developer on the reason for the timeline and on what it brings to the user.

0 Likes
Message 7 of 19

jeff_strater
Community Manager
Community Manager

"Indeed, the notion of returning to time T when you want to make a modification to an element related to another element of the future is more time-consuming than productive. Solidworks, onshape even inventor doesn't work like that, why fusion made this choice?"

 

I don't understand what you mean by this statement.  All of the systems you mention absolutely do implement rollback when editing a part.  If you edit a sketch in any of those systems, all the later features are suppressed (or "rolled back"), just the same as in Fusion.  The only difference is that the timeline is horizontal, while a feature browser is vertical.  Is it the fact that Fusion also uses the timeline for assembly operations, such as creating a joint, inserting a component, etc?  If so, then you are not required to use Fusion in that way.  You can use Fusion very similarly to how you use solidworks:  Define each "part" in a separate design, create a top-level Direct Modeling design to serve as your assembly, and insert each part into your assembly.  Yes, Joints are different than Mates, but my sense here is that you are not referring to that aspect of Fusion. 

 

I see from the images in your original post that you are taking advantage of Fusion's ability to define "internal components".  I understand why you would do that, I love the ability to define components without creating a new external design.  It's super convenient and efficient.  But, yes, it comes with this price:  that means that those same local components are defined as part of the history of the single design you are making, and therefore you must live with the history-based nature of those components.  I feel fairly certain that there is no way to support local components in a history-based system without having this behavior.

 

So, the choice is up to you.  I would recommend you try using the "all components are external" approach, and see if you like it.

 


Jeff Strater
Engineering Director
Message 8 of 19

mac_ito
Collaborator
Collaborator

Thanks for the comments, I'll investigate.

0 Likes
Message 9 of 19

mac_ito
Collaborator
Collaborator

no on sw the behavior is not quite the same and it is this detail that is important. The edition of the joints does not have this notion of going back, difficult to describe and in addition I have not sw for a few days so I cannot argue with a visual.

thanks for taking the time to respond.

0 Likes
Message 10 of 19

HughesTooling
Consultant
Consultant

@mac_ito When you design in solidworks do you have a file for each component then an assembly file? In the assembly do you use edit in place and\or edit in separate window? 

 

Haven't tried this but fusion has edit in place now so you could build all components in separate designs, assemble then either edit in place or edit the components in a separate window. This might give you a similar workflow to other solid modelers. Even in more tradisional solid modelers there's still a  sort of timeline in that you can't project features from the end of the tree back to the first sketch. Fusion just takes this further as you can have all components in one design.

 

Mark

Mark Hughes
Owner, Hughes Tooling
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.

EESignature


Message 11 of 19

jeff_strater
Community Manager
Community Manager

"no on sw the behavior is not quite the same and it is this detail that is important. The edition of the joints does not have this notion of going back"

 

That is exactly why I recommended using a Direct Model for your assemblies.  Direct Models do not roll back when editing joints.  That workflow:  Parametric designs for parts, Direct Modeling for assemblies, is the closest you will get to a pure SWX workflow.  It will avoid your complaints about joint editing.


Jeff Strater
Engineering Director
Message 12 of 19

mac_ito
Collaborator
Collaborator

Thanks for the advice, I'll find out and try this solution.

0 Likes
Message 13 of 19

mac_ito
Collaborator
Collaborator

Apart from what is written here, are there any tips on this process?

 

https://help.autodesk.com/view/fusion360/ENU/?guid=ASM-DESIGN-MODELING-MODES 

0 Likes
Message 14 of 19

mac_ito
Collaborator
Collaborator

@jeff_strater where can I find detailed documentation on this process please?

0 Likes
Message 15 of 19

jeff_strater
Community Manager
Community Manager

I don't know of any documentation of this method, specifically.  It may be out there, in some Youtube channel or other, but I have not stumbled across it.  It would be a good thing to document, I agree.  But, the concepts are pretty simple here:

  • assemblies are all Direct Modeling (disable design history) designs
  • parts are all Parametric (history-based)
  • parts are all external designs (don't use internal components)
  • place joints in assemblies to connect parts together

Jeff Strater
Engineering Director
Message 16 of 19

mac_ito
Collaborator
Collaborator

ok, thank's for this tip.

 

On a related subject, do you know of documentation on good practices to have for designing a complex assembly (with several assemblies and subassemblies) in a Top-down design?

0 Likes
Message 17 of 19

mac_ito
Collaborator
Collaborator

re-up, 

 

On a related subject, do you know of documentation on good practices to have for designing a complex assembly (with several assemblies and subassemblies) in a Top-down design?

 

  • assemblies are all Direct Modeling (disable design history) designs
  • parts are all Parametric (history-based)
  • parts are all external designs (don't use internal components)
  • place joints in assemblies to connect parts together

Where can I find documentation on these design processes?

 

 

0 Likes
Message 18 of 19

TrippyLighting
Consultant
Consultant

I would not design a larger assembly strictly in a top down design.

However, I need to explain what  mean with "large". In my my professional occupation I create concepts for custom manufacturing automation systems. That often involves thousands of components and it isn't too unusual for a "final" assembly to have 10000 components.

 

Imported components or assemblies that I done need to modify or don't need to modify parametrically will not have a timeline.

Everything else does, including subassemblies.

I break my assemblies into smaller external subassemblies. Some of these smaller assemblies might be top-down assemblies.

 

The ONLY way to properly position parts in an assembly is joints. The new(er) ground-to-parent attribute can be very helpful to reduce the number of joints.

 

I am not aware of any documentation or good, professional level educational level materials that cover assemblies.

 

 

Most stuff on YouTube is hobby level, created by more or less advanced hobbyists.


EESignature

Message 19 of 19

mac_ito
Collaborator
Collaborator

Thank you for sharing your experience

 

" I am not aware of any documentation or good, professional level educational level materials that cover assemblies. " > This is also the observation I made and it is a great frustration for me.

0 Likes