nighthawk2174 Posted November 26, 2019 Share Posted November 26, 2019 (edited) Something that is really really strange to me and a few others is that in the upcoming TWS mode you manually have to designate between track and system files. Yet in every F16 manual out there (that i've seen), this is automatically done and the distinction is not made rather they are just called system track files. It just seems weird that something that was already heavily automated in earlier blocks would just stop being automated? Edited November 26, 2019 by nighthawk2174 Link to comment Share on other sites More sharing options...
Alfas Posted November 27, 2019 Share Posted November 27, 2019 (edited) as in WAGS video, manual system files is a optional. You can automatically turn all track files to system files by just a TMS right (if none system file is present). Edited November 27, 2019 by Alfas Link to comment Share on other sites More sharing options...
Santi871 Posted November 27, 2019 Share Posted November 27, 2019 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. Link to comment Share on other sites More sharing options...
Beamscanner Posted November 27, 2019 Share Posted November 27, 2019 do trackfiles change color based on AIM-120 support, pitbull, etc in the block 50 modeled? Im curious if this is coming. Link to comment Share on other sites More sharing options...
Frederf Posted November 27, 2019 Share Posted November 27, 2019 Keeping in mind this is description of APG-66v2 while DCS module is APG-68v5. It may or may not be the case that the two radars share this feature in common. There are five kinds of targets in TWS of increasing priority: search, tank, system, cursor, and bugged.Search is contacts similar to RWS, upgrades to tank track if correlation successful. Search type are contacts with history and radial velocity tics and are upgraded to tank if subsequent scans produce a correlated track. Tank type are tracks, filled squares and act like SAM tracks. These cannot be cursor or bug directly. System type are tracks, hollow squares and act like non-bugged TTS track. They are result of manual or automatic promotion from tank-type. This can be manual on an individual basis, automatic by TMS right (>1s) without any tracks higher tank type, automatic by empty display receiving its first tank type and TMS right short having been pressed to arm this automatic elevation or manual by TMS right short elevating all tank to system after the previous armed elevation of first tank. TMS right steps through system tracks. Cursor type is a system track with promoted importance by snapping the FCR cursor to it. Azimuth/bar is reduced (50 wide, 3 bar) to support this. Bugged typeis the highest priority track and the singular target of interest (TOI) for missile launch and status display. Scan volume is reduced with bug the same as with cursor type. System or higher are bugged by designating (TMS up) on them or stepping the bug to them (TMS right). Tracks are demoted typically with several TMS aft presses. Transitioning to and from TWS with various target states is done smartly. E.g. SAM transitions to TWS with bug retained. TTS's secondary target is introduced as a system track and the next in priority for bug stepping. Link to comment Share on other sites More sharing options...
Recommended Posts