LÖVE

aidenn wrote:Any way to do clean and healthy frame-Hz relationship with LÖVE?

That's exactly what vsync does. The 1 frame off that you sometimes notice is at best a display error and at worst completely irrelevant.

Well, it's not completely irrelevant. I do agree it's a minor thing and doesn't influence the game's logic, but it's still bugging me. Ah well, no point in worrying about it now.

I think you are going on about this the wrong way. Instead of messing and trying to limit the FPS, why not just make a collision system that works on low FPS as well as high FPS?

That's a good point, but I'm still learning that bit. Could you point me to an easy-to-understand FPS-independent implementation overview? I'm doing standard box collisions. So far I can't get rid of a slight 1-frame jerk as soon as the player hits the ground after jumping (which isn't present with really high FPS).

aidenn wrote:That's a good point, but I'm still learning that bit. Could you point me to an easy-to-understand FPS-independent implementation overview? I'm doing standard box collisions. So far I can't get rid of a slight 1-frame jerk as soon as the player hits the ground after jumping (which isn't present with really high FPS).

This is becoming increasingly unrelated to FPS and more about collisions, perhaps you would benefit from a separate thread featuring your code and what problems you're experiencing.

Good point. I'll leave the question hanging though, because I'd like to limit the FPS anyway for cases when one does not want to use vsync but still wants to keep CPU usage as low as possible.

aidenn wrote:Good point. I'll leave the question hanging though, because I'd like to limit the FPS anyway for cases when one does not want to use vsync but still wants to keep CPU usage as low as possible.

I have never seen a game with this feature though. If one really would want to limit a programs resources this can be done outside of the program.

Many games have FPS limiters, most of them are 3D though.