[1/5] [ALL VERSIONS OF MIRAGE] Better FPS Lock

[ark0n]

Step 1
Look for the current FPS Lock.
Step 2
  Remove the whole FPS Lock
Step 3
Add a timer to FrmMirage or FrmStable or whatever the place you have the PicScreen on.
and set its tickrate to 33ms. This will give it a 30 FPS Lock.
Step 4
Add the boolean canDraw as a Global Boolean
Step 5
In the tick section for that timer, have the code "canDraw = true"
Than after that, go to sub GameLoop

Step 6
As the first line add this code:
```
If Candraw = False Then
Exit Sub
else
Candraw = false
end if

```

That should be a much better FPS Lock :D
Credits:
Me: For making this tutorial
Homicidal Monkey: For teaching me how to do this.

[ark0n]

UPDATE: Forgot to say where the Current FPS Lock is, it is in sub GameLoop

[Joyce]

And what's the purpose of replacing a cap with a different cap? It's still capped. :huh:

[Robin]

The point is so that you're not running through the entire loop only to start sleeping it to keep the FPS low.

This tutorial is horrible though. It has absolutely no explanation and it's pretty much you just copying & pasting Fabio's code over.

[Joyce]

Are they still doing that in Mirage nowadays then? I thought they stopped using that horrid method ages ago.

[Robin]

@YamYam:

> Are they still doing that in Mirage nowadays then? I thought they stopped using that horrid method ages ago.

Mirage is dead. Active development and the community is, anyway.

The main sources now are my old Mirage Realms game which was released as open-source and Eclipse Origins.

[Joyce]

Wow.. I guess having a life does makes you miss things.

[Kimimaru]

@Robin:

> This tutorial is horrible though. It has absolutely no explanation and it's pretty much you just copying & pasting Fabio's code over.

You claim that the tutorial is horrible, but is his edit horrible? Should I consider implementing this edit into my game?

[ark0n]

Well, actually it's really good, i just got it from HM. And i wanted to teach you guys how to do it.

[Homicidal Monkey]

fixed it a little, you forgot to re-engage the lock.
Basically, it indirectly locks the fps by having a lock system based off of a timer, and pretty much guarantees that it will function at the desired framerate. You might want to set the timer to 33 instead of 66\. 1000ms (1 sec) / 30hz = 33ms.

[ark0n]

Thanks =D

[Homicidal Monkey]

yeah, i was trying to build a fps lock myself and after several tests, one similar to this design proved to be the most accurate.

[ark0n]

Cool, lol. This work for EO?

[Kimimaru]

I think I'll put this in my code, thanks! However, I'm still confused as to how it works. You said to make a timer and set its Interval to 66, meaning it will execute every 66 milliseconds. When it executes, according to your tutorial, it will set **CanDraw** to **True**. Then, in the main **GameLoop**, you have this code:

```
If CanDraw = False Then
    Exit Sub
Else
    CanDraw = False
End if

```
So basically, every 66 milliseconds, **Sub GameLoop** stops executing for another 66 milliseconds to stop processes from executing? Something similar to this is seen in the existing Eclipse Evolution system, where the program stops execution using the **Sleep** command for 1 millisecond. The loop continues until 31 milliseconds have passed by, effectively keeping the FPS down to about 31.

With this system, as Robin pointed out, instead of going through the entire **GameLoop Sub** simply to lock the FPS, it does it at the beginning of the Sub so that it has to search through less code.

Even with the inaccuracy of the Timer API Tool Function, this still works well? Anyway, please let me know if I'm correct on all of this. Thanks!

[Homicidal Monkey]

yeah, basically. Its also a more passive means of locking than the old fps lock. And you dont really need the timer to be accurate. If you get +- 5 ms accuracy, it really wont matter.

[Kimimaru]

@Zetta:

> yeah, basically. Its also a more passive means of locking than the old fps lock. And you dont really need the timer to be accurate. If you get +- 5 ms accuracy, it really wont matter.

Okay, I got it. Thanks a lot!

[damian666]

when ya say pu it on first line, you mean the first line of the sub, or the loop?

because that makes a difference ya know, a big difference actually xD

Damian666

[Joyce]

> Cool, lol. This work for EO?

I tried it following your very vague directions(Had to guess what you meant at times?) And it just froze the entire screen rendering it only once. And yes the timer was there. So I removed it and went on with doing other stuff. ;D

[ark0n]

Oh, lol. Okay, So it works for all mirage -EO.

[Joyce]

It should work really, but your explanations are rather vague so I probably ducked it up somewhere along the line

[Robin]

He can't explain it because he doesn't understand it.

It's not his code.

[DFA]

yes, lets re-invent the wheel, but this time, lets do it half-assed

[Kimimaru]

@Robin:

> He can't explain it because he doesn't understand it.
>
> It's not his code.

Maybe people looking at this topic can check out my explanation on my last post of the first page.

[Zytox]

Jusus crist! I mean, holy hell. I am currently in shock at how fluently my game is running by changing that fps lock. It's amazing, really. I'm using my own engine which is based of the early mirage stuff and in all this time of developing I've never noticed this small error, do I feel stupid xD

[Mikekan13]

using Eo and tried to do this. The directions like everyone said really are vague. The game just doesn't initialize at all. just sits at a black screen. If someone understands how to make this work please help.