[FIXED] RWR indication start too cloce to the threat

[DeMonteur]

When started mission airborne,

 

RWR did not indicate threats unless they are way too close.

 

Tested on MiG29A; start indication at about 28km

For F14 start indication about 38km

For JF17 it was also about 30km.

 

For S-300 indication started only after missile launch. Surveilance and tracking radar was not indicated.

RWR-AJS37vsMiG29A.trk

RWR-AJS37vsF14B.trk

RWR-AJS37vsJF17.trk

RWR-AJS37vsS300.trk

[RagnarDa]

Thanks for the reports and track-files. Turns out there where two problems: one was that there was somehow a hard-coded max distance for detection by the RWR. The other was that there was a blind-spot somehow at 12'o clock on the RWR.

 

I've finally implemented the "overlapping" functionality of the RWR-antennas now so there will be two lights on the RWR on when the emitter is between the coverage of two antennas. This will also help with ELINT-analyzis as the accuracy will improve. Fixes will be in next patch of DCS open beta.

[TOViper]

Thanks for the reports and track-files. Turns out there where two problems: one was that there was somehow a hard-coded max distance for detection by the RWR. The other was that there was a blind-spot somehow at 12'o clock on the RWR.

 

I've finally implemented the "overlapping" functionality of the RWR-antennas now so there will be two lights on the RWR on when the emitter is between the coverage of two antennas. This will also help with ELINT-analyzis as the accuracy will improve. Fixes will be in next patch of DCS open beta.

 

Cool.

I fully understand the dilemma with the 12 o'clock position, and I love RagnarDa's idea which helps massively.

Just a question for information purposes, not intended to make the patch not happening: was this the real behaviour of the aircraft too?

[RagnarDa]

Yes

[Airhunter]

Nice, so finally I'll be able to get a launch warning from my 12 o'clock. :P