Santi871

TWS is constantly trying to determine whether a new hit should be associated to an existing trackfile, which implies that there's always going to be room for error and sometimes different hits might be correlated to the same track, or the opposite, hits on the same target might create separate tracks even though there's only one target present. RWS doesn't try to correlate anything, so as long as the radar determines there's two separate hits, they'll show as such. However, targets can be so close together that they fall within the radar's resolution and so even in RWS they'll show as a single target.

Already reported, thanks

Reported, thanks

It's fixed internally

Reported, cheers

I dunno.

I'll check, thanks.

https://forums.eagle.ru/showpost.php?p=4387824&postcount=15

Reported. It only happens in snowplow pointed mode.

It is the SURV unknown symbol. Since the AWACS "magically" classifies targets into friendly/hostile instantly, it wasn't possible to see this symbol until the neutral faction was added. Now it's possible.

Laser ranging isn't implemented ATM

The current implementation is correct, pressing undesignate twice within one second.

Thanks, reported

Sorry for the delay, it's already reported

I'll try to reproduce, but a track would be appreciated

Will investigate some more.

Thanks! No worries, limits are limits, but if it can be helped a bit, all the better

It's reported/fixed internally :)

Yes, I experience this all the time depending on our pings to the server. The code syncing the radar antenna and TCS line of sight seems to be very susceptible to ping, which means it hard for a RIO and pilot to play together if one has a ping of like 200 due to radar and TCS stuttering, in my experience. For example, with a pilot playing from the US with a RIO from Europe. Hopefully there is some way to alleviate it.

It's the same with radar with a human RIO. Latency and network come into play and the pilot will see a very stuttery radar pipper when in PAL mode, for example.

New AIM-120 can see and react to chaff. Chaff rejection rate is just high, as it should be for a modern fox3.

Are there any plans to bring the Phoenix to the new missile FM just like what the 120 got? I realize it's far from a trivial task, but just curious

What is a bug? You asked if you can designate outside the cone, and you can't, unless you mean something like setting the scan azimuth to something below the full azimuth and trying to designate, in which case I'm not sure what should happen. Once you make a designation it doesn't matter where you point the radar, the designation has already been made. About the centering on TDC, no it shouldn't. Edit: reading the post again I see you're talking about sub-120 degree azimuth settings. I'll try to dig, but I'm not sure what should happen exactly here.

Nope

You are not locking anything with the radar, just designating the location under the cursor. The tracking modes - FTT and GMTT will come later.