Welp...finally got my first nuke...and then the drop bomb command on spacebar didn't work...?

I looked this particular issue up on Reddit and saw it occasionally happened to other people years ago - but I’m curious - how common is this particular bug? As I play plenty of prop aircraft, I have long since had specialized keybinds for things relevant to using the nuke plane, specifically separately opening the bomb bay doors (bound to “X”). But then upon flying over the map with the bomb bay doors already opened, despite repeatedly pressing the spacebar for dropping the bomb (which worked fine with normal plane spawns in prior matches in the same session), the nuke did not drop even when over the map.

So yeah. Quite the letdown.

Also, how exactly do you set a keybind to spawn the nuke plane without J’ing out first? I cannot find it in the controls anywhere.

1 Like

It should work no problem. I’ve never had an issue once your over the actual battlefield and then drop the bomb.

My letdown for a nuke was clipping a tree in that shitty B29 that wallows through the sky.

1 Like

If it adds any context, I was approximately 1-1.5km up, just under the low cloud ceiling. No enemy plane was anywhere close by. An M19 was trying to shoot at me but was spraying & praying from too far away to even get close. I have seen instances of the nuke bomb being shot out by enemy gunfire, so that did not happen. I noticed when I was mashing the spacebar to drop my bomb that my engines turned off for some weird reason - normally that is bound to the “I” key which I did not press then.

Is it possible that since I was trying to drop the thing from more normal bombing altitudes and not at near-treetop level, that due to bomb computer ballistics it did not consider me yet “over the battlefield” and thus wouldn’t let me drop?

Should I fly at treetop level next time just in case to prevent weirdness like this from happening again?

replay

https://warthunder.com/en/tournament/replay/389454775269254733

Here you go. Maybe I did something else wrong or server desync caused issues, idk.