MeshCAM 7151
I just uploaded MeshCAM 7151 to www.grzsoftware.com/files/MeshCAM-Setup.exe . You will not find it in the check for updates feature of the last few versions because I only want people to try the latest after reading this message. This is a transition release as I wrap up V2 and begin V3. I made a number of SIGNIFICANT changes including a new installer and the app is now compiled in Unicode to support multiple languages. Win98 is now unsupported, even though it was never explicitly supported, since Unicode is not available there. I made literally thousands of changes to make this possible and I’ve been using it in my shop without errors. There are a good handful of other fixes as well. I will be curious to hear what your feedback is. Please tell me if this one worked or didn’t for you.
Why should you try this release and not just wait for the next one (other than me begging)? I really need your help and every bit of feedback I get will make more more sure that I’m ready to call this the final V2 (after some new translation files from my foreign distributors) and move on to V3. As of right now I have the following items underway on V3:
1) The ability to save an image as 3D in either an efficient or fast manner. Efficient will do the current triangulation method that can take quite a while. Fast will just use 2 triangles for each pixel and do it quickly and with very high accuracy.
2) Better 3D zoom. This will zoom into the current mouse position as you spin the mouse wheel. It should would very closely to Rhino or other CAD programs.
3) Option to calculate the machining time when inspecting the toolpath.
4) Antialiased 3d window. No special graphics card needed.
5) Ability to save the current job including the STL files after translation/rotation, supports and check surfaces, stock, program zero, stock type, job type. There are other things hidden in there to support future options as well.
As a reminder, all current users will get a free upgrade to V3. V3 betas will become available after I can stamp V2 "Done."
Build 6738
I just uploaded Build 6738 to http://www.grzsoftware.com/files/MeshCAM2-6738.exe . I’m posting it here only until I get some feedback to make sure I didn’t break anything.
In this build you’ll find the new stock dialog, the new menu, and some new rendering code. All are pretty significant either in terms of lines of code or because they modify parts of the program that have been static for years. I really want to get whatever feedback you can provide to make sure everything is correct.
Build 6713- Mandatory Upgrade!
Several people mentioned problems with 6701 toolpaths but Klaus was the first to send me an STL file that let me replicate the error. It was a bad bug where some triangles could be totally ignored when using a flat endmill. A new version is being uploaded now that has a fix and adds the slicing back in. Slicing is not totally done but it’s in the build already and I need to post it now to get rid of the bug above. Since it’s a public release you can get it at http://www.grzsoftware.com/v2dl.php .
Build 6699
Jeff D. was the first to point out a significant bug in the latest releases. It turns out that the finish path could gouge if the roughing tool was much bigger than the finishing tool. This was due to a bug in one of my optimizations and has been fixed in 6699 at http://www.grzsoftware.com/files/MeshCAM2-6699.exe . Build 6699 has a few other little fixes and tweaks in addition to the big bug above. I also added Lua scripting access to modify some of the internal machining parameters for the real tweakers out there. I’ll try to post a Lua script in the next few days that will describe the parameters and show how to modify them.
Test Release
I just posted a test release of the new version at www.grzsoftware.com/files/MeshCAM2-6512.exe . I’ve spent the last half a day in a hotel room finishing everything up to the point that I believe it works will and decided that I have several users who would probably like to participate in the test process. Please run it through the wringer and let me know what you think. Here are some important notes:
1) The oversampling value now has no effect on the parallel finishing. You control the accuracy with the tolerance parameter. I would start with something like .001″
2) For historic needs, a ZMap will still be created but will not be used. Luckily, the creation of the ZMap doesn’t take much time- the offset does and that will not be done.
3) There are probably quite a few lurking bugs so don’t start machining that rare African hardwood right away without testing it on a cheaper material or in CutViewer first.
Finally, I now have an Authenticode signature on the installer and the program. This should put an end to the Vista and XP SP2 warnings about all the terrible things that a program from an unknown author could do to your computer.
As always, let me know what you think.
Build 5694 Released
Build 5694 has been released to http://www.grzsoftware.com/v2dl.php . There are a number of fixes including many for the 4–axis jobs.
- Added option to change image file in image size dialog.
- Fixed Black is Z-/Black is Z+ option in image size dialog.
- Cannot execute a command if another is already running. (Jeff D.)
- Fixed bug where first move in a 4-axis program had a feedrate of 0.0.
- Each index of the 4th axis now generates a comment for those who’d like to search and replace to generate a machine pause instead of an ‘A’ move.
- No longer Work-in-Progress. Since V2 is never likely to be stamped “Done” I’m going to just go by build numbers.
- Fixed a big bug where the first index in a 4-axis program would be written after every rotation.
- Added 4th axis option to output each setup as a separate file.
- Added option to center geometry along axis-of-rotation for 4-axis jobs.
- New rendering code to draw a 4-axis job.
- Changes to the Retract Height command to make them logical for a 4-axis job.
- Fixed bug is “Draw Full Program Zero” option.
- Fixed “What are borders?” help link in 2-side stock dialog.
- Run Script command will now set the working directory to the script directory.
As always, let me know what you find.