Author Topic: getting current fps?  (Read 1373 times)

Is there a way to get the current running FPS, like what's displaying when you do metrics(fps);?

Is there a way to get the current running FPS, like what's displaying when you do metrics(fps);?

$fps::real ?

$fps::real ?
cool thanks, I didn't think to look in global variables.

There was a client side mod on RTB that told your fps, but when I compared it to the fps from metrics(fps); the one through the mod was reporting roughly 25% less. I would be interested to find our what method it uses

There was a client side mod on RTB that told your fps, but when I compared it to the fps from metrics(fps); the one through the mod was reporting roughly 25% less. I would be interested to find our what method it uses

There is $fps::real and $fps::virtual.

There is $fps::real and $fps::virtual.

what's the difference between them?

what's the difference between them?
one is around 25-35% less than the other.
I had 1000 fps according to $fps::virtual, and i had 613 fps according to $fps::real.

one is around 25-35% less than the other.
I had 1000 fps according to $fps::virtual, and i had 613 fps according to $fps::real.
So, what's the difference between the methods then

Times the game says it's ready to refresh per second versus times actually refreshed per second, perhaps?

Hasn't there been an addon to render your Virtual FPS and Real FPS on your HUD? If not, someone make this, please.

Hasn't there been an addon to render your Virtual FPS and Real FPS on your HUD? If not, someone make this, please.
render? do you mean having a GUI at the bottom right?

$fps::virtual is how many times per second actual visual calculations are done, $fps::real is the actual displayed framerate.
« Last Edit: October 24, 2012, 06:18:31 PM by Trinick »

What the hell do you mean by "the virtual frame system"? Schedules ("core code" too, really) and the actual "core code" are processed together in iterations of the same main loop.

What the hell do you mean by "the virtual frame system"? Schedules ("core code" too, really) and the actual "core code" are processed together in iterations of the same main loop.
Well, first, I updated my post. Second, that's not true. The render loop and the processing loop are two different loops.

Well, first, I updated my post. Second, that's not true. The render loop and the processing loop are two different loops.
guess what you have to do in order to render?

That's right, process. Contradiction found.