Smooothness

[SMcNeill]

`_Limit 60` will give you the smoothest, though you can't get it perfect. The gist of the problem is that the QB64 window is rendered at 60 FPS, and every time you call `_Display` you're queuing another frame to be displayed in the window. If you queue too many frames then some of them have to be dropped and the pixels will skip a spot. If you queue them too slowly then at some point QB64 will have to display the same frame twice and they'll appear to get stuck.

Thanks, @DSMan195276. That makes sense. So one should use trial and error to find the FPS sweet spot for a given graphic function? Or just go with _limit 60 and call it a day, given that it'll never be perfect? Thnx.

Fancy mod, Bplus! 

I'd think perfect factors of 60 would work just as well.

For example, with a _LIMIT 30, each frame should stay up for 2 complete tics of the display, without having them suffer from that stray being left over.

Same with _LIMIT 120.  Each frame would be up for 1/2 tic of a display, so you'd basically always have the 2nd frame overwrite the 1st, but it'd be a consistent change, making it seem like the ball is just dropping 2 pixels per frame instead of 1.  It'd still be smooth, without that odd frame out which would either lag up or jerk ahead to catch up.