Beamscanner

What would prevent them?

while in STT, targets do not move smoothly (via extrapolation) accross the radar screen. Instead, target motion appears as discrete jumps from position to position in both range and azimuth(when turning). This becomes very noticeable at range scales below 20 miles. Track previously posted: https://forums.eagle.ru/attachment.php?attachmentid=232898&d=1587174323

Under normal operation, if a tracked target performs a maneuver in excess of 3Gs, the target's vector indicator should have a another bar added to the end of (and perpendicular to) the targets vector, on the side of the targets turn. Currently in DCS, if I have a target in STT, and I perform a maneuver in excess of 3Gs, the target locked up will have the 3G maneuver indication, even though the target may not be maneuvering at all. STT3gvector.trk

This is a tricky problem since we dont know the logic within RWRs. The possibilities include: 1. Trigger launch alert only when missile seeker or illumination is detected. Has a low false alarm rate, but prevents any detection of a FOX 3 prior to Pitbull, limiting the time to warn. 2. Trigger launch alert only when mid-course guidance/illumination is detected. Provides early warning to the pilot, but has a high false alarm rate since missiles fired at people other than you will still trigger the launch warning. 3. Trigger launch alert only when both mid-course guidance(or illumination) and radar tracking are detected (ie a "lock on") and coming from approximately the same direction. A balanced approach that allows early warning and a low false alarm rate. The only weakness it has is against TWS launches, since the RWR doesn't know its being tracked. But a Fox 3 fired in STT would be detected with this logic. I prefer #3. But Whatever ED does, I just hope they stay consistent among the modules.

If you know anything about radar theory, you'll know that a low PRF waveform is highly ambiguous in doppler. hence why true pulse doppler radars use high or medium PRFs. now go ask your SME what PRF it used. :P

Anyone else seeing tracks stutter across the radar page during STT? You can see it in this video at 1:50. This didn't happen before TWS was implemented, and doesn't occur in the Viper.

do you have the link to where wags said this? i cant find it

any update on this?

to clarify, it is coherent. But its not "Pulse Doppler" in the western sense of the phrase. ie it doesnt measure velocity, but instead can filter out non-moving targets. Thus, it is Coherent MTI, but not PD.

just add for i = 1, 16 do AddAirborneSymbol(i, {{"AirborneSymbol", i-1}}) end to the RWR_ALR56_MAIN_page.lua within \Program Files\Eagle Dynamics\DCS World\Mods\aircraft\F-16C\Cockpit\Scripts\EWS\RWR\indicator

Yes they do dim by time. But the time to dim in DCS is shorter than the longest revisit time. Meaning trackfiles could dim even if the target is detected on every scan. The fundamental point of dimming is to indicate to the pilot that the trackfile is starting to ageout as it hasnt been seen awhile. Imagine target X is at the left edge of a 1 bar scan, and target Y is centered in the same 1 bar scan. Target Y will be detected (revisited) on a regular and even schedule, but target X will have an irregular revisit schedule. Target X will have a short revisit, followed by a much longer revisit time while the radar scans across the right side of its scan area. The 'time to dim' should be extend long enough so that even off center tracks (like target X) can be revisited before initiating a dim.

Scan centering is available in RWS. Already PM'd nineline on this.

Does the Harrier not have an SA page IRL? I think this is missing in the DCS AV-8B

That mod cannot be used with MFD exports. Wish ED would just address this.

yes but the new radar tone are not in there. listen to the tone of an F-15 lock, then look through the few tones in that folder. its not there

I was convinced i adopted too early as well (HP Reverb is my first HMD). but after some time tweaking I find it enjoyable. even in MP. The main issues i have are the narrow sweet spot, fog, and washed out colors.

In addition to making current shaders compatible with Vulkan, are new shaders being made for new FLIR and Ground mapping APIs?

I cannot find the tones in the F-16C mod folder, and the RWR lua shows the F-5E sound path (the new tones arnt there either). Anyone know where that sound files are located for the new ALR-56 tones?

This paper somewhat describes the theory of operation. http://www.radarindia.com/irsi13papers/13-FP-015.pdf

Exactly this.

Undesignate button, when placed over a L&S or DT2, will not drop the designation. "Manual undesignate" occurs when the cursor is placed over a trackfile. This drops whatever designation the contact had. RWS Manual undesignate = L&S -> Brick TWS Manual undesignate = L&S -> Ranked Trackfile Track can be found here: https://forums.eagle.ru/showpost.php?p=4147257&postcount=1 Mods require separate threads for each item, but the forum will not allow me to upload the same track twice. "You have already attached this file in thread : [ONE ITEM PER REPORT] TWS and other Radar issues"

TWS azmiuth slewing offsets the RWS scan area when switched back. Track can be found here: https://forums.eagle.ru/showpost.php?p=4147257&postcount=1 Mods require separate threads for each item, but the forum will not allow me to upload the same track twice. "You have already attached this file in thread : [ONE ITEM PER REPORT] TWS and other Radar issues"

L&S/DT2 trackfile icons appear below the LAR icons on the radar display. They should be above Track can be found here: https://forums.eagle.ru/showpost.php?p=4147257&postcount=1 Mods require separate threads for each item, but the forum will not allow me to upload the same track twice. "You have already attached this file in thread : [ONE ITEM PER REPORT] TWS and other Radar issues"

Raid Scan does not function properly. RAID scan is not used to zoom in on closely spaced trackfiles. (thats what EXP is for) RAID is used on a single trackfile to see if that one trackfile is actually two (or more) aircraft in close proximity sharing a very close doppler. RAID scan will center the screen on the trackfile and populate Hits behind it in a range vs doppler display (X axis = doppler, Y axis = range). The pilot then monitors the path of the Hits to see if there are two or more linear paths indicating two or more aircraft within the beam. further details: https://forums.eagle.ru/showpost.php?p=3956626&postcount=1 https://forums.eagle.ru/showpost.php?p=4129145&postcount=12 Track can be found here: https://forums.eagle.ru/showpost.php?p=4147257&postcount=1 Mods require separate threads for each item, but the forum will not allow me to upload the same track twice. "You have already attached this file in thread : [ONE ITEM PER REPORT] TWS and other Radar issues"

"Angle Only Dugout" should not have range based contacts (ie Hits or trackfiles) max range of radar should end just below the dugout. Track can be found here: https://forums.eagle.ru/showpost.php?p=4147257&postcount=1 Mods require separate threads for each item, but the forum will not allow me to upload the same track twice. "You have already attached this file in thread : [ONE ITEM PER REPORT] TWS and other Radar issues"