Ping, Latency, Jitter ...

@Braddock512

Need a sticky!!

##bump##

Well… just jumped on tonight and it’s . My ping/latency was between 25 and 40 and i had the lag markers all over the right side of the screen and watching players lagging everywhere. Good job on the hotfix Dice :confused:

If it was latency symbols to the right side of ur screen then it’s ur connection.

Whether it’s on Google or not is irrelevant. The Rev took time out to explain all of that to us, you should be grateful instead of being a dbag about it.

Ur dog is cute so props for that.

Nothing but lag/packet loss/whatever markers on 3 servers in a row… balls

Lol :smiley: …thanks but I can’t take credit for it. I had a pic of Brian spanking Lois since BL but one of the mods changed it.

Don’t pay attention to this one guys, he’s just another “there is no high ping advantage” believer. Why don’t you deny the holocaust existed while your at it lol.

My ping at the time was around 30, my mate was having the same problem and his ping is also <40 - personally i think my connection is fine and Dice has just made a right royal of these netcode changes.

ar se is filtered out? Jeezo


Which one were u seeing at that time.

You got to use the / slash.

Oh ok thanks. :slight_smile:

There’s a bug that doesn’t spawn bullets in the server-side simulation, thus no hit reg. it affects players at random and at all pings.

https://twitter.com/mischkag/status/859391132790161410

Ahhh, server performance was the main one… which pretty much explains it then, typical crappy EA servers! Did have the packet loss one too but i’m guessing that can be down to a crap server too? The high latency marker popped up a few times too even although i was constantly checking and i never climbed above 45 latency.

Seemed ok in the last round i just played.

Im starting to think my issue is with the extrapolation offset being to high and flucuating to much. I watched a video today

in it he explains all of the netgraph. In it he says the extr offset value should be around the value of the server tick rate, which is always at 30 for console. My value is around 30 but sometimes sneaks up to 40 (yellow icon) and sometimes as high as 60 (red icon). Yesterday and today the icon for latency variation is showing up like mad. Im going to have to get on to my ISP and ask about the connection. My ping has been low like the above poster said. But this extr offset makes for very unpleasant game play i.e slight rubber banding, things happening in slow motion, bullet build up etc.

Bit of a hard bug to figure out as you can’t constantly play with your scoreboard showing to check everyones ping and sometimes it’s your connection or poor aim

You’d have to record your entire matches and check em; * doing that on console; 5 minutes is the limit per clip

The developer’s tool set gives them the benefit of not having to go through that process. And console is the same as pc. It’s written on pc. Xbox is Windows based, PS is Centos based. Not much conversion there.

From what I’m reading from the devs the server simulation isn’t spawning bullets. No bullets spawned means no hit reg arbitration. What can cause bullets to not spawn? First thing I’d look at is packet formation/fragmentation issues. For low ping that’s hit claim packets (damage data), for high ping it’s “whenever I shoot”.

Narrowing it down on the low ping side (client->server hitreg) I’d use the visual sequence clues as a guide. I’d look for blood splatter. If there’s blood splatter animation, then client has deemed it a hit and should be forming/sending that hit claim to the server. If the server at that point isn’t spawning bullets, well then there’s an issue with either the packet data or a hang up in one of the read/execute calls to functions/class. This could literally be the wrong decimal position in a float val. The difference between 0.0125 and 0.125 is huge.

If there isn’t blood splatter, when there clearly should be, then that’s something on the client-side not deeming a hit…thus no hit claims to the server.

On ps4 you can record at least 1 hour, so it shouldn’t be a problem recording a match