[LATER IN EARLY ACCESS] Possible Waypoint Designate Inaccuracy

[045]

In a past mission, I noticed waypoint designate caused my Maverick to slew well short of the waypoint (almost like it lacked elevation data like in the Ka-50's PVI-800 Nav Tgt system). Then later that mission when doing an auto bombing run, my bombs fell remarkably short and wide and in a similar manner to how the Maverick's slew deviated. The bombs missing by a similar margin is what made me think it might not have been pilot error.

I checked the track file but it had me run into the drink well before that point (which totally didn't happen... this time). I tested it on another mission and took the attached screenshots. The offset from the waypoint is less extreme than I remember in the first mission, but that was a stressful mission so I might be misremembering.

I am attaching both mission files and the track file for the first mission in question, just in case it's a fault of my computer that the track deviates from the original.

Anapa - Multi-Practice - Wypt Inaccuracy.miz

[045]

I have attached the first mission file to this post. The track file is too large unfortunately.

26th 1989-DEAD - Operation T-Off.miz

[Tholozor]

Not really a bug, just a missing feature for the Hornet.

 

The MGRS coordinates of your waypoint in the first mission file are: 37T CK 83703 72231, this is accurate down to 1 meter. When converted into DMS format, the coordinates turn into:

N 44°53'38.4202"

E 37°31'37.7402"

 

This is consistent with the Lat/Long coordinates you're seeing in the editor. The problem exists within the Hornet's systems, since at the moment it can't utilize MGRS coordinates. Since you can't input coordinates longer than 6 digits, the decimal remainders are truncated, resulting in coordinates of:

N 44°53'38"

E 37°31'37"

Edited March 6, 2019 by Tholozor

[045]

I have reproduced and taken screenshots of it in the first mission we noticed it in, this better shows the disparity and this track file is small enough to fit. The differences this time were that is was in singleplayer, I didn't have the identical loadout, didn't do my fire tests and my jet was invisible, but the results were functionally identical.

 

 

The F10 view shows the location of the waypoint as entered in the mission editor. The distance between the point on the ground the Mav's seeker head auto slewed to is about 3km, but what I found interesting is that the point got closer to the waypoint as my jet closed, almost as if it were looking at a point below the surface (why I originally thought of the Ka-50).

 

To clarify, I did undesignate, cage my Mav and used waypoint designate again with the same results.

Hornet Wypt Dsg.trk

[045]

Thanks for the info Tholozor.