ORIGINAL: herwin
I accept that, but we're dealing with divisions spread over at least 15 miles of road space on a march or at least 25 square miles deployed. The lethal radius of a 500 pound bomb was 60-90 feet, so it took a minimum of 1500 bombs for 70% casualties on a marching division assuming it stayed visible in 4s on a road--and the normal effect of air attack was for the unit to scatter away from the aim points--or 250,000 bombs for 70% casualties on a deployed division.
You're making stuff up now, professor.
We're dealing with a hex. Just that, a hex. You should know after all the posts to you by the devs that this is not a simulation with a military-grade tactical engine. IT'S A HEX. It's a data point. There are no statistical distributions of men inside that data point, no "2399 men in the first 0.8 mile, then a gap of .072 miles where that platoon stopped to take a piss, then a gaggle at .56 miles where the company clown was telling a really good story and they drew in to hear." It's a hex.
In exchange for it being just a hex, all the AA has instantaneous azimuth and range on any and all aircraft in the hex. Every manjack in the LCU has the same fortification level (no lazybones with the digging), the same health, the same psychological state, the same training. Nobody panics and runs away. Nobody goes crazy. No officers get fragged for dragging those poor draftees onto that godforsaken plain to get their behinds bombed by uber-bombers from Wichita, Kansas. Why? Because it's a hex.
Similarly, your manuals about how "every" division deploys are just that. Manuals. Are they Japanese manuals for operations versus the Soviets in Asia? And exactly 25 square miles. Really? What if it's only 22 square miles? Does somebody get demerits? Well, no. It's just a hex.
It's altitude, speed, terrain, op mode, pilot stats, aircraft stats, weapon stats, weather, and some randoms. You can quote manuals to the end of time and the model is going to be that. Why? Because it's a hex.