DSplayer Posted November 6, 2021 Share Posted November 6, 2021 (edited) With 2.7.7, the JF-17's detection range has stayed relatively the same but holding and acquiring tracks beyond ~40nm in look up and maybe ~30nm in look down has significantly diminished compared to 2.7.6. Sometimes when you're trying to bug someone that has a track file built in TWS beyond ~40nm or in a look down, it doesn't stay bugged and you'll drop the track pretty quickly (even if the target is hot). I'm a bit curious to how accurate the radar is now compared to the real deal or if it even is supposed to act this way. Edited November 6, 2021 by DSplayer -Tinkerer, Certified F-14 and AIM-54 Nut | Discord: @dsplayer Setup: i7-8700k, GTX 1080 Ti, 32GB 3066Mhz, Lots of Storage, Saitek/Logitech X56 HOTAS, TrackIR + TrackClipPro Modules: F-14, F/A-18, JF-17, F-16C, Mirage 2000C, FC3, F-5E, Mi-24P, AJS-37, AV-8B, A-10C II, AH-64D, MiG-21bis, F-86F, MiG-19P, P-51D, Mirage F1, L-39, C-101, SA342M, Ka-50 III, Supercarrier, F-15E Maps: Caucasus, Marianas, South Atlantic, Persian Gulf, Syria, Nevada Mods I've Made: F-14 Factory Clean Cockpit Mod | Modern F-14 Weapons Mod | Iranian F-14 Weapons Pack | F-14B Nozzle Percentage Mod + Label Fix | AIM-23 Hawk Mod for F-14 Link to comment Share on other sites More sharing options...
Napillo Posted November 20, 2021 Share Posted November 20, 2021 It appears so, Deka seems to be modeling radar more completely than any other airplane now, which gives it a bit of a disadvantage. Link to comment Share on other sites More sharing options...
Recommended Posts