Omg nice GUI .. Not
- Thread starter archerRin
- Start date
To wait x seconds you enter the number of frames you'd like to wait (as you already are).
20 frames is supposed to = 1 second (pressing f1 should give you a bit of extra info on topics you have open). Though I find you usually need to try a few different wait times to get exactly what you're looking for.
20 frames is supposed to = 1 second (pressing f1 should give you a bit of extra info on topics you have open). Though I find you usually need to try a few different wait times to get exactly what you're looking for.
Yeah Clockwise is right, on average, 20frames = 1 second, however, some computers will be slightly faster, some will be slightly slower, so some may only wait 3-4 seconds, while others have to wait 6-7 seconds.
Try working like this and see if it gives you the appropriate time gap.
Try working like this and see if it gives you the appropriate time gap.
Did you guys see the SS? I want the Frames to be random from 20 to 100 :X
When you say X amount, it does not really mean a fixed number... it's a variable >_>
Also wow.. that's interesting how it's random by default , lol. I am depending on them for my encounter system, in which you swing a weapon at monsters. And the Waits actually control the cooldown of your weapon. That's so funky if it's like random. jeez.
When you say X amount, it does not really mean a fixed number... it's a variable >_>
Also wow.. that's interesting how it's random by default , lol. I am depending on them for my encounter system, in which you swing a weapon at monsters. And the Waits actually control the cooldown of your weapon. That's so funky if it's like random. jeez.
Brewmeister
Sponsor
It's not "random", it's just not a perfect constant. You can get much closer to 'actual time' by dividing the current # of frames by the current frame rate. (@total_sec = Graphics.frame_count / Graphics.frame_rate). The Window_PlayTime class uses this to display the play time in seconds.
That being said, everything is relative. (if your wait time is slightly off, so is everything else (by the same amount))
Jbrist example suggests that there is a +-40% variance. I think this is highly unlikely unless you are running on a very old computer with a very slow processor, or you have drastically over-clocked your processor.
To use a script command to set a wait, just set
@wait_count = x
in this case, x will be at 40 frames / second
That being said, everything is relative. (if your wait time is slightly off, so is everything else (by the same amount))
Jbrist example suggests that there is a +-40% variance. I think this is highly unlikely unless you are running on a very old computer with a very slow processor, or you have drastically over-clocked your processor.
To use a script command to set a wait, just set
@wait_count = x
in this case, x will be at 40 frames / second