T1gge pls you have any more info on the freezing issue because I don’t know what you have done in the latest update with some maps but is working pls do it again but fast because is getting worst.pls respond and thanks i n advance
No, I can confirm that the “netcode”/hit detection in particular is incredibly wonky in DT. Just today (when I could still play) I had a handful of killtrades (more than ever since the “netcode” patch combined, in fact pretty much ever since the TD release I’ve been having absurd amounts of killtrades again!) and one particularily eggregious case of die-behind-cover on Propaganda map where I saw a scope glint, instantly dove into prone position behind the solid cover between the points A and C (Conquest Small), went through the entire going prone animation and THEN, just shy of a second, suddenly was dead, with the kill cam showing a sniper vapor trail going over the cover. I was fully covered and had height advantage, so the sniper did not hit any exposed part (nevermind it showed the headshot icon) and could not have arced the shot above the cover to hit me.
Old netcode woes are back. Don’t know how (because as you said, it makes no sense), but empirical, personal experience belies that notion.
No, I wasn’t revived right before any incident of this glitch occurring. It even occurred right after my EOD bot was destroyed by an enemy while I was laying prone at the Chinese deployment on the map Sunken Dragon.
I am saying the error randomly appears and randomly disappears. Or conversely, most of the time Battlelog/the client works and other times it doesn’t, fo whatever reason (it is certainly not port 3659 UDP not being forwarded!).
It happens in Windows when trying to join servers via Battlelog. I can play on a server perfectly, exit it, try to join a new server and suddenly get this message “Game disconnected: Client closed down connection… make sure that port 3659 (UDP) is open”. From that moment on, I can’t join any server until the error somehow disappears.
Hi!
I cant play bf4 online on ps4 .it says lost connection to ea online first when i started the game. Then i restarted it and now i cant even get into the menu??? I only see the background now and nothing else… Whats happening?? I played online yesterday.
Had a weird texture-glitch today where the textures of soldiers would expand over the whole world, basically blinding me. Went to update Catalyst to latest drivers, restarted pc. servers are basically offline, origin blaming my network speed ( http://www.speedtest.net/my-result/3631309050 [speedtest.net] ), ‘‘try again later’’-> problems logging in to battlelog via browsers (chrome/FF). When eventually getting somewhat through, it says it cannot connect to BF4.exe. This is getting ridiculous, I didn’t pay for premium with very high expectations, but this just blows. Please fix this, or throw away this battlelog-thing and remake it to be in-game.
Are you looking into the issue where the sound and map textures in the beginning of a round is not present? I mean, the sound and textures take about 15-20 seconds to get work.
Also, any eta on the second CTE-to-Vanilla patch? Any time given is hella appreciated
This is all related to what ping your enemy had there (and how much the server allows that) - it would still have happened on a vanilla map. We got more fixes for this coming, but I assure there is no changes in this patch regarding this. If anything you play against more different people (more people are playing) and the possibility of high pingers is bigger?
Hello, while playing a round of Conquest on Sunken Dragon, I suddenly lost quite a few of the controls. I couldn’t ADS, I couldn’t sprint, I couldn’t throw Grenades and I couldn’t jump/vault. I lost these controls when I was on the water barrier.
I do not think it was my controller as when I died (I redeployed), I had regained full controls of my soldier.
This is because of EA-online connectivity issues (the login problems), that caused the disconnect. I’d force stop the bf4.exe (if its still there), and restart the browser and try again.
