Jak525

I asked about this and Wags says this is how it works according to their info for this timeframe. But IDK, maybe it can be double checked. https://forums.eagle.ru/showthread.php?t=258117

When an L&S is designated, the Aircraft-to-TDC BRA indication in the lower left disappears. BRA L&S bug.miz.trk

When you're in STT, the target's HAFU symbol has 2 issues: there is no color for unknown or hostile HAFUs, and there is no L&S star. STT HAFU bug.miz.trk

When the search mode is TWS and then the A/A Gun is selected, Gun Acquisition mode is not entered. TWS GACQ bug.miz.trk

When entering ACM from TWS, the RTS option indicates "RTS RWS" instead of the correct "RTS TWS". In addition, the "HITS" option remains. Also to note, tying into the not-yet-fixed bug I reported separately on Gun Acquisition, when the A/A Gun is selected, the RTS indication should always say "RTS GACQ" (since TWS/RWS shouldn't be able to be entered with the A/A gun selected). TWS ACM bug.miz.trk

His video is out of date/wrong. They only added the ability to guide with LTWS at the same time as TWS, presumably because they only now added the code to guide the AMRAAM onto a non-STT trackfile.

No, in RWS Undesignate should step the L&S or swap L&S/DT2, just as it does in TWS. That is entirely correct behavior. Hit RSET to get rid of the L&S or disable LTWS. Dont know, probably something to do with TWS scan centering and AMRAAM launching. Not functional as far as I can tell.

Yes. LTWS is just TWS without the fancy scan centering and artificial scan volume limitation.

I think RWS is or at least should extrapolate like TWS... but yeah, I agree with your conclusion.

From my understanding yes, pretty much. RWS correlates the hits as well. LTWS doesn't change any operation of the radar, it's just a user interface option to show the trackfiles. The mode that's truly different is Velocity Search which we don't have. This mode shows closure rate opposed to range and doesn't create trackfiles (or might create angle only tracks).

RWS can also attack 10 targets. The only reason TWS has a higher update rate generally speaking is because the scan volume is forcibly smaller. A 20 degree, 2 bar scan in RWS should yield the same track quality as a 20 degree, 2 bar scan in TWS. TWS is just better cause you can center the scan to always keep the target.

Thanks very much, I'm glad you like it. Very sorry to hear this caused such confusion for you, I had actually edited that section just the other day and I never noticed that got messed up; so again, thanks a lot for pointing it out. Yeah I'd really appreciate reports of any other errors you find. If you have Discord, you can join Hoggit's server and reach me there (I'm Jak) - discord.gg/hoggit. If not then just direct message me here on the forum.

You can guide against as many targets in TWS as you can in RWS. TWS is just better so you can have the scan centering and scan volume limitations. Certainly though, I agree. More than 2 is pushing it, but you can do it if you want. You'll have the ability to select TWS with the TDC cursor soon, as you can the bar setting, etc.

See what Harker said. Remember: RWS (with LTWS enabled) and TWS are not all that different. TWS really just provides scan centering / volume limitations, and the EXP/SCAN RAID modes. Other than that, they're the same. If you really want you can even fire off an AMRAAM in RWS.

EXP - zoom in on screen RAID - zooms in on screen, does a fine 22° scan on L&S to do "raid assessment" - attempts to break apart trackfile into multiple trackfiles for targets very close together and picked up as one by the radar.

The TDC option selection function is not working correctly. DCS manual pg. 229 illustrates the fact that the PRF and search mode options should be selectable. RSET should also, which does not work, although I think I reported that at another time. Something that once worked, but is now broken - in RWS, it appears the "expanded options" for azimuth selection are not drawn, although seem selectable still as demonstrated. The azimuth option should 'expand' when the TDC is put over it just like the bar setting does. In TWS, azimuth selection is done via successive TDC depresses to cycle through it, as opposed to an expanded view as I mentioned above. Unless a change in mechanization of this for TWS is specifically documented it should work as I described above (aka, how it's worked since it broke this patch). Side note: I notice the zones might be slightly too small. I feel like once both "captain's bars" are outside of the tactical region border you should be able to select the option. You end up having to move it quite a bit farther which makes it difficult. Thanks! RDR ATTK TDC selection bug.miz.trk

Screenshot an example please

As indicated in the DCS Hornet manual: with the AIM-7 selected and an L&S designated outside of STT, 'GO STT' should be displayed by the target designator box on the HUD.

Great stuff

Correct, 17 and 19 should be swapped. Thanks for pointing it out; it's fixed.

Technically no, practically if he's in formation with you yes.

Thanks @Wags!

The fly out cue is definitely displayed right now for the AIM-120 as well, in STT. I believe it should be displayed in TWS also. If anything, it'd be more useful for the AIM-120 in TWS as opposed to STT in a saturated environment, so as to see what trackfiles you've actually shot at, and also the individual missile statuses.

Yes.

Only one target can be shot at simultaneously. You can't shoot the AMRAAM at the DT2 - you have to make it the L&S first. Like Rob said, it's just to get targeting information (Launch Acceptable Region) on another target, see the 'X' overlayed on the HUD, and also be able to quickly swap it for the L&S.