If this is truly an indexing situation, using G68.2 would be most desirable. That would also allow the use of standard cutter comp, G41/G42.

Okay great shut up or put up. Show us some Endmills made of this material to cut 625 or 718 with some speed and feed recommendations. Then someone might call you until then I consider it just a sales pitch.

In the View Tab - Show Gnomons (turn off the show Gnomons)

I said "warning > if no Comp is enabled", but I meant "if comp is on, and no lead in/out is enabled". Lead in/out is still required to enable 5X comp.

On/Off for 'each pass', would be my vote. You can't please everyone, since there are so many cut pattern options. I would imagine the Uses Cases for turning on 5X Compensation, would be limited to the paths where someone is using one-way cutting only, and has enabled Lead In/out Vector output. I would recommend adding a Comp Warning message, if Comp is enabled, and a Zigzag cut pattern is used/set. Also, another error check if no Comp is enabled. (Of course, it should also include a 'disable this warning for the active session' option.) Would it make sense to add a "Compensation Output Type" drop-down? (By pass, By Operation), to let the user choose which output method they would get in the NCI?

This is an awesome discussion, thanks to everyone for contributing, especially the code samples of what you're getting. My notes as of now are, please dissect them: Interface: Curve 5x/CNC Swarf = Everything is fine, don't touch it. Well, it may not be mostly applicable in Swarf depending on your input, but, whatever. Don't touch it! Flow/Morph/et. al = Add a "use Comp" checkbox somewhere (probably Misc. page for MW toolpaths), remove the "Control/Comp/Wear..." Drop downs from CNC toolpaths. Output Code (NCI) is where I'd like a bit more guidance as we have two options: Insert it right below the G1002 (tool change) line, so that we enable it before any moves happen at all. I'm not sure what the code would be, that's up to the Post team to tell me :) G20016 ALUMINUM inch - 2024 G20017 G20018 Toolpath Group-1 G20019 G20800 0. G1002 0 100 2 7 7 7 0 6800 100. 0 -5.01556361 0.2011463 10.9606967 10. 10. 10. 0 0. XXXXX <Multiaxis comp on here> G-11 START DISPLAY TYPE - Rapid G11 -5.01571148 0.20087843 10.77319695 -5.01556361 0.2011463 10.9606967 -2. 40 0 0. 0. 0. 0. 0. 0. G11 -5.01571148 -0.08216697 7.06129472 -5.01556361 -0.0818991 7.24879447 -2. 40 0 0. 0. 0. 0. 0. 0. G-12 END DISPLAY TYPE - Rapid G-11 START DISPLAY TYPE - Plunge G11 -5.01886605 -0.0878815 3.06130005 -5.01871818 -0.08761363 3.2487998 50. 40 0 -0.99999547 0.00290666 -0.00077659 -4.61816706 -0.0887779 3.24911087 G-12 END DISPLAY TYPE - Plunge G-11 START DISPLAY TYPE - Feed G11 -5.0404189 -0.11562662 3.06135669 -5.04027103 -0.11535876 3.24885644 100. 10 1000 -0.99999565 0.00288727 -0.00060266 -4.6182474 -0.11657726 3.24911077 G11 -5.06427254 -0.15203947 3.06142752 -5.06412467 -0.1517716 3.24892727 100. 20 0 -0.99999147 0.00318632 0.00262704 -4.61836225 -0.15319195 3.24775623 Output a Comp on/Comp Off like 2d does for every feed move, turning it off for Rapids (Here's what a 2d contour looks like): Gcode NCI [Contour (2D) - Wear Comp] G1016 2 10 1 1 0. 0. 0. 41 -1 1 4 0 0. -1 1 1 2 0. 2 1 <--- The "41" means Turn on Left Wear Comp, 42 would be Right> G-11 START DISPLAY TYPE - Entry G1 41 -31.65207146 46.3877151 0. 3.58125 2000 <--- The "41" means Turn on Comp> ... G1 140 -11.65207146 56.3877151 0. 3.58125 200 <--- The "140" means Turn off Comp> G-12 END DISPLAY TYPE - Exit I'm leaning towards Option #1 (a single line before any moves happen), as I haven't seen a spec for a control requiring the on/off behavior of 2d, but again I'm asking you guys what you want to see. Thanks again!

Thanks fellas! I greatly appreciate all of your tine. If I came off as being Rude, or having an attitude, this was not my intention . I am extremely grateful for all of your time and help. I responded after 7 hours of my initial post. I was just checking to see if anyone had given some advice, saw none, and made a quick response. This part is running 90% well and if so can just figure out the 2 moves on the tool path, I can wrap this part up. I was hoping to figure it out before we pulled the fixture down and moved ion to the next job, but I made notes and will definitely fix this issues. In the coming days I just want to also say, I totally understand that this forum is FREE, and folks help out of the kindness of their heart. I do the same on many other forums where I know much more about the subject at hand. I help anyone who needs it, for free in Photography, photoshop, illustrator, premiere pro, after effects, c4d, maya, blender, post processing, as well as in the UAV world. In short I always try to pay it forward. So I get it, I really do. I hope that in time you folks will see that as I learn this software I plan to help anyone I can that needs help. Again, I appreciate your input, all of you, and I’ll follow up once I figure it out or ask more newbie , less rude, (hopefully), questions.