reported F/A-18 Markpoints erroneously saving elevation in meters instead of feet

[jbiebes]

In the latest update (2.9.9.2280), F/A-18 Markpoint function is erroneously saving target elevation in METERS instead of FEET (but is still labeling it as FEET).  When the markpoint is recalled, it is no longer pointing at the actual target.  Occurs with both ATFLIR and Litening pod (and likely any markpoint generated from any source).

e.g. Min-Vody runway actual elevation = 1050 ft.  After targeting and hitting MK1, the markpoint elevation is 320 FEET.

 

FA-18 Markpoint Elevation Bug.trk

[Alex_Weyland]

Confirmed. Track added.

f-18_brokenelevation_markpoints.trk

[Lord Vader]

Hey @jbiebes

Weird one. Thanks for letting us know. Reported internally. 

[Rufuz64]

If I understand this correctly, the result should be that markpoints are offset if they are set from the side. This has been confirmed in a test.
- Designated a target with the ATFLIR and set a markpoint MK1
- Undesignated
- Designated the Markpoint MK1 with WPDSG
Result: The pod immediately jumps away from the target.

null

Edited November 2, 2024 by Rufuz64

[Phantom711]

vor einer Stunde schrieb Rufuz64:

 

If I understand this correctly, the result should be that markpoints are offset if they are set from the side. This has been confirmed in a test.

 

This could be a bug. But it could also be „correct as is“ if it is meant to portray some inaccuracies in target location if looking at it from an angle and also slight inaccuracies in terrain elevation data.

[Rufuz64]

1 hour ago, Phantom711 said:

This could be a bug. But it could also be „correct as is“ if it is meant to portray some inaccuracies in target location if looking at it from an angle and also slight inaccuracies in terrain elevation data.

You mean ~10 m could be an "inaccuracy"?

[Phantom711]

@Rufuz64

vor 3 Stunden schrieb Rufuz64:

- Designated a target with the ATFLIR and set a markpoint MK1
- Undesignated
- Designated the Markpoint MK1 with WPDSG

If you are actually doing this in relatively quick succession, I think the error should not be as big as it apparently is. Which would then probably make this a bug.

 

vor einer Stunde schrieb Rufuz64:

You mean ~10 m could be an "inaccuracy"?

Well, yes, it can be inaccurate. Google "DTED (Digital Terrain Elevation Data)". This is now talking real life...don´t know how that is reflected in DCS.

Edited November 2, 2024 by Phantom711

[Harker]

6 hours ago, Rufuz64 said:

If I understand this correctly, the result should be that markpoints are offset if they are set from the side. This has been confirmed in a test.
- Designated a target with the ATFLIR and set a markpoint MK1
- Undesignated
- Designated the Markpoint MK1 with WPDSG
Result: The pod immediately jumps away from the target.

null

 

I tested myself, and what you're seeing here is the reported bug in the OP. MK saves the elevation in FT, but with with the value of M. In this case, the elevation was probably 33FT, and was saved as 33FT -> 10M -> 10FT, as per the bug.

The pod is looking at the same LAT LONG coordinates, but it looks offset because it's looking "below" the ground elevation. So, nothing to do with DTED or drift etc, this is just the bug at work.

[Phantom711]

@Rufuz64 @Harker

Alright...it all starts to make sense now. I didn´t read rufuz´post as providing an example of the problem at hand but rather another unrelated problem. And my thought process was more like, if the system saves 33ft to be 33m, then the MK point would be above the previous designation. But as I said, it makes sense now....

My bad for causing more confusion. (Even though I believe, nothing I said is actually wrong, it just isn´t the cause of this particular problem).

[Rufuz64]

nullIf you repeat the same test, but now fly exactly over the target, there is no deviation. A false altitude is therefore definitely stored.

[jbiebes]

Worth noting that you’re testing at an airfield close to sea level, so you’re getting a minor deviation of the TPOD (which is looking slightly below ground level), but try this on the Syria map at 3000 ft, you won’t even see the target at all since the magnitude of the error is much greater.

[BIGNEWY]

Thank you for your reports a fix is being tested internally for a future patch.