A new Fusion 360 Tutorials & Philosophy

[Beyondforce]

Dear Forum Administrator,

Since I joined this forum, I have noticed many new Fusion 360 users who are struggling in the beginning with this amazing software (including myself).

There are many reasons to why it is happening, which is why I would like to suggest a new Fixed post above the "Survey - Simulation & Sustainability" and the name should be "Fusion 360 Tutorials & Philosophy".

Inside this Post, we can add links to all the Standard tutorials AND add all the new Tips & Tricks, not only from Fusion 360 guys but also from other experienced user. There are many real life Tips & Tricks posts out there, and it's a shame they are not in one place. 

Since the Forum is the first place people are turning to, when something goes wrong or can't figure out how to-do something. It's only logical to create a Tutorials page in here.

When people initially starting to use Fusion 360, they are assuming that the Mindset behind Fusion 360 it is the same as the other CAD programs, but we all know it has a different Mindset/Philosophy!

Fusion 360 tutorials are spread everywhere and for a new user is a bit overwhelming. We are all ending up in this forum anyway, then why not move/open the "Fusion 360 Tutorials & Philosophy" in here?

May The Force Be With You.

Ben.

[cekuhnen]

@Beyondforce Yep to learn what and how the constraint system works I used Inventor and SW videos.

[Beyondforce]

I have seen @TrippyLighting writing to people this: "Fusion 360 R.U.L.E #1: Before doing anything, create a component and make sure it's activated."
That was the first thing he wrote to me when I first started with Fusion 360, and thank God he did! 🙂

I'm sure there are many out there that don't know about this R.U.L.E #1.

Ben.

[cekuhnen]

@Beyondforce Hhmmm I don't do that 😉 I create components later when needed. But that is because I first use Fusion just to explore ideas and then later will structure the design or even rebuild a cleaner approach then with components.

[Beyondforce]

@cekuhnen, my work process is like yours, but there are still people out there, who don't know or forget to create components from their bodies. Then, they are don't understand why things don't work as they should 😉

[cekuhnen]

@Beyondforce

I fully agree. However what I think is missing the most are quality instructions not only into how to do something

but much more important about why you should do it.

It is learning a software vs. understanding the process. If you get the process down learning the software is then a lot easier.

[Beyondforce]

You are a wise man Mr. @cekuhnen,

"You give a man a fish, you feed him for a day. You teach him to fish, you feed him for a lifetime." Or at least till the next Update 😉

[cekuhnen]

@Beyondforce Wise? Not sure - but I have now over 10 years of teaching design under my belt.

When I started I focused a lot on teaching technicality and how to use the software.

That works great when somebody (like I am) knows a lot about CAD already and has thus a foundation to connect

the nearly learned material to.

For beginners however this was a mixed field.

Today I rather focus on the process because I found that once the process is understood students have an easier

time to learn the tools of a software because it make more sense to where to use them for.

My CAD course today is rather a typical industrial design course. I teach them how to design with digital tools

and this seems to be a good combo of learning a software process and sharpen your design skills at the same time.

It is however in defense of Autocad easier to create video tutorials then working on a lecture series that is a learning path.

[Beyondforce]

@cekuhnen, I hope someone from the Fusion 360 team is reading this post, and will take our conversation under consideration. It will be great for everyone.

People will enjoy more working with Fusion 360 and learn faster how to use it correctly, when they will first learn about the Workflow / Processes in Fusion 360.

ben.

[cekuhnen]

@Beyondforce It is not just Fusion. In my teaching students often obviously complain about the software I use. Not Solidworks.

However my counter argument is that SW is only a different UI for accessing the same solid modeling tools and sketching principles

Fusion 360 employes. So does Inventor Pro-E and others.

Thats also why I think process and how tools (solid surface and mesh) work. This will make it very easy to get along with nearly

every app. Their UI is then the only problem.

I learned Maya - Maya helped me to jump into Rhino - Rhino made it easy to get along with Alias - now I hate Rhino. MOI is a pretty cool Rhino alternative.

Now I wish Alias would not be so fricken picky and the story goes on ...

[Beyondforce]

@cekuhnen, you are right. But we must remember to keep it simple. This forum is about Fusion 360 and why is it so Awesome.

People need to know about the basic rules when using Fusion 360 and the different Workflows. Then, talk about real life experience, which we see every day in this forum.

[cekuhnen]

@Beyondforce "Simple" is not really a problem when you use a smart way in teaching and introducing the tool process and its application.

Then learning Fusion is like learning how to play with Lego.

Once you understand the basic building blocks you can make discoveries on your own.

[brianrepp]

Hey Ben - thanks for the suggestion!  Curious though, have you spent much time in our Tips & Tricks board?  I almost feel a pinned post like your suggesting is ultimately part of the intent behind the Tips board, combined with our Learn section.  Great point about Rule #1 though, and I'd like to ask if @TrippyLighting would be willing to post Rule #1 on our Tips board, and then I can pin the post to the top?

BTW, this conversation is very reminiscent to a thread earlier this year that you might appreciate.  The team has taken feedback from that discussion and adjusting content and structure within the learning section.

[cekuhnen]

@brianrepp

I am working for a media house right now creating lecture material for Fusion actually and instead of making some videos here and there

the plan is to develop a modular system that step by step explains the process.

I am not sure if something like this is also feasible for AD to consider.

I see this problematic because all videos have to be tailored towards each other in terms of learning outcomes and software functions also evolve.

Years old loft videos are all invalid cause they show the old UI.

But I could see with a basic design a from start to end video sessions could be a good start and then further videos will be useful to solidify the understanding.

[fritter63]

@Beyondforce

Are you saying there should always be a subcomponent in a file? By default, things in a file are in the main component. You're saying don't put anything in there? Not even sketches?

[Beyondforce]

Hi @brianrepp,

Yes, I have checked out the "Tips & Tricks board". It's good when you are allready have a good understanding about Fusion's Workflow and processes. I have also used the "Learn section" a bit, but most of my knowledge is from the Autodesk University seminars and the initial help that I got from @TrippyLighting. I used Fusion like Inventor and it was really weird 🙂

I'm with @cekuhnen "a modular system that step by step explains the process". It seems we need to take a step backwards and talk about the Fusion 360 mindset and Why?! We need a more structured approach.

The board title should be called "Before you start with Fusion 360". It should be linked at the top of every Fusion 360 forum, so a new user won't miss it.

Before Fusion 360, I worked on Inventor. There was one guy, who really help me to understand what is Inventor and how to approach it. This is his YouTube TFI CAD Tips You might know him.

I decided to write this post, because there are quite a lot of people who don't know Rule #1, and if you don't follow it, the experience with Fusion 360 will be very confusing.

Ben.

[Beyondforce]

Hi @fritter63,

Sorry, but hmmmm are you sure your comment is for me? 😮

[PhilProcarioJr]

@fritter63

"Are you saying there should always be a subcomponent in a file? By default, things in a file are in the main component. You're saying don't put anything in there? Not even sketches?"

This is just my opinion but the only time you should have sketches in the main component is:

a) Your file only contains one model and will never contain more then one model.

b) If your assembly requires some sketches for location, placement or testing functionality of the assembly.

Otherwise every model and it's associated sketches should be in its own component.

[PhilProcarioJr]

@Beyondforce

You did say..."I have seen @TrippyLighting writing to people this: "Fusion 360 R.U.L.E #1: Before doing anything, create a component and make sure it's activated."
That was the first thing he wrote to me when I first started with Fusion 360, and thank God he did! 🙂

I'm sure there are many out there that don't know about this R.U.L.E #1."

So I think that was for you. 

[Beyondforce]

Hi PhilProcarioJr,

This is a classic example to why I started this post. People must know those things before they start working with Fusion 360! 🙂

Ben.