This happens to me all the time, especially in crucible - I ADS and then fire almost immediately and nothing happens. Trigger is depressed - but weapon not firing!
Does this happen to anyone else, and does anyone know why this would happen?
English
#destiny2
-
1 ReplyIt's 2024. I just googled this because it's been a recurring problem in iron banner tonight and last night. I guess it won't be getting fixed if it's a 6 year strong problem.
-
Edited by Johnatello: 1/30/2021 7:21:49 PMOf course all the time when 'pro' in games and I don't think its about aiming downsights or running or reloading or any of skipping things, I experienced with hand cannons, shotguns, energy grenade luncher same shit, and not once in a match several times atleast if not all the times whenI'm in fight with a particular player. Mouse and keyboard here and only in pvp its this issue
-
same issue 2021 on pc
-
I did some IB last night and I think you fellas are correct in staining that it is a run and gun issue. I started out sprinting and dry firing again and getting killed - ended up walking around, stopping then aiming and firing, seemed to work. I ran a lot less yesterday, which sucks, and was gentle on the L3 button - but I didn't notice my gun jamming after I made those adjustments... it sucks that this happens though - weapon should fire at some point when you pull the trigger... even if you are sprinting!
-
2 RepliesThat crap has been going on since D1, it’s not a controller issue, often the weapon will lower into the relaxed stance and then......BOOM.....you’re dead.
-
7 RepliesI have seen this as well. If it's not a bug: The only thing I can think of is maybe hitting run accidentally while firing. For some reason, the game is prioritizing run over shoot. Shoot should always be prioritized when both are pressed if you are not allowed to do both. Especially in pvp.
-
1 ReplySounds like you have... Projectile Disfunction. They sell a little colored pill for that.
-
It happens to me, and no 3 new controllers didn't help. It happened today to me on a $200 custom smart trigger controller which works perfectly fine. I think it has something to do with their net code being an abyss of horror.
-
Get new controller. I did and it helped some.
-
It happens to me every single time i go to fire a rocket launcher, i have to press fire a good 2-3 times before it fires. Hardly ever happens to any other weapon.
-
Happens to me in crucible aswell, but strangely not all the time, peace
-
This happens often when I use rocket launchers. Heres a few weird ones: After I'm done with my super my weapon won't be the same one before I went super. ADS. Start firing. Suddenly my sights will slide over people like identical magnetic poles. Switching weapons sometimes will just not happen.
-
3 RepliesAre you using no land beyond?
-
Happens to me all the time in gears of war 4 so annoying
-
I had that problem with my elite controller from time to time, I turned off the trigger locks and haven't had a prob since
-
2 RepliesIt happens when you sprint cancel the reload. In Destiny, theres a timer on when you can actually fire the gun again when you press reload. So if you sprint cancel it, you still have to wait the same amount of time it would take to go through the reload animation before you can fire the gun again.
-
2 RepliesI thought you were talking about the Uriel's Gift bug where it would sometimes stop firing causing you to die in a firefight.
-
The games response time is terribly slow, I’ve noticed this a lot,also with melee and slide.
-
1 ReplyI have had this happen in D2, plenty of times. PVE, Pvp. Full mag. I’m not running or trying to run. I’ve three controllers, two are new and it still happens. Doesn’t happen in other games. Just D2. I put it down to lag.
-
1 ReplyAre you sure you have ammo? Because a gun would not fire if you didn't have any bullets.
-
1 ReplyThis is something that started to happen after one of the updates in Destiny 1, and has been present since day one in Destiny 2. Sometimes your weapon will fire a single bullet before failing to fire, and sometimes it just refuses to fire even after repressing. It is not a controller issue as I have tested this on several brand new controllers, and it has happened on every single one of them.
-
If you reload-cancel by running, it won't let you fire for a little bit
-
Edited by MithBesler: 3/4/2018 6:42:59 PMI saw in a comment that you bought a new controller, I did this as well no luck. I had one of the white PS4s that was sold with a copy of Destiny and I first started to notice it with Crota when I would try to smash him with the sword. I would just stand there doing nothing till I hit the trigger again. I was at Gamestop figured I would just replace my controller again, my luck just got a bad one. They had one of those mod packs that add paddles to a normal Dual Shock for 10 bucks so I said the hell with it and figured I would try that first. This turns off the Bluetooth and the controller data is sent via USB. Sure enough no more dead trigger pulls and everything was back to normal. Due to my Bulldog freaking out while trying to get his ball out from behind the TV I was forced to buy a new PS4 and have not had the same problem that I had with the White PS4. This whole thing leads me to believe that something went wacky with the Bluetooth card in my PS4 because like I said if I used the mod it worked just fine and when I got a new PS4 never had the problem while using the same controller minus the mod pack. Oh for info this is the mod pack I got. https://www.amazon.com/Collective-Dominator-Controller-Adapter-playstation-4/dp/B01L8QHXJA I guess it can do stuff that is rather unsavory, I just used it so my damn controller worked right. EDIT: I added a quick video I did showing what would happen with the sword. After getting that MOD pack I tried for like 20 minutes to get it to happen again and it never did.
-
Yes happens on occasion
-
5 RepliesIt’s the controller. I was sceptical when this happened to me a while back in D1. Bought newer controller and worked. Reconnected old one just to see and the problem was there still. Try new controller.
-
1 ReplySame. However I did switch controllers and it hasn't happened to me yet.