Short netcode story (videos)
Funny how much bs you can see in this game when you can watch stuff back. Can't really explain this one. His feet are covered and wasnt a headshot.... Plus a dead center hit.
Forum Discussion
But what if you look at different games? When looking at COD or CS, I can't recall much of what we experience in Battlefield throughout the years.
Battlefield has always been plagued with not the best "netcode" that a game could have
1942 - not the best hitboxes
BFV - not the best hitboxes
BF2 - having to lead targets because hit boxes where placed differently according to ping, dolpin diving and bunny hopping was a prefered tactic of many tryhards
2142 - somehwere inbetween BF2 and BC2
BC2 - can't recall this being all too bad, hit boxes where very generous though and movement very slow
BF3 - fine as long as ping was limited, 100+ become a god, also many OHKs
BF4 - started to look like what we have in 2042
BF1 - kinda similar to 2042 I guess
BFV - also similar, but very high mobility of players kinda messed stuff up
2042 - current state
Yes I played them all, after BF3 playtime got lower and lower though, I wonder why 🙂
I think anything pre BF1 had big issues with higher ping players but dedicated servers helped a lot. But after BF1 and to some extent also BF4 imo the netcode sorta melted everything together and was hard to tell good from bad players in terms of engagements, you can even feel you already lost eventough you are not dead yet. And it is basically consistently bad, you either feel like bullets can't hurt you or that everyone is out to get you. Gunplay in 2042 surely doesn't help at all.
@doubleome I remember that in BF4 the netcode changed as the 60Hz servers were introduced.
Our experience was, that certain maps couldn't handle 60Hz and 64 players at the same time, prominently "Paracel Storm" here.
I remember that Nitrado had issues with their server hardware and network equipment shortly after the change. Apparently the then typical Xeon 2.8GHz servers struggled to provide 60Hz for 64 players. Having people on the server having pings higher than 50-60 usually made the servers crash.
After we moved to new server hardware with a faster cpu, the crashes stopped, but then we experienced router issues with out provider, which caused lost packages or out of order packages.
Still high pings hurt everybody, and put additional stress on the servers.
Our experience was, that certain maps couldn't handle 60Hz and 64 players at the same time, prominently "Paracel Storm" here.
I remember that Nitrado had issues with their server hardware and network equipment shortly after the change. Apparently the then typical Xeon 2.8GHz servers struggled to provide 60Hz for 64 players. Having people on the server having pings higher than 50-60 usually made the servers crash.
After we moved to new server hardware with a faster cpu, the crashes stopped, but then we experienced router issues with out provider, which caused lost packages or out of order packages.
Still high pings hurt everybody, and put additional stress on the servers.
Short netcode story #3
Second try on short netcode story #2
- I can only agree, the netcode is not working properly. I'm usually in a different language area here at the forum but there are the same complaints that the netcode isn't good. The official EA employees always tell us that the netcode is OK, although we always provide examples of the opposite
There are many problems with the netcode. Shot around corners, one hit kills, synch issues all over the place, spawn ins behind us. Mouse that feels like it's in molasses and the list goes on and on. Two years in and still we have all these issues.
@doubleome wrote:Short netcode story #3
That's definitely the invisible player bug. He just appears out of nowhere like being teleported in Star Trek. You can clearly see the teleportation if the video is played back at 25% speed.
- @OskooI_007 Actually have another one of these somewhere, that was 20+ meter teleport when I could actually see the frozen player first and just shoots across the screen behind me.
- I also have a lot of videos like this.
Personally I think it's a synchronization Server Netcode problem, the player was probably actually standing in that Position earlier in his game and saw/shoot you, the server just didn't send his location to your game and you got killed instatly becouse you could't see him at that moment.... The result the server transmitted only your death. wth is with this week, just did 2 games tonight, consider this just unplayable at this point, this was just the tip of the ice berg
I know this isn't all netcode related but it's a meme at this point I guess. Dice working really hard to rebrand "Only in Battlefield moments"
- @doubleome The beginning of that video looks like spectator mode.
- @doubleome Doesn't sound like it was a fun experience. That must have been pretty annoying.
Quit not too long after this video ended, only suffered for 5 mins but cba doing another game after at least
@doubleome
Have you tried a tracert? type CMD in the run box right click CMD and select run as administrator. "With the game open" type "netstat" without quotes and hit enter find the server IP, then in the CMD box type "tracert" without quotes then a space and server IP number you just looked up and hit enter. If you can't find the server IP number try "tracert google" without quotes and hit enter.
When your done with CMD type exit.
Check your hops for dropped packets or high ping hops. You could have an ISP issue. Then again it could just be BF2042 being its normal self but at least you tried.
Worth a try!New day and again a game with everyone invisible...... 2nd game of the day.....
- @doubleome
Are you sure your game doesn't need repairing? drivers up to date tried older drivers. Usually when I see missing textures its client-side thing. Or the luckiest player that all those bullets missed from that distance (server did crash with an error towards the end for everyone)
Neo?
Not had everyone invisible but have had a game with some infantry were invisible and vehicles. All I could see was guns running about and people sat in invisible vehicles.
quality game 🤣
This was the average experience on this one server, enemy facing away instant turn 2x HS no misses. Like playing older FPS game with bots turned to ludicrous mode, aimlessly walking and instant turn and you are dead
And you do well still top kills but the experience just isn't there it just feels god aweful to play
@doubleome The damage log says the TTD was 3 ticks (135ms) by two headshots but it felt a lot faster than that. It also felt like 1 bullet hit instead of 2 bullets. I hate how insta-deaths feel in this game. They feel horrible.
2 for one deal, this server was a weird one felt ok but constantly this 0 hit regs out of nowhere.
After I got revived nothing hits anymore and a second part all the APS about a million of them only 2 die the rest takes zero damage. An a ton of other poor hit regs during this round.
@OskooI_007 wrote:@doubleome The damage log says the TTD was 3 ticks (135ms) by two headshots but it felt a lot faster than that. It also felt like 1 bullet hit instead of 2 bullets. I hate how insta-deaths feel in this game. They feel horrible.
Even the sound effect of the insta deaths are crazy. All the sounds of 5 shots hitting you, but all within 1ms.
It seems they are aware of the hit reg issues and are working to get a fix out. Crazy to think an FPS 2 years post-launch is dealing with NEW hit reg issues when the core of the game revolves around hit reg.
Did watch the Enders video 2 years of Battlefield, that about sums it up. And Dice should be fortunate when you see this kinda stuff when playing and still plenty of die hard fans sticking with it, any new IP that launches in a state like 2042 is forgotten forever. But seems the micro transactions are what is keeping this ship afloat and that has me really worried for the future titles.
Featured Places
