Fusion
Community
July 5, 2023 Update
Hello all, the current Insider Build of Fusion now has native Apple Silicon support, and as you read some of the latest comments in this thread, the results are looking great. Our goal is make it available to everyone by our next product update, which should be happening towards the end of the month. If you want to try it now, you can sign up to join our Insider Program, and get access to the Insider Build. Keep in mind that once you become a member, you are under NDA and cannot sharing information publicly, with the exception of this particular project since it is already public knowledge.
Click this link to sign-up and join: https://www.autodesk.com/campaigns/fusion-360/insider-program
Thank you to those you have who've expressed interested and have been testing it! Please continue to let us know about your experiences.
___
November 23, 2022 Update
As you know we have been working closely with Apple on native support for Fusion on Apple Silicon Chipsets (i.e. M1 & M2). We are pleased to announce that we expect to achieve full native support by Summer of 2023.
As we have explained in this thread, the delay is a result of the need to ensure 100% compatibility between components from over 100 3rd party vendors including Autodesk.
If you want to access this functionality as soon as possible, please consider joining the Insider Program. If you have any questions on the topic please contact @Rajkumar.ilanchelian.
October 28, 2021 Update
Hey all, thanks again for the passionate discussion here. Even though we haven't chimed into this thread as much as we wanted, we are reading every single response and are actively working on getting Fusion to be natively supported on the new Apple chipset. Here's what I know from talking to the development teams:
We are actively working on getting native support. This is still going to take some time because Fusion uses a multitude of services to work the way it does (Autodesk-owned as well as 3rd party) many of which are also not natively supported on M1 chipsets yet. We are collaborating closely with those teams to taking the necessary steps to ensure that the services we use are also natively supported. There is a lot of passion internally to get this done as well, so we definitely feel you. Again, I can't not say when this will happen, but as soon as we have something more concrete to share, we'll be sure to update you all.
April 29, 2021 Update
We've been actively working on resolving the issues mentioned below and are glad to report that these issues no longer exist when running Fusion on the M1 chipset. We are also working closely with Apple and are in the process of certifying Fusion as 100% compatible running on M1 chipsets via Rosetta 2.
In terms of running Fusion natively on the M1 chipset without Rosetta 2, we are still working towards this goal but is going to take some time to reach. We are confident to say that running Fusion on the M1 chipset via Rosetta 2 should be indistinguishable from running it on an Intel-based chipset, if not faster.
If there are specific issues you've experience and are not mentioned below (strike-through items), please chime in and respond to this thread so we are aware and can look into it ASAP. Thank you for your continued support!
___
Apple's original press release
We are delighted to see Fusion being featured in the most recent Apple ARM-based M1 Macbook Pro announcement. Although Fusion isn’t natively compatible on Apple’s new M1 chipset architecture yet, Rosetta 2 should enable you to run Fusion*. We will be sure to keep you posted on our progress towards support of Apple’s new line of chipsets.
-
* While much of Fusion 360 works as expected under Rosetta 2, we discovered that some Fusion 360 components were not yet compatible. If you run Fusion 360 using Rosetta 2, you may experience issues in these areas:
· Switching Team Hubs in the Data Panel
· Insert from McMaster-Carr
· Explore Generative Design and Electronics Cooling Simulation results
· ECAD Tool Libraries and Content Manager
· Local Simulation Solves utilizing NASTRAN
If you rely on the impacted areas for your work, we recommend you to stay on Intel-based Macs until we have these issues sorted out.
I would base it off of your development stack. If I wanted to dual boot Windows/Linux and macOS, or use eGPUs, the x86-based Macbook Pro is going to be a much better experience for that due to current lack of support for those features with Apple silicon.
A brand new Mac purchased today is probably going to be supported for at least 4 years, given Apple's rate of development and OS support, but if you keep your devices longer than that, the M1 is probably going to be a better play for long term viability assuming ARM-based development and optimization ramps up while x86 dwindles. That is just my personal speculation, though.
What specific workflows or workspaces do you utilize most? eCAD, CAM, Generative, etc.
Lance Carocci
Fusion QA for UI Framework/Cloud Workflows, and fervent cat enthusiast
@mail easiest way would probably be to either DM me the exported file and/or a link to it shared via your A360 drive (password protected, if you prefer). The comparison of durations is helpful, thank you for that.
@rknall the DTKs have never worked with Fusion 360, which is what inspired this post. The issues causing this were inherent to the hardware, and have been fixed in production M1 chips.
Lance Carocci
Fusion QA for UI Framework/Cloud Workflows, and fervent cat enthusiast
@Berkamin, as far as I know, the experience is largely smooth and seamless via Rosetta 2. A Universal Binary is still the goal, and the migration of some of our development tools and dependencies to support Apple silicon is currently underway. We will provide updates as a native client begins to materialize.
Lance Carocci
Fusion QA for UI Framework/Cloud Workflows, and fervent cat enthusiast
Forums Links
Can't find what you're looking for? Ask the community or share your knowledge.
Post to forums
