Hit reg issues, TTK vs TTD inconsistency.

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???