Page 1 of 1
[RESOLVED] LGB Malfunction
Posted: Tue Apr 09, 2019 12:36 am
by TXTBOOK
Is this normal, just bad luck, or is this due to the munition losing its laser lock because the aircraft lasing the target has dashed off, no longer lasing?
Code: Select all
8:13:12 AM - 8:13:12 AM - Weapon: GBU-27/B Paveway III LGB [BLU-109/B] #23638 has malfunctioned.
8:13:12 AM - 8:13:12 AM - Weapon: GBU-27/B Paveway III LGB [BLU-109/B] #23640 has malfunctioned.
8:13:12 AM - 8:13:12 AM - 100% penetration achieved
8:13:12 AM - 8:13:12 AM - Weapon: GBU-27/B Paveway III LGB [BLU-109/B] #23648 has impacted Shaibah AB A/C Open Parking 2.
8:13:10 AM - 8:13:10 AM - Weapon: GBU-27/B Paveway III LGB [BLU-109/B] #23647 has malfunctioned.
8:13:10 AM - 8:13:10 AM - Weapon: GBU-27/B Paveway III LGB [BLU-109/B] #23639 has malfunctioned.
8:13:10 AM - 8:13:10 AM - Weapon: GBU-27/B Paveway III LGB [BLU-109/B] #23637 has malfunctioned.
8:13:10 AM - 8:13:10 AM - Weapon: GBU-27/B Paveway III LGB [BLU-109/B] #23645 has malfunctioned.
8:13:10 AM - 8:13:10 AM - Shabah #4 (F-117A Night Hawk) is dropping Shaibah AB SAM Bty (SA-2f Guideline) from its target list (Reason: The target is not auto-targeted, and no outstanding weapons or assignments against it exist).
8:13:10 AM - 8:13:10 AM - Nightowl #4 (F-117A Night Hawk) is dropping Shaibah AB SAM Bty (SA-2f Guideline) from its target list (Reason: The target is not auto-targeted, and no outstanding weapons or assignments against it exist).
8:13:07 AM - 8:13:07 AM - New contact! Designated SAM #1977 - Detected by Shabah #3 (F-117A Night Hawk) [Sensors: Mk1 Eyeball] at 16deg - 4.6nm - No Contrail Detected.
8:13:06 AM - 8:13:06 AM - Weapon: GBU-27/B Paveway III LGB [BLU-109/B] #23651 has malfunctioned.
8:13:06 AM - 8:13:06 AM - Weapon: GBU-27/B Paveway III LGB [BLU-109/B] #23650 has malfunctioned.
8:13:06 AM - 8:13:06 AM - New contact! Designated SAM #1976 - Detected by Shabah #3 (F-117A Night Hawk) [Sensors: Generic FLIR] at 17deg - 4.4nm
8:13:05 AM - 8:13:05 AM - Weapon: GBU-27/B Paveway III LGB [BLU-109/B] #23642 has malfunctioned.
8:13:05 AM - 8:13:05 AM - Weapon: GBU-27/B Paveway III LGB [BLU-109/B] #23643 has malfunctioned.
RE: LGB Malfunction
Posted: Tue Apr 09, 2019 7:38 am
by Gunner98
I think the laser illuminator is no longer lasing the target except in the case of the third one down. LGBs are a bit tricky, unlike normal bombs they are really a 'one at a time' weapon.
Have you played around with the Strike Tutorials? That might help show you how to manage these strikes.
B
RE: LGB Malfunction
Posted: Tue Apr 09, 2019 10:11 am
by TXTBOOK
Good idea, back to basics!
RE: LGB Malfunction
Posted: Tue Apr 09, 2019 10:14 am
by CV32
ORIGINAL: Gunner98
I think the laser illuminator is no longer lasing the target except in the case of the third one down. LGBs are a bit tricky, unlike normal bombs they are really a 'one at a time' weapon.
I think in that case you get a message that the weapon has lost laser illumination, and will impact with severely degraded accuracy, rather than the 'malfunction' message. The latter seems to instead be a die roll of random problem (e.g. a dud or faulty weapon.)
RE: LGB Malfunction
Posted: Tue Apr 09, 2019 5:33 pm
by AndrewJ
I've noticed a lot of LGB malfunctions in some cases too, and I get the feeling that multiple drops are most susceptible to 'malfunction', but I've never been able to reliably reproduce it in a test. When I do enough drops the odds creep towards the expected value.
What were the circumstances of your string of malfunctions?
RE: LGB Malfunction
Posted: Tue Apr 09, 2019 5:54 pm
by Gunner98
LGB in real life have the annoying disadvantage of being thrown off by smoke and debris from previous strikes. I am really not sure if CMANO models that or not. Probably.
So a good drill is to drop one two bombs simultaneously with two lasers on the target if double pinging - then go away and hit something else for about 15 min. If you need to re-strike come back later. Targets within about 3-400 meters from each other could cause problems by obscuring the lasers so space things out. Hit opposite ends of an airbase etc. This is assuming CMANO takes this into account of course.
RE: LGB Malfunction
Posted: Tue Apr 09, 2019 9:43 pm
by TXTBOOK
Good stuff guys.
In my scenario, I was letting go about 16 at a time from a flight of 4... clearly not ideal now that I have a better understanding!
RE: LGB Malfunction
Posted: Wed Apr 10, 2019 9:11 am
by Dimitris
Do you have a save file of this prior to impact? We'd like to take a look. Thanks.
RE: LGB Malfunction
Posted: Sun Apr 21, 2019 5:38 am
by Dimitris
bump
RE: LGB Malfunction
Posted: Mon Apr 22, 2019 9:48 pm
by TXTBOOK
ORIGINAL: Dimitris
Do you have a save file of this prior to impact? We'd like to take a look. Thanks.
Sorry, I don't. But I've been releasing LGB's 1 or 2 at a time plus making sure the lasing aircraft is sticking around to impact that seems to help (user error I think originally...)
RE: LGB Malfunction
Posted: Tue Apr 23, 2019 1:06 pm
by KungPao
wow, so many malfunction
DB gave a Surface PoH/Reliability on GBU-27/B as 85%
Hopefully you will have a better luck tomorrow [8D]
RE: LGB Malfunction
Posted: Mon May 13, 2019 3:12 am
by Dimitris
Is this still an issue in the current public release? (B1009.27.14)
RE: LGB Malfunction
Posted: Mon May 13, 2019 9:33 pm
by TXTBOOK
Haven’t seen it again