Hit reg issues, TTK vs TTD inconsistency.

@Adomonic This is a game killer. I am so sick of dying instantly but needing an entire clip to kill someone.,,I am dead in an instant and got all those rounds off before they kill me with 2-3. Fix this cr4p.

I don't even want to play the game anymore until this is resolved, if ever. It is not fun at all. The game is literally the antithesis of fun right now.

I am not wasting my time beyond this season if this doesn't get resolved and a Server Browser added.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Kind of scary what you typed above as that was my exact thoughts before uninstalling BF 2042 three weeks into season 1 launch. First game I have ever played online in which my sub 40ms ping responded more like 400ms...👿

So until a server browser is added, I don't think Dice can fix this issue as it seems to be server side lag compensation gone wild...and thus why we see zero comments from Dice on this forum concerning any sort of future patch.

Yet how can Dice "patch" an issue caused by lack of players...unless said "patch" magically increases the player count 500% for MM to start working correctly again...🤔

---

@Adamonic wrote:
TTD is still instant for me. I am never wounded and survive. I am hit dead, regardless of what weapon is used, and it feel like 4-5 rounds are lumped together as one.

For TTK, it gets even worse when the player is beyond 100m. I don't even both anymore because no matter where I shoot, on target, ahead of target any distance or even behind the target, hits do not register.

---

Same. Unless I can get the jump on them I dont. I just let them run

I give up for the night. MP9s and K30s taking me out from 125 meters with headshots while my AR cant hit crap. 

I dont get that. It should be nerfed long range and mid. Up-close I know im screwed but it shouldn't  be outdueling an AR from 100M. 

---

@edgecrusherO0 wrote:
@GrizzGolfDon't worry, DICE is nerfing the K30!...at least its close quarters damage, because apparently that's the problem DICE is hearing about in feedback? It's weird because I haven't seen any complains about that, just the mid-long range strength of the SMG that's designed to be strong in CQC.

---

@DeepSixxxxGreat post. Why hasn't EA responded.

---------------------------------------------------------------------------
Not easy to respond as EA/Dice had to choose the lesser of two evils...either keep the net code fair for low latency players but not be able to fill games due to "Waiting for X Players", or twist the net code to allow high ping players to compete by destroying the experience for low ping players but allow servers to fill quickly before players left the server in seven seconds due to the seven second attention span of our screen addicted populace. Ea/Dice seems to have chosen the latter...

What EA/Dice may not have seriously considered is that there are profitable solutions, such as allowing server browsers via portal with non-rotating permanent Official game modes. It takes thousands of online players for MM to work properly, but only a few hundred for server browser setups in private portal, but because portal is experience throttled heavily, players avoid it and stick to MM AOW and even avoid the experience throttled rotating official game modes in portal that unfortunately also utilize MM (although unlike AOW, keeps the same player groups when changing maps...very nice!). Enhance portal official game modes with server browsers as a trail for future AOW server browsers. Allow players to rent dedicated Amazon game servers and create a different experience via portal, with their own net code limits on ping/packet loss/etc...their own TTK/TTD settings, etc. At the very least this would act like a trial to see what works best as Dice would have the server data for thousands of servers, and could use this to enhance official server browser portal modes and features and even help shape the next version of BF in a better direction...

The final uninstall straw for me was after I had wrongly reported someone I thought was a cheater in BF 2042 for the first time for any Xbox game, but then figured out via the forums that Dice Season 1 update has created these impossible TTD/TTK/desync/invisibly/etc/etc/etc situations and not aim bots and/or wall hacks, etc.

I honestly wish Dice good luck unwinding the layers of complexity created via dozens of patches on a game that was launched 3-6 months before actually "polished". I actually bought out the rest of season one before I uninstalled as a hedge/donation Dice actually adds server browsers by the time season 2 arrives and players come back...🤔

---

@Adamonic wrote:
@GrizzGolfI missed a recording of me emptying an entire clip from the M5A3 with 7-8 hit markers and after jumping around, 2 instant hits and I am dead. They are at 36%? Like how the hell is that possible?

---

That was all my matches last night 

---

@DeepSixxxx wrote:

So until a server browser is added, I don't think Dice can fix this issue as it seems to be server side lag compensation gone wild...and thus why we see zero comments from Dice on this forum concerning any sort of future patch.

---

Dice have asked you guys to show them examples, but the examples being posted are just people painting the walls. I know what I think if someone shows me a recording of them missing practically every shot and blame it on the netcode. Maybe they are not commentating because calling out peoples aim is against their code of conduct.

I have read several places in this thread people saying this happens in every round they play, so it shouldn't be difficult to get a proper recording of it. Just record a whole round and point at the time indexes when it happens and that should be pretty conclusive. 

OK.

I'll post it again.

I had no ADS once I exited the vehicle but it's pretty clear I hit this guy in the head multiple times long before he started shooting back at me.

The game managed to recognise hits on the equipment.

Why didn't it recognise a single hit on the player?

Slow it down to 0.25 play speed and it gets worse.

I clearly "dust" this player 7 times IN THE HEAD and once that might count as the top of his backpack.

He then 3 shots me after taking 8 hits at close range.

Battlefield 2042 - BUG- No hit registration? - YouTube

Kap.

---

@Kaptyn027 wrote:

OK.

I'll post it again.

I had no ADS once I exited the vehicle but it's pretty clear I hit this guy in the head multiple times long before he started shooting back at me.

The game managed to recognise hits on the equipment.

Why didn't it recognise a single hit on the player?

Battlefield 2042 - BUG- No hit registration? - YouTube

Kap.

---

I watched your video and noticed another desync issue. Right after you die the hovercraft changes location in the minimap. My guess is the server saw you tangled up with the hovercraft and it was blocking your shots.

Yep....fair call.

How did I destroy the spawn beacon then?

Kap.

I dunno, I'm just pointing out another desync issue with the hover craft changing location after you die.

No probs.

That vid is pretty bad.

1) No ADS after exiting the vehicle,

2) 8 shots that "dust" the enemy player clearly with no hit markers and no damage (yet I destroy the spawn beacon with no trouble),

3) spooky moving vehicles with no one in them.

All in the 10 seconds after I respawn.

What a quality product. 

Don't think this one is a de-sync issue as the enemy player likley hasn't moved for some time prior to me arriving (he has to reload after what looks like 3 shots on me).

This one below is a de-sync issue.

Battlefield 2042 - hey DICE! Want to explain this? - YouTube

Kap.

To be honest I think they're both desync issues. I think you were able to shoot the spawn beacon because it was right after you jumped out of the hover craft and you didn't move much. So you were still close to where the server saw you.

But then you took quite a few steps forward on your screen, but on the server's 'screen' your player model was hung up on the hover craft and didn't move forward.

Now there's too much desync between where the server sees you and where you see yourself. Which causes the server to reject your hits (and you were hitting him as evident by all the blood).

This whole hit rejection thing is an anti-cheat measure hard coded into the game engine's netcode to prevent cheaters shooting through walls, but it's going haywire and rejecting hits from legit players due to desync issues caused by buggy netcode.

---

@Kaptyn027 wrote:

No probs.

That vid is pretty bad.

1) No ADS after exiting the vehicle,

2) 8 shots that "dust" the enemy player clearly with no hit markers and no damage (yet I destroy the spawn beacon with no trouble),

3) spooky moving vehicles with no one in them.

All in the 10 seconds after I respawn.

What a quality product. 

Don't think this one is a de-sync issue as the enemy player likley hasn't moved for some time prior to me arriving (he has to reload after what looks like 3 shots on me).

This one below is a de-sync issue.

Battlefield 2042 - hey DICE! Want to explain this? - YouTube

Kap.

---

This video sums up every round for me lately 

To me it’s very obvious that the more players in a server the worse it gets which is not that strange. The funny thing is if I compare 2042 to portal modes the portal modes feel so much more polished in terms of gameplay feel

@ Pantleon Dice have asked you guys to show them examples, but the examples being posted are just people painting the walls

======================================================================================

Rather than upload 300MB of videos, below is some BF 2042 screen capture "Fails" from my Xbox Series X game videos:

Fail 1--Got killed by a high ping enemy 5-7 feet down a staircase and 5 feet around a corner versus my 40ms low ping (see highlighted enemy location and the final location I actually fell to my death in photo below).  Note the clip is from 80 days ago and after Season 1 launched, "time delay penalty"  got much, much worse.  Getting shot around corners is a complete buzzkill as latency luck is more consequential than gamer skills.  I have ever seen it this bad in any game to be honest, my 40ms feels like 400ms when engaging high latency players.  Note I'm playing Xbox Series X and the enemy was on Xbox but I see it across all platforms...and it seems to be getting worse as less players are available for MM, and thus Dice most likely is allowing 400ms with 40ms players to get games to fill 24/7...

Fail 2 - Getting shot by invisible players that show up as red dots seems to be a new "feature" from Season 1 launch.  Total buzzkill as whoever gets the invisibility "perk" will easily win any battle. Note I mark out all the names in these photos as I had joked about the player being invisible with "phantom" in his name...and I may or may not have been removed for a name and shame time out.  Note to admins--->I have blocked out all names, so please don't remove this reply or me as they have been scrubbed to remove EA/Dice liability...

Fail 3 - Xbox Series X Graphics Fail on new Exposure Map--->This sort of glitch should have never, ever happened if play tested thoroughly before Season 1 release.  I believe five different platforms is too net code complex and thus amplifies the TTD/TTK/Desync/etc issues...

Fail 4 - Instead of showing videos killing 4-5 human enemies in a row with the 50 cal in TDM, I can simply state that the net code is so twisted now, I have went from 90% accuracy shooting at stationary enemies and 70% accuracy shooting moving players for one shot kills to maybe 50% accuracy hitting stationary players and now it takes complete luck to hit moving players as either the hit box was reduced drastically, or the net code was twisted to the point that where I see players on my Xbox is not where the players are actually standing on the BF Amazon servers.  Weirdly I actually hit players when I "miss" on my screen, but the player on the Amazon server must have been where I "missed".  Again what a buzzkill, as now it is more luck than skill to kill with the 50 cal even though I'm running 40ms ping on a Series X.  This all happened after Season 1 release, and I assume it has to do with net code changes to fill MM as the player numbers fall...

Fail 5 - I could do this all day yet what is the point if Ea/Dice do not post theories or updates to future fixes???  It would be useful if EA/Dice would respond more in the official BF forum (versus the very difficult to filter and follow Reddit)...so until then, most gamers will stay silent as again, what's the point???