Back to General and Gameplay Programming

Game Loop timings coming up slow?

Scott Richard Howell · 2012-08-23T21:29:20

I'm giving android development a go, just for the sake of trying it, but I'm getting a slow game loop. Target FPS is 60 but I'm getting results returned 24 - 26 FPS instead, I've probably made a stupid mistake in measuring the time or something, but for the life of me I can't find the problem. I've gone with an un-throttled Update and a throttled draw, most examples I saw used Thread.Sleep , but I've always been told its an unhealthy practice, so I've steered clear. Here is the game loop. Update and Draw are currently empty. @Override public void run() { Canvas canvas = null; long updateCount = 0L; long updateTime = 0L; long tickCount = 0L; long tickTime = 0L; long tickLoopStart = 0L; long updateLoopStart = 0L; long elapsedNanoseconds = 0L; double timeDelta = 0; while (running) { canvas = null; tickCount++; tickLoopStart = System.nanoTime(); try { canvas = surfaceHolder.lockCanvas(); updateLoopStart = System.nanoTime(); elapsedNanoseconds = System.nanoTime() - tickLoopStart; while (elapsedNanoseconds < NANOSECONDS_PER_DRAW) { updateCount++; Update(timeDelta); timeDelta = (System.nanoTime() - updateLoopStart) / 1000000000; updateLoopStart = System.nanoTime(); elapsedNanoseconds = System.nanoTime() - tickLoopStart; } updateTime += System.nanoTime() - tickLoopStart; updateLoopStart = System.nanoTime(); Draw(canvas); } finally { if (canvas != null) { surfaceHolder.unlockCanvasAndPost(canvas); } } elapsedNanoseconds = System.nanoTime() - tickLoopStart; tickTime += elapsedNanoseconds; timeDelta = (System.nanoTime() - updateLoopStart) / 1000000000; } Log.d(TAG, "Game loop has run " + tickCount + " times. Averaging " + (tickTime / tickCount) + "ns per loop. with a target of " + NANOSECONDS_PER_DRAW + "ns."); Log.d(TAG, "Update has run " + updateCount + " times. Averaging " + (updateTime / updateCount) + "ns per loop. taking up a total of " + updateTime + "ns."); Log.d(TAG, "Draw has run " + tickCount + " times. Averaging " + ((tickTime - updateTime) / tickCount) + "ns per loop. taking up a total of " + (tickTime - updateTime) + "ns."); } Any and all help is greatly appreciated, Thanks in advanced, Bombshell

General and Gameplay Programming Programming

Started by Bombshell93 August 22, 2012 06:57 PM

9 comments, last by SimonForsman 11 years, 8 months ago

SimonForsman

7,644

August 23, 2012 09:29 PM

would it really oversleep by a rather consistent 66ms?
5 I could deal with 10 I could deal with 15 - 20 is the expected, but over 60 ms?
with 30FPS needing 33ms loops 60ms is a dramatic frame drop.

how much difference would using a simple while(under ideal frame length) loop make?
and would it be plausible to use the while loop as I build the game up on windows and then swap to sleep in later development where I may test it on an android device?

With the emulator nothing is strange, yes you can leave out the sleeping for now if it causes problems with the emulator (its only purpose is to avoid draining the battery afterall),

a simple while loop should make things more stable with the emulator, it might still be hard to hit 60fps in the emulator though (atleast once your app starts doing things), The emulator is very slow (+ you're most likely running the emulator with a debugger attached which slows it down even more)

[size="1"]I don't suffer from insanity, I'm enjoying every minute of it.
The voices in my head may not be real, but they have some good ideas!

Game Loop timings coming up slow?

This topic is closed to new replies.

Popular Topics

Recommended Tutorials

Game Loop timings coming up slow?

This topic is closed to new replies.

Popular Topics

Recommended Tutorials

Reticulating splines