Miko, please forward the part in question to me and I'll take a look at it.

Support for dogleg rapid moves has been added to Verify for X7. It now recognizes the configuration switch in Control Definition.

In X5, the ability to apply cutter compensation in Verify was added to 5 axis toolpaths. It is triggered by a combination of the compensation type in the toolpath and the Verify Options / Cutter comp setting. In looking at this part, yes, you get two different results with and without compensation: In this case, to get the desired results (not showing cutter compensation), disable the compensation using the Verify Options dialog: When using compensation and 5 axis toolpaths, the "Tool Radius" edit box is enabled and allows you to specify the offset distance.

Actually that feature was added to X3 MU1 in response to the request. Here's where to look for the info:

In the event you get Verify's "Fatal error..." message: Please send a copy of the file, a screen shot like the two above and a brief description of the Verify function you were doing at the time (saving an STL file, cutting stock in tool simulation mode, etc) to this email address: [email protected] It will get immediate attention. Thanks, Don

A change has been put into X3 to allow the shape of the holder to follow the Speed/Quality slidebar just like the tool does. The image below shows two views of the standard Mastercam holder with a 1" lollipop cutter. The one on the left is at max speed and the one on the right shows max quality. Hope this helps.

Our Verify vendor has supplied us with a fix for Dave's problem. It has been incorporated into vX2 MR2. There is no guarantee that this will fix other problems exhibiting similar symptons. Once again, if you are running into this problem, please send me the parts so that we can test them. Thanks...

I don't know if you'll consider this simple, but here goes. Robert's problem: In the process of saving the STL file, it was simply using up all the available memory. The solution was to pre-compress the memory used by the results of the Verify session. By doing this, there was sufficient memory to complete the saving of the STL file. Dave's problem: There is a bug in the API call we use to convert the model into an STL file. That problem has been reported to the vendor and we are awaiting a solution. Hope this helps.

This is a good example of why it's so important to properly report bugs to CNC. Robert's file, while exhibiting the same symptoms as Dave's, was a different problem. It has been fixed in vX2 MR2.

Please note that the problem has been identified for the part Dave provided. There is no guarantee that the solution will fix all the problems. If you can identify more parts that exhibit the same problem, please forward them to me so that I can get them to the vendor. The more parts they have to test against, the more robust the solution will be.

Sorry, my bad. Right now I'm looking at the problem with the STL file creation.

Guys, I've been looking into this problem and could use a few of your files. Please send me the file with the toolpaths selected and the Verify settings you are using with it. This includes which engine you are using (Turbo or tool and/or holder simulation), the Speed/Quality setting and a snapshot of your Verify Options settings.

Guys, I've been looking into this problem and could use a few of your files. Please send me the file with the toolpaths selected and the Verify settings you are using with it. This includes which engine you are using (Turbo or tool and/or holder simulation), the Speed/Quality setting and a snapshot of your Verify Options settings.

When a tool gives that "extruded" look in Verify, it usually indicates an error in MachineWorks. Please send in the part so we can get it to them to have it fixed.

Monty, if John's suggestions don't work, please send me an MCX file and the appropriate STL file to be used for stock and I'll give it a quick test. Also include your Verify configuration settings.