ExNusquam Posted April 23, 2020 Posted April 23, 2020 The radar currently has no range gate on targets in MEM mode. The radar should extrapolate last known track motion and age when attempting to reacquire. Current behavior would be extremely susceptible to range-gate pull-off DECM, a technique employed since the 60's. Attached is a track where the STT lock jumps 12+NM (well beyond last known track position/vector).STT_HPRF_No_RangeGate.trk 476th vFG/510th vFS
Santi871 Posted April 28, 2020 Posted April 28, 2020 Hey, I can reproduce this quite clearly in OB, but there's currently a bug in the dev build that prevents me from reproducing there, so I have the track and report ready, and when the bug that's in the dev build is fixed, I'll circle back on this and report it.
hein22 Posted April 28, 2020 Posted April 28, 2020 Can you guys elaborate more about this? I don't seem to understand what this is all about but I'm interested in. Stay safe
ExNusquam Posted April 29, 2020 Author Posted April 29, 2020 https://en.wikipedia.org/wiki/Range_gate_pull-off 476th vFG/510th vFS
hein22 Posted April 29, 2020 Posted April 29, 2020 https://en.wikipedia.org/wiki/Range_gate_pull-off How does that relate to DCS? We don't have that pulse feature to deceive others. Sorry I don't understand. Stay safe
Swift. Posted June 5, 2020 Posted June 5, 2020 How does that relate to DCS? We don't have that pulse feature to deceive others. Sorry I don't understand. The bug isn't about the pull-off jamming, but about the lack of a range gate. Meaning our radar might switch between two targets on the same azimuth and elevation but at different ranges. 476th Discord | 476th Website | Swift Youtube Ryzen 5800x, RTX 4070ti, 64GB, Quest 2
Mongoose83 Posted June 27, 2021 Posted June 27, 2021 Came here from the locked topic "Target locks for BVR, RWS or TWS keep and keep disappearing for no reason" ETA for fix?
Recommended Posts