Well, the stuttering in cas, delventhal and gafferongames was big like 5-10px which means that the framerate dropped dramatically (high frametime) so something processor-heavy must have happened - just like if GC has kicked in or something. What's strange to me about this problem is that it seems too fundamental and well-known a problem for us to have gone this long without having had someone pop in and say, 'Oh, we dealt with this ages ago, everyone knows how to deal with that! Here's your solution!' Are we overlooking something completely ordinary here.? Is it really just that Game Maker involves more 'native' code (am I expressing that accurately?) than Java, as I think someone mentioned earlier in this thread? Does Java do too much under the hood, as a TA at my university (I think) once told me? Does C++, Flash or Python fare any better? If we really have ruled out all those possible causes we've encountered so far, then I don't know what the problem could be. Well, I can think of a few more things we could try, but. I haven't really observed how computers react to Slick2D games, though. Yup! Thing is, Slick2D seems, by default, to draw very fast, so I don't know why I'd have problems with doing the same in LWJGL.

Athlon X2 2.9GHz + GF 9600.Īnd, of course not using 'sleep' causes stress on the CPU because it just computes and draws and stuff all the time. Well I have a (somehwat) fast computer and vsync has worked always AFAIK.

Java 60 fps