Jump to content

GBU-31 V3/4 Penetrator different results from different Planes


Go to solution Solved by rob10,

Recommended Posts

Posted

I just noticed that the GBU-31 Penetrator has different effects on targets when dropped from different planes.

Dropping 4 GBUs on the Command Center from the Hornet they can't kill it while being dropped from the F-15 they kill the Command Center each time.

I used both the USN and the USAF versions on the Hornet.

Not sure if it's a weapons bug or a plane bug or a bug anyways but I find it strange; well knowing that the Command Center is quite hard to level.

Maybe someone has insights - I can upload trks if so wished - should it be a bug...

Thanks out

Brrrrrrrrrrrt

I'd rather call in a Strike Eagle...

I7 6700K, MSI Z270 Gaming Pro Carbon, 32GB G.Skill Ripjaw V 3200, Inno3D GTX 1080, Samsung 970 Evo, Thrustmaster 1.6000M, TrackIr 5

Posted

There going to ask you to upload a track file and possibly logs, just saying 😉

Windows 10 64 bit | Intel i5-9600k OC 5 Ghz | RTX 2080 |VENGEANCE® LPX 32GB DDR 4 OC 3200

 

Hotas Warthog | Logitech G Flight Rudder Pedals | Track IR 4

Posted

Used a single GBU-31 on a command and control bunker on Saturday from the F-18 and took it out no problem.  Are you changing the fuzing delay on it in the Hornet?  I set it to the maximum (can't remember what it is).  Not sure if the F-15 has options for that yet so that may be the difference.

And yes, a track file is pretty much a need to do to get a real answer.

Posted

Bombs were set to .06 delay which is max. For the Mudhen you only can set fuze settings for the center station and copy these to the other stations. No clue if this really works at the current status of the F-15. Anyways the Mudhen's bombs does their job. Both planes used the AF versions of the GBUs.

Find the trk attached and just to be sure we're talking about the same Comm Center here's what I mean:

Screen_250410_083011.png

f-15e_comm_center_kill.trk f-18c_comm_center_nokill.trk

  • Thanks 1

Brrrrrrrrrrrt

I'd rather call in a Strike Eagle...

I7 6700K, MSI Z270 Gaming Pro Carbon, 32GB G.Skill Ripjaw V 3200, Inno3D GTX 1080, Samsung 970 Evo, Thrustmaster 1.6000M, TrackIr 5

  • Solution
Posted

Well there's your problem: you used the AF variant and it didn't like being dropped off a Navy plane 🤣.  I did use the USN variant but they should in theory be identical.

Yes, that was the C+C bunker I dropped on (good to check).

So in quick testing it's related to the fact that you set the fusing in the stores page to DLY1.  If you set it as INST (with the 0.06 sec set in the re-arm menu or mission editor) it will take them down with a single GBU-31 (naval or AF).  I suspect this is it looking for something functionally when you have DLY1 set that doesn't work with that particular fuse (I assume you were using the default FMU-139?) when you have it to DLY1 and isn't triggering at the appropriate timing.  I don't have in depth enough knowledge to speak intelligently any deeper than that on it though.

  • Like 2
Posted
13 hours ago, rob10 said:

Well there's your problem: you used the AF variant and it didn't like being dropped off a Navy plane 🤣.  I did use the USN variant but they should in theory be identical

😬 that was it, go Navy!... no - fun aside

You're right. I tried it with the FMU-139 and 'inst / .06' setting and got it levelled with one bomb.

I'm sorry for bringing this up by just fiddeling with the wrong buttons and thank you for your time to check it out.

BUT as it works now - I'm damn sure I found this behavior while using my standard settings which always was 'INST' and not 'DLY1' as I wasn't using fancy fuze options as I'm just not familiar with yet. Whatever it was - works now. Rest is left for the X-Files.

Thanks again, solved, and out!

  • Like 1

Brrrrrrrrrrrt

I'd rather call in a Strike Eagle...

I7 6700K, MSI Z270 Gaming Pro Carbon, 32GB G.Skill Ripjaw V 3200, Inno3D GTX 1080, Samsung 970 Evo, Thrustmaster 1.6000M, TrackIr 5

Posted
12 hours ago, NoJoy said:

I'm sorry for bringing this up by just fiddeling with the wrong buttons and thank you for your time to check it out.

It was legit to bring it up.  We don't have good details on the fuses to suggest whether it's correct the way it is or whether the option to select DLY1 is bugged.  I might not have noticed except that I never even thought to change it to DLY1 when I dropped it Saturday, so I noticed you did (was watching to make sure you had armed the fuses and that wasn't the issue).

  • Like 1
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...