[Post modified by moderator to remove "360"]
Fusion Rule #0 - How to effectively learn Fusion
The Fusion Documentation has a full explanation of commands and a number of excellent
Tutorials embedded within. They can be found here:
https://help.autodesk.com/view/fusion360/ENU/?guid=GUID-1C665B4D-7BF7-4FDF-98B0-AA7EE12B5AC2
The Fusion Self Paced Learning has a series of step by step videos to get you started on
your learning journey. They can be found here:
https://help.autodesk.com/view/fusion360/ENU/courses/
The AutoDesk YouTube Channel has excellent general purpose learning tutorial videos and explanations.
They can be found here:
https://www.youtube.com/@adskFusion
Some of the Gurus lurking in the Forum also have great YouTube Channels, like this one:
https://www.youtube.com/@TheCADWhisperer
Warning: There are Cowboys on YouTube, not everyone knows what
they are doing. These links all DO know what they are doing.
General Tips for learning Fusion
1. Sketches should be simple and fully Constrained to prevent problems later.
2. If you can't find where the Sketch is unConstrained (no Lock icon) use the Text Command
Sketch.ShowUnderconstrained
3. Dimension critical stuff and constrain the rest.
4. Work logically. The Browser tree is your friend not a beast to be wrestled to the ground and tamed.
5. There is more than one way to kill a cat than drowning it in butter. There are also many ways to do the
same thing in Fusion.
6. Learn to use the Timeline early and fix issues with it WHEN THEY HAPPEN. If the timeline is yellow
or red and you didn't fix it then that is probably causing you grief now.
7. Sketch simple and use the Tools to sculpt your models. Fancy Sketches are easily broken and sometimes
hard to fix.
8. Refer to Rule #1 and Rule #2 OFTEN.
9. Practice a lot. Draw what interests you for fun, it makes learning much easier.
10. Challenge yourself. Give it a shot. Ask for help when needed. Follow through to the end. Look back and
see what you have achieved. Reward yourself for the improvements.
Requirements for asking for help in the Forum.
1. If you have a problem then ask a question.
2. Attach your File and a picture or screenshot of the behaviour or what you want to achieve.
3. If your File is proprietary, create an example of the behaviour to share and upload that. Re-creating
the behaviour may either solve your own problem or prove it may be a genuine Bug.
4. Gurus and Developers lurk in the Forum. Be nice to everyone but especially them!
5. Be humble if someone is pointing out things you have not seen or be aware of. They are NOT aiming a
personal attack at you they are trying to help you learn.
6. Never stop learning.
I used the wrong wording. Always create components. Assemblies are collections of components. Therefore, any file that has one or more components becomes, by default, an assembly. I would never need a component if I never needed a joint. At least that was my thinking.
@Steve_Worley wrote:
... I would never need a component if I never needed a joint....
I would disagree with that statement. The more complex a design gets, the more objects are collected in the browser and the timeline fills up with features.
How do you know what face of what body, or what construction plane was chosen to create a sketch on?
What feature belongs to which body?
Etc.
Components help organize all that stuff used to create the body , or bodies in that component.
Activating a component filters the timeline to show only those features that were used to create a particular component.
Can't find what you're looking for? Ask the community or share your knowledge.