Just out of curiosity.

I don't normally monitor these values (other than ping), but here's my numbers based on less than 5min of running around on a couple different servers. I have access to BF2042 on a variety of platforms (yeah for GamePass!):

• PS5
• PS4 (running on PS5)
• XSX
• XBone (Running on XSX)
• Low end laptop (3050 GTX, 5800H, 16GB RAM, running absolute lowest graphics setting BF2042 allows, I've done exactly zero to optimize this laptop for gaming. Running 'Studio' drivers from Nvidia rather than 'Gaming', probably some bloatware/background programs, etc...)

PS5 is hardwired (gigabit fiber). 

XSX is wireless thru 4 walls. 

PC is wireless thru 4 walls + there's a 83" TV directly between the PC and router that's likely not helping.  PC WiFi says 3/4 bars.)

All numbers taken within about an hour of each other.

Region - Seattle

Ping - 22-24ms for all consoles.  28-30ms for PC.

Average Latency - 40-45

Time Nudge - XSX and PS5 were 7-12. 'XBone' 15-20. 'PS4' 25-30. PC 15-400, occasionally spiking to 700.

Very small sample size.  Hard to confidently draw any conclusions, but I'll draw them anyway:

• Time nudge for all consoles was rock solid, maybe fluctuating +/-3.  
• Average time nudge for PS5/XSX was significantly lower than PS4/Xbone. 
• PS4 (wired) time nudge was much higher than XBone (wireless). 
• PC time nudge was all over the place.  Would stabilize around 15 in quiet areas of the map.  Get around other players and it'd constantly spike to 150, 400 even 700.  Constantly getting the packet loss icon.  Night and day compared to any of the consoles.  

Curious how much of that PC time nudge issue is due to my 'worst case scenario' PC setup versus issues inherent to the PC networking.  I'll see if I can try the PC in the same room as the router to minimize that variable.

Edit: Moved laptop into room with router and gave it a fresh reboot.  Time nudge spikes are gone, pretty steady at 20.  Ping went from 30 to 25.  Improvements could possibly be attributed to 1) Better connection/less interference thru TV 2) Fresh restart closed some resource hog of a program.  3) I just got lucky with a better server.  

@Ironhead841 

I basically just copied pasted because everything is near the same for me.

• Region - Midwest U.S.A.
• Ping - usually in the 30-40ms range
• Average Latency - usually in the 30-40ms range
• Time Nudge - average is 20ms

I'm a bit confused about whats the difference is between latency and ping. Also, have no clue what a "Time nudge" and how to measure it, and how it affects things.

I live in Ireland, and ping is always 44ms, according to the scoreboard.

I don't have any issue with hit reg. 

Getting shot behind the cover is a big issue, but that has been there since launch so yeah...

@UP_LordPlumber 

It's an info bar you can enable under "Options" it's called "Network stats" or something like that, it will appear as a thin bar at the top oof the screen (doesn't obstruct your view at all) and it has all your network info.

There is also another larger graph you can enable that appears on the right side of your screen (although this one DOES obstruct some of your view) it's also where you can find your damage graph too.

I would at the verry least enable the bar at the top of your screen, as I said it doesn't obstruct your view and it as a lot of good info on it.

All off a it is directly tied to a lot of the weird "stuff" people see in-game such as getting shot behind cover like you mentioned.

The thing with 2042 on PC, there isn't a framerate limiter if Vsync is disabled. The game will render as many frames as possible and it doesn't take much to max out the CPU with 2042. A maxed out CPU leads to bad frame pacing and stutter gameplay.

The trick is to limit your framerate so the CPU doesn't max out to 100% on ANY of it's CPU cores. There used to be an in-game console command to limit framerate called GameTime.MaxVariableFps, but I think DICE turned it into a legacy feature. Turning on Vsync to limit the framerate is the easiest way. You'll have a ton of input lag but the game will play super smooth if the monitor's refresh rate is below where the CPU maxes out.

I had all kinds of inconsistency issues in Battlefield 1 on PC until I figured out mouse input in that game is completely broken with no way to fix it. Once I figured out how to work around the issue the game suddenly became way more consistent. I always thought it was server issues causing the inconsistency, then I discovered the game was just running like crap due to mouse input being broken.

Not saying the same applies here. Just sharing my experience with poor performance and inconsistencies in Battlefield titles. Sometimes it's due to the game running like crap on the console or PC due to bugs like broken mouse input or one of the CPU cores maxing out.

@OskooI_007 

My issues seem to stem from different server "instances" some rounds the game run perfect, the next round a full mag-dump won't take somebody down.

I am running a 5950X and my CPU rarely gets above 30-40% CPU usage, so I don't think it's a CPU related issue, but I could be wrong.