Elysian Shadows

dandymcgee wrote:http://lazyfoo.net/SDL_tutorials/lesson14/index.php

superLED wrote: "Fuck your expensive hardware, I'll cap the game at 60 fps"

superLED wrote:Instead of capping it at 20 like in this tutorial, I would go for 60.

But if you want a frame independent system, which moves an object X pixels in Y seconds/milliseconds, go ahead and read this one: http://lazyfoo.net/SDL_tutorials/lesson32/index.php
That way, you can still play the game at 200 fps and 10 fps, and get the same timing.
Using this method, you won't say to a person with hardcore computer specs "Fuck your expensive hardware, I'll cap the game at 60 fps"

dandymcgee wrote:

superLED wrote:Instead of capping it at 20 like in this tutorial, I would go for 60.

But if you want a frame independent system, which moves an object X pixels in Y seconds/milliseconds, go ahead and read this one: http://lazyfoo.net/SDL_tutorials/lesson32/index.php
That way, you can still play the game at 200 fps and 10 fps, and get the same timing.
Using this method, you won't say to a person with hardcore computer specs "Fuck your expensive hardware, I'll cap the game at 60 fps"

Completely agree with this. I had forgotten lazyfoo has tutorials for both methods. This is definitely better than a simple framerate cap for anything you plan on distributing as a serious product.

Benjamin100 wrote:OK. Thanks.

OK. Now when I go from Triangle to Rectangle, things aren't working so well.

Code: Select all

 glBegin(GL_QUADS);
	   glColor3f(0.0, 0.0, 1.0);
	      glVertex3f(0.1, 0.5, 0.0);
		  glVertex3f(0.1, 0.1, 0.0);
		  glVertex3f(0.3, 0.5, 0.0);
		  glVertex3f(0.3, 0.1, 0.0);
    glEnd();

This seems to produce 5 vertices.
Any reason you would think for why that would happen?

-Benjamin

	glVertex3f(0.1, 0.5, 0.0);
	glVertex3f(0.5, 0.5, 0.0);
	glVertex3f(0.5, 0.1, 0.0);
	glVertex3f(0.1, 0.1, 0.0);

Ginto8 wrote:

dandymcgee wrote:

superLED wrote:Instead of capping it at 20 like in this tutorial, I would go for 60.

But if you want a frame independent system, which moves an object X pixels in Y seconds/milliseconds, go ahead and read this one: http://lazyfoo.net/SDL_tutorials/lesson32/index.php
That way, you can still play the game at 200 fps and 10 fps, and get the same timing.
Using this method, you won't say to a person with hardcore computer specs "Fuck your expensive hardware, I'll cap the game at 60 fps"

Completely agree with this. I had forgotten lazyfoo has tutorials for both methods. This is definitely better than a simple framerate cap for anything you plan on distributing as a serious product.

I think that this is actually a bad idea, at least as lazyfoo does it. It may not be an issue for a very small game, but if there are any lag spikes, your logic is very likely to be messed up (read: possibly very large location jumps). I would recommend that you take this sort of method, but add lag protection: for example, you could limit the amount of time each logic loop can process. If you want your game to respond in a timely manner without major lag jumps, you could ensure that at least 20 iterations of the game logic occur each second by processing <=1/20 of a second each frame. It has the best of both worlds: the game responds consistently even during lag spikes, and it can still take advantage of faster hardware.