resolved TGPs not inaccurate [user error/wrong elevation set]

[AstonMartinDBS]

Mission setup:

• Map: Caucasus
• Targets: 4 static tanks
• Hornet: each tank has a WP 1 - 4 at ground level

Flight:

• HSI/DATA/PRECISE activated
• JDAM full aligned prior release

Issue:

WPDSG doesn't point the TGPs exactly to the selected WP/Target, that counts for the LITENING as well as for the ATFLIR

Each WP shown in the ATFLIR is several meters offset from the ME WP, which has been set exactly on target (and at ground level, of course).

Tracks:

• (removed)

Notes:

• This 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 A-10C II (see https://forum.dcs.world/topic/316657-tgp-inaccurate/) as well. So the problem appears also in other modules and is might related to the core.
• Also the JDAMS are quite inaccurate, too. Only two of four JDAMs hitted their target directly. But I don't know if this inaccuracy is realistic or not.

 

Edited January 7, 2023 by AstonMartinDBS

[Tusky]

Can you post the .miz file so that we can give it a try? 

[razo+r]

4 minutes ago, Tusky said:

Can you post the .miz file so that we can give it a try? 

the .miz file is included in a .trk. A .trk can be opened with the mission editor.

[AstonMartinDBS]

16 hours ago, razo+r said:

the .miz file is included in a .trk.

Exactly.

16 hours ago, Tusky said:

Can you post the .miz file so that we can give it a try? 

Sure, here's the tiny mission file (corrected version for A-10C II and F/A-18C): CA A-10C-II F-16C FA-18C TGP Test.miz

Edited January 8, 2023 by AstonMartinDBS

[Phantom711]

I am nowhere near my PC so I could not watch the trk files nor try to reproduce the issue.

First thing that would come into my mind would be, that you might have gotten something mixed up with the coordinates. People often get confused with the different formats for Lat/Long. (i.e.: Degrees/Minutes/Seconds vs Degrees/Minutes/Decimalminutes)

[AstonMartinDBS]

26 minutes ago, Phantom711 said:

First thing that would come into my mind would be, that you might have gotten something mixed up with the coordinates.

Impossible, the WPs have been placed in the ME, exactly over the four targets and at ground level.

[Phantom711]

vor 8 Minuten schrieb AstonMartinDBS:

Impossible, the WPs have been placed in the ME, exactly over the four targets and at ground level.

Ah ok…

[razo+r]

2 hours ago, AstonMartinDBS said:

Each WP shown in the ATFLIR is several meters offset from the ME WP, which has been set exactly on target (and at ground level, of course).

 

 

JDAM page and HSI Data page shows elevation 41m but the elevation of those T-90s is 13m. So the waypoint is not on ground.

[AstonMartinDBS]

2 hours ago, razo+r said:

JDAM page and HSI Data page shows elevation 41m but the elevation of those T-90s is 13m.

Great catch - but that's sadly not the solution (as marked by yourself), but the way to the source of the issue.

 

2 hours ago, razo+r said:

So the waypoint is not on ground.

All four WPs have been proper set to ground level (36 ft/~11 m) in the ME (that only counted for the F-16C in the test mission):

After manually correcting the wrong transferred elevation of the WPs in the Hornet (HSI/DATA/UFC) the ATFLIR has been perfectly aligned:

As the problem occurs in several modules (at least in the Hornet, Viper and Warthog), there might be a problem in the core by transferring the elevation from the ME into 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 (see above ME screenshot).

 

 

Edited January 7, 2023 by AstonMartinDBS

[Tusky]

I usually set all coordinates on the deck by the UFC (I never use preset waypoints) but with so many missions available and DTC on the way, it is worth having a look...

Edited January 7, 2023 by Tusky

[AstonMartinDBS]

3 minutes ago, Tusky said:

If the altitudes you set in the ME get sometimes corrupted when transfered to the ATFLIR/TGP, it is worth a look.

It was my fault, there's no problem by transferring the elevation from the ME to the planes:

24 minutes ago, AstonMartinDBS said:

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 (see above ME screenshot).