Tempest Planning - Preliminary information and testing

REally, 2 axis is good and 3rd axis is rough? Or do you mean your using x,y an dA for example?
Its true that using rotart is not perfect as yet in tempest, Ive focused primarily on cartesian...
but using x,y and Z should be fine?

Art,
I went back to the machine to look at what was going on with the tool paths I was testing on my machine and realized the issue might have been short segment code vs longer segment code, so I squashed my drawing and made a flat short segment code of the same surface. I set the jerk to 10000 and the bend to 50 units. I set the feed rate at 4000 mm/min the flat program ran at about 2000 mm/ min and the 3d at about 300 mm / min. I guess the issue was more the speed of the cut possible with smooth motion, hence my thought about applying the algorithm to the two flat axies and proportionally pulsing the third as it usually moves at lower rates relative to the other two. I am running a smooth stepper to alleviate my difficulties with windows interrupts. so I would think that calculation speed shouldn't be a problem, I haven't built my 4th axis on this machine yet, so my comment on that was just assuming that if the 3 axis motion was a lot slower, than 4 would add to the problem.