Jump to content

Recommended Posts

Posted

Didn't see this anywhere else so i figured i would bring it up hopefully its not a repost.

the F10 map is not displaying the appropriate coordinates for DDM (degrees minutes decimal minutes ) i would imagine that this could be an explanation for some of the GPS guided munitions not tracking appropriately maybe not however an error in the system regarding the exact location of an object can be rather detrimental to a game that relies heavenly on precision. however you can see by the crater photo that there is a significant enough deviation in coordinates. they were GBU-38's dropped from 11K off an A-10C at approximately 260ish knots. a set of 3 each were dropped and had a nice grouping at each location. all of the other coordinate systems appear to be functioning correctly. hope this helps!:joystick:

Converter.thumb.PNG.774666b5173f973d09af8a8a812a5972.PNG

1242023204_dmsfrommap.PNG.8ac79b77a748fa52d2d13d595232ba70.PNG

1308320379_ddmfrommap.PNG.4ea9db5b3c42ac1cbe408c3ac9b0b491.PNG

1266061031_gbu38test.PNG.94332f9741201cd4bde8622aec3f7771.PNG

Discord: SSG HALO#1394

Modules: A-10C, AJS-37, Black Shark 2, M-2000C, UH-1H, F-16C, F/A-18C, L-39, AV-8B, FC3, F-5E, F-14B, P-51, Mig-29, Persian Gulf, Nevada, Normandy, Combined Arms.

Posted (edited)
The GBU-38 does not have a CEP of 0. It does not guide like a GBU-12 tracking a laser spot.

TL;DR:

 

This report is not about the GBU-38, it is about the F10 Map and how it displays inaccurate co-ordinates when using DDM (degrees decimal minutes).

 

If you use DMS (degrees minutes seconds), the co-ordinates step @ 1 second intervals as you move your cursor.

 

If you use MGRS, the co-ordinates step @ 1m intervals

 

If you use DDM, the co-ordinates step @ 0.016 intervals, rather than 0.001 no matter how zoomed in you are on the F10 map*.

 

What seems to happen is the position is converted to DMS and the integer seconds then divided by 60 to give DDM but losing precision.

 

*Note: DDM increments correctly in the Mission Editor and Mission Planner

 

Detail:

 

Consider one of the static helicopters @ Batumi

 

It's co-ordinates are:

 

X/Y    = X-00355964 Z+00618011
MGRS   = 73 T GG 17276 09501
DMS    = N 41°36'27"    E 41°36'26"
DMS.SS = N 41°36'27.57" E 41°36'26.91"

DDM    = N 41°36.450'   E 41°36.433' => N 41°36'27"    E 41°36'26"

 

but it's 'real' DDM to 3 decimal places (+/- 6 ft) should be

 

• N 41°36'27.57" = N 41° 36'+ (27.57/60)' = N 41°36.460'

• E 41°36'26.91" = E 41° 36'+ (26.91/60)' = E 41°36.449'

 

The F10 map Northing error is:

 

• 36.460 - 36.450' = 0.010' (approx 60ft)

 

the F10 map Easting error is:

 

• 36.449 - 36.433' = 0.016' (approx 90ft)

 

Tested using Open Beta 2.5.5.32299

Edited by Ramsay
Add DCS version number

i9 9900K @4.8GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 11 Pro x64, Odyssey G93SC 5120X1440

Posted (edited)
But you dropped three bombs on one point, right?

The OP dropped sets of 3 bombs on several targets.

 

All I’m saying is that there’s a pretty good chance no two (or three) 38s will ever hit precisely the same spot.

 

AFAIK the OP is satisfied with the spread of each group.

 

... a set of 3 each were dropped and had a nice grouping at each location.

 

The problem is that when using DDM co-ordinates from the F10 map, it displays the wrong co-ordinates and the grouping is not at the target location(s).

 

NZGCvOk.jpg

Edited by Ramsay
Add explanatory picture/diagram

i9 9900K @4.8GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 11 Pro x64, Odyssey G93SC 5120X1440

Posted

ahhhh

 

So its a game calculation resolution issue not an actual calculation error how silly well at least it makes sense I prefer the hand calculations anyway. Thanks for the response Ramsay and also thanks for trying to clarify it for Emmy they missed the issue completely lol.

Discord: SSG HALO#1394

Modules: A-10C, AJS-37, Black Shark 2, M-2000C, UH-1H, F-16C, F/A-18C, L-39, AV-8B, FC3, F-5E, F-14B, P-51, Mig-29, Persian Gulf, Nevada, Normandy, Combined Arms.

Posted (edited)
So its a game calculation resolution issue not an actual calculation error how silly well at least it makes sense I prefer the hand calculations anyway.

Retesting in Open Beta 2.5.5.32533, F10 map DDM co-ordinate precision has been fixed.

 

Using DDM, the F10 map cursor co-ordinates now step @ 0.001 intervals and match the ME and Planner co-ordinates.

 

Note: in Open Beta 2.5.5.32533

 

 

• Map coordinates in status bar doesn't changes after format change until user moves mouse - fixed

 

is only true for the ME and Planner.

 

Changing the co-ordinate format (LAlt+Y) in the F10 map while playing - still needs the user to move their mouse to take effect.

Edited by Ramsay
Add note re: Open Beta changelog

i9 9900K @4.8GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 11 Pro x64, Odyssey G93SC 5120X1440

  • Recently Browsing   0 members

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