Happens on console at times

I've been suffering from this bug for many years now. Here's a lot of what I learned: If you jump or are airborne, your first click/trigger pull wont fire the weapon. Instead that input actually READIES your weapon (pulls it into firing position instead of down at the hip from you being in motion). So if you're having an issue firing a rocket or Witherhoard or something from midair, know you need to pull the trigger twice to get a shot off, and there will be a slight delay while the weapon moves into the ready position. If you're suffering from snipers or other weapons not firing on that first few trigger pulls I've noticed a couple causes. 1: Tabbing out/entering an overlay (Steam, GeForce, Xbox Game Bar, etc.) will for some reason dissociate your mouse from the game. Fix this by firing a primary weapon at the wall before engaging in combat to ensure your game is registering your mouse clicks before you fight. A warning to you as well, if you're running some kind of capture software in the background or have a web browser up, be careful its not overloading your processors. If your computer is overworked, that could contribute to worse performance and possibly missed registration on inputs. 2: Reload cancelling sometimes doesn't work right (you achieve this by sprinting or using some other movement ability to cancel the reload animation as soon as you see the bullets appear in your magazine). Instead of cancelling the animation and letting you fire, the gun appears to maintain an internal cooldown of how long that reload should take and doesn't allow you to fire until that time is up. It should be noted however, that this does NOT occur every single time you reload cancel, nor does allowing a reload to complete normally guarantee your weapon will actually fire properly. After a lot of time and examination, it really does not appear reloading or animation cancelling has any real effect on this bug. Its an issue with the weapon system programming. The best solution I've found is that after a reload you need to quick swap off and back on to your weapon for the highest chance of having the gun actually work (essentially resetting the weapon state and hoping that rolls the dice in your favor). Its superstition, but it makes me feel more hopeful the gun will work at least. 3: Weapon perks (primarily snapshot, but any perk that affects handling) sometimes feel like they affect this. Using a sniper WITH snapshot and the same sniper without snapshot has a noticeable difference. WITH snapshot, I constantly notice the firing issue. As if the gun scopes in faster, but the game still won't allow you to fire faster than if you didn't have snapshot. By the same token, using a gun with barrel and mag perks that boost handling makes your ADS faster and doesn't affect that first shot functioning right or not. In fact, its to the point where I almost feel safer using a sniper WITHOUT snapshot on it and instead something like Killing Wind or a good barrel because it will function more consistently, at the cost of a fraction of a second longer time to ADS. 4: Network issues. It should shock absolutely nobody to hear that the connection issues in crucible have been SIGNIFICANTLY worse than in the past. Not a single game will have a full 12 person lobby with good connections. At least one or two people will have pings so high you wonder if they're playing from the moon. This unfortunately has repercussions on your game's performance as well. Inputs may not register for the host, eating your shot. This is also why shots you clearly hit dont register at all, or why you appear to die in a single handcannon shot from full health. The connectivity issues are tanking the quality of the pvp experience in a way that even if you're doing everything right, the game could screw you anyway. Its still a theory, but I've noticed that any time one of those laggy people in the match is in an engagement near me, I have a higher tendency to encounter my guns not actually being capable of firing. A big bit of evidence I have for this is that a map like Anomaly (moon map, tiny) has significantly more registration issues than a map like Javelin (Io map, hangar) or Vostok (Earth map, snowy mountains). I can't prove this is a root cause, but its something for the community to keep an eye on and see if there's actually any merit to it. 5: This is something that my friends don't encounter but I sometimes do (I use a gaming laptop, so that could be why), but occasionally my weapons will start firing themselves with no input from me. I'll just be jogging through a patrol zone and my smg starts spraying wildly as if I were holding down the trigger. Or my rocket launcher will decide that right now, while im two feet from a wall and taking cover, is the perfect time to unload its package. I use a USB mouse and my trackpad is disabled so there's no way I'm accidentally firing from that, meaning it may be a coding issue with the game that's mistaking some other input as a trigger pull, or possibly the game is not properly reading/registering what a proper trigger pull is and is acting out in both directions (either eating it or making it happen from thin air). I'd be interested in hearing if anybody else has this issue too. In conclusion though, after a lot of testing and analyzing various instances of these glitches, I'm 95% sure this is a coding issue and likely a network issue combined. Until Bungie figures out the reason(s) behind it conclusively, your best bet is to slow down your play and take a moment to cycle weapons, let that reload finish, and make sure you let the game play itself out as designed instead of trying to squeak out some extra efficiency. Cant hurt to make sure your drivers are all up to date too. One thing that could also be causing the issue is individual settings. I have not done any testing yet, but its not unheard of for your framerate in D2 to have unforeseen consequences (like that damage bug from late 2021). Or for your FOV to impact the functionality of your weapons. It could be worth checking into whether a particular setting might be a potential cause.

Yup. Due to the horrible level of pvp coding this game offers, I left. I can't recall this ever happening back then, but has happened now 3-4 times in survival (as of past 2 weeks); literally changing the matches :( Another reason to leave again. Of course I missed felwinter's lie. Kinda sums d2 up though. This should be literally one of the main bugs to fix but the game only has pve merit. Don't expect any quality in pvp (comp), it simply doesn't exist. EDIT: No, this isn't reloading. This is upon first would be shot of the games sometimes too. It's something which unlike anything else. so definitely not reloading.

Happened on console at the start of a match using Jade Rabbit. Fired two shots and then nothing on the third. Fourth trigger pull fired. Cost me the fight. But it didn't happen again tonight. And no I was not spamming the trigger. I main scouts

I find this happens when I reload izanagi’s turning it into honed edge Takes a few trigger presses before it shoots. Pain in the ass when I’m shooting champions

Never noticed it before yesterday but had more than a few times that i'd quickly switch to Witherhoard and it wouldn't fire for a second or two, definitely not what you want when trying to earn those Massacre medals in Gambit Prime

This has only happened to me with wardcliff coil, but multiple times. I shoot and I see one rocket come out and then it dissapears. Its always in pvp for me too. Lol rip.

Happens on controller too. Feels the worst with shotguns. Slide up to someone...pull the trigger, and just sit there. There is always a “wtf...oh I’m still alive” pause on the other side before they annihilate you, not quite long enough to pull the trigger a second time.

Happens to me ALL THE TIME. Glad to see it ain't just me.

Ive noticed it on mt. and very very rarely for SG, and yea its always when doing a quick swap. As for cost benefit analysis on bungies side, good luck getting them to address it. Games on life support it seems.

It happens with a lot of guns in the game especially after switching weapons or sprinting. It is by far the most annoying thing I have seen in any shooter

*flashbacks to no land beyond after reload glitching*

Happens with Felwinter’s a lot. Bungie needs to address the damage glitch and this

[quote]This happens across mouse brands btw, I know logitech guys using it (im on a razer mouse)[/quote] Also happens on console.

This happens very rarely which means that if it is a bug then it is a bug of crooked hands.

This happens with TLW too

Its highly annoying. Sort of like when Wardcliff would only fire one or two projectiles.

Keeps shooting my bow mid draw then fires the follow up shot instantly