jwbflyer Posted February 3 Posted February 3 Went up against a JF-17 twice BVR Never saw the first guy - no radar return, died. second guy never saw him until about 20% inside of R-Max, died. is anyone else having issues seeing a JF-17 on radar? i literally kept driving into them just to see when the stupid radar would give a return and only saw the second guy right when I already got his missile warning.
Hulkbust44 Posted February 3 Posted February 3 What was the altitude difference? Sent from my moto g stylus 5G (2022) using Tapatalk
Muchocracker Posted February 3 Posted February 3 (edited) 1 hour ago, jwbflyer said: Went up against a JF-17 twice BVR Never saw the first guy - no radar return, died. second guy never saw him until about 20% inside of R-Max, died. is anyone else having issues seeing a JF-17 on radar? i literally kept driving into them just to see when the stupid radar would give a return and only saw the second guy right when I already got his missile warning. Cant't really help you if you don't give us trackfiles showing what you're running into. Check your scan volume in azimuth and elevation to make sure the target is within the frame. Reduce the azimuth setting to decrease the frame time and get more hits to build trackfiles at long range. And use the correct PRF for the target's aspect. I use the radar mutliple times a week and have no problems detecting and tracking fighters at +60nm. Edited February 3 by Muchocracker 1
jwbflyer Posted February 3 Author Posted February 3 I was 40s he was 30s I had a 40az and 4bar with his alt in heart of the radar elevation i put it on autopilot and just worked the radar to focus on trying to get a return nothing ….and this is specifically only the JF-17 i was locking other jets fine
Muchocracker Posted February 3 Posted February 3 (edited) Collect a trackfile that demonstrates the issue and post it. Edited February 3 by Muchocracker
Muchocracker Posted February 3 Posted February 3 (edited) semi-stable trackfile built at 77nm in 4/40 HPRF. Edited February 3 by Muchocracker
rob10 Posted February 4 Posted February 4 19 hours ago, jwbflyer said: I was 40s he was 30s I had a 40az and 4bar with his alt in heart of the radar elevation i put it on autopilot and just worked the radar to focus on trying to get a return nothing ….and this is specifically only the JF-17 i was locking other jets fine I just tried this on our squadron server, JF at about 20K so I went up to 30+K. No problem locking and holding him (actually 2 of them) at 50+ nm. Double check your radar altitude and that you're in an appropriate PRF. Really sounds like either he's notching you (MED PRF can help) or you're not on ideal PRF for distance (HI for longer range, MED for <20 nm)
jwbflyer Posted February 5 Author Posted February 5 (edited) Reference the last 20 minutes or so of the file- it’s the last engagement. was able to easily replicate it again tonight, if the JF-17 is lower, then I'll be blind until short range or I sacrifice altitude and dive. This is happening every time I fight a JF-17. in this scenario once AWACS called him about 40nm, I chose to dive and see if that would change anything- it did, I was able to see him and lock him. Previous engagements i did not dive and the range at which he appeared was shorter. also don’t know if he was jamming. SDCS_Syria3-20250204-190552.trk - Shortcut.lnk Edited February 5 by jwbflyer
Muchocracker Posted February 5 Posted February 5 (edited) 6 hours ago, jwbflyer said: Reference the last 20 minutes or so of the file- it’s the last engagement. was able to easily replicate it again tonight, if the JF-17 is lower, then I'll be blind until short range or I sacrifice altitude and dive. This is happening every time I fight a JF-17. in this scenario once AWACS called him about 40nm, I chose to dive and see if that would change anything- it did, I was able to see him and lock him. Previous engagements i did not dive and the range at which he appeared was shorter. also don’t know if he was jamming. SDCS_Syria3-20250204-190552.trk - Shortcut.lnk 1.61 kB · 6 downloads this file you posted is a shortcut and not the actual .trk Edited February 5 by Muchocracker
Muchocracker Posted February 5 Posted February 5 (edited) 2 JF-17's 1 at 30 thousand and the other 5 thousand. Both of them the radar starts getting low Pd hits around the same time and eventually become semi-stable trackfiles in that 80-75nm area like the shot i showed before. Same scan volume setting and HPRF as my previous screenshot. You'd know if he's jamming by looking for a [JA] symbol in the dugout box at the top of the radar page along the bearing line of the target. The hornet radar has not had any imposed look-down penalties since the start of the phased radar overhauls, ED said as much in the phase 2 whitepaper that look-down penalties would be reintroduced with phase 3. Edited February 5 by Muchocracker 1
jwbflyer Posted February 5 Author Posted February 5 Apologies first time trying a track fike ill fix when I get home
jwbflyer Posted February 5 Author Posted February 5 it was 120mb ill try to get a new shorter one today
ED Team BIGNEWY Posted February 15 ED Team Posted February 15 Hi check out this video it may help Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal
Recommended Posts