Jump to content

Recommended Posts

Posted (edited)

MGRS coordinates (as shown on the DED after creating a markpoint or converting from LAT/LONG) are missing leading 0s, making the MGRS designation wrong.

For example, on the Caucasus map the LAT/LONG coordinate N42°27.715 E042°35.844 should be 38T LN 02463 03861 in MGRS, but instead the F-16 converts it to 38T LN 2463 3861, so the leading 0's are missing, resulting in a totally different coordinate.
It gets even more weird with an MGRS coordinate, where only one of the two blocks has a leading zero (38T LN 02463 43861), which results in a 9 digit MGRS designation (38T LN 2463 43861) in the F-16, which is totally invalid.

EDIT: Added track file below

Edited by QuiGon
  • Like 1

Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit

DCS Panavia Tornado (IDS) really needs to be a thing!

Tornado3 small.jpg

  • ED Team
Posted

Please include a track replay when reporting a bug. 

If memory serves me you can enter the MGRS and omit the leading zeros, but I will check in the morning.

smallCATPILOT.PNG.04bbece1b27ff1b2c193b174ec410fc0.PNG

Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status

Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal

Posted (edited)
8 hours ago, BIGNEWY said:

Please include a track replay when reporting a bug. 

If memory serves me you can enter the MGRS and omit the leading zeros, but I will check in the morning.

No, you can't omit the leading zeros (unless I have done it all wrong during my time in the army...).

LN 02463 03861 is a different place than LN 2463 3861.
And LN 02463 3861 ist just invalid as both blocks always need to have the same number of digits.

Check for yourself here: https://coordinates-converter.com/en/decimal/42.461914,42.597392?karte=OpenStreetMap&zoom=11
(Use "Degrees Minutes" for the F-16 Lat/long format and "MGRS/UTMREF" for MGRS)

I'll create a track file when I can.

Edited by QuiGon

Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit

DCS Panavia Tornado (IDS) really needs to be a thing!

Tornado3 small.jpg

Posted (edited)

Here's the track file, using the coordinates from the theoretic example I gave above (there's also a rounding inaccuracy for the last digits in the F-16 resulting in LN 2462 3860, but that doesn't really matter).
I used marks on the F10 map to show the results of the erronous conversion to MGRS that resulted in a positon error of 22nm(!) because of the missing leading zeros.

MGRS error.trk

Edited by QuiGon

Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit

DCS Panavia Tornado (IDS) really needs to be a thing!

Tornado3 small.jpg

  • ED Team
Posted

Reported thanks. 

Yes looks like any MGRS coordinate that leads with zeros is showing incorrectly. 

example 

If MGRS coordinates are 
38T LM 00296 00516

the DED shows 
254 829
which is incorrect

  • Like 1

smallCATPILOT.PNG.04bbece1b27ff1b2c193b174ec410fc0.PNG

Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status

Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...