Jump to content

Recommended Posts

Posted

This has always happened but not as flagrantly as what I noticed today. Flying the F-15, using TWS mode, I got a return at approx. 17nm away. I locked it and held the lock until it broke at about 9nm. When it broke, the original return at 17nm was still on the radar screen. I know there is a built in delay for returns to disappear on both the TEWS and the radar, but this was way too much time for the original return to still be there.

Posted

OK, here's a track. Maybe I didn't explain it well, or maybe nobody cares.

 

Once lock is broken, (I broke it on purpose in the track by moving the scan away from the bandit) the bandit shows up back at the point where he was originally locked.

Posted
ED knows the problem. See the sticky on top.

 

This is NOT the RWR bug. And it gets worse. I just came out of the 504th server.

I was capping for a pair of A-10s in formation. At one point, there appeared a second pair of returns where the A-10s were. I think my TWS scan cone moved away from them for an instant.

 

And this: I was dragging a 77. It just wouldn't stop and it wouldn't spoof. It seemed to chase me for way too long. I was getting audible warnings the whole time. I cycled RWR and it disappeared. It might have been a coincidence, but I don't know. Hopefully the RWR fix will cover this, if it is indeed part of the problem

Posted

The thing with the 77 will be the main RWR ghosting bug though won't it - an active radar disappears (gets shot, blows up, hits the ground etc) while showing on your RWR & stays there till you clear it.

Cheers.

Posted

Except for the audible warnings. And it was flashing, not solid like the normal RWR ghosts.

 

The TWS contacts are definitely not the RWR bug, but could be related. I'd bet it has to do with the new way that you lose locks outside of scan range.

  • Recently Browsing   0 members

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