Beamscanner

RWR trackfiles on the radar display should be layered by priority. Currently they have illegible overlap. #1 priority RWR track should be on top and legible. 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"

RWR trackfiles on radar display should be just below the angle only dugout. Just below the dugout, not inside 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"

Interleaved PRF mode does not invert after each frame. In order to properly scan all elevations with both HPRF and MPRF, the radar switches the order of its waveforms. Example: 4 Bar scan Frame 1 - Bar 1 = HPRF Frame 1 - Bar 2 = MPRF Frame 1 - Bar 3 = HPRF Frame 1 - Bar 4 = MPRF Frame 2 - Bar 1 = MPRF Frame 2 - Bar 2 = HPRF Frame 2 - Bar 3 = MPRF Frame 2 - Bar 4 = HPRF etc.. 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 "Hits" are extrapolated. "Hits" and bricks should not be extrapolated. ie they should not have predicted movement like trackfiles. 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 ageout does not match ageout of ranked track files ( 1 - 8 ). Put L&S/DT2 tracks at the edge of a TWS sweep and you'll see that they dim out before the radars even gotten back to revisit them. Dim should only occur when a revisit results in no detection. 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"

Why do TWS contacts need to disappear / reappear in order to move? I think it should work similar to U.S. radar tracks.. They're detected velocity should be used to extrapolate seamless motion.

L&S/DT2 ageout does not match ageout of ranked track files ( 1 - 8 ). Put L&S/DT2 tracks at the edge of a TWS sweep and you'll see that they dim out before the radars even gotten back to revisit them. Dim should only occur when a revisit results in no detection. TWS "Hits" are extrapolated. "Hits" and bricks should not be extrapolated. ie they should not have predicted movement like trackfiles. Interleaved PRF mode does not invert after each frame. In order to properly scan all elevations with both HPRF and MPRF, the radar switches the order of its waveforms. Example: 4 Bar scan Frame 1 - Bar 1 = HPRF Frame 1 - Bar 2 = MPRF Frame 1 - Bar 3 = HPRF Frame 1 - Bar 4 = MPRF Frame 2 - Bar 1 = MPRF Frame 2 - Bar 2 = HPRF Frame 2 - Bar 3 = MPRF Frame 2 - Bar 4 = HPRF etc.. RWR trackfiles on radar display should be just below the angle only dugout. Just below the dugout, not inside the dugout. RWR trackfiles on the radar display should be layered by priority. Currently they have illegible overlap. #1 priority RWR track should be on top and legible. "Angle Only Dugout" should not have range based contacts (ie Hits or trackfiles) max range of radar should end just below the dugout. 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. https://forums.eagle.ru/showpost.php?p=3956626&postcount=1 https://forums.eagle.ru/showpost.php?p=4129145&postcount=12 L&S/DT2 trackfile icons appear below the LAR icons on the radar display. TWS azmiuth slewing offsets the RWS scan area when switched back. 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 TWStest.trk

Expand = zoom display on target RAID = refines radar processing (uses doppler beam sharpening) to break out multiple targets that would otherwise be detected as one large target. Two or more targets sharing the same range and doppler bin would appear as one target (but their combined RCS would increase the range they'd be seen from). "Expand" wouldn't break the target up, it just zooms in. Spotlight has nothing to do with RAID. Spotlight is used to rapidly scan an area where a radar hit is intermittent and the pilot wants a trackfile built on it. Or to quickly find a data link contact / AWACS call. great video of RAID assessment mode (RAM)

radio frequency does not influence the RWR tones. Only PRF, PRF modulation, Scan and illumination time do. Technically PRF audio can be generated from Pulse Descriptor words (PDWs) to generate a synthetic tone that matches the detected PRF/scan. Modern digital RWRs may choose this route so as to eliminate the requirement of an AM receiver for the PRF audio. Unfortunately their tones are sinusoidal and dont have the PRF complexity, mainlobe/sidelobe of a high fidelity tone. https://forums.eagle.ru/showpost.php?p=4046507&postcount=14 I've been working on authentic PRF tones for awhile now. LPRF scanned radar Example: https://forums.eagle.ru/showpost.php?p=4042722&postcount=7 I agree that real parameters are not needed, nor available (most of the time). However, one can still make the sounds more authentic by including PRF modulation types (MPRF dwells, LPRF staggers, etc) with proper scans, beam width illumination time, and sidelobes.

are you assuming TWS doesn't perform monopulse processing?

if anything, those ground targets stand out too much in RBM. My understanding was that RBM was primarily for navigation and terrain referencing due to its poor resolution. With other modes like GMTI, DBS, SEA, etc being the primary means of detecting targets with the radar.

on that note, in HMD bore mode, shouldn't the radar oval trail HMD movement due to radar scan speed limits? ie should the radar oval struggle to keep up with head movement?

i just looked at the RWR lua.. Its got the F-5's RWR lua data in it. :huh:

HUD and HMD characters have weird artifacts where lines overlap. The artifacts dont blend in when you zoom out. This is with 1440p ultra wide display (settings set to 5360x1440p; second monitor is 1080p)

I'm very curious to know what the 'ball park' is for units sold for a module.. 2,000? 10,000? at what point is it no longer profitable to sell modules?

Wags stated that it would take so time to build the RWR sound library. (PRF audio for each radar)

The APG-68 did get the ability to add up/down lines on raw hits (even in RWS). Its not a velocity vector, just says if target doppler is + or - The real question is which model in what year got this capability.

This has to be WIP. All single hit detections should lack a velocity vector. This should be true for both TWS and RWS search hits (non-trackfiles) A single detection (small square with inbound/outbound line) has range, azimuth, elevation and doppler. Doppler alone wont tell you the targets vector. It only tells you if the target has positive or negative doppler shift. You need two or more correlated detections (ie trackfiles) to determine target heading.

I see. so you think all RWRs should wait at least 3 seconds to confirm that its just a momentary lock (~2 second STT, ~2 second scan, ~2 second STT, etc) rather than a full fledged lock on..? Is this delay modeled in all the RWRs? Is there anything indicating this to be true? I agree that RWRs look at other factors as well for lock on indications (PRI, PD, Scan, etc) but I do not believe they have the luxury of waiting 3 seconds to inform the pilot of a lock on. (and that'd be 3 seconds on top of the normal signal processing delay) I agree with you that other parameters are used by RWRs to distinguish lock vs search, etc. That being said, are you assuming that the STT segments in SAM should have different radar parameters than a normal STT? Given the sensitive nature of these things, i think it best for DCS to draw its own lines in the sand for what constitutes a lock on and when a missile launch should be indicated. In this case, I believe the simplest and most probable answer is that the STT segment in SAM uses the same tracking, waveform (PRIs, PD, etc) and scan (antenna fixed on target, constant amplitude seen by RWR) as normal STT. We have no reason to believe that normal STT has a different signature than SAM STT segments (other than the STT stopping and starting every other ~2 seconds) Thanks for the kind words. Im currently reading up on U.S. RWR history and processing.

do trackfiles change color based on AIM-120 support, pitbull, etc in the block 50 modeled? Im curious if this is coming.

- VS search was mentioned by some of the ED staff more than a year ago. So maybe? I'd rather them finish up on RWS, LTWS, and TWS before moving to a mode no one will use. - IMO SAM mode should give a STT indication.. https://forums.eagle.ru/showthread.php?t=251079&page=2 But to answer your question, SAM works differently than TWS/LTWS. But if all you really want to know is if the Hornet will have the ability to launch AIM-120's without alerting the target, then yes. It will gain this capability when it gets full TWS. (LTWS is like a low quality TWS for RWS mode) - Silent wont restart your radar. Your radar mode and settings wont go away. you also still get data link tracks. So use SIL..

I firmly believe that the SAM mode will generate a STT indication.. It only takes an RWR a quarter of a second to process a lock on. And SAM mode has STT segments that last roughly 2 seconds.

yes, but i just recently got my reverb (first VR headset). I've only played with it the past week.

Perhaps this work can be applied to other applicable modules like the F-5.

Need help. The gauge text in the Hornet is sharp, clear and easy to read (all of them!) But the DDI text looks blurry unless I: 1. increase MSAA to 4x 2. adjust headset to a an incredibly small "sweet spot" that will misalign within seconds. (i have an IPD of 64) This is weird because text smaller than that of the DDIs text will come through sharp just fine. So I'm wondering if their are some optimizations or settings that I'm missing..? Does display resolution of "XXXX every frame" matter?