maxTRX Posted July 3, 2021 Posted July 3, 2021 (edited) Since JDAM's don't take direct grid input and O/S button on JDAM page is inactive, I used HSI data page to input 6 digit grid from JTAC (no high expectations for accuracy ;/). I decided to use O/S for the grid so I wouldn't have to change my WPT. Everything looked good until I exited DATA and designated O/S as target. JDAM was showing OAP coords. So, I then decided to make my OAP a target using the same grid I used for O/S. Once OAP was programmed, I had to re-designate it as target so the JDAM would switch from original OAP (wpt1) to my new OAP. It worked. When I went back to HSI > DATA, I could verify my new OAP was correct and jibing with JDAM but the O/S grid was different now. It looked like the new OAP 'took' the old O/S and placed it at the bearing and range inherited from the original designation... I know it all sounds chaotic. Another issue I noticed was JDAM in TOO would not retain coordinates after undesignating the last target in a sequence. If I kept the last JDAM's target designated, I couldn't s step through previously programmed JDAMs without the last coords being forced on all stepped bombs. If I undesignated the last target in a sequence, the last JDAM would loose the program (unlike in previous OB builds) and stepping through other bombs would wipe them out too. Also, this affects QTY release, since the release drops them in sequence so all the bombs take the coords from the first released bomb. It steps through all the JDAMs selected for QTY release. Can someone confirm that at least some of these issues are bugs, some may not be implemented yet and there's always a possibility of user error. Edited July 3, 2021 by Gripes323
dorianR666 Posted July 4, 2021 Posted July 4, 2021 2 hours ago, Gripes323 said: Another issue I noticed was JDAM in TOO would not retain coordinates after undesignating the last target in a sequence. If I kept the last JDAM's target designated, I couldn't s step through previously programmed JDAMs without the last coords being forced on all stepped bombs. same, this is reported i think. TOO is all around broken right now. CPU: AMD Ryzen 5 1600X GPU: AMD RX 580
Recluse Posted July 4, 2021 Posted July 4, 2021 Reported several times....(Undesignate wiping TOO coords) let's hope it gets addressed
maxTRX Posted July 4, 2021 Author Posted July 4, 2021 Thanks, I wonder if I should pile up the O/S part on top of the QTY issue. I'll probably make a separate post in the bugs section when I get a chance. Does anyone know what's up with the 'O/S' button on JDAM's page? Non functional or any other mech. required to activate?
Recommended Posts