Zone5 Posted March 23 Posted March 23 Trying to get GBU 10s and 12s to guide. I've tried multiple missions (including one I made just for this purpose with the way point at the target on the ground). Static targets, moving targets it doesn't matter. I think I'm doing it all right: Altimeter set INS aligned (with ground start...) TGP active A-G Mode Master Arm ON Laser ON Laser code set (1688 and I've tried others...) Laser code set in DED Autolase set in DED (8 sec, 10 sec, 12 sec, 15 sec and even 30 sec) CCRP NSTL Fuse RPL 1 Rel Ang 0 (or 45) TGP SOI Target set in crosshairs (TMS UP/Point or TMS Right/Area) ON Steering cue Weapon away at drop cue Laser comes on at correct time Follow target on TGP MFD Bomb flies OVER the target to land in the dirt 1000-1500 yards beyond the target EVERY bloody time. I'm sure I've missed something, but 2 days of looking at Chuck, the Manual, MANY YouTubes, and I can't think of anything else. Like the title says...what am I doing wrong or missing? Any help would be appreciated.
Tholozor Posted March 23 Posted March 23 A track replay would help us get a look at the process to see if anything is missing or user error. 1 REAPER 51 | Tholozor VFA-136 (c.2007): https://www.digitalcombatsimulator.com/en/files/3305981/ Arleigh Burke Destroyer Pack (2020): https://www.digitalcombatsimulator.com/en/files/3313752/
Solution Zone5 Posted March 23 Author Solution Posted March 23 36 minutes ago, Tholozor said: A track replay would help us get a look at the process to see if anything is missing or user error. That would take about 25 tracks, which is why I didn't send any in the first place, but I see your point. In any case, I finally figured it out--it was a mod (specifically the VSN F-4B/C) which was removing all my REDFOR groups at start up. Apparently this showed up with 2.9.14.8222 last WED. I don't run many mods (and I can live without this one) once it occurred to me that a mod might be messing things up, it only took an hour of rerunning with and without specific mods to find the one that did it. My goal was to learn the GBU procedures--I think I now have them memorized... Thanks!
Sinclair_76 Posted March 27 Posted March 27 My guess is you're releasing on the toss cue and not the straight and level drop cue. When toss was introduced I tried using the 0 for toss angle as well but found that not to equate with the normal release cue. 1
Mike_CK Posted May 9 Posted May 9 Glad you figured it out. I was going to say that years ago I had a similar issue with LGBs landing all over. Turned out it was the map…I had never deleted the contents of my FXO (and whatever the other one is) file like you should after each patch. Doing so did the trick
saile Posted May 25 Posted May 25 (edited) I had the exact same problem recently and I was going crazy. In my case, the problem came from the NSTL fuse — it had to be switched to NOSE for it to work. Also, make sure that the TGP remains SPI until impact, I sometimes had bugs where it designated itself. And finally, avoid maneuvering too much after the drop, it seems to disturb the trajectory. Since I've been doing this, my GBUS have been hitting the mark. Mini Militia App Lock Edited June 4 by saile
Nealius Posted June 3 Posted June 3 NOSE for an LGB should dud the bomb. The nose fuse well is taken up by the battery for the guidance system. NSTL or TAIL has worked with 100% reliability for me. 1
Recommended Posts