I have a carbide create file which is a batch of ~15 repeat units.
It is undertaking alot of unnecessary motions around the features of all the units, doing a couple of features in the first and then moving onto another and doing another bunch of random features on that before moving to the next - rather than just finishing all the features of one of the units for that tool first and then moving on.
for context, the advanced v-carve toolpaths were created on 1 unit first, and then that one unit was array replicated to add the other 14 repeat units where it automatically adds their toolpaths based on the first units
The only real control you have over the toolpaths is the order that you put them in. To have it complete one item and then move to the next, you would need to create separate toolpaths for each item, then put them in the order you want them run.
CC has had bad toolpath routing for quite some time - they know about it, but have yet to come up with something better.
People would point out that this problem (the ‘Travelling Salesman Problem’) is inherently hard, and that getting an optimal answer can take a very long time to compute. While true, it’s not actually really relevant, since the goal here is good routing, not optimal routing.
From what I can infer just watching the order that the operations are performed, it appears the problem to fixing this is more about the structure of the current code than the difficulty of the problem.