[http://sourceforge.net/p/ufoai/bugs/3292 Item 3292] imported from sourceforge.net tracker on 2013-01-28 20:05:19

[quote]
one of my stilettos is for some reason showing what looks like a shiva's firing radius ring, even though it's equipped with missiles. It fires the missiles, too, so it's not a case of having ran out of ammo. Savegame attached, the "faulty" stiletto is to be found in the american base.

removing and re-equipping the missile racks fixed the problem.
[/quote]

see http://ufoai.org/forum/index.php/topic,6704.0.html for more details
===== Comments Ported from Sourceforge =====

====== tlh2000 (2012-05-26 11:31:15) ======


====== geever (2012-07-15 13:52:04) ======

I started investigating this, I could add a workaround into the code but I would rather try to find out how/when the range-state broke. Could you help me with this? Can you reproduce the issue?

-geever
====== geever (2012-10-12 20:41:01.402000) ======

- **milestone**: 2.4 --> notReproducible

====== geever (2012-10-12 20:41:44.450000) ======

Any help on reproducing, other than using this corrupted savegame is welcomed.

-geever
====== darkrainx (2012-12-21 20:37:04.751000) ======

Recently I suffered this bug, and managed to reproduce it later, what happened was that I forgot to buy more sparrowhawks and thus the racks of my stiletto were empty, then I got a new laser canon from the workshop and replaced the shiva with it, next time I sent it to combat the it was showing what seems as the firing radius of the ALC

====== geever (2012-12-21 22:06:05.100000) ======

Thanks for the repro. Actually what you described is normal. The bug was that on assigning/reloading ammo, weapon range attribute of the aircraft was not updated so it remaint laser range after you fed sparrowhawk launchers with rockets. This should be fixed by now. Please recheck.

-geever
====== geever (2012-12-21 22:07:31.345000) ======

- **status**: open --> closed

====== darkrainx (2012-12-22 01:53:56.266000) ======

Yeah, I forgot to mention that the shorter radius persisted after reloading the launchers, anyway, tested it again and its indeed fixed.