I always thought vcarve did write the gcode till the end when you are actually saving as you can change your machine settings at the very end but I might be wrong. I usually use something like NC Viewer // GCode Viewer and Machine Simulator where you throw the code file in. Im sure its not that but its a good place to start.
Looking at your video I dont think 200IPM is too high I typically run my elite at 190 when I use a .25” end mill. Plus in your video you are doing an air carve which is much less stress on the machine so I doubt thats an issue. Have you tried another file with a larger shape to see if the issue persists? Would be able to tell if the size of the issue scales or not.
Otherwise Ill let others chime in with their ideas.
So I have solved my issues.
I did use the “fit curves” in node editing, I also changed direction to “climb instead of conventional”
The last thing I did was slow down my IPM to 100 instead of 200.
I then took a scrap piece of wood and tried my toolpaths.
Everything went as it should, no missed steps and no binding.
I really didn’t think it was something wrong with my machine.
I believe it was #2 on your list. Tight curves and heavy Node counts.
Thank you all for the help.
I always learn something with every job, Just hope I can remember it all