RAZBAM_ELMO Posted December 16, 2020 Posted December 16, 2020 A brief but detailed explanation on how you can enter in the UTM/ MGRS coordinates for the Harrier. AV8BNA_UTM_Cooridnates_Input_be1217eb-bda1-4d69-a174-ca61d503c516.pdf 5 1 Know and use all the capabilities in your airplane. If you don't, sooner or later, some guy who does use them all will kick your ass. — Dave 'Preacher' Pace, USN.
SGT Coyle Posted December 17, 2020 Posted December 17, 2020 These instructions are for an upcoming update? Night Ops in the Harrier IYAOYAS
Ramsay Posted December 17, 2020 Posted December 17, 2020 Yes 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
QuiGon Posted December 17, 2020 Posted December 17, 2020 (edited) 3 hours ago, SGT Coyle said: These instructions are for an upcoming update? For todays update: Edited December 17, 2020 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!
SGT Coyle Posted December 18, 2020 Posted December 18, 2020 Looking forward to trying this in a mission. Night Ops in the Harrier IYAOYAS
kgd192 Posted January 3, 2021 Posted January 3, 2021 One quick comment regarding note #2: Usually you would add not leading but "trailing" 0s since a MGRS Coordinate with less than 10 Digits usually denotes one of lesser accuracy. So to enter 32U LV 123 456 you should type 32U LV 12300 45600 and not 32U LV 00123 00456 as suggested in your manual Greetings 1
Wisky Posted January 4, 2021 Posted January 4, 2021 if you want the middle of the square you would actually add ‚55‘ instead of 00 1
Torun Posted April 25, 2021 Posted April 25, 2021 On 1/4/2021 at 12:53 PM, Wisky said: if you want the middle of the square you would actually add ‚55‘ instead of 00 I don't agree because the digits no longer represent squares, they depict an X-Y offset from the SW corner of the grid segment (for every map but Nevada, where it's the SE corner), it separates that segment into an array of points separated by meters. If you cut down on the digits, now there's less points farther apart. You could argue that it's still squares, but what you're doing then with the fives is offsetting those squares in a way someone giving you the coordinates didn't intend, so you can be off by one of those squares instead of being in the same one. If you get coordinates from a source that actually gives you more digits than you need, just round up or down as with a regular number, e. g. 12342 45671 to 123 457 and then you shouldn't add fives. If it's a source that you know always rounds down, then fives might be useful, but it's highly unlikely this is a thing. If you need more precision, just ask for it.
Recommended Posts