Bought this game on Thursday. 20+ hours in and I can't believe some of the bs I've seen and experienced. I've come to the conclusion that what you are seeing and what the person shooting at you is seeing are 2 completely different things. Just now I got sniped for 60, backed way down the hill and 2 seconds later I get killed by the same guy. And yes, the kill cam shows his silhouette, no way he should be able to see even a part of me, but he did, and he shot me. I'm 3 feet below the crest of the hill. As soon as you get lit up you are toast, there is no such thing as cover, you think there is, but there isn't. I wonder how many people I've killed who thought they were safely under cover?
Don't get me started on player movement. This is Morrowind levels of bad. And that game was released in 2002. Constantly getting stuck on objects. Pogo sticking up and down. Climbing rubble is awful. Hit prone and slide around like you are on a yoga ball until you settle. I played BF1 last year and don't recall these issues. I am not asking for parkour levels of greatness but geez man. Every 3D game since 2005 has been smoother than this.
It's appalling that a AAA title can play like this.
13
Comments
I played games 10 year ago with better netcode
Apex does have worse netcode than BFV though, but again everything else just works and the game is fun. In BFV the netcode is not the best and almost everything else has "issues", which makes the whole gaming-experience frustrating and not fun.
In a way, you are right. What the enemy sees IS different from what you see, and everyone else on the server for that matter. Remember it takes time for your client (Console or PC) to send position updates to the server, and then it takes time for the server to send them on to everyone else. Everyone is always seeing your historical position, and you are seeing theirs.
It sounds bad, but in reality we are normally talking less than a tenth of a second behind. How long does depend on both your internet connection, and that of the person looking/shooting at you. And it happens in pretty much every single online multiplayer game to some degree.
And if someone kills you and continues moving, the kill cam isn’t showing you the position they may have shot you from, but where your client thinks they currently are. In order for them to get a hit, they must have shot you on their screen and the client thought it was a hit, and then the server simulates the shot too and verified it was a hit.
If it was genuinely 2 whole seconds after you think you got into cover, then it’s unlikely to be related to latency. Odds are frankly that you just weren’t in as much cover as you perhaps thought and the person had you in their sights fair and square.
It’s been an issue with battlefield for years.
I've never really experienced it before BFV. There was the dying behind corners and the occasional high ping bullet sponge, but otherwise killing and dying felt a lot smoother.
In this game dying is extremely frustrating almost every single time for me, because you either don't have enough time to react as someone from across the map put 10 bullets in you and they hit you all at once, or you're up close and think an enemy should have died, but they kill you and walk away with 98 damage.
I've had times where the person that just killed me wasn't even facing me, and no one else was around to damage me, ruling out that explanation. I've also had times where I shoot someone for what should have been 100 damage (4-5 shots at near point blank range), but the numbers say 96-99, and then the numbers change and the game says I only damaged them for 80, but I still died in a heartbeat when all their damage hit me at once.
Earlier I ran into some level 3 dude using a Sten gun that killed me like a bolt-action headshot every single time. Just instantly dead. I'm not totally convinced he was legit considering he was such a low rank, but had more kills than anyone else, and I was dying to him faster than I could blink. The game, however, is so bad that in any other situation I'd be almost certain that guy was cheating, but not in BFV. That's just how awful the netcode is.
Or, and this might sound a bit crazy, he's a BFV vet with a second account to show better stats.
Not everyone is a cheater, and not every quick kill is because of the netcode. With my time in BFV, I've experienced it all, but the percentage of time where I feel hard done by is extremely low. 99% of my deaths are because of my own human error. It's frustrating when we die because of the netcode, absolutely, but the reality is that it just doesn't happen that often.
Yeah, everyone is just lying and BFV is perfect. Let's also forget about DICE themselves admitting to, and trying to fix TTD issues, which are NETCODE issues.
He's baiting for replies, mate.
This whole thread is baiting for replies with its hyperbole.
Not really. BFV has the worst netcode out of any previous BF game. And such issues have been confirmed by Dice itself. So no, thread has valid complaints.
I totally agree that there are issues with the netcode, but please, these threads are a dime a dozen with people exaggerating the issue. People just rush in to the forums after what they felt was an unjust death and vent their toxic frustration... I mean just look at the title of this thread! 😂
Well if those people were the minority, your assumptions would be true. But in reality the game suffers from por netcode and all issues it brings.
I just don't feel like making threads with each complain I have. Mostly because Dice doesn't give a thing about this place and doesn't take any sort of feedback.
How was movement worse in BF1? I actually feel the opposite, but the netcode was definitely better in BF1 among many other things.
But yes, net code is bad. There could be a one or two second delay between clients. The all bullets in one package shows this. In general you would waste at least a second firing full auto at enemies, yet they receive all bullets at once.