thewood1 -> RE: DB request OECM emiter range (11/9/2017 7:41:16 PM)
|
I haven't found this to be a high priority issue for a couple reasons... 1) most of the info is available on the web. But there aren't many sources on ranges because of the number of variables. You can find max power, but that is only one dimension. 2) A little experimentation is in the editor isn't fairly easy if you know the radars you are going up against. I am not sure how the ECM ranges could be shown anyway. I don't think its that the devs think its too complex for most people to understand, though it might be. Its the complexity of having the range dynamically shown. There are so many variables involved in the range of countermeasures that an entire sim could be built around how dynamically it would show that range. It is so dependent on the exact radar that it is going up against and the variables associated with that set that the range would be so generic as to almost useless. The only way I could see to do it is similar to how ECM is handled in real life, before the mission, you would have to set each ALQ or equivalent for the potential radars it might run into. And lock the range(s) to that set. A good read is Osprey's New Vanguard on SA-2s in Vietnam and you'll see that its not just a simple turn on and forget. Every raid the US executed had no idea what ranges for countermeasures they were working with. They were adjusting ECM power and settings on the fly. Its gotten a little more automated, but only fairly recently. Does Command simulate to that level...I don't know. But I think accepting the devs at their word is not beyond reason.
|
|
|
|