BF4 seems to have the gun glitch too!

[Gonzo]

Spotted in Daskro's new video:

phpBB [video]

Player can only drop medpacks, respawns multiple times but doesn't get a weapon until he bails out of the gunship later in the game. Is this you playing daskro? Can you shed some light on this?
I don't expect them to carry this over into the release version, so maybe fixing it in BF4 (where they have the finacial pressure to do it) will help them fix it in BF3 (which they are probably giving less shits about, the closer the BF4 release is coming).

[zorplex]

I would love to get this addressed by someone from DICE. I may start sending a link to it to the DICE devs on Reddit until one of them acknowledges it. Anyone with more clout (perhaps Sao with Symthic) could maybe push it along to someone at DICE. This is an excellent citation to show them; I really hope it gets fixed though it might be a problem with the engine which might make it much harder to fix.

Then again.... I don't remember it occuring before October 12 or so. So it had to have been introduced at some point with a patch and been carried over into BF4.

I've started to send the following message to DICE devs on Reddit:

Could you briefly take a look at the player spawning here: http://www.youtube.com/watch?feature=pl ... rVs#t=115s

The bug is the player can not use any weapons but can drop support kits. (med kit, ammo kit) The bug persists through death. The bug (in BF3) will propogate to multiple players on a server until they all leave.

I've been playing BF3 with a 64p competitive team weekly since February 2012. We started to experience that exact gun glitch weekly around October 2012. We've talked to EA support, been redirected to server support, switched servers several times, switch settings, paid for cpu priority; nothing has fixed it. We have this exact glitch every week in several matches and have to restart rounds which wastes time and corrupts our tournaments.

I was hoping it would be fixed in BF4 and haven't really pursued the problem further. But now that I have evidence it was in the E3 pre-alpha, I'm afraid it might make its way into the final release. I know it is an alpha, but could you please confirm that DICE is at least aware of the bug and currently working to correct it?

If anyone in the alpha would please post it to the alpha forums as well and try to get some attention from the devs. I will most definitely pursue it in the beta even if I don't see it occur. At least until I see a DICE dev address the issue directly. With a little foot work we may just be able to get them to fix it before BF4 launches. (Assuming they haven't already)

[Ash2Dust]

I would love DICE to deliver. But this is exactly why I still have not bought BF3 premium for $20. It took them a long time to start to deliver on BF3 what they promised on pre-sales. I'll pay when they deliver. Thats why I'm not paying.

And GSP's are unable to deliver stable servers with Dice/EA required hosting from our experience.

I'd love to talk to EA or Dice and figure out an enjoyable 32 vs 32 battleday without crashing servers or gun glitches.

[Darkrider312]

I can confirm that this is Daskro playing. On his channel, he has a short clip of him bailing out of the AC-130 and moving towards Charlie point after the building collapses.

https://www.youtube.com/watch?v=ozMTNO-dIQU

This video roughly corresponds to the 9 to 10 minute mark on the video that LordGonzo posted. Therefore, the longer version that Daskro posted on his channel is what he recorded during the pre-alpha at E3.

We're definitely fortunate that Daskro actually posted this footage and confirming that the glitch is present. I'd highly doubt other youtubers would actually put such content on their channels.

[zorplex]

Heard back from one of the Battlelog devs on Reddit:

Considering our current internal builds have this bug 9 out of 10 times you spawn, I think it's going to be fixed pretty quick
But I'll follow it up internally and see if there isn't another way it's triggering in BF3, thanks for the report!

I thanked him and sent a link to one of our BF3 gun glitch vids so he could see the similarities. Who knows, maybe if they find the problem in BF4 they can/will fix it in BF3. (One can hope...)

[Jokerle]

words of hope! Thx zorplex!

[Sarantini]

Yep its pretty common, its exactly the same as in bf3

[Hitman47]

Zorplex our hero!

[Necromancer]

major turn off for BF4.
And too little too late for BF3.

[dan1mall]

well done zorpzorp!
If this gets fixed Im buying you beer

[InsanityRocks]

well done zorpzorp!
If this gets fixed Im buying you beer

I'll also buy him a beer (That's 2 beers, Zorplex )

Who else is in?

[KoffeinFlummi]

You have my wallet.

[Bock]

You have my wallet.

And my manpurse!

[Jokerle]

well done zorpzorp!
If this gets fixed Im buying you beer

I'll also buy him a beer (That's 2 beers, Zorplex )

Who else is in?

I'm in.
(czech beer is so ridiculous cheap, anyway )

[zorplex]

Well it looks like I got someone's attention:

Do you know how to exactly reproduce this bug?

I haven't responded yet. I'd like to give a terse but comprehensive response and hope it makes it to the right people. What I have so far:

Unfortunately, no, not consistently. But it's almost guaranteed to happen a few times during our Saturday matches which last 6 hours over the course of 10 rounds or so on various maps. (What I wouldn't give for server error logs...)

I know that doesn't count as reproducible as we don't know exactly what triggers it but if it helps I've included some of its characteristics below:

-It appears after several rounds (6-8) have been played with the same players connected. (Possibly why it isn't seen on public servers as we only switch out a handful of players and most stay connected)
-As soon as it is triggered for one player, it cascades to multiple players usually affecting a quarter of the server.
-The bug will persist through death until all players effected leave the server and wait a bit and rejoin.
-The bug is more prevalent on certain maps (Sharqi and Armored Kill maps in particular)
-Server settings don't seem to effect its presence (We've played with vanilla settings and had it occur and so many permutations therein to try and force it to trigger. Our server plays with all weapons unlocked and we thought that might be the cause.)
-Having all players leave and restarting the server seems to delay the bug. This could either be due to all players leaving or the server itself clearing cache/memory. We haven't determined which.

Have I missed anything?