Has anyone had luck using Vericut for simulation of very detailed toolpaths? The toolpaths that I'm working on right now have a lot of small move and Vericut is very slow in processing them.
I think it has to do with the way that Vericut runs the simulation. It appears as if the block processing rate is constant. A block with a long distance move takes the same amount as a block with a short distance move.
Is there any way to change it so that vericut processes the g-code the same way the CNC machine would?
I think it has to do with the way that Vericut runs the simulation. It appears as if the block processing rate is constant. A block with a long distance move takes the same amount as a block with a short distance move.
Is there any way to change it so that vericut processes the g-code the same way the CNC machine would?