The mill seemed to handle the arcs much better than the linear paths. I ran my first real toolpath today using the code and it seemed to run really well. My new code is taking the output from that code and trying several optimizations on the toolpath to make it as smooth as possible.
I would call my first release of the code a “one-pass” arc fitter. I got feedback from a number of users who demonstrated cases where my code failed to produce good results. It’s been quiet here for a little while but work has quietly been progressing on the arc fitting code.
#Cutviewer mill change stock dimensions 64 Bit#
That being said, I’ve put a lot of work over the years in my “warnings are errors” policy and I’m not eager to relax that now even for 64 bit builds. Many of the warnings you get when you move to 64 bit are warnings that will never cause any trouble in MeshCAM. Part of the problem is that I build all of my release code with Visual Studio set to treat warnings as errors.
#Cutviewer mill change stock dimensions how to#
Hours and hours of little changes, finding out how to rebuild all of my 3rd party libraries as 64 bit, and removing old code that I didn’t need anymore and I can start to see the light at the end of the tunnel. Since I had been planning to add a 64 bit version in the future I figured I’d just try to compile it as 64 bit to see what happened. Most of the time this is a problem with the settings they’ve chosen but there are a few people who are looking to do really big work with MeshCAM. I’ve been getting more and more people who are running against the 2GB memory limit imposed on 32bit Windows programs. The bug reports have been slowing down so I think the trend is heading in the right direction. The latest updates have been mainly been bug fixes as I try to “complete” V4 so I can take a break and then start V5.
0 kommentar(er)
