are missile and radar ranges represented incorrectly in ME?

[Zyll]

hi team,

 

The attached screenshot shows in red, the missile range of 65nm for an S-300 launcher. The larger yellow rings show the detection range of the Big Bird search radar, and the Flap Lid tracking radar. The smaller yellow ring shows the detection range of the Clam Shell search radar.

 

There is no terrain to affect the test. I expect that I should be engaged by the missiles right at the red ring, 65nm. In actuality, I'm getting engaged consistently at 35nm. Aircraft is at 25,000 feet.

 

Is it possible that the range rings are incorrect across the board? I ask because Wikipedia tells me that the Big Bird should have a detection range of 190nm, but the game has range rings at 86nm. Clam Shell radar should have a detection range of 75nm, but the game shows 32nm. It seems as if everything is halved in the game, perhaps ranges are incorrectly being represented on the map with diameter instead of radius.

[Ramsay]

In actuality, I'm getting engaged consistently at 35nm. Aircraft is at 25,000 feet.

 

Detection range depends on radar cross section e.g. a F-18C AN/APG-73 can detect a Tu-142 @ 110 NM but a F-5 is only detected at ~45 NM.

 

Similarly, it would unwise for the SAM to launch at max range as it's missiles could easily be avoided/depleted.

 

Adjusting the AI skill level helps a little but DCS's SAM behaviour is greatly simplified when compared to RL tactics.

[nighthawk2174]

Sort of and yes. Detection ranges often depend on how big of an RCS you decide to base that max detection range off of. Now for missile ranges a really good example is the SA10 I would say has ~50 less range than it probably should.