The last few logged bugs for cutter comp in Verify were fixed this afternoon. The changes went into vX MR2.

You should be able to save an STL file while in turbo mode. If you want, send me the file and I'll check it out.

No, sorry. The display option was changed to simply display the XYZ positions and some states when stopped.

Sorry, but there's no way to have that option set as the default condition. As you've found out, you have to manually set it after Mastercam has been started. I'll pass it along as a request...

A fix for light positioning in Verify when using WCS went into vX MR2. It corrected a similar sounding problem. If you want to send me the part(s) in question, I'll take a look.

That bug has been fixed in MR1.

In vX, all the lighting is configurable under the "Settings/Configuration" 'Shading' option. Define your lights there and that's what you should wind up with when you go into Verify.

The internal resolutions used as a result of the settings of the speed/image quality slide bar are identical between v9 and vX. The "tolerance" value on Verify's configuration dialog is the same as the backdoor editing of line #77 in v9's verify.prm file. In vX (as in v9), this extra fine tuning only takes effect if the speed/image quality slide bar is set to max quality. To do an accurate test, I'd take a v9 part, verify it in v9 and vX, and compare the results .

Quite a few changes went into Misc Op support in Verify went into MR1. Hopefully you'll be seeing them soon...

Sorry, but I missed your request yesterday. No, there's not any configuration switch that will allow you to set the default state of the duplicate drill point filter switch. Basically it comes up as "off" until you set it to "on". It will remain in the last state you set it until you exit Mastercam. I will run your concern past the Product Managers.

Whoops! I meant post-SP1 update.

Assuming that your part is named "Sandybar.mcx", when you save your STL file, it is saved as "c:mcamxdataSandybar.stl" (please make sure of the directory path). You should also have a file created there named "c:mcamxdataSandybar.lwn". Delete "sandybar.lwn". Then go back into Verify and try to bring up your part and specify "Sandybar.stl" as your stock file. It may come up in the proper orientation. If this works, you'll have to repeat this process everytime you save your Verify stock as an STL file until you get your next post-MR1 update.

Sandybar, a fix for the scenario you've described was found and fixed a couple of weeks ago. It'll go out in the next release.

The cut color changes when the Verify Options dialog's "Change tool/color" option is selected and a change to a different tool occurs. If all your operations use the same tool, only a single cut color will be displayed.

Tool colors: There never has been a way to change the color of individual tools, only the color of the cut material (10 colors max - serially allocated on tool changes). You can change the color of ALL tools permanently via Settings / Configuration / Verify or on a session basis via the Verify Options dialog. Stock WCS origin: Yes, this appears to be an issue. XYZ coordinates display: It was decided that the update of the status display states and positions in Verify's verbose mode was only to be done when Verify was stopped. The main reason was that it had a negative effect on performance.

One of the reasons why there's a difference in the stock orientation between v9 and vX is that in vX, we've added a "Stock view" selection under "Stock setup". This allows for the definition of the stock in a constant orientation. Lacking that feature in v9, the stock was orientated in relative to the view of the first selected toolpath to be verified. There were several threads relative to the confusion over the stock moving in Verify. Hope this helps answer your question.

In v9, the stock is orientated relative to the WCS of the first selected toolpath. That is why the stock may appear in different orientations depending upon which operations you have selected. In vX, this has been changed to allow the user to select a WCS for the stock. That way the stock will always appear in the same orientation regardless of the toolpaths being verified.

There were a couple of items in this thread that could be clarified for you. First, the issue of the radio buttons to define the stock (box, cylinder or file). When we implemented the STL file option, some users would leave that option set, but change parts or go to a new part, go into Verify and have to sit there while it loaded a large STL file. And they weren't happy. So the compromise was that Verify would remember you stock type of "file" as long as you were in the same Mastercam session. Shut down Mastercam and then rerun it, if it sees that it's set to "file", it reverts back to "box". It only takes a couple of seconds to reselect "file" and the file name is retained. As for the "lwn" files: These are copies of the TrueSolid model that is saved behind the scenes when you select the "Save as STL file" button. The content of these files is as accurate as the stock was when you saved your file. The STL file created is only a close approximation. When you select a file to be used as stock (i.e. "results.stl") and there's the companion lwn file in the same directory ("results.lwn") and its modification date is ever so slightly newer than the STL file, we know you haven't tried to modify the STL file so the lwn file gets loaded automatically. As to why you were having problems that were cleared up by the removal of the lwn files, I'm at a loss. If you can recreate the problem, please report a bug. Hope this helps.

One of two things is going on. If you are using the TrueSolid turbo setting, this will always happen. This configuration is only meant to be used for 3 axis, top view parts. It takes the input STL file and extrudes it downward in Z. Doing this, a tube becomes a loaf of bread. The other possibility is that you are using another configuration (non-TrueSolid turbo) and the input STL file is found to be non-water tight (lots of threads about this). In this case, we detect it and run it through the above configuration behind the scenes to create a stock that won't cause other problems (like seemingly inexplicable crashes while verifying). This was deemed to be the lesser of two evils. We have been working with the vendor we use for verification modeling on this problem for a while. Any time you run into a problem with an STL file, we request that you send us a copy of the STL file to: [email protected]

Just keep sending them. I've made sure that the email box has plenty of room. If the flood becomes too great, I'll cry "uncle". Too many is better than too few.

I guess I would be your whipping boy on this one. This problem has been around for a while and we’ve been trying to come up with an adequate solution for it since then. Your concerns have not fallen upon deaf ears. It is a nasty problem without a quick fix. Unfortunately the problem lies with our vendor, so it has been pretty much out of our hands. They have been aware of the problem and actively working on a solution. And now it seems like the solution is inching towards availability. They currently have it in their “pre-Beta” stage. To help, we’ve taken all of the problematic STL files that our customers have sent us over the last couple of years and have provided them to the vendor. Initial results are encouraging. At this point, it seems like the general consensus is, “Yeah, it’s a problem. Yeah, CNC knows about it. Learn to live with it.” I’d like that to change and am asking any/all users out there that come across these files to send them to: [email protected]. They will all be forwarded to the vendor for testing. The more files we have for testing, the better the solution is bound to be. Thanks for your patience.

If you're content with your threading toolpath and will tolerate concentric circles instead of true threads, you can dramatically speed up the verification of it by setting the speed/image quality slide bar setting on Verify's configuration dialog to anything other than max quality. This feature is available in v9.1 SP2.

I stand corrected. The previously mentioned changed will be in the release of v9.1. Beta 3 went out a few weeks ago. Sorry about that.

The ability to automatically come into verification with the last file selected as stock will be available in v9.1 Beta 3. If you pick "file" as stock, it won't default to box and force you to make the trip to the configuration dialog to select the "file" option.

In v9.1 verify, you can zoom in and out just like in wireframe Mastercam. Prior to v9.1, an unzoom will simply fit the stock to the screen.