Harlikwin Posted June 5, 2020 Posted June 5, 2020 So. Question for the team. Currently the Jeff Radar instantly knows the vector of the enemy airplane, and it seems, well "gamey" in that no other radar instantly updates the vector information of target in TWS modes, there is always a "lag" as the track file is built an interpreted. i.e. when I shoot someone down in TWS or DTT I can basically see the velocity vector just start to spin and flop around which I don't think is accurate for this type of radar (maybe for an AESA). I can't see this sort of behavior on either the Viper radar or the F18 radar. I assume the radar is still a WIP? Will this be fixed. New hotness: I7 9700k 4.8ghz, 32gb ddr4, 2080ti, :joystick: TM Warthog. TrackIR, HP Reverb (formermly CV1) Old-N-busted: i7 4720HQ ~3.5GHZ, +32GB DDR3 + Nvidia GTX980m (4GB VRAM) :joystick: TM Warthog. TrackIR, Rift CV1 (yes really).
falcon_120 Posted June 5, 2020 Posted June 5, 2020 Good point. The JF17 is a great module but definetely the radar seems quite optimistic in those aspects. Also in detection range btw given the jf17 small nose and size in general. Enviado desde mi SM-G950F mediante Tapatalk
foxwxl Posted June 6, 2020 Posted June 6, 2020 Yep, some feature will come online in later patch, like target acquisition pattern, scan-predict-scan pattern, etc Deka Ironwork Tester Team
sora_061 Posted June 6, 2020 Posted June 6, 2020 I may be wrong, but the target should be first scanned when bar passes through it. Then it predicts it movement until again the bar passes. The way it works in game, the updates are really fast in my point of view. It's like Radar can see the target real time even when the bar is not passing the target. I know Datalink would also update. But Donor aircraft also has to scan by bar, then there is latency. It should be like the ACM mode where there is delay locking target when the bar is not in the aircraft zone. Hope I can clear my doubt. Sent from my Redmi K20 Pro using Tapatalk
Recommended Posts