Bug: v1.15b C3C - Percentages are off when the sum of AA Unit defense values in a city are greater than the attacking Air unit. This occurs with or without a SAM in the city and only when the combined AA defense is greater than the Air unit D. I have ruled out a coding error in the calculator itself.
Steps to Reproduce:
1. Create a scenario with the above parameters, and 500 air units, Debug mode
2. Set the defense of the AA units to 999
3. Set the Bombard D of the SAM to 999, leaving its Air value @ 8
4. Start the scenario (turn off animations), Bomber Attack 1, Bomber D = varies, ROF = 1
5. Make note: How many bombers were intercepted?
6. Do this test also with the following...
(this is for confimation that my reverse engineered formula is correct, skip if you have access to the exact method of interception calcs)
a) Sum of AA units <= Air Unit D w/ SAM
b) Sum of AA units <= Air Unit D w/o SAM
c) No AA units, Air Unit D (any value) w/ SAM
Observed Result:
Notice how 6a-c agree are within 1 standard deviation of my combat calculator results. This confirms that the formulas for calculating this are correct.
Then notice how the 'special scenario' outcomes vary from the calculator results only in specific cases noted above, by more than 1 standard deviation, sometimes as much as 3 s.d.
Expected Result:
The results should follow a predicible pattern based on the formula for interception. See the thread in my signature for these details on interception.
Possible causes
a) There was an intent, whenever the Air unit D was less than the combined AntiAir Defense that the AA was to have a BONUS to hit, but instead it seems to have a PENALTY.
b) It is a bug with C3C and the outcomes should happen like the formula predicts.
c) There is an unknown variable in my formula that I have not accounted for.
Possible solution
a) Release the exact mechanics of an interception (preferably directly from the source code), so this beta tester can conclude this topic.
b) Someone at Firaxis/Breakaway perform the tests and let us know if it is functioning as intended or it indeed is a bug...
I apologize in advance for not including a save, but I have about 30+ of them and this description will accurately reproduce the possible bug. This coupled with testing by Firaxis/Breakaway, their knowledge of the interception formula and a little statistics, they will be able to arrive at a solution.
If the formula cannot be posted for some reason it could be PM'ed to me and I would only use the information to enhance my combat calculator and close this bug report...
Steps to Reproduce:
1. Create a scenario with the above parameters, and 500 air units, Debug mode
2. Set the defense of the AA units to 999
3. Set the Bombard D of the SAM to 999, leaving its Air value @ 8
4. Start the scenario (turn off animations), Bomber Attack 1, Bomber D = varies, ROF = 1
5. Make note: How many bombers were intercepted?
6. Do this test also with the following...
(this is for confimation that my reverse engineered formula is correct, skip if you have access to the exact method of interception calcs)
a) Sum of AA units <= Air Unit D w/ SAM
b) Sum of AA units <= Air Unit D w/o SAM
c) No AA units, Air Unit D (any value) w/ SAM
Observed Result:
Notice how 6a-c agree are within 1 standard deviation of my combat calculator results. This confirms that the formulas for calculating this are correct.
Then notice how the 'special scenario' outcomes vary from the calculator results only in specific cases noted above, by more than 1 standard deviation, sometimes as much as 3 s.d.
Expected Result:
The results should follow a predicible pattern based on the formula for interception. See the thread in my signature for these details on interception.
Possible causes
a) There was an intent, whenever the Air unit D was less than the combined AntiAir Defense that the AA was to have a BONUS to hit, but instead it seems to have a PENALTY.
b) It is a bug with C3C and the outcomes should happen like the formula predicts.
c) There is an unknown variable in my formula that I have not accounted for.
Possible solution
a) Release the exact mechanics of an interception (preferably directly from the source code), so this beta tester can conclude this topic.
b) Someone at Firaxis/Breakaway perform the tests and let us know if it is functioning as intended or it indeed is a bug...
I apologize in advance for not including a save, but I have about 30+ of them and this description will accurately reproduce the possible bug. This coupled with testing by Firaxis/Breakaway, their knowledge of the interception formula and a little statistics, they will be able to arrive at a solution.
If the formula cannot be posted for some reason it could be PM'ed to me and I would only use the information to enhance my combat calculator and close this bug report...