- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
After a few (well, many) preliminary explorations of how to create different parts of what I am designing, I am setting out to do the 'real thing'.
I am requesting comments on how I intend to structure the Fusion360 file types and hierarchy.
MAIN PROJECT
>MAIN DESIGN (which is, if I understand it, actually a component but is the topmost one)
contains main design items needed by many components, bodies, or sketches
contains the user parameters that will be used in various sketches/bodies/components
also includes overall elevation and plan views that will be used (traced) to create sketches inside other components
this is where the subassemblies are assembled into the whole thing
>SUBASSEMBLY_A COMPONENT
an assembly of other components created within this component, but has no bodies of its own
may have sketches needed by the components inside this component
>COMPONENT OF SUBASSEMBLY
will contain its own sketches and bodies plus more components
>COMPONENTS (if needed as independent 'jointable' objects within the above component)
each will contain its own sketches and bodies
>SUBASSEMBLY_B COMPONENT
an assembly of other components created within this component, but has no bodies of its own
may have sketches needed by the components inside this component
>COMPONENT OF SUBASSEMBLY
will contain its own sketches and bodies plus more components
>COMPONENT(S) (if needed as independent 'jointable' objects within the above component)
each will contain its own sketches and bodies
Is this the correct structure?
Am I asking for trouble by nesting components?
What to do if this is not the proper approach?
Cheers for replies,
Drew
(Edited for typo)
Solved! Go to Solution.