Speed of balls depends on target FPS

Bug #407419 reported by Olof Bjarnason
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
fortressdefender
Undecided
Unassigned

Bug Description

The Ball implementation is not framerate independent; it is based on a discrete number of steps (fixed at 10 right now). That means that changing the target FPS constant in Constants.py will effectively change the speed of ball movement.

A better idea is if the balls move with a certain number of pixels per second. Then any target FPS could be set, even dynamically at boot time (eg. to target the same FPS as the current desktop resolution refresh, for smoothest possible experience).

Related branches

Olof Bjarnason (objarni)
description: updated
Olof Bjarnason (objarni)
Changed in fortressdefender:
status: New → Fix Committed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Related blueprints