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

I've got this part I am working on that has a few hundred different sized holes. I want to change the attributes of each of the certain sizes but cannot get Mastercam to mask on arcs of a certain diameter. I know I'm just missing something here today. Can anyone lead me in the right direction? I remember this being very simple in V9.

All good to go here. Thanks John. I've been a little rushed here this morning and I apologize to all if I've been a little abrupt in my postings. Thank you too Gcode. You guys have been a huge help.

Okay, that worked and I'm back to 256 colors. I'm not real comfortable with the new forums setup and could not find on how to select which forum to post it it. Thank you.

16 rows of the same 16 colors. I accidentally ran the V7colors.dll chook and can't figure out how to go back to the original.

I seem to be stuck on the old V7 colors and cannot figure out how to return to the 256 colors. Yes the 256 colors box is checked but is only showing 16 rows of 16 colors. Any idea's on how to change it back?

I'm just writing the pdf's right out of X4 using the Cutepdfwriter as we go forward. IT is handling converting all the existing ones over. These inspection sheets are a duty of the programmers. We usually have a small amount of them available for the operators to use but when somebody uses the last one, the'll need to print out more. The programmers just need to have these inspection sheets available for the operators to use. We really don't want our operators converting files and things like that.

We've got other stuff in work also that will use these pdf's. We've got about 85% of a program done that will print out set up sheet instructions, tool library, inspection sheets and any other information that will be needed to get a job thru the shop and documented properly. It will print out the total work order with all the steps for each department in the plant. The planner will just need to click on an assembly # and the program will generate all needed documentation for the manufacturing of it. So the pdf's work very well in this scenario. Chris, with the pc spec's you got listed there, I would never think you would be a smart a$$. LOL. I am sure my IT guy is reading this also, but we're kind of in a lock down on spending money here so don't hold your breathe on any offers. But thanks anyhow.

gcode, yep that works very well here. I just selected the cutepdf writer as my printer and then saved the file as a pdf when prompted to do so. It doesn't get any better and simpler than that. Thanks for the input.

Yeah, we're really leaning towrds the pdf files for this now. Does anyone have a efficient way to convert mcx files to a pdf?

I like the idea of the .pdf files over the Demo or LT version of Mastercam. That way our operators would have less of a chance of manipulating the files and possibly changing them. I'll run these idea's by the IT guys. Thanks for the input everyone. [ 06-15-2010, 10:50 AM: Message edited by: Scooch ]