Forum Discussion
I can tell you from many years of renting servers and administrating them (all the way back to BF1942, just for reference) that "People with a high ping do not impact server stability" is just factually wrong.
That's why we used to have ping limiters on our servers.
- Ironhead8413 years agoHero
What "iteration" are you talking about?
- 3 years ago
@Ironhead841I'm talking about this game not BF1942
@0ski that thread do not say anything about server stability
- Ironhead8413 years agoHero
OK so let me try to explain one more time, what I said is I have been renting servers and administrating them since BF1942 and all the way through to BF4, not just BF1942.
In some cases, running multiple servers per game and all those servers have had issues once high-ping players attempted to play on them.
Hence, we ultimately decided to set ping limitations on all our servers, and ya know what? Problem solved!
So, my question to you is why would BF2042 not suffer from the same server stability issues caused by high ping players that have plagued literally every other Battlefield title?
- 3 years ago@Ironhead841 Maybe because different softwares are different ?
The thing is what are you calling server stability, because it seems to me we don't use that term for the same thing. - RanzigeRidder23 years agoLegend@ugdpy So how would you explain the fact that in BFV where we still had both the ping of all players in lobby as well as the server location visible, playing would become impossible due to high ping player's entering the server probably out of region?
You would immediately feel something was off, rubberbanding would start and games became unplayable. No matter what you call it, lag, netcode, server instability, it is an issue! An issue that probably is still present in BF2042 too. - 3 years ago@RanzigeRidder2 In my 800 hours playing this game (mostly on public lobby) I have never encountered this issue.
The fact that people keep referencing older titles, kinda proves my point. - doubleome3 years agoSeasoned Ace
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.
- UP_Hawxxeye3 years agoLegend
@doubleomeyeah, the movement on BFV was simply ridiculous.
Check this, it is the most "what the heck" moment I experienced in BFV https://www.youtube.com/watch?v=kU3vUNMbJY8At least they toned down the ice skating slide since then.
But I still loathe every death to someone sliding on dry concrete as if it was a polished marble floor covered with high quality face shaving gel
- doubleome3 years agoSeasoned Ace
Anyone know how to properly add a video? All I get is this really small video that is nearly impossible open
It's another short netcode story, someone spawns nearly 2 seconds after I destroy a beacon, completely catching me off guard.
- UP_Hawxxeye3 years agoLegend
@doubleome
During the dialogue about including the video on the post, make sure you select "large".Anything else will compress the video frame like the water pressure at 10000m bellow the sea level.
- doubleome3 years agoSeasoned Ace@UP_Hawxxeye Yeah made sure it was large, nothing seems to change it ☹️
- ElliotLH3 years agoHero+
@doubleome wrote:
Anyone know how to properly add a video? All I get is this really small video that is nearly impossible open
It's another short netcode story, someone spawns nearly 2 seconds after I destroy a beacon, completely catching me off guard.
Best way I've found is to just not use it and to go with a YouTube link instead.
If you're on a PC at least though, you should be able to use the pop-out feature to make it bigger. It's fiddly, but if you click the "view in my videos" text you can then see the picture-in-picture option. Clicking this will let you stretch out the video when it pops out.
It gets a bit blurry though...
- doubleome3 years agoSeasoned Ace
Ill try YT later
- kregora3 years agoSeasoned Ace@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. - doubleome3 years agoSeasoned Ace
Short netcode story #3
- doubleome3 years agoSeasoned Ace
Second try on short netcode story #2
- 3 years agoI 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
- sk1lld3 years agoLegend
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.
- 3 years ago
I wouldnt argue with that guy, he's a fanboy shill, The fact of the mater is these are the cheapest Amazon servers money can by and all though this problem might not be the net code the net codes dog DooDoo. Thats why Dice cant fix the mouse input issue that's been in the game since day one. its in the net code. lol
- iigloo3 years agoSeasoned Ace@ugdpy I've played a couple of hundred hours more and i have the opposit experience.
I have thousands of hours of experience from 1942 to 2042 as a player, server owner and competetive player so the fact that you talk against us kinda proves my point that many of the "experts" and "knowhow" are feeding DICE with bullcrap that leads to dissaster titles like BF2042.
GG - doubleome3 years agoSeasoned Ace
Short netcode story #4 or is this what I think it is? Did smell of fish afterwards
- OskooI_0073 years agoLegend
@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.
- doubleome3 years agoSeasoned Ace@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.
- 3 years agoI 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. - doubleome3 years agoSeasoned Ace
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"