[http://sourceforge.net/p/ufoai/patches/676 Item 676] imported from sourceforge.net tracker on 2013-01-28 20:46:59

Intended to address feature request 2350462.
This patch modifies distance and velocity calculations for UFO/aircraft movement on the geoscape to use a dynamically changing velocity.
Damaged/unarmed UFO's should move away from interceptors at higher speed; interceptors should approach their assigned target with increased speed.
===== Comments Ported from Sourceforge =====

====== tlh2000 (2012-06-19 09:40:26) ======

any progress on the reformat?
====== faichele (2012-06-23 12:03:32) ======

Dynamic velocity patch part 1 (cleanly formatted this time)
====== faichele (2012-06-23 12:04:17) ======

Dynamic velocity patch part 2 (cleanly formatted this time)
====== tlh2000 (2012-07-01 21:04:26) ======

can you describe the state of this patch a little bit in the comments please. what is working? where are problems left? and so on.
====== tlh2000 (2012-07-02 16:59:21) ======

there are a lot of magic numbers in this patch -can you maybe extract them to constants?

please also note that the style does not match our coding guidelines. it's ok for me to reformat it before we apply it, but it would be of course easier if i would not have to do that ;)
====== faichele (2012-07-07 12:00:58) ======

Concerning "magic numbers": I suppose you're referring to the velocity calculations in the "fight or flight" logic for interceptors and their targets? I can replace the values with one or several constants, of course; but the logic for the behaviour of aircraft can certainly use some more work.

Concerning open issues:
- Modify fuel consumption calculation: I've chosen a simple approach where the fuel consumption is increased based on the ratio between the default (preferred) speed as given by the aircraft's stats and the actual speed (rounded to the nearest integer).
- Course plotting for intercepting aircraft: There's a slight "jitter" in the movement of aircraft that are acting as interceptors; the effect is hardly visible on geoscape level, and I haven't found the actual cause yet.
====== geever (2013-01-26 15:41:09.954000) ======


====== geever (2013-01-26 15:41:10.414000) ======

Any progress on this?