What It Means to Simulate Combat

"Simulating combat" is actually a single phrase covering many different problems. Whether a tank round penetrates a given armor plate (milliseconds, millimeters) and whether a corps wins a week-long operation (days, kilometers) are completely different questions. One resolution cannot answer both. That is why combat modeling goes multi-resolution.

The Resolution Pyramid

Rendering diagram…

Moving down the pyramid: more precise but slower. Moving up: faster but more abstract. Even with the same label "combat simulation," the right tool depends on which layer the question lives at.

Two Resolutions — Physics (T1) vs. Abstract (T2)

In practice, two layers get the most use.

• T1 (physics) — A projectile physically flies and penetrates armor via PhysX. High fidelity, but computationally expensive per engagement.
• T2 (abstract) — Combat is solved with probability distributions and differential equations. Thousands of entities, corps-scale engagements, in milliseconds.

The Bridge Between Them — Calibration

The heart of multi-resolution modeling is that the two layers calibrate each other rather than operating in isolation.

Rendering diagram…

T2 rapidly filters hundreds of courses of action (COAs), and only the most promising candidates go to T1 for precision validation. The empirically measured kill probabilities (Pk) from T1 are then fed back to recalibrate the T2 abstract model. You get speed (T2) and precision (T1) simultaneously.

💡 Multi-resolution in practice — When the same operation is solved by both T2 (abstract) and T1 (physics) and the results consistently converge, the model is trustworthy. In one real case, unit survival rate was 0.94 in T2 abstract and 0.88 in T1 physics — different resolutions, same direction of conclusion.

⚠️ Do not trust abstract models alone — T2 is fast, but if the coefficients (Pk, Ph) are wrong, the entire result is wrong. Regular recalibration against T1 physics (or real-world measurements) is essential. "Fast answer" and "correct answer" are not the same thing.

In a nutshell

📌 Combat simulation is multi-resolution — layers range from engineering (milliseconds) to strategy (weeks). In practice, T1 (physics: precise and slow) and T2 (abstract: fast and approximate) work together: T2 rapidly searches the COA space, T1 precisely validates selected candidates, and measured values from T1 recalibrate T2. Multi-resolution means getting both speed and precision.