Wait(40);

Started by TheJBurger, Mon 30/08/2004 20:25:59

Previous topic - Next topic

TheJBurger

Hi, I just had a question here out of my curiousity.

Why is Wait(40); equal to 1 second?
Why wasn't it Wait(50); or Wait(100); that was 1 second?

Is it because that was just the way the engine was made or is there some other reason?

I'm not suggesting that it should be changed or anything, it's fine the way it is right now, but I was just wondering why it was like that.

rtf

I think that "40" is the number of game cycles.  40 game cycles = 1 second.
I fail at art.

Ashen

That's only by default though, isn't it? I mean if you change the game speed, you change the number of game loops per second (higher speeds = more loops).

As to why 40 was chosen as default - I think it was just the best frame rate for low-end machines, as higher speeds take more memory and so mightn't be playable, and lower speeds may look kind of choppy (according to the SetGameSpeed entry in the manual, anyway).
I know what you're thinking ... Don't think that.

Ishmael

This is all in the manual somewhere, too...

(See below :P)
I used to make games but then I took an IRC in the knee.

<Calin> Ishmael looks awesome all the time
\( Ö)/ ¬(Ö ) | Ja minähän en keskellä kirkasta päivää lähden minnekään juoksentelemaan ilman housuja.

Scorpiorus

Quote from: Ashen on Mon 30/08/2004 21:47:52
That's only by default though, isn't it? I mean if you change the game speed, you change the number of game loops per second (higher speeds = more loops).
Yeah, so if you want to wait a second a more reliable way would be:

Wait(GetGameSpeed());

SMF spam blocked by CleanTalk