Back
General
Ask your question
Why is the software so slow: laggy preview, endless toolpath calculation, sluggish drawing?
Updated Oct 13, 20262 min readVCarve Pro & Aspire
Why this happens
- Modeling resolution × job size: a huge job at Highest resolution creates an enormous component grid; every model edit and 3D toolpath recalculates against it. The Job Setup page lists Standard, High (3x slower) and Highest (7x slower).
- Tiny tool + tight tolerance 3D toolpaths: a 1/16" ballnose at 8% stepover over a big relief is simply millions of moves, so long calculation is expected, not broken.
- Graphics: old GPU drivers or software rendering (VMs always software-render) make the 3D view itself laggy.
- Huge imported STLs: million-triangle meshes take RAM and time to convert.
The fix
- Match resolution to the job. Don't default to Highest. A 12×12" 3D job at High is usually plenty; reserve Highest for jobs that truly need it, such as very large parts with small details.
- Model detail separately: build detailed components in their own small job, export, and import into the production layout as clipart, so the big file stays light.
- Update GPU drivers.
- Hardware that matters: RAM first (16GB+, 32GB for heavy 3D work), then SSD, then CPU single-core speed. Toolpath calc is CPU-bound; the 3D view is GPU-bound.
Pro tips
- Simulation quality in Preview also has a big speed cost. Drop it while iterating, raise it for the final check.
- If one specific file is slow but others are fine, hunt for an accidentally imported monster STL or a component far larger than the visible design.
Sources and further reading
Forum thread 37447the software maker's forum (opens in a new tab)Job Setup - Single Sidedthe software maker's documentation (opens in a new tab)Forum thread 19997the software maker's forum (opens in a new tab)Forum thread 6155the 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.