Leg2ion Posted January 15, 2022 Posted January 15, 2022 (edited) I have just 'upgraded' the single missions to A10C2 by opening up the missions in ME, and selecting A10c2 and an appropriate loadout - but not sure if they are working correctly. I had an issue with a mission - possibly 'Shooting Gallery'- that involves JTAC support. The 9 line co-ordinates seem messed up, in that if I create a waypoint from them the target is around 80 - 90 miles away. Then after around 30 seconds the target is reported as destroyed with an abort message. If I offer support again the same re-occurs. I watched the map after getting a 9 line, and sure enough a missile seemingly appears out of nowhere and takes the target out. I see here DCSW A-10c - Single Player Missions (Patch for game) (v2.55x) (digitalcombatsimulator.com) Maddog uploaded new mission files for 2.5 as they were broken - does that still stand for 2.7 or are they all now working correctly? Edited January 15, 2022 by Leg2ion AMD Ryzen 5 5600X; ASUS ROG Strix X570-F, Corsair Vengeance 64 GB (2x 32GB) 3600MHz; Seagate FireCuda 510 500GB M.2-2280 (OS); Samsung 860 EVO 2TB M.2-2280 (DCS); MSI GeForce RTX 3090 SUPRIM X 24GB OC GPU. TM Warthog Hotas; T.Flight Pedals; DelanClip/Trackhat.
Yurgon Posted January 16, 2022 Posted January 16, 2022 5 hours ago, Leg2ion said: The 9 line co-ordinates seem messed up, in that if I create a waypoint from them the target is around 80 - 90 miles away. That's odd. Those coordinates should be 850 miles away! Kidding aside, the JTAC doesn't take the time to tell you which grid zone the target will be in, and assumes all pilots know this by heart. When you check this map on Wikipedia, you'll see how the border between grid zones 37T and 38T runs through western Georgia. It just so happens that most of your preset waypoints are in grid zone 38T, while the JTAC's targets are in 37T. Long story short, before you punch in the coords for the new target waypoint, change the grid zone to "37T" in the line above the MGRS coord. Afterwards, when you punch in GG 328 675, it'll be some 15 or so miles away. 5 hours ago, Leg2ion said: Then after around 30 seconds the target is reported as destroyed with an abort message. I just flew the stock mission with the A-10C module and didn't notice anyone else shooting; TacView confirms I was the only shooter. We'll need a track or a TacView to see what happened in your case. And when you modify a mission, of course uploading it can also help us run it and check for ourselves. 1
Leg2ion Posted January 16, 2022 Author Posted January 16, 2022 Thanks @Yurgon - all comments noted. Once 'aloft' again I will see what I can get... AMD Ryzen 5 5600X; ASUS ROG Strix X570-F, Corsair Vengeance 64 GB (2x 32GB) 3600MHz; Seagate FireCuda 510 500GB M.2-2280 (OS); Samsung 860 EVO 2TB M.2-2280 (DCS); MSI GeForce RTX 3090 SUPRIM X 24GB OC GPU. TM Warthog Hotas; T.Flight Pedals; DelanClip/Trackhat.
Leg2ion Posted January 16, 2022 Author Posted January 16, 2022 @Yurgon 37T did the trick very nicely. I cannot replicate what I did - I think I may have 'released' the other flight into action after the initial start up cue to do something with the radio using F10 - so were rolling in when I was still trying to figure which way was up. Either way all seems to be now working as advertised - thanks. 1 AMD Ryzen 5 5600X; ASUS ROG Strix X570-F, Corsair Vengeance 64 GB (2x 32GB) 3600MHz; Seagate FireCuda 510 500GB M.2-2280 (OS); Samsung 860 EVO 2TB M.2-2280 (DCS); MSI GeForce RTX 3090 SUPRIM X 24GB OC GPU. TM Warthog Hotas; T.Flight Pedals; DelanClip/Trackhat.
Recommended Posts