What are the most common VCarve Pro & Aspire beginner mistakes and how do I avoid them?
Updated Oct 13, 20263 min readVCarve Pro & Aspire
Compiled from years of user forum questions. These are the issues that cause the most confusion and wasted material. For the Z-zero and XY mismatch cases in detail, see the entries on cutting air or plunging into the spoilboard and on cutting in the wrong place.
Z-Zero Mismatch (Most Dangerous)
Mistake: Z Zero set to Material Surface in the software, but the machine zeroed to the spoilboard (or vice versa).
Result: Every cut is off by exactly one material thickness. Too deep in one direction of the mismatch, cutting air in the other.
Fix: Always verify the software's Z Zero setting matches the machine zeroing method. Pick one method and never deviate.
"No Toolpath Generated"
Common causes:
- Open vectors for pocket or V-carve (must be closed)
- Overlapping vectors (run the Vector Validator, fix with Weld)
- Tool too large to fit inside the boundary
- Start depth greater than material thickness
- Cut depth = 0
Fix sequence: Check for open vectors, run the Vector Validator, check tool size vs pocket, verify depths.
Profile Cut Not Going Through Material
Cause: Cut depth exactly equals material thickness but the material is slightly thicker.
Fix: Type z+0.05= in the Cut Depth box (the = key evaluates the calculation, and Z means the material thickness). Always use tabs to hold pieces.
Resolution Too Low for Detail
Mistake: Job size set to the full machine bed (for example 4' x 8') for a 6" x 12" part.
Result: The 3D model resolution is spread over 4,608 square inches, which is very coarse for a 72 square inch part.
Fix: Set the job size to match the actual part size.
V-Carve Looks Wrong
Most common causes:
- Vector has self-intersections: run the Vector Validator
- Script font has overlapping outlines: Weld text vectors before V-carving
- Start depth set incorrectly
- Vectors too small for the V-bit angle
Toolpath Preview Looks Wrong But Cut Is Fine
Cause: Low preview quality setting. The simulation resolution is lower than the actual toolpath.
Fix: Raise Toolpaths > Preview Simulation Quality (Maximum is the best and slowest).
Saved G-Code Does Not Run Correctly
Common causes:
- Wrong post-processor (machine controller mismatch)
- Units mismatch: the post-processor must match the units your controller runs in. If the machine moves 25.4 mm when commanded 1", the post-processor is outputting the wrong units.
- ATC post-processor selected for a non-ATC machine
Fix: Verify the post-processor name matches your controller. Run a simple air-cut test first.
Tabs Not Holding Parts During Cutout
Fix: In the Profile toolpath Tabs form, use Avoid corners and curved regions to place tabs on flat sections. Use 3D tabs for thin material prone to lifting.
Model Disappears or Looks Flat After STL Import
Cause: The model was compressed to fit the material thickness during import.
Fix: Adjust Gap Above Model in Material Setup, or use Scale Model Height.
Sources and further reading
Toolpathsthe software maker's documentation (opens in a new tab)Calculation Edit Boxesthe software maker's documentation (opens in a new tab)Material Setupthe software maker's documentation (opens in a new tab)Forum thread 28the software maker's forum (opens in a new tab)Still stuck? Ask the community
Ask in your own words. Vector answers first, from the guides. If that does not cover it, post it to members and the shop from there.