investigating Hornet Radar Look Down Penalty Still Seems Too Severe in Some Cases

DCS FIGHTER PILOT · July 28, 2022

4 Tracks From The Most Recent Open Beta Update

1st Track: Co-Altitude with Viper head on, 35,000ft Mach 1: Detection Range~45nm, Tracking Range~41nm

2nd Track: Look Up With Viper head on, Viper Altitude and Speed 35,000ft and Mach 1, Hornet Altitude and speed 20,000ft and Mach 1: Detection Range~40nm, Tracking Range~37nm.

3rd Track: Mild Look Down With Viper, Both Planes ~ Mach 1, Viper altitude 25,000ft, Hornet Altitude 35,000ft: Detection Range~30nm, Tracking Range~27nm.

4th Track: Extreme Look Down With Viper, Both Planes ~Mach 1, Viper Altitude 2500 AGL, Hornet Altitude 35,000ft: Detection Range~30nm, Tracking Range~27nm.

As one can see, there exists a striking similarity in terms of detection and tracking ranges between tracks 3 and 4 even though the differential altitude between the two aircraft is far more extreme in the later. It seems as if the radar look down penalty is simply modeled here and reverts to prescribed values regardless of altitude difference past a certain differential altitude.

Additionally, though I have not tested it thoroughly yet I believe this issue still affects the Viper.

Co-Alt.trk Look_Up.trk Mild_Look_Down.trk Mild_Look_Down.trk Extreme_Look_Down.trk

Edited July 28, 2022 by DCS FIGHTER PILOT

MARLAN_ · July 28, 2022

In my limited tests when the bandit is any more than 5000 ft below you your radar range is ridiculously reduced as you've shown. About 48nm to 31nm vs. a Fulcrum. Definitely needs fixing.