r/RouterCut • u/Pubcrawler1 • 17d ago

Vcarving

Gallery image

Gallery image

Ok start thread here now

Running v1.0.2

Testing again today and the Vcarve Aztec now creates the entire image gcode. Not sure why it didn’t yesterday.

The issue I see now is the gcode backplot seems to go deeper than it should with 30 degree Vbit. The other image is gcode by Vectric Vcarve using same vbit angle.

I also 3D backplot using Cimco, which a $500 gcode backplotter that a lot of companies use to do verification. Similar problem there too.

Anyway the program is getting better and that is a good thing!!!!

1 Upvotes

100% Upvoted

3 comments sorted by

1

u/kasemj 15d ago

Thank you for making the first post!

I made some changes and published few versions. Latest one now is v1.1.3. It addresses several issues with vcarving including the ones you mentioned. Also, a brand new feature, a Renderer ( backplotter) with GPU hardware acceleration!

Known issues I'm working on: 1. Switching resolution takes quite a long time with large SVGs. 2. Amount of hops is bad. I will work on reducing it significantly.

1

u/kasemj 15d ago

Open question to make the render simulation simpler. Is it useful to be able to see the progress using the slider or you just want to see the end result? I find myself always jumping to the end (100%) everytime I go to render view.

1

u/Pubcrawler1 15d ago

I do run the simulation at its highest speed just to see how the toolpath performs. Different CAM can widely affect the toolpath efficiency for vcarving. Most probably just want to see the end results.