Setting artillery ILLUM or SMOKE round amount to 1, 3, 6, 12 or 24 (and HE to _any_) and firing the available amount with a full volley (1, 3, 6, 12 or 24 depending on the set amount) will after

1. firing ILLUM
2. make HE rounds disappear from the Ordnance list

Doing in that order also gives 2 times the amount of ILLUM rounds available than what was initially set. This means that setting for example 6 rounds of ILLUM will actually make 2 * 6 = 12 rounds available.

(cnt'd)...will after

1. firing SMOKE
2. make HE rounds disappear from the Ordnance list
3. after the second volley of SMOKE make ILLUM rounds disappear from the Ordnance list

Doing in that order also gives 3 times the amount of SMOKE rounds available than what was initially set. This means that setting for example 6 rounds of SMOKE will actually make 3 * 6 = 18 rounds available.

Tested with Arma 1.56, CBA 2.2.0.151130 and ALiVE 1.0 in use.
Also this was tested only with Arty/Mortar type O_Mortar_01_F thinking that this out of anything else would have the least to do with the earlier described behavior.

Since I just recently updated to CBA_A3 version 2.3.1.160220 I just now redid this test (with Arma 1.56 and ALiVE 1.0) to confirm that there was no change in the earlier described behavior. And there wasn't.

@GunnyDev What do you mean out _any_?

Hi Gunny.

_any_ in this case means anything between 1 and infinite. Though I don't know if infinite is possible but whatever happens to be the max amount of rounds that you can actually put in the field.
For simplicity's sake let's say anything between 1 and 1000 or anything else than 0.

I hope I didn't mix this any further with that description but please do ask if I did.

For testing I'm using:

Callsign: FOX SEVEN
Arty/Mortar Type: O_Mortar_01_F
Number of HE Rounds: 180
Number of ILLUM Rounds: 24
Number of SMOKE Rounds: 6
*any other type* Rounds: 0

Edited the earlier post to include the parameters I've been using while testing.

ALSO tested with A3 1.56.134787, @CBA_A3 2.3.1.160220 and @ALiVE 1.0.2.1603251 with no change compared to the original behaviour.

@GunnyDev Thanks for the report, I have managed to repro and have commited a fix into Dev branch.

Gunny

Great to hear! Though probably not the most common problem out there and more like that you happen to stumble on it.. still looking forward to give it another run after the fix to put this one in the books.

Fixed in release 1.0.3.1604121.

(no more disappearing ordnance :) )