ww2 gone laggy

[mike]

ww2 has gone laggy for me ,im using cloud settings 42,40,28 auto and bleeding are not selected filtering is set to 982km strict is on is there a cloud update or should i tick auto and bleeding ?.

 

heres somethings i have noticed in mp games

 i can press the fire button and my finger has lifted off the button before my gun fires.

since the war machine has dropped the game has got worse im seeing frame rate drops when nades/flash bangs go off near me and im in a fire fight this is now happening on all maps

.

also something that really puzzles me :-

 

if ww2 is now on dedis as everyone says why is it that i get randomly kicked with no explanation or error msg and if someone leaves a game everyone then freezes for about 10 secs then everyone gets kicked back to the lobby and we get told lost connection to host , i thought if we are on dedis they host the game and not the players , this seems to tell me that we are still hosting the game ?.

 

another curious thing is on the start of a game (ill pick a random map just as an example) on gibralter whilst the count down to start the games is running down i have found that i can jump up and down but if i go back onto that map later i cant jump up and down even in the same lobby when we play the same maps back to back , is this an indicater of who is host again proving that its not a true dedi set up ? , when i remember ill check this with mates.

 

thanks for thoughts ideas.

[pollutionblues]

ww2 has gone laggy for me ,im using cloud settings 42,40,28 auto and bleeding are not selected filtering is set to 982km strict is on is there a cloud update or should i tick auto and bleeding ?.

 

heres somethings i have noticed in mp games

 i can press the fire button and my finger has lifted off the button before my gun fires.

since the war machine has dropped the game has got worse im seeing frame rate drops when nades/flash bangs go off near me and im in a fire fight this is now happening on all maps

.

also something that really puzzles me :-

 

if ww2 is now on dedis as everyone says why is it that i get randomly kicked with no explanation or error msg and if someone leaves a game everyone then freezes for about 10 secs then everyone gets kicked back to the lobby and we get told lost connection to host , i thought if we are on dedis they host the game and not the players , this seems to tell me that we are still hosting the game ?.

 

another curious thing is on the start of a game (ill pick a random map just as an example) on gibralter whilst the count down to start the games is running down i have found that i can jump up and down but if i go back onto that map later i cant jump up and down even in the same lobby when we play the same maps back to back , is this an indicater of who is host again proving that its not a true dedi set up ? , when i remember ill check this with mates.

 

thanks for thoughts ideas.

You should be using auto and bleeding edge as this give you the very latest cloud update. See if that gives you a better experience. If you do not see the ‘update’ button on the geo filter page then you are playing on a dedicated server.

 

It is possible you are getting put in P2P lobbies as it uses both servers and P2P, I have noticed an increase in P2P lobbies on FFA since last weeks update. The ‘lost connection to host’ message is probably a generic message that you would get with either a server or a P2P host if you were disconnected from it.

 

Not sure about the jumping thing, I would doubt it’s an indicator of host though, probably just a glitch in the game.

[Netduma Jack]

I reckon the latest update could have caused this change in your connection - what's your ping to the game? Has it played fine until this point?

 

The advice above is great - let us know your ping and also your Internet Diagnostics stats. Could be something changed on your line which is causing you to lag!

[mike]

everything is fine exceptional on everything no packet loss :-

 

PING 8.8.8.8 (8.8.8.8): 56 data bytes

64 bytes from 8.8.8.8: seq=0 ttl=58 time=13.580 ms

64 bytes from 8.8.8.8: seq=1 ttl=58 time=13.113 ms

64 bytes from 8.8.8.8: seq=2 ttl=58 time=13.436 ms

64 bytes from 8.8.8.8: seq=3 ttl=58 time=12.889 ms

64 bytes from 8.8.8.8: seq=4 ttl=58 time=13.002 ms

64 bytes from 8.8.8.8: seq=5 ttl=58 time=13.137 ms

64 bytes from 8.8.8.8: seq=6 ttl=58 time=13.296 ms

64 bytes from 8.8.8.8: seq=7 ttl=58 time=13.131 ms

64 bytes from 8.8.8.8: seq=8 ttl=58 time=13.510 ms

64 bytes from 8.8.8.8: seq=9 ttl=58 time=13.159 ms

64 bytes from 8.8.8.8: seq=10 ttl=58 time=13.039 ms

64 bytes from 8.8.8.8: seq=11 ttl=58 time=13.382 ms

64 bytes from 8.8.8.8: seq=12 ttl=58 time=13.266 ms

64 bytes from 8.8.8.8: seq=13 ttl=58 time=13.441 ms

64 bytes from 8.8.8.8: seq=14 ttl=58 time=13.310 ms

64 bytes from 8.8.8.8: seq=15 ttl=58 time=13.400 ms

64 bytes from 8.8.8.8: seq=16 ttl=58 time=13.286 ms

64 bytes from 8.8.8.8: seq=17 ttl=58 time=12.951 ms

64 bytes from 8.8.8.8: seq=18 ttl=58 time=12.789 ms

64 bytes from 8.8.8.8: seq=19 ttl=58 time=12.956 ms

 

--- 8.8.8.8 ping statistics ---

20 packets transmitted, 20 packets received, 0% packet loss

round-trip min/avg/max = 12.789/13.203/13.580 ms

Trace

traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 38 byte packets

1 192.168.1.254 1.012 ms 0.915 ms 0.909 ms

2 84.93.253.96 11.809 ms 11.468 ms 11.545 ms

3 84.93.253.99 12.191 ms 11.923 ms 11.986 ms

4 195.99.125.130 12.178 ms 12.249 ms 11.928 ms

5 62.172.103.195 12.853 ms 109.159.252.130 12.615 ms 62.172.103.199 12.013 ms

6 109.159.253.67 12.077 ms 109.159.253.189 12.666 ms 195.99.126.187 12.346 ms

7 108.170.246.129 13.254 ms * *

8 64.233.175.152 14.903 ms 108.170.232.104 15.470 ms 74.125.253.228 12.886 ms

9 8.8.8.8 13.837 ms 108.170.230.165 12.948 ms 216.239.47.195 13.571 ms

[pollutionblues]

You could run PingPlotter for a more in-depth test of your line just to completely rule out any faults. There is a great guide on PingPlotter here: http://forum.netduma.com/topic/23881-ping-plotter-quick-guide/

 

Run a test with congestion control sliders set to 100%, make sure no one is using the internet at the time and run the test for a minimum of 10 minutes. I would then run PingPlotter again while you are gaming with the sliders set to 70%.

Post your results here if you need any help with them

[RL317]

 

everything is fine exceptional on everything no packet loss :-

 

PING 8.8.8.8 (8.8.8.8): 56 data bytes

64 bytes from 8.8.8.8: seq=0 ttl=58 time=13.580 ms

64 bytes from 8.8.8.8: seq=1 ttl=58 time=13.113 ms

64 bytes from 8.8.8.8: seq=2 ttl=58 time=13.436 ms

64 bytes from 8.8.8.8: seq=3 ttl=58 time=12.889 ms

64 bytes from 8.8.8.8: seq=4 ttl=58 time=13.002 ms

64 bytes from 8.8.8.8: seq=5 ttl=58 time=13.137 ms

64 bytes from 8.8.8.8: seq=6 ttl=58 time=13.296 ms

64 bytes from 8.8.8.8: seq=7 ttl=58 time=13.131 ms

64 bytes from 8.8.8.8: seq=8 ttl=58 time=13.510 ms

64 bytes from 8.8.8.8: seq=9 ttl=58 time=13.159 ms

64 bytes from 8.8.8.8: seq=10 ttl=58 time=13.039 ms

64 bytes from 8.8.8.8: seq=11 ttl=58 time=13.382 ms

64 bytes from 8.8.8.8: seq=12 ttl=58 time=13.266 ms

64 bytes from 8.8.8.8: seq=13 ttl=58 time=13.441 ms

64 bytes from 8.8.8.8: seq=14 ttl=58 time=13.310 ms

64 bytes from 8.8.8.8: seq=15 ttl=58 time=13.400 ms

64 bytes from 8.8.8.8: seq=16 ttl=58 time=13.286 ms

64 bytes from 8.8.8.8: seq=17 ttl=58 time=12.951 ms

64 bytes from 8.8.8.8: seq=18 ttl=58 time=12.789 ms

64 bytes from 8.8.8.8: seq=19 ttl=58 time=12.956 ms

 

--- 8.8.8.8 ping statistics ---

20 packets transmitted, 20 packets received, 0% packet loss

round-trip min/avg/max = 12.789/13.203/13.580 ms

Trace

traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 38 byte packets

1 192.168.1.254 1.012 ms 0.915 ms 0.909 ms

2 84.93.253.96 11.809 ms 11.468 ms 11.545 ms

3 84.93.253.99 12.191 ms 11.923 ms 11.986 ms

4 195.99.125.130 12.178 ms 12.249 ms 11.928 ms

5 62.172.103.195 12.853 ms 109.159.252.130 12.615 ms 62.172.103.199 12.013 ms

6 109.159.253.67 12.077 ms 109.159.253.189 12.666 ms 195.99.126.187 12.346 ms

7 108.170.246.129 13.254 ms * *

8 64.233.175.152 14.903 ms 108.170.232.104 15.470 ms 74.125.253.228 12.886 ms

9 8.8.8.8 13.837 ms 108.170.230.165 12.948 ms 216.239.47.195 13.571 ms

Looks about as stable as the connection of anyone else getting milked by spongebobs haha

[mike]

well i have turned on auto and bleeding edge and the results are even worse , im getting shot by players i cant see eg i can be running across the map no ones there , no ones there and im shot in the face by someone who it seems has teleported in , on v2 a player ran past me and had no idea i was there so i turned fired and didnt even get a hit marker even though i was aiming dead center he was moving that fast i had to exit ads turn aim again and fire (i know that the slow turning is down to my settings so thats not the issue) i then turned back and got another 2 kills , now as this was the play of the game i got to watch it all again in slo mo.

 

just now i ran into 3 players in du mont and im thinking the triple is on here maybe a quad as there all in a line , i got one kill the screen jumped and im dead.

 

on du hoc i ran down the trench ramp past the tunnel on the right that leads to the pill boxes again the screen jumped and im dead only im now at the bottom of the ramp and near the tunnel i had already ran past !!!.

 

ill keep the R1 on for the rest of today and monday when i finish work ill plug my ps4 into the isp router direct to see if theres any difference.