On windows 98, Thread.sleep() is poorly accurate (minimum sleep is 50 ms, so Thread.sleep(1, 2, 3...) == Thread.sleep(50) ). The timer gets better on later versions of windows, but still under what we expect off of Linux Solaris, and macs.

http://www.mactech.com/articles/mactech/Vol.14/14.05/WritingJavaCross-Platform/
This links to an article with some help with threads based on the mac. Evidently the biggest thing that is handled differently on the mac is how the threads operate... So I went to work and redid a bunch of the Java2D code, and now with Thread.yield() I can get up to 500FPS, but an average of about 150... not too bad! Now, all I have to do is see if it works on windows better then the last build...

Anyway, screenshots!!




The First one is with 'Smart Render Mode', Second one without it, and the third one is what happens when the FPS is too low.

The reason there is a black bar on the bottom of the first one, is so that when the game isn't refreshing, the FPS and the Load still are. So in order to keep from having to triple buffer, I just blacked out that section... why not? it is only for debugging right?

I'm heading back into VPC to recompile with JSmooth... new demo should be up soon.

Operating System  	       System Clock
Windows 95, 98 	                55 ms
Windows NT, Uniprocessor HAL 	10 ms
Windows NT, Multiprocessor HAL 	15 ms
Windows NT 4.0 Alpha 	        7.5 ms