Welcome to the Onshape forum! Ask questions and join in the discussions about everything Onshape.
First time visiting? Here are some places to start:- Looking for a certain topic? Check out the categories filter or use Search (upper right).
- Need support? Ask a question to our Community Support category.
- Please submit support tickets for bugs but you can request improvements in the Product Feedback category.
- Be respectful, on topic and if you see a problem, Flag it.
If you would like to contact our Community Manager personally, feel free to send a private message or an email.
24 Hours of Fusion later...
I've been a longtime (happy) user of Onshape. Recently I decided to give Fusion a serious try to see how much pain the integrated CAM, Eagle connector, and FEA could save me. I'm a semi-hobbyist one-man-band doing everything from PCB layout to machining parts so the idea of a set of tools that are tightly connected is conceptually very appealing. After a decent period of time here's how I'm feeling:
1. The integration with Eagle feels almost magical. I was able to turn my existing board into a usable mechanical model in no time. It wasn't perfect (no 3D models for the parts) but good enough for lining up mounting holes and cutouts. Haven't tried serious edits that would move components yet to see how well that flows through but first moment of truth experience was great.
2. I hate sketching in Fusion. Maybe I'm just so used to how Onshape works now, but after a decent number of hours of use doing what I would consider fairly straightforward mechanical design (I generally design parts for simple 2.5D machining with 1-2 setups), and Fusion still feels like an ornery horse. It often resists going where I tell it, and every moment I start to relax I end up in the mud. It takes effort to select the thing you want to select.
3. Assemblies and design flow are frustrating. I imported some STEP files from an Onshape design for off the shelf parts whose geometry won't change. Added those to my design, fine. Then I went back and changed them to components. Guess what, all my assembly references broke, and when I went to fix them, it became apparent that it would be easier to just delete everything and start over. Just what I want to spend my "fun" time doing.
4. I had a MUCH easier time setting up and running a simple static stress analysis in Fusion. I tried doing one in Onshape with Intact, and it "worked," but I didn't really understand it. If I was a real injeneer, or maybe even stayed at a Holiday Inn Express last night, I might have had a much easier time. Fusion had a really good tutorial on Youtube that I was able to follow with my part, and the result felt right compared to the real part. Again, not sure if this scales as things get more complex but so far so good.
5. I haven't tried Fusion's CAM part yet. I have looked at each of the beta CAM tools Onshape has offered. VisualCamC is the first one I took seriously, but at least as of a few months ago it seemed to be missing associative toolpaths. That is, If I program a bunch of holes to be drilled, then move one or two holes an inch to the left, the CAM tool can update the drill locations automatically. If and when VisualCamC can do this, I'd be happy to give it a more serious look. Without it, there's really no value in the integration for me.
6. Pricing: A while back I tried the IDF-to-3D module in the app store with one of my Eagle boards and it worked very well. The issue was that after 30 days I'd have to start paying $40/mo, which is reasonable for any commercial use, but my usage is too occasional to really justify $500/year. When VisualCamC comes out of beta and (presumably) goes to a similar model, I'd have a similar issue. Fusion's start-up licensing deal is hard to beat given that I get all of the pieces in one box. I am fine with Onshape's free tier since my projects are either personal goofy ones or intended-for-open-source, maybe they should consider encouraging cloud app partners to match that.
Taking all of this into consideration, I'm going to keep soldiering on a little longer with Fusion and see if the gains from integration outweigh the frustration in basic modeling. If this was my job and I spent most of my time in mechanical design, I'd strongly prefer Onshape based on experience so far.
1. The integration with Eagle feels almost magical. I was able to turn my existing board into a usable mechanical model in no time. It wasn't perfect (no 3D models for the parts) but good enough for lining up mounting holes and cutouts. Haven't tried serious edits that would move components yet to see how well that flows through but first moment of truth experience was great.
2. I hate sketching in Fusion. Maybe I'm just so used to how Onshape works now, but after a decent number of hours of use doing what I would consider fairly straightforward mechanical design (I generally design parts for simple 2.5D machining with 1-2 setups), and Fusion still feels like an ornery horse. It often resists going where I tell it, and every moment I start to relax I end up in the mud. It takes effort to select the thing you want to select.
3. Assemblies and design flow are frustrating. I imported some STEP files from an Onshape design for off the shelf parts whose geometry won't change. Added those to my design, fine. Then I went back and changed them to components. Guess what, all my assembly references broke, and when I went to fix them, it became apparent that it would be easier to just delete everything and start over. Just what I want to spend my "fun" time doing.
4. I had a MUCH easier time setting up and running a simple static stress analysis in Fusion. I tried doing one in Onshape with Intact, and it "worked," but I didn't really understand it. If I was a real injeneer, or maybe even stayed at a Holiday Inn Express last night, I might have had a much easier time. Fusion had a really good tutorial on Youtube that I was able to follow with my part, and the result felt right compared to the real part. Again, not sure if this scales as things get more complex but so far so good.
5. I haven't tried Fusion's CAM part yet. I have looked at each of the beta CAM tools Onshape has offered. VisualCamC is the first one I took seriously, but at least as of a few months ago it seemed to be missing associative toolpaths. That is, If I program a bunch of holes to be drilled, then move one or two holes an inch to the left, the CAM tool can update the drill locations automatically. If and when VisualCamC can do this, I'd be happy to give it a more serious look. Without it, there's really no value in the integration for me.
6. Pricing: A while back I tried the IDF-to-3D module in the app store with one of my Eagle boards and it worked very well. The issue was that after 30 days I'd have to start paying $40/mo, which is reasonable for any commercial use, but my usage is too occasional to really justify $500/year. When VisualCamC comes out of beta and (presumably) goes to a similar model, I'd have a similar issue. Fusion's start-up licensing deal is hard to beat given that I get all of the pieces in one box. I am fine with Onshape's free tier since my projects are either personal goofy ones or intended-for-open-source, maybe they should consider encouraging cloud app partners to match that.
Taking all of this into consideration, I'm going to keep soldiering on a little longer with Fusion and see if the gains from integration outweigh the frustration in basic modeling. If this was my job and I spent most of my time in mechanical design, I'd strongly prefer Onshape based on experience so far.
4
Comments
You're rushing your judgment. Each CAD is different and you shouldn't try to force workflows that you are already familiar with.
Try to learn it (F360) as if you would be a noob for CAD.
projektowanieproduktow.wordpress.com
In all seriousness, Fusion has a lot of features but for the most part they seem half-baked. There is a major feeling of incongruence using Fusion or as someone else called it: confusion360.
Onshape on the other hand never crashes and the overall user experience is incredible. Are we missing features....sure. The missing gaps in functionality are filling quickly and I remain very bullish on the future of onshape.
PhD, Mechanical Engineering, Stanford University
I think a lot of people seem to forget that Fusion 360 is made by Autodesk and Fusion 360 will never be a full 3D cad program, if you want that you have buy Inventor, more profit for Autodesk.
That's why they are still teasing that sheetmetal is coming to Fusion 360 ????
And what has happend with "Project Leopard" the next "final" version of Fusion 360???
So my opinion is the workflow in Fusion 360 is confusing, integration with other software is confusing, using the cloud is confusing and that is not going to change.
The thing I'm fighting with now is the whole Component/Assembly structure. My project was designed to use about a dozen primary parts put together into subassemblies and slightly different configurations, and I've been fighting the way Fusion thinks about standalone components vs. subcomponents and assemblies of assemblies.
Plus there's just weird things about how if I leave a sketch plane visible on a component, then include it in a assembly, it shows the sketch plane, or joints, or whatever, and the best way to hide them seems to be to go back to the original and shut if off there. That counts as an update which forces me to "Get Latest" everywhere that part is used. I've watched some videos around this to try and understand the "Fusion way" to solve the problem, and so far all it seems is that it has baggage/overhead where OS has little to none for me.
In some cases I can edit the solid model in BobCAD rather than importing the updated one from OS and starting over, and that can save time, but the fact that most of my work is one/two/three-offs of my own prototypes is why associative toolpaths would be a major win for me. The Eagle integration is nice, but I could live with just using Fusion to generate STEP files for board outlines and probably be fine, in a pinch.
Guys, I'm amazed by your modesty, I like to browse through topics like DYHANMTS_2018 and you've really master modesty to a virtue.
Nothing like Fusion 360 community, they love to show off.
Like for example Michael Ramos
or Israel Del Toro
or 真介 宮崎
or Peter Böker
or Kirill Chepizhko
or Mark Rogers
or even one of developers Mike Prom
maybe Djordje Jovanovic
Sergei Kolesnik??
and my best friend Phillip Procario Jr
Enough of LOLZ, I'm in pain already.
I'm not gonna wipe my mouth with others work, I also use Fusion 360 in my everyday work.
I work in POS/POP industry:
another one:
These models are fully parametric and I do use Sheet Metal.
Guys your comments are at best unbalanced.
While your impression about Fusion is valid as an impression, it's worthless as an opinion.
projektowanieproduktow.wordpress.com
https://www.g2crowd.com/compare/fusion-360-vs-onshape
I'm questioning your (all) attitude and efforts to discourage someone from exploring new tools. If you are wondering why am I doing it, you can read this thread: https://forum.onshape.com/discussion/7156/onshape-vs-rhino
projektowanieproduktow.wordpress.com
Competition helps fuel innovation. If there were limited choices, the major player would become complacent, happy at the top of the mountain and innovation would be sluggish.
When multiple companies are competing with each other for our business....its a good thing.
projektowanieproduktow.wordpress.com
projektowanieproduktow.wordpress.com
Fusion has CAM and rendering.
They are two very different products operating in the same space. Neither onshape nor f360 is a complete tool to accomplish every single task...and probably never will be.
projektowanieproduktow.wordpress.com
Disliking the particulars of a specific tool is not the same as insulting the quality of the products created with that tool.
I must admit that @dick_van_der_vaart is right, you've nailed it, your hammer parallel is perfect.
While I never accused you of doubting "capabilities nor skills", I did question your attitude and accused you (not just you @mahir) of discouraging @cwmk from exploring new tools. The second one is a bit of a stretch, I should say that you've reassured @cwmk in blaming the software for his confusion, and in result possibly not overcoming it.
This is the main reasons why I've posted my original, short answer. Seeing @cwmk posting his doubts here and not on Fusion forum is for me a sign that he don't have trust/faith in Fusion development. Your comments could only reassure him in his approach.
Hammer parallel is wrong, you would have to prove that we have some predisposition to one workflow over another. New tools/workflows are confusing because they taking the different approach. Usually, that approach is different not because developer doing something wrong, but because they are aiming at different goals, different fruits.
I'm encouraging everyone to explore "new realms" if they have a chance or already had reasons to go "there". To avoid frustration we should stop thinking that we have predispositions to what we are already familiar with (hammer parallel). Give yourself a chance, and try to start from zero.
Lastly, I'm happy that this discussion did unfold as it did because any "noob" reading this thread will get the right impression. Images that I've posted should show that Fusion is enough good for professionals to use, and my opponents were able only to counter me with rhetoric.
projektowanieproduktow.wordpress.com
January 2016 Bruce is posting: https://forum.onshape.com/discussion/comment/14277/#Comment_14277 and gets two vote ups.
March 2018 I'm posting survey from the same source and no one likes it two vote downs: https://forum.onshape.com/discussion/comment/37944/#Comment_37944
projektowanieproduktow.wordpress.com