Jump to content

[WIP] Radar Lock Bug?


wilbur81

Recommended Posts

Here's a strange one (I've noticed behavior like this off and on but decided to document today):

 

Today, I was flying towards a group of Mig-29's. After playing around a little bit with LTWS/MSI radar DATA options, I deselected both because I was tired of not being able to accurately STT the target that I wanted. I went to lock the target (seen in the first screenshot) and the radar immediately locked on to a distant helicopter that wasn't even on my scope. The second screenshot was taken one second or so after the first. I did note that the Migs were flying at about 13.9K ft rather than the minimum 14K that my TDC elevation indicated, but I still don't understand why the radar locked what it did?

Screen_190805_132810.thumb.png.f8bfddf2a95f6abeafc037bf2a283788.png Screen_190805_132822.thumb.png.589d27d682554c79e0376bc74f58fe48.png

RDRBug.trk

 

I've found (maybe more lately?) the Hornet's radar a bit wonky when it comes to TDC-locking the target that I want.

i7 8700K @ Stock - Win10 64 - 32 RAM - RTX 3080 12gb OC - 55 inch 4k Display

 

 

Link to comment
Share on other sites

Radar locks targets off of the scope

 

Update:

 

Today, I tried the same mission again.. this time I used AACQ in order to lock one of the Mig-29s that was about 20 mi or less off my nose. Again, the pic on the left was taken right as I selected AACQ and the pic on the right was the target the Radar actually locked a second or so later. Again, my radar completely bypassed the Migs on the scope and lock up some helos over 30 miles away? Has any one else had problems with this?

 

1.thumb.png.254899e162542d437868f9490210413a.png 2.thumb.png.fc12d37c8719ba2e316c07ad384739cf.png

 

RDRBug2.trk

i7 8700K @ Stock - Win10 64 - 32 RAM - RTX 3080 12gb OC - 55 inch 4k Display

 

 

Link to comment
Share on other sites

This has been an issue for a long time. If something else is on the same bearing as a target you are trying to lock up and is within the current scan area of your radar elevation setting, then you could lock up something you did not expect. It happens even more frequently when using AACQ. Not sure if it's really a "bug" or just an unfortunate consequence of using the hornet's radar. Maybe in real life, the radar is intentionally programmed to ignore and avoid STT locks on targets outside of the current range setting.

Link to comment
Share on other sites

Just as a sidenote to your screenshots: It would be very helpful to see the actual scale of the SA page. You are in a submenu in which the scale is not shown.

 

SA scale was 40mi (note the radar scale [20 mi] and contacts' position halfway b/w plane and edge of SA...half of 40 = 20. Also note my giant red arrows made in windows paint. :-) )


Edited by wilbur81

i7 8700K @ Stock - Win10 64 - 32 RAM - RTX 3080 12gb OC - 55 inch 4k Display

 

 

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...