F-14 radar generates false targets in TWS/TWS cannot resolve multiple targets

[nighthawk2174]

1 hour ago, TordinVarglund said:

Bumping this because I'm having massive issues with lost tracks recently that I did not have ~2-3 months ago.

I don't know what exactly is going on, but it seems to have something to do with targets flying in relatively close formation (like .5nm or less).

 

All of this is with Jester in TWS-A, and applies both in single and multiplayer.

 

Best way to test this is to jump into the PG BVR and Syria BVR Instant Action missions, and observe the difference in track behavior. The Syria one seems to spawn the two MiG-29s with wider separation, and the radar is better at separating them and maintaining independent track files, and missiles correctly guide and go active. In the PG one, it might pick up both targets initially, but it will very quickly reporting lost tracks (Track Extrapolated symbology). 

Yeah it is quite strange

[captain_dalan]

But is this a bug or a feature? Maybe this is exactly how the AWG9 should behave. 

[nighthawk2174]

I think that the odd behavior I saw of the contacts switching is almost certainly a bug.  You have the initial combined target then when the new target is found the initial contact is lost (sometimes resulting in a false return that flies off at Mach 10) and then having the new one designated as the old one; sometimes also producing a false target. The first issue identified by the OP is also almost certainly a bug as well I'm not sure what's going on with it though.  This is where on the DDD you sometimes get a random contact separated in azimuth significantly from the target. The third thing identified is the fact that RWS as substantially better ability to break out contacts with TWS which seems very odd, i've not seen anything in the various radar books i've read that would indicate that TWS/RWS should be any different in their performance here.  Imo this is a bug but i'm willing to be proven wrong here.

[TordinVarglund]

One of the things that makes me think this is most certainly a bug is the fact that this happens with targets separated by quite large distances (.5nm) and at ranges as low as the mid 20s, with altitude separation as you will see in the PG BVR scenario.

 

Initially I figured maybe they were close enough that the Radar couldn't separate them, but it seems a bit far fetched when we're talking thousand of feet of lateral and vertical separation at distances less than 30nm. 

 

First encountered it flying the Fear the Bones campaign in a scenario where you're launching head-on onto a bomber formation. Felt a bit underwhelming to say to least when 5 out of 6 AIM-54s missed when fired from 35nm...