Copy-paste from this thread:
http://www.matrixgames.com/forums/tm...&key=�
Here are some screenshots from the Radar Calc MS/Excel sheets I've used to balance out the radar model. It should give some clues about the input parameters and also the model's complexity. Note that stats from
public sources are in
black, my wilda$$ guessimations are in
red. Lots of comments here and there. And yes, we only have one operating mode per radar set, which is the most typical operating mode.
Since the Command sensor code is written in Visual Basic, we use the _exact_same_ code in both the simulator and the above MS/Excel spreadsheet. Pretty neat huh!
The
1980-2015+ database contains 1838 (finished) radars and they've all been balanced out like this. Yes, that was a
insane job. The 1950-1979 database has a load of earlier sets extinct by 1980. The database editor has the same VB sensor code as the sim and the MS/Excel spreadsheet, and thus also does a bunch of sample calcs in the editor itself just to make sure the input params aren't out of whack.
Here are some range estimations for some ESM sets against five typical radar sets. Again, black stats are from public sources, red are my wilda$$ guesses. And as for radars, this was a big job as well.
And as you can see, high-end ESM/ELINT sets produce some pretty ridiculous range estimates against powerful radars hehe.
Here are some ECM vs radar examples. As you can see it is pretty complex. Black stats come from declass sources, red stats are my guessimations.
The effects assume the target radar antenna points directly at the jammer beam. Sidelobe jamming (which Command also simulates) has less effect.
