[http://sourceforge.net/p/ufoai/bugs/3464 Item 3464] imported from sourceforge.net tracker on 2013-01-28 20:10:24

2.4 bug 3292 still exists in 2.5, if a weapon is mounted on an aircraft at a moment when ammo is not available at that base, the firing radius ring will not be drawn in geoscape after ammo has been loaded and weapon fires normally.

Easily reproducible, just equip a missile rack/launcher on a new interceptor when you don't have any missiles.

http://ufoai.org/forum/index.php/topic,7475.0.html
===== Comments Ported from Sourceforge =====

====== geever (2013-01-14 21:04:21.588000) ======

Commit bcbdf5eca6a78d17163d1ace2cde1f16192f7cbd fixed it 24 days ago. And I cannot reproduce it with the current code.

If you have a broken save which still have the issue with a recent version, open the aircraft equipment window, remove then readd the ammo of the weapons.

Please report back if this solved the issue or serve with more details.
====== geever (2013-01-14 21:05:01.434000) ======

- **status**: open --> pending

====== geever (2013-01-14 21:05:35.219000) ======

- **assigned_to**: Tamás Fehérvári

====== jkkurja (2013-01-14 21:33:12.138000) ======

Correct, re-equipping the missiles helps.

I just tried jan 9th 2.5 version: start a new game to avoid any "bad save" issues, sell missiles in storage, buy a new interceptor, and equip missile rack - no firing range indicator ring (after re-purchasing missiles ofc). Missiles are fired normally in aerial combat. Savegame from this experiment attached.
====== geever (2013-01-14 23:50:27.729000) ======

Please retest with the latest and reopen THIS issue if still reproducible.

I think the bug I found cannot cause the effect you described as ammoLeft was either negative or zero or triggered range update, but my only other idea is that you somehow running an old version (like fetch wo merge), so let's give this a try.

====== geever (2013-01-14 23:50:51.483000) ======

- **status**: pending --> closed

====== jkkurja (2013-01-15 21:36:12.211000) ======

Updated to jan 15th version, pull --rebase followed by ./configure and make. Should be correctly updated?

Behavior is the same, both with that save or starting a new game.
====== geever (2013-01-16 01:03:07.740000) ======

Wow, found a new bug! It was sleeping a bit more than 4 years in the codebase!

On determining the actual firing radius, useability of the items are checked - a gun that is not yet fully installed cannot increase the range. BUT due to the bug always the first weapon slot was checked which was empty in your case: unusable, no range update.

I fixed the issue, please retest.
====== jkkurja (2013-01-19 10:07:30.443000) ======

yup, that fixed it!