euthyphro Posted January 12, 2016 Posted January 12, 2016 This has happened to me a couple times now. I enter the JTAC coordinates and the target is 800 miles away. Anyone else have this bug or am I just doing something stupid?
Deezle Posted January 12, 2016 Posted January 12, 2016 The map sits on two different grids, 37T and 38T, if you take off from one and enter coordinates for the other without first changing the grid you will find yourself with the wrong coordinates. Type in 37T or 38T and click the corresponding LSK to change the grid you're entering coordinates for. You must change the grid before entering the MGRS coordinates. Intel 9600K@4.7GHz, Asus Z390, 64GB DDR4, EVGA RTX 3070, Custom Water Cooling, 970 EVO 1TB NVMe 34" UltraWide 3440x1440 Curved Monitor, 21" Touch Screen MFD monitor, TIR5 My Pit Build, Moza AB9 FFB w/WH Grip, TMWH Throttle, MFG Crosswinds W/Combat Pedals/Damper, Custom A-10C panels, Custom Helo Collective, SimShaker with Transducer
Blech Posted January 12, 2016 Posted January 12, 2016 Hi, :dunno: Target GRID # Preselected GRID e.g., 38T # 37T [ame] [/ame]
OttoPus Posted March 25, 2016 Posted March 25, 2016 This has happened to me a couple times now. I enter the JTAC coordinates and the target is 800 miles away. Anyone else have this bug or am I just doing something stupid? Hi, I'm experiencing the same issue in Kutaisi area. To reproduce the issue: - takeoff from kutaisi - few miles away (3-8 nM) try to input into cdu a new waypoint with GG XX ( i.e. GG75) - the waypoint should be few miles south west from Kutaisi but EGI shows a point 800 miles North away - No issues with other quadrants (i.e. LM, KM, and so on)
MadDog-IC Posted March 25, 2016 Posted March 25, 2016 Hi, I'm experiencing the same issue in Kutaisi area. To reproduce the issue: - takeoff from kutaisi - few miles away (3-8 nM) try to input into cdu a new waypoint with GG XX ( i.e. GG75) - the waypoint should be few miles south west from Kutaisi but EGI shows a point 800 miles North away - No issues with other quadrants (i.e. LM, KM, and so on) Read the above posts, take note of the 37T or 38T, if your that far away from the cdu entry, this is your problem, change it from 38T to 37T or if it is 37T change it to 38T, this map reference is normally specified with any map coordinates, but not always, especially as you just did it off the cuff. Cheers, Ian. Asus p877v-pro, Intel I7 3770k 4.2ghz, 32gb Ripjaw X ram, Nvidia RTX-2070 Super, Samsung 32" TV, Saitek x52 pro Joystick and Combat rudder pedals, TrackIR 5, Win8.1 x64 with SSD and SSHD protected by (Avast AV). DCS Tech Support.
Gizzy Posted March 25, 2016 Posted March 25, 2016 (edited) There may be a problem with MGRS in the DCS map in the Senaki / Kutasisi area - at least the MGRS reference reported by the map is wrong in several 10km 'blocks'. How this relates to input with the A10 I have no idea but here is a small video illustrating a possible error or bug... ? Best viewed full screen - it shows the DCS map zoomed into the Senaki / Kutasisi area. Look at the top left corner MGRS reference as the mouse is moved from GG48 across to LM08 In MGRS GG58 the reference is shown as KM68 and so on until you reach LM08 and it then shows true. The map shows the 37T / 38T overlap at GG98 / LM08 but in this example GG58 to GG98 are shown as being KM's [ame]https://www.youtube.com/watch?v=qEzCAzbcRIE[/ame] Edited March 25, 2016 by Gizzy
Recommended Posts