I belive I know what the problems is and I belive it is a problem in Aspire.
David,
This is NOT a problem with Aspire or VCarve Pro. The V-carve toolpath needs well defined closed vector shapes and when it is given poorly defined or overlapping shapes, it does the best it can to figure out what is what. Only the user can give it the shapes it needs to obtain the results they want.
As for your file, the shapes overlap and this is causing the issue. One trick in this situation is to select every other shape and calculate the toolpath, then select the remaining shapes and calculate it again. Since the toolpaths use the same bit, they can be saved to one cut file so at your machine the fact that you have multiple toolpaths becomes invisible. See attached file.
You should also do the free upgrade to version 6.504 - use Edit>Check for Upgrades and follow the prompts.
As for Wolffie's file, there are multiple issues.
First, I believe the feed rate to be too aggressive, but will leave that to the others that own that model machine.
Second, the vectors are poorly designed to do v-carving and would be better off using a Profile-On toolpath with a v-bit with the exception of the outer donut shape.
Third, the toolpath option to 'Project toolpath onto 3D model' is selected but there is no 3D model present. This option should never be selected unless you are really projecting onto a 3D surface as it can cause unpredictable results.
This is just after a quick scan of the file. I believe the machine issues need to be resolved first using simple designs, then more complex (and better laid out) designs can be tested. If you aren't getting the same results as shown in the preview, the issue has to be the post processor, machine, machine's control system or project setup on the machine.
Tim
