Jump to content

[MISSING SHORT TRACK FILE] CB99 disappears after firing AGM65E


Recommended Posts

Posted (edited)

This has happened to me twice so far, both times with an AGM65E and CB99 combination payload.

 

This time I have 2xAGM65E and 4xCB99. As you can see in the following picture I set the CB99s to drop 2 singles with 150' spacing. Therefore pressing the pickle button once should result in 2 bombs being released.

 

MpHO1Xnm.png

 

I fired one AGM65E at the target. Circled around, fired my second AGM65E at the target. Here you can see both launches. Note how I still have a total of 4 CB99s.

 

mgoLAa6m.png

dik77Z0m.png

 

Now I run in with CB99s. I press the pickle button once. Two CB99s come off.

 

4dWdOPAm.png

 

Uh, where are my other two? My Stores page shows empty as well. I somehow lost 4 bombs while only dropping 2!

 

XpXu3t1m.png

 

Now it gets even weirder if I look at the debrief. Note that within 13 seconds of shooting my second AGM65E, the debrief registers 2 of my CB99s being dropped. This is strange because, unless I went senile and purposely boxed the CB99s in my Stores page and then pressed the pickle button in those 13 seconds, I'm pretty damn sure that I did not drop them. Additionally, note that those 2 CB99s that I supposedly dropped did not burst (no M-61 start/end shooting entries) despite the bombs being armed VT.

 

qmkp5T8m.png

 

Track here (it's a long one)

Edited by Nealius
Posted

Have you tried to reproduce the problem again? If yes, does it happen all the time?

 

 

As for the fusing, the fuses need to be VT for MFUZ and INST for EFUZ for the CBUs.

The vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord.

CVW-17_Profile_Background_VFA-34.png

F/A-18C, F-15E, AV-8B, F-16C, JF-17, A-10C/CII, M-2000C, F-14, AH-64D, BS2, UH-1H, P-51D, Sptifire, FC3
-
i9-13900K, 64GB @6400MHz RAM, 4090 Strix OC, Samsung 990 Pro

Posted (edited)

Found a workaround for the LMAV bug introduced in the 16JAN update. I could not reproduce when testing in my own mission, however prior to the 16JAN update it happened twice while playing the Through the Inferno mission on PG. Either a) something is wonky with that mission, or b) the 16JAN update fixed my problem. Since Through the Inferno uses persistent lasing I cannot test again in the same conditions until the LMAV bug is fixed.

Edited by Nealius
  • Recently Browsing   0 members

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