jppsx Posted March 19, 2021 Posted March 19, 2021 (edited) there trk file showing the issue whit the com center and com tower M , there probably other building/antenna causing the problem . command center lock isue .trk com tower M lock isue .trk Edited March 19, 2021 by jppsx
Ramsay Posted March 19, 2021 Posted March 19, 2021 AFAIK it is caused by the size of the antenna (and supporting guy wires) "collision" box and is a DCS "world" issue, rather than JF-17 issue i.e. it effects other modules/targeting pods. IRL it's common for TGP's to "lock" onto the wrong (brightest/darkest) contrast and they often have ways to offset their laser designator to the compensate. While the lock/laser designation issues we see with guy wires are not totally realistic, they are IMHO analogous to RL TGP problems. It's possible ED's FLIR improvements will change things for the better but we'll have to wait and see. i9 9900K @4.8GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 11 Pro x64, Odyssey G93SC 5120X1440
jppsx Posted March 19, 2021 Author Posted March 19, 2021 anyway to mark a target for gps bomb whitout locking it ?
Alesia_Aisela Posted March 22, 2021 Posted March 22, 2021 On 3/19/2021 at 1:04 PM, jppsx said: anyway to mark a target for gps bomb whitout locking it ? You do not need to be in point track to launch an IAM at your desired target. Just enter area track and pan over your target, confirm the coordinates on the Tpod against the ones shown on the IAM subscreen (normally on the lower part of the right mfd by default) and release.
Recommended Posts