Velocities do not 'tick' correctly

[knowknowledge]

All velocities should move sprites based on the time since the last 'tick' in a way that creates the same illusion of speed regardless of the framerate.

Currently, slower framerates cause movement to be much slower than normal. This means that ships turn jerkily and weapons do not fire as far on slower systems.

While we should try to avoid low framerates caused by slow algorithms, many systems will run at below maximum framerates. It is important to have the same gameplay regardless.

[chris]

Please see the 'Fixed Frame Pig' demo at http://olofson.net/mixed.html for a great example of how to do this.

Basically, the work should be done in the Timer class. The Timer class then has a function like GetDelta?() which is a multiplier to be used against all position updates. That way, if Timer::Pause() is called, GetDelta?() will return 0s to ensure that if the logic loop is run, we don't end up moving anything.

[chris]

Arke has indicated he's interested in working on this (and he'd do a good job) but he won't be able to meet the January deadline. We might want to do just a little work on this and push it to 0.3.0 for him.

[knowknowledge]

Chris started to implement a virtual framerate timer.

[knowknowledge]

Multiple draw steps per update step causes the Engine Animation to flicker.

The current engine draw logic 'turns itself off' after every draw, but turns on only when it is updated.