I talked about it on my gruedorf blog, but I post it here for help.
It's almost copy/paste, cause well, me lazy ;)

I have a problem that is with me from the beginning with Verge. Everytime I’m in some kind of loop, like, let’s say, inside a menu or in my battle system, Verge3 uses 100% of my CPU. I have no idea how to make it work less aggressive.
In the loop I am making sure it does things once per 1/100s only, but if 1/100 has not passed yet, it just runs in the loop until it has. :/
I guess I could put everything in a HookTimer function instead of a simple while() loop, but then I heard that if HookTimer takes more than 1/100s to process, it could get ugly.
So how does people do it? Is HookTimer the way to go?

Looks good, thanks :) ! That function seems to miss from the V3 Documentation hehehe.
So would the function inside HookRender() be called everytime I call Render()? If there is a Render() inside the function that gets HookRendered, will that make an infinite loop? :/

Oh hehe :P
Thanks, that should do the trick. I'll try it as soon as I can and I'll let you know how it goes :)

Render calls anything hookretraced. So if you call render inside a hookretrace, you get a suddenly infinite number of calls. But there is a way around that.

Something like this:


int renderstopper;

void HookFunc()
{
if(renderstopper == 0)
{
renderstopper = 1;
// code stuffs go here
render();
// and probably here too
renderstopper = 0;
}
}


This might seem useless, or possibly a sign of poor design, but it is occasionally quite handy. Like if you need the engine to render the map several different ways before one showpage. Or if your code gets... complicated, and you want it to be safer or something, I guess.