Santi871

It does not. In practice TWS is heavily inaccurate elevation wise, one of the reasons why it's not popular.

Absolutely hope ED will implement this. The TD box should dance around the target as it hits every time and gets a different error, and the bigger the range the bigger the error, especially vertically as you said, and especially in the Viper because the beam is larger vertically than horizontally..

Thanks for the info Wags!

Correct me if I'm wrong, but the threat classification is not based strictly on signal type (search/lock/launch) but also on strength. The ALTITUDE button for example allows swapping to a secondary library which contains threat priority classification tailored to low altitude threats.

This is not how it works ingame. OP is correct in saying it's based on strength (ingame). The DCS Hornet works this way however.

Did they disappear shortly after bugging them? From my testing it seemed they haven't included a timing-out track symbology (blinking track) and it was just making them invisible instead.

RWS search targets should *not* have a full heading vector Hi, RWS search target symbology is bugged: 1. RWS search targets can only display fully hot or fully cold vector based on closure rate - called Search Doppler Vector (later renamed to Enhanced Search Display), ie target is getting closer or further away. Not full heading vector. 2. For older tapes (M5.2 and below), Search Doppler Vector is only displayed for RWS search targets under the cursor. Otherwise, RWS search target is simply an upright filled white square. I can provide track later if really needed, just busy right now and wanted to get this reported.

That's right, locklines only show from your (link16) wingmen.

This option is OFF with air or cold start and without it you will not share your bugged target over L16 (top right - change it to XMT L16):

So far link16 flights still depend on mission editor groups, like in the hornet.

It's not possible to bug two targets simultaneously.

Targets transmitted on link16 by player Hornets do not display in the Viper. Nineline said no track is required for now, I'm adding pictures.

Only the bugged target is transmitted on link16, bug or feature? No other TWS tracks are transmitted. This is with another player F-16. Nineline said no track was needed, I'm attaching pictures. There were several targets infront of us, but only the bugged one is transmitted.

It's modern enough indeed, but the question is whether it was removed at some point. Perhaps to prevent cluttering the display. And Full blown velocity vectors is bug/wip/needs to be fixed though, I think.

It's described in the MLU M1 manual, but that is for european A/B's, and we don't know where ED is getting their info so... good question.

RWS can't determine velocity vectors, but it can determine closure rate. Certain viper versions show that with hotlines, which is what I showed in the second picture. Certain versions only show the bricks. But I've never seen full aspect vectors in RWS, hence the question.

In wags' latest videos we can see the RWS symbology for search targets has changed - they are now a white box with a velocity vector coming out of it. Is this accurate? I was under the impression the "hot lines" that show in RWS search targets can only point fully upwards (opening target) or fully downwards (closing target)

On the radar page, MSI HAFUs are displayed with a PPI projection (like the SA page) instead of the correct b-scope projection. This causes an incorrect aspect vector. https://giant.gfycat.com/SpanishClutteredGreathornedowl.webm However, they are displayed with the correct b-scope projection when putting the cursor over them, which causes a discrepancy in the aspect vector when moving the cursor on top or away from a HAFU. Please see attached track. To be clear, this is the difference between b-scope and PPI projection: msi_ppi_on_radar.trk

1. Would be nice if it was added for complete-ness but I don't think it gets much use irl as it's pretty much just a "legacy" mode leftover from older radars. 2. TWS 3. SIL has some extra functions, for example ACTIVE which scans one frame then it goes back to silent, and there's also some passive radar stuff that's not implemented afaik.

Yes, link16 works like you are normally used to from the Hornet. You just won't be attaching IFF info to tracks, or changing their classification (ie unknowns will stay unknowns). Like you can see in Wags' video, once your radar finds and correlates the track, it will go back to the usual white square symbology on the radar, and it only stays red (if it was hostile) on the HSD.

It's still up to you to IFF and do whatever you need to verify it's actually hostile, same as you would in the hornet. Granted, in the more or less flawless world that DCS is, if you lock a hostile in DL, it will actually be hostile (barring you locking the wrong target).

I would assume we will get at least unknown. There's no ambiguous symbol for the viper. Have in mind you can't change the symbol of a track in the viper, it will just display what it gets out of the network, and contribute unknowns with its own radar - although maybe there's some obscure way of changing them that I'm not aware of (maybe with NCTR?). AFAIK this is also why there's no ambiguous symbol.

Wow, nice to see this is being done.

I am fairly confident they do use the HAF manual as a source, because of mistakes such as stating the comm switch has IFF functions and TMS left = expanded data on radar page which is not correct for USAF CM vipers (they ended up correcting themselves and now TMS left = IFF interrogate).

e: nevermind, read viper instead of hornet. Does the viper radar use STT waveform+processing during the bugged target revisit portion?