So I am getting deeper into my default settings for my controllers and I would post these dynamic toolpaths and end up with 20,000 lines worth of code for a program. I have updated my control definition to maintain arcs as opposed to linearizing. A G01 helical entry for a pocket may be 1,000 lines, whereas when it used I,J,K, it is like 5 lines of code. So my question is what advantage is there to linearizing these operations and creating a mountain of code? Is there a reason I cant try to maintain arcs for everything within tolerance? It seems like my controller would appreciate the code being shorter, having less issue with look ahead, etc. Why does Mastercam default on linearizing? Thoughts?

its a minor issue that only causes annoyance when i accept a transform without realizing Copy. Its like 10 seconds to fix but I have been trying to optimize my workspaces with 2017. Every second counts! Thanks for the input though, Cheers

Hey all, Is there a way to modify the defaults for Xform>Translate so that it defaults to Move instead of Copy? I am sure I am overlooking an obvious config setting but I can't seem to find it. Thanks!

The university where I work recently updated to SolidWorks 2015 and now we are having trouble importing and opening Solid files in MasterCam X7. It is the "Unable to define parasolids" issue and I was hoping someone here could point me to a fix that doesn't involve converting all our files to Parasolid files in SolidWorks before bringing them into MCX. Thanks in advance! C