AstonMartinDBS Posted January 7, 2023 Posted January 7, 2023 (edited) Mission setup: Map: Caucasus Targets: 4 static tanks Hog: each tank has a WP 1 - 4 at ground level Issue: TGP doesn't slave exactly to the WP/STP/Target. The TGP points far offset from the STP (> 20 m) Track: (removed) Note: The same issue occurs in the F-16C (see https://forum.dcs.world/topic/316221-jdam-and-targets-of-opportunity/?do=findComment&comment=5124926) and in the Hornet (see https://forum.dcs.world/topic/316650-tgps-inaccurate/) as well. So the problem appears also in other modules and is might related to the core. Edited January 7, 2023 by AstonMartinDBS [Modules] A-10C, A-10C II, AH-64D, F-4E, F-14A/B, F-16C, F/A-18C, FC3, Ka-50, P-51D, UH-1H, CA, SC [Maps] PG, NTTR, Normandy, Sinai, Syria, TC [OS] Windows 11 Pro [PC] MSI Pro Z790-A, i9-13900K, 128 GB DDR5, RTX 4090 24 GB GDDR6X, 2 x SSD 990 PRO 2 TB (M.2), Corsair 5000D Airflow, HX1500i, H150i RGB Elite, Acer X28, TM HOTAS Warthog (Grip@WarBRD Base), MS SW FFB2, Thrustmaster TFRP, TrackIR 5 & TrackClip Pro [Checklists] A-10C, F-16C, F/A-18C, AH-64D, Ka-50, UH-1H
Solution razo+r Posted January 7, 2023 Solution Posted January 7, 2023 The steerpoint page indicates a waypoint elevation of 136 feet is set while the tanks are at 42 feet. Your waypoint doesn't seem to be on the ground. 1
ASAP Posted January 7, 2023 Posted January 7, 2023 Like Razor said, it looks like an elevation error. Try lasing the target and taking a mark. Then you can update that mark to a steerpoint and it should be accurate. Or you can lase the thing where your steerpoint should be, read the elevation off the TGP screen and manually punch that into the waypoint page. The most obvious indicator of an elevation error when looking at your targeting pod is the will look like the pod is wondering around the general area of the target when it's slaved to a steerpoint (or may wondering nowhere near it depending on how big the elevation error is) 1
AstonMartinDBS Posted January 7, 2023 Author Posted January 7, 2023 (edited) Thanks @razo+r & @ASAP! I think, we've located the source of the issue. The elevation has been proper set to the ground level (36 ft) in the ME. But there might be a problem by transferring the correct elevation of the WP from the ME to the planes. Sorry, my bad. By copying the original F-16C to the F/A-18C and A-10C II for testing purposes the original WP elevation of 36 has changed to 136 - and sadly I didn't double check this on the other planes. Edited January 7, 2023 by AstonMartinDBS [Modules] A-10C, A-10C II, AH-64D, F-4E, F-14A/B, F-16C, F/A-18C, FC3, Ka-50, P-51D, UH-1H, CA, SC [Maps] PG, NTTR, Normandy, Sinai, Syria, TC [OS] Windows 11 Pro [PC] MSI Pro Z790-A, i9-13900K, 128 GB DDR5, RTX 4090 24 GB GDDR6X, 2 x SSD 990 PRO 2 TB (M.2), Corsair 5000D Airflow, HX1500i, H150i RGB Elite, Acer X28, TM HOTAS Warthog (Grip@WarBRD Base), MS SW FFB2, Thrustmaster TFRP, TrackIR 5 & TrackClip Pro [Checklists] A-10C, F-16C, F/A-18C, AH-64D, Ka-50, UH-1H
Recommended Posts