> And I'm sure ATC can be added back in as a post-process, since it must at least stop for a manual tool change, or its CAM would be useless for even hobbyists

> And I'm sure ATC can be added back in as a post-process, since it must at least stop for a manual tool change, or its CAM would be useless for even hobbyists I believe ATC moves are implemented as macros by the machine. So the code emitted looks like: M6 T2 and the ATC behavior is filled in with a macro for the specific machine. To nerf ATC users, Fusion is preventing toolpaths with multiple tools from being exported in the first place. So you have to generate individual toolpaths for each tool. The sad part is that hobby machines also make use of the "M6 T<tool number>" macros to move the machine to a place where it's easy to change tools and then do automatic touch-off before continuing. It's not only professional-class machines that will be affected. It should be theoretically possible to run the multiple generated files through a script to put them back together, but this is likely too much complexity for the vast majority of users.