From: Mosquito Bite, Texas
That doesn't make any sense, as the combat model, to my understanding, is supposed to calculate by element, not just by overall CV. It would also allow for a division that has one tank left to have the tank destroy a bunch of units late in the calculation, and then turn around and be destroyed on the first shot when the opposing side's routines were run.
Well, it doesn't make any sense because you don't understand my point. I said nothing about using the entire CV, now did I?
Yes, combat is done by element, but IRL it is not. So, by doing it by element, some results are applied first, and others later. The only result that really matters is the total of all the elements once the combat is over. The final result is all that matters.
Do you think, for example, that in a real battle, the artillery fires, then the infantry autmatic weapons, then the small arms, followed by an armored assault, etc. No, it can all happen at once. Most combat models do it element by element these days. So, you see the results of one lement, then another, then another. In your example, the ones that caused your casualties were run first. So, your guys aren't bullet proof, it's just that all the casualties you tok were calculated early on.
It's simple when you realize that there's no real guys shooting in your computer.
Occasionally, and randomly, problems and solutions collide. The probability of these collisions is inversely related to the number of committees working on the solutions. -- Me.