Color looping, go figure! That's the last place I would've looked to fix the issue. Thanks MIL-TFP-41.

Well, that is kind of vague!! Error box pops up when trying to verify a transformed tool path. They do verify properly though. ???

Yeah, been there done that and wound up ordering duplicate tools because it did not show up in the slot mill selection when filtered. True story.

I'm kind of having the same issue here. Trying to define a new slot mill cutter. There's nowhere to put in a neck diameter or length. I used the dxf file from Harvey for their tool #43562, cleaned it up, made sure all lines where connected, no overlapping entities, no hidden features and I get this (see below). It would be nice if we could enter a neck length and diameter for slot mills. Right now our shank diameters, are designed using the neck diameters, for all our slot mills. Any ideas on how to get around this properly?

Gotta love those simple fixes! Thank you Fred.

Is there any way to shut off the surface density lines in Mastercam 2017? They show up when we print out the setup sheets and apparently our operators and setup people find the confusing.

I'm having the same kind of issue. I've got an aluminum extrusion I'm trying to show up as the raw stock, with no luck yet. It was much easier in previous versions when you could select a file for you stock dispaly.

Right mouse click in a blank area in the toolbar, customize, then select the options tab, and check the Large Icon box.

I am getting this same exact error for the first toolpath, in each toolpath group, in everything I've done so far in X7. It is definitley statring to get to be a PITA.

On ours, we have had issues with parentheses inside the parentheses, theses ones { } and this one # too. ???

Here's another instance of a "Not Responding" status. I am experiencing this when trying to generate large surfacing toolpaths. I use a nethasp and am saving to a network. Windows 7, 64 bit, X6 MU2. Can anybody shed some light on this? It sure would be appreciated. Thanks.

FYI, After talking with support and our IT guys, we came to find out that my .config file was corrupted. Luckily I had saved a copy of this file just in case we had to do a re-install. Replaced the corrupt one with that one and all is better.

I just today started experiencing this "Warning-profile is not correct" issue. I am running X6 MU2 on my windows7 x64 system. Nothing has changed since yesterday. Anyone have any ideas what is going on here?

Rob, Well tha's a cool c-hook. That'll save some time in the future. Thanks for sharing it.

Thanks John. I knew it was someting simple. Scott