LOL john, what's that cliche about history?

100% to Scott's Solution - The 5 axis engine solves the waterfall problem. If you're a relatively new Mastercam user you wouldn't recall a similar problem with the old verify engine doing the same thing. I think CNC is working on a user setting interface for MU1 so we'll have something like the access to verify options we had in config up thru X6

assuming you're running mastercam from a network hasp, run nhasp.exe and click "read"....

The "extra Z move is most likely from the feed plane - .1 incremental

response time is all about having the right reseller..............

gird baby gird

Kevin has the correct answer. These data paths are determined in the Machine definition (.Tool & .Material Libraries). These are in the control definition (.defaults libraries inch & mm and .operations libraries inch & mm). Section 7 of the S4A basic training curriculum(s) covers all this stuff

"property analysis" will mean something different depending on the type of entity analyzed. "analyze entity properties" (F4) works on your wireframe (lines, arcs, splines created in mcam, or re-propogated as edge curves). "analyze distance" can lock to their endpoints or the virtual snap points on a solid. "analyze dynamic" wants you to click on a solid's face or on a surface. it shows things like curvature, extents in XYZ, or current position.

didja check "use island depths" in the depth cut params?

boss vs. body - creating two bodies is creating two bodies (check the solids tree in the op mgr) adding a boss to a body adds a feature on an existing body; thus one entity in the tree. think about it

It's really not a good idea to run to sessions

The issue is related to tool profile and how it is compensated differently (Z only for drilling, D or ID and Z for profiling/facing). If Mastercam is sharing one common geometry file for the tool you have to be careful. Better to have separate profiles saved for the insert drill as a drill and as a boring bar, Then reference those in the Mastercam ops/tool manager. Its also helpful to lock the drilling op that's calling, say, T0202 for drilling before creating a boring op with T0220 (same tool in the actual turret calling both D and Z compensation. Only serves to emphasize the value of good training and tech support.

Better in general, not in topic specific terms... I'll play both sides here- The electric arming switches on the SBD Dauntless didn't work right either; make the pickel hot and it drops in the ocean . But that didn't stop Max Leslie and the other aviators launched from Hornet, Yorktown, and Enterprise from succeeding at Midway. The larger problem is most likely Mastercam's total integration: Main Interface GUI to Ops Mgr to Verify and back. I am not a software engineer so I can only imagine the difficulty of the task; multiple hardware & operating system variables plus multiple native format support. That said, you as end users have an expectation; The product you purchase will work (in legalese terms I think its referred to as " the implied warrant of merchantability". Talk to your reseller, voice your concerns. Have them advocate for you to corporate. Or seek out corporate reps in appropriate forums (like the exhibit floor at IMTS) but keep it civil. We do this and more for our maintenance and TSA customers at S4A, its even paraphrased in our website/mission statement

You may have to resort to supressing all helical output - i.e. - linearize it part and parcel to using the Fadal control

Not a good idea to run multiple mastercam instances....ever.