I just upgrade to Pro 8 , having fun and see a big difference and swapped out the compact for the Makita.
But a funny thing with a file I started in V7 CC free, and in the Pro a BIG jump in cut v carve time but I think it might be the file.
Wondering if anyone has seen this.
I found this Oreo cookie file a few weeks back and in Carbide Create Free V7 set up a (leftover) 3/4" walnut blank about 14 x 9 for the top and bottom. (video on YT w/ a file)
In V7 I had the top and bottom set to v carve side by side and the carve was maybe 20 minutes.
I opened up the same file in CC Pro 8 and its giving me a cut time of 162 minutes hu wa??!!
The default feed rate is higher than the previous version, and still the long cut time. I checked and double checked feeds and speeds.
Also no more cut to bottom of stock and the v carve depth doesn’t update to reflect the project settings.
Wish I hadn’t uninstalled V7 regular to make sure I’m not crazy, archived version available?
Why I think its the file…
I imported into CC I get the error message. SOP I go to 3D Max and the svg is on multi layers so I selected all verts and put them on zero, re imported and no errors.
Strange because the cut time went from 190 minutes to the 162.
I checked other v carve cut times on some signs and other items and it all looks kosher so that’s why I think its the file.
In this case the info provided is fine. I took the last image, oreo.svg & imported it into V7 & created a Vcarve path, saved it, opened in v8. Times are definitely longer.
It looks like V8 has a lot more green / cut feedrate motion, where V7 has more rapid motion.???
Meaning travel time is longer than cut time? The feed rate is 100 in V8, but 35 in V7 , color me confused but Im sure the answer is starting me in the face.
Im fiddling with the numbers and the V8 file isnt below 150 minutes , what did you change?
Thanks for taking the time. Thanks William for the link I couldn’t find it.
Here’s some files!
I have 21 minutes in V7, just hit vcarve and go default settings.
23 minutes for the bad file I needed to fix so that was a file issue from the go.