clanitho Posted April 18, 2022 Share Posted April 18, 2022 Hello, I don't understand why the standard JTAC of DCS gives me wrong coordinates of my targets while the CTLD script gives me the exact coordinates. In the mission editor, the coordinates of SAM 13 are 36SYB57966833, CTLD gives me the same coordinates, but the standard JTAC gives me YB 580834. On the Caucasus map, I don't have this problem, the standard JTAC works correctly. Is it related to the Syrian map? I attach my test mission (AH-64D), if you can test it and give me an explanation thank you very much. Translated with www.DeepL.com/Translator (free version) syria_test_2_AH-64D.miz MSI Z97 Gaming 5 - Intel I7 4790K - Artic cooling freezer 7 pro rev 2 - GSKILL 32 Go - SSD Crucial M5 120 go - SSD Crucial 2To - HDD western digital caviar blue 1 TO - Gigabyte GTX 1070 Gaming G1 - Windows 10 home 64 bits Link to comment Share on other sites More sharing options...
Ramsay Posted April 26, 2022 Share Posted April 26, 2022 (edited) On 4/18/2022 at 3:07 PM, clanitho said: I attach my test mission (AH-64D), if you can test it and give me an explanation thank you very much. I had to install the "SAM Asset Pack" mod to test and use the ME to find the JTAC's radio frequency (VHF 133 MHz) but otherwise the JTAC's coordinates seems good. On 4/18/2022 at 3:07 PM, clanitho said: In the mission editor, the coordinates of SAM 13 are 36SYB57966833, You've missed off the last 2 digits of the northing. The co-ordinates in the mission editor of the SA-13 are "36 S YB 57966 83389" On 4/18/2022 at 3:07 PM, clanitho said: JTAC gives me YB 580834 This is correct and simply the previous 10 digit MGRS rounded to the nearest 6 digit MGRS (3 easting and 3 northing) = YB 580 834 AFAIK IRL MGRS coordinates are truncated, not rounded (as 6 digits "define" a 100m grid square where the target can be found) - perhaps this changes for stuff that you are going to drop a bomb/missile on. With regards to the Apache, it takes 8 digit MGRS coordinates, so YB 580 834 --> YB 5800 8340, and is input/edited as "36SYB58008340". Here, I used the TSD cursor to create a target point near the target area and edited it's coordinates to match the 9-line, before "placing it" Edited April 27, 2022 by Ramsay 2 i9 9900K @4.7GHz, 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 10 Pro x64, 1920X1080 Link to comment Share on other sites More sharing options...
clanitho Posted April 27, 2022 Author Share Posted April 27, 2022 @Ramsay, Thank you for responding and spending time on my problem. MSI Z97 Gaming 5 - Intel I7 4790K - Artic cooling freezer 7 pro rev 2 - GSKILL 32 Go - SSD Crucial M5 120 go - SSD Crucial 2To - HDD western digital caviar blue 1 TO - Gigabyte GTX 1070 Gaming G1 - Windows 10 home 64 bits Link to comment Share on other sites More sharing options...
Recommended Posts