Netcode is just so enfurating

---

@Echo6Echo wrote:

I tell you what really fries my bacon, is the same narrative over and over...I've usually got a ping under 40ms and the ALAT is usually around 85-100 or so...one of two narratives happen.

1. I get hit once and immediately try to move. There is a very perceptible pause and then I get hit again and die. The damage log may or may not add up to 100. Most times not.

2. I begin firing at someone. I get two to four hit markers, possibly one of them a headshot, then suddenly I stop getting hits, get hit once or twice sometimes getting another hit in myself and then I'm dead, meanwhile the enemy is at 56% most times sometimes more. It's like a broken record. This happens regardless of the weapon I use and the damage log rarely shows 100 damage. 

100 % This

and then there's the weapon stats. How can the DM7 be listed at 65 firepower, the SVK at 70 and the VCAR at 46, yet all take the same amount of shots center chest at 50m? (3 hits and why is that when it shows 70, should be 2 right?) How about the well felt input lag any time someone shoot at you? The whole game is a broken mess of false weapons stats and balance with crappy net code and bad hit detection that favors people with lousy connections and crappy computers over those with low pings and fast PCs. I've NEVER had this bad of a hit detection/Dsync issue even when I used to play on a 3M DSL with 380K upload while someone was posting a Facebook video chewing up all the bandwidth  

Never focused on this so i believe your word on this...lol

I want to like this game, I really do, but it seems to be designed at it's core to * you off, demoralize you and make you want to kick your mouse and give up.

Me too, and yes it sure seems like it, Been there, done that...over the years it costed me 8 mouses...3 keyboards..and a frontplate of a computercase, the last few years i luckely tempered a bit..lol

---

---

@Echo6Echo wrote:

I tell you what really fries my bacon, is the same narrative over and over...I've usually got a ping under 40ms and the ALAT is usually around 85-100 or so...one of two narratives happen.

1. I get hit once and immediately try to move. There is a very perceptible pause and then I get hit again and die. The damage log may or may not add up to 100. Most times not.

I also get like some type of audible thud after the pause, like multiple sounds put together. 

2. I begin firing at someone. I get two to four hit markers, possibly one of them a headshot, then suddenly I stop getting hits, get hit once or twice sometimes getting another hit in myself and then I'm dead, meanwhile the enemy is at 56% most times sometimes more. It's like a broken record. This happens regardless of the weapon I use and the damage log rarely shows 100 damage. 

Yep same here, so frustrating, especially when you have the clear advantage. 

and then there's the weapon stats. How can the DM7 be listed at 65 firepower, the SVK at 70 and the VCAR at 46, yet all take the same amount of shots center chest at 50m? (3 hits and why is that when it shows 70, should be 2 right?) How about the well felt input lag any time someone shoot at you? The whole game is a broken mess of false weapons stats and balance with crappy net code and bad hit detection that favors people with lousy connections and crappy computers over those with low pings and fast PCs. I've NEVER had this bad of a hit detection/Dsync issue even when I used to play on a 3M DSL with 380K upload while someone was posting a Facebook video chewing up all the bandwidth...

I don't understand the weapon stats either, they are not accurate at all. 

---

I play a PVE shooter with guys from the other side of the planet, running 200 to 300ms pings, and I can play it fine as I know when I have a high ping, I have to compensate and adjust my play style.  When the high ping players are on my server, then I can play more aggressive.

Same with fast first person shooters.  Certain weapons need low ping, like lightning guns that track, but other weapons like rockets tend to do fine at higher ping.  If players know where they stand in the latency hagiarchy, then the can easily compensate their own gameplay styles to match their pings...

The problem with BF 2042 is players never know when in battles with other players if the are the "high ping lucky", or "low ping screwed".  I think it is much better knowing how the net code will perform and having consistency versus having the BF "Time Machine" net code play God with gamers base reality as it gets old quick inconsistently getting "Rolled by Dice"...🤔

---

@DeepSixxxx wrote:

I play a PVE shooter with guys from the other side of the planet, running 200 to 300ms pings, and I can play it fine as I know when I have a high ping, I have to compensate and adjust my play style.  When the high ping players are on my server, then I can play more aggressive.

Same with fast first person shooters.  Certain weapons need low ping, like lightning guns that track, but other weapons like rockets tend to do fine at higher ping.  If players know where they stand in the latency hagiarchy, then the can easily compensate their own gameplay styles to match their pings...

The problem with BF 2042 is players never know when in battles with other players if the are the "high ping lucky", or "low ping screwed".  I think it is much better knowing how the net code will perform and having consistency versus having the BF "Time Machine" net code play God with gamers base reality as it gets old quick inconsistently getting "Rolled by Dice"...🤔

---

Exactly...100% this too. I played for years on a crappy DSL connection. Laggy to begin with usually around 80-120 ping. If I got below 80 I felt blessed but it usually didn't make a difference with the slow upload anyway. I adjusted to it...yeah I'd get killed once I made it to cover, but a few "inches" behind cover. In this wreck I can be 5 feet behind cover for half a second and still get killed. I most times felt like I had a fair chance to win the gunfight even though I was the lagger. Also, I NEVER had input lag and stall as bad as this unpolished poop nugget. How is it that we had lag comp mostly figured out for years and years yet suddenly in 2022 it's a train wreck...heck I've played a certain nameless BR on servers hosted all over the planet with pings from the 30s to mid 150 or 200ms and it all worked out somehow. 

I constantly play 40ms or less. I'm going to find a way to get my ping around the 85ms range and see what that's like.

@Echo6Echo yeah I'd get killed once I made it to cover, but a few "inches" behind cover. In this wreck I can be 5 feet behind cover for half a second and still get killed.

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Only 5 feet, I wish...🙌

How about getting shot by "magic bullets" from a high ping Xbox player standing at the bottom of a ladder located 5-7 feet around the corner, as I was on the third step 3-5 feet around the OTHER side of the corner.  I post this photo too much but I just can't wrap my mind around how crazy the net code lag compensation "Time Machine" changes after Season 1.

How is my 40ms ping feel worse than my 300ms latency for another game I play with gamers on the opposite side of the globe???...👿 

I was literally talking to the screen in disbelief so time to uninstall from the "BattleField Matrix Infinite Multi-verse"...😬

9/10 (netcode related) deaths for me are caused by console players.  If Dice would just set cross-play to default OFF I'm betting pc players would experience a hell of a lot less issues, too bad most players are too lazy/ignorant to just do it themselves.

It seems a lot worse after the patch to me, I dump entire mags into console players and get one shotted a lot of the time, not fun.