Can someone help me out with carbide create. I’m trying to do a simple v carve into a simple CC font. One word is taking 5 min and the another word estimated at 4 hours. Something is definitely wrong.
4 hours really looks like some weird bug
are you using the (beta) “advanced vcarve” ?
One thing to try is to break the word into pieces (easiest way to do that is to draw a circle somewhere else and ‘subtract’ that circle from the text, that will make the text shapes instead of text, and then you can select the pieces one by one) and see if there’s gain in doing one letter at a time
also generally, vcarve time is often dominated by “retract height” (this is set in the overall settings for the work in the “sprocket” menu)… for reasonably flat stock this shouldn’t be more than 0.08" or so
3 Likes
Vcarve paths are notorious for having ridiculous cut time estimations that dont really reflect the actual cut time. Have you tried sending to Carbide Motion and seeing what the est cut time shows? I know there have been times I loaded up a vcarve path that CC claimed to be 3+ hours that CM est at around 2 hours and only really took about 1.5 hrs to cut.
2 Likes
I’ve had that happen a few times, I think what I did is save everything and exit out of Carbide Create and then start up Carbide Motion, load the file and it recalculated the run times when I went to the Tool Path tab.
This was on some 4.x version, not too old, from December or January.
I was having this happen to me regularly and noticed that it was making several passes without taking out any wood. Even on simple projects I would have to stop it mid-way once I realized it wasn’t doing anything else. If you want to save some time Vectric Vcarve will save a lot of time. I switched that and my project that was estimating 3 hours but would actually take 90 once I stopped it manually, now only take 35 minutes total. It is just a lot more efficient at choosing the paths and not retracting up and down so often.
Carbide Create has indeed a behavior where it will do multiple passes based on max DOC of the V bit and the deepest (widest) part of the cut… but it then does these number of passes for equally for your whole selection.
The workaround is to split your selection into pieces, so that small parts don’t get all the passes of the biggest part
2 Likes
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.