Jump to content

R1 Settings. Fifa 18


Recommended Posts

Yes you made the correct choices for cloud. I'll check that ID and see what is happening. 

 

Your ping assist will allow you to get games outside your radius.

everytime i use netduma in fifa 18 i keep getting fast forward lag and then i keep getting disconnected without the netduma i dont get dc and this didn't happen in fifa 17 

Link to comment
Share on other sites

  • Replies 67
  • Created
  • Last Reply

hi fraser, I did other tests and my ping  and tracerouting with easo.ea.com its hight 126/128 ms. i called upc and the technician did the same test from his place and its the same. Ea support told me they are perfect, the made perfect game, the servers working good so a prerecorder message with bullsheet.

I opened a case with upc but im not sure that is ISP problem. So many peoples sent message with tracerouting on attach nobody less to 100ms. the good thing are i don't have packet loss.

yesterday night my connection was terrible fast. scripting matches, crazy menus. i did the traceroute 128 ms

Today the game was close to be perfect. i did traceroute the SAME. Same ping same route, same steps

i think this is fake test to hidden the true.

i dont understand when i play on the fut champion server netduma show me Francoforte ping 19ms and that is not indicator for a good game. the ping are always the same, the matches change.

the netduma ping with that server are so many different in front at the path ping to the easo.ea.com

I need good help because we have to clarify this situation on the deep fog

 

 

traceroute to easo.ea.com (159.153.234.54), 64 hops max, 72 byte packets
 1  r1 (192.168.88.1)  0.603 ms  0.302 ms  0.262 ms
 2  * * *
 3  ip-86-49-55-193.net.upcbroadband.cz (86.49.55.193)  6.796 ms  6.727 ms  6.267 ms
 4  cz-prg01a-ra4-vla2156.net.upc.cz (84.116.221.225)  6.844 ms  7.071 ms  7.114 ms
 5  cz-prg02b-ri1-ae10-0.aorta.net (84.116.137.18)  7.321 ms  7.224 ms  8.111 ms
 6  213.46.180.82 (213.46.180.82)  6.965 ms  6.699 ms  7.951 ms
 7  win-bb2-link.telia.net (80.91.249.179)  12.442 ms  13.325 ms  12.880 ms
 8  ffm-bb4-link.telia.net (213.155.136.140)  20.196 ms  20.694 ms  20.698 ms
 9  ffm-b4-link.telia.net (62.115.125.215)  19.817 ms  20.399 ms  20.630 ms
10  akamai-ic-317158-ffm-b4.c.telia.net (62.115.149.19)  40.829 ms  40.354 ms  39.888 ms
11  a72-52-48-192.deploy.static.akamaitechnologies.com (72.52.48.192)  40.450 ms  39.339 ms  40.029 ms
12  a72-52-48-197.deploy.static.akamaitechnologies.com (72.52.48.197)  40.289 ms  39.578 ms  41.289 ms
13  * * *
14  a209-200-168-132.deploy.static.akamaitechnologies.com (209.200.168.132)  129.078 ms  128.868 ms  127.841 ms
15  159.153.93.2 (159.153.93.2)  128.001 ms  128.287 ms  128.357 ms
16  159.153.225.69 (159.153.225.69)  127.896 ms  127.878 ms  127.767 ms
17  159.153.226.67 (159.153.226.67)  127.897 ms  129.339 ms  127.915 ms
18  easo.ea.com (159.153.234.54)  128.735 ms  128.387 ms  129.053 ms

 

 

 

Ping has started…

PING easo.ea.com (159.153.234.54): 56 data bytes
64 bytes from 159.153.234.54: icmp_seq=0 ttl=112 time=128.872 ms
64 bytes from 159.153.234.54: icmp_seq=1 ttl=112 time=129.435 ms
64 bytes from 159.153.234.54: icmp_seq=2 ttl=112 time=129.671 ms
64 bytes from 159.153.234.54: icmp_seq=3 ttl=112 time=128.509 ms
64 bytes from 159.153.234.54: icmp_seq=4 ttl=112 time=133.687 ms
64 bytes from 159.153.234.54: icmp_seq=5 ttl=112 time=128.308 ms
64 bytes from 159.153.234.54: icmp_seq=6 ttl=112 time=128.719 ms
64 bytes from 159.153.234.54: icmp_seq=7 ttl=112 time=128.391 ms
64 bytes from 159.153.234.54: icmp_seq=8 ttl=112 time=128.233 ms
64 bytes from 159.153.234.54: icmp_seq=9 ttl=112 time=129.408 ms
64 bytes from 159.153.234.54: icmp_seq=10 ttl=112 time=128.357 ms
64 bytes from 159.153.234.54: icmp_seq=11 ttl=112 time=128.261 ms
64 bytes from 159.153.234.54: icmp_seq=12 ttl=112 time=128.684 ms
64 bytes from 159.153.234.54: icmp_seq=13 ttl=112 time=128.212 ms
64 bytes from 159.153.234.54: icmp_seq=14 ttl=112 time=129.498 ms
64 bytes from 159.153.234.54: icmp_seq=15 ttl=112 time=128.554 ms
64 bytes from 159.153.234.54: icmp_seq=16 ttl=112 time=128.839 ms
64 bytes from 159.153.234.54: icmp_seq=17 ttl=112 time=129.484 ms
64 bytes from 159.153.234.54: icmp_seq=18 ttl=112 time=128.598 ms
64 bytes from 159.153.234.54: icmp_seq=19 ttl=112 time=129.041 ms
64 bytes from 159.153.234.54: icmp_seq=20 ttl=112 time=128.358 ms
64 bytes from 159.153.234.54: icmp_seq=21 ttl=112 time=128.574 ms
64 bytes from 159.153.234.54: icmp_seq=22 ttl=112 time=128.644 ms
64 bytes from 159.153.234.54: icmp_seq=23 ttl=112 time=128.611 ms
64 bytes from 159.153.234.54: icmp_seq=24 ttl=112 time=128.145 ms
64 bytes from 159.153.234.54: icmp_seq=25 ttl=112 time=127.848 ms
64 bytes from 159.153.234.54: icmp_seq=26 ttl=112 time=135.816 ms
64 bytes from 159.153.234.54: icmp_seq=27 ttl=112 time=128.258 ms
64 bytes from 159.153.234.54: icmp_seq=28 ttl=112 time=128.369 ms
64 bytes from 159.153.234.54: icmp_seq=29 ttl=112 time=128.092 ms
64 bytes from 159.153.234.54: icmp_seq=30 ttl=112 time=128.720 ms
64 bytes from 159.153.234.54: icmp_seq=31 ttl=112 time=129.764 ms
64 bytes from 159.153.234.54: icmp_seq=32 ttl=112 time=129.933 ms
64 bytes from 159.153.234.54: icmp_seq=33 ttl=112 time=128.456 ms
64 bytes from 159.153.234.54: icmp_seq=34 ttl=112 time=128.477 ms
64 bytes from 159.153.234.54: icmp_seq=35 ttl=112 time=128.676 ms
64 bytes from 159.153.234.54: icmp_seq=36 ttl=112 time=130.208 ms
64 bytes from 159.153.234.54: icmp_seq=37 ttl=112 time=129.046 ms
64 bytes from 159.153.234.54: icmp_seq=38 ttl=112 time=128.133 ms
64 bytes from 159.153.234.54: icmp_seq=39 ttl=112 time=128.420 ms
64 bytes from 159.153.234.54: icmp_seq=40 ttl=112 time=128.578 ms
64 bytes from 159.153.234.54: icmp_seq=41 ttl=112 time=128.647 ms
64 bytes from 159.153.234.54: icmp_seq=42 ttl=112 time=128.555 ms
64 bytes from 159.153.234.54: icmp_seq=43 ttl=112 time=128.533 ms
64 bytes from 159.153.234.54: icmp_seq=44 ttl=112 time=128.615 ms
64 bytes from 159.153.234.54: icmp_seq=45 ttl=112 time=128.703 ms
64 bytes from 159.153.234.54: icmp_seq=46 ttl=112 time=128.758 ms
64 bytes from 159.153.234.54: icmp_seq=47 ttl=112 time=128.636 ms
64 bytes from 159.153.234.54: icmp_seq=48 ttl=112 time=128.328 ms
64 bytes from 159.153.234.54: icmp_seq=49 ttl=112 time=127.966 ms
64 bytes from 159.153.234.54: icmp_seq=50 ttl=112 time=129.496 ms
64 bytes from 159.153.234.54: icmp_seq=51 ttl=112 time=129.247 ms
64 bytes from 159.153.234.54: icmp_seq=52 ttl=112 time=128.397 ms
64 bytes from 159.153.234.54: icmp_seq=53 ttl=112 time=128.055 ms
64 bytes from 159.153.234.54: icmp_seq=54 ttl=112 time=128.695 ms
64 bytes from 159.153.234.54: icmp_seq=55 ttl=112 time=128.555 ms
64 bytes from 159.153.234.54: icmp_seq=56 ttl=112 time=128.747 ms
64 bytes from 159.153.234.54: icmp_seq=57 ttl=112 time=128.531 ms
64 bytes from 159.153.234.54: icmp_seq=58 ttl=112 time=129.393 ms
64 bytes from 159.153.234.54: icmp_seq=59 ttl=112 time=129.626 ms

--- easo.ea.com ping statistics ---
60 packets transmitted, 60 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 127.848/128.923/135.816/1.211 ms
 

Link to comment
Share on other sites

  • Administrators

You did a test on an EA server from California so I'm not surprised the ping is that high at all. If you do one with the ping I provided that will give us a much better indication of what's going on as it's an Amsterdam server.

Link to comment
Share on other sites

You did a test on an EA server from California so I'm not surprised the ping is that high at all. If you do one with the ping I provided that will give us a much better indication of what's going on as it's an Amsterdam server.

i know the server are on Francoforte. but in anycase when i played Fifa 17 on fut champions(california) netduma show me 45/50 max.

what do you think about that situation? why the support use the faking address for the traceroute like a gun to hidden the true? beacause if you read the answer of ea support the standard messages are: i have a problem. ok post traceroute. im sorry you have packet loss, hight ping, you are guilty. its not fifa problem. if we have a general problem all players have to complain but its only a little part of comunity, we are ok

Link to comment
Share on other sites

traceroute to 159.153.28.49 (159.153.28.49), 64 hops max, 72 byte packets
 1  * * *
 2  ip-86-49-55-193 (86.49.55.193)  7.271 ms  6.280 ms  6.373 ms
 3  cz-prg01a-ra4-vla2156.net.upc.cz (84.116.221.225)  6.870 ms  6.802 ms  6.897 ms
 4  cz-prg02b-ri1-ae0-0.aorta.net (84.116.136.169)  7.561 ms  6.353 ms  7.166 ms
 5  213.46.180.90 (213.46.180.90)  7.270 ms  7.033 ms  7.233 ms
 6  * * *
 7  213.19.196.186 (213.19.196.186)  30.874 ms  30.628 ms  30.421 ms
 8  159.153.18.122 (159.153.18.122)  30.936 ms  31.375 ms  30.884 ms
 9  gosprodfeapp7121.ea.com (159.153.28.49)  39.457 ms  39.440 ms  39.677 ms
 

Link to comment
Share on other sites

  • Administrators

i know the server are on Francoforte. but in anycase when i played Fifa 17 on fut champions(california) netduma show me 45/50 max.

what do you think about that situation? why the support use the faking address for the traceroute like a gun to hidden the true? beacause if you read the answer of ea support the standard messages are: i have a problem. ok post traceroute. im sorry you have packet loss, hight ping, you are guilty. its not fifa problem. if we have a general problem all players have to complain but its only a little part of comunity, we are ok

 

If the Netduma was showing you that low a ping to a server in California then it was a mislocated server on our map as it is impossible to have a ping that low to a place that far away. I can't answer how/why they do support the way they do.They likely have a ping in their mind that you can play the game on without too much issue and it will be higher than what you think.

 

traceroute to 159.153.28.49 (159.153.28.49), 64 hops max, 72 byte packets

 1  * * *

 2  ip-86-49-55-193 (86.49.55.193)  7.271 ms  6.280 ms  6.373 ms

 3  cz-prg01a-ra4-vla2156.net.upc.cz (84.116.221.225)  6.870 ms  6.802 ms  6.897 ms

 4  cz-prg02b-ri1-ae0-0.aorta.net (84.116.136.169)  7.561 ms  6.353 ms  7.166 ms

 5  213.46.180.90 (213.46.180.90)  7.270 ms  7.033 ms  7.233 ms

 6  * * *

 7  213.19.196.186 (213.19.196.186)  30.874 ms  30.628 ms  30.421 ms

 8  159.153.18.122 (159.153.18.122)  30.936 ms  31.375 ms  30.884 ms

 9  gosprodfeapp7121.ea.com (159.153.28.49)  39.457 ms  39.440 ms  39.677 ms

 

 

Okay that's a bit more like it. Could you please do it using ping plotter please so I can see the graph, letting it run for 10 minutes as well will give as an idea of it's fluctuations during a game.

 

https://www.pingplotter.com/download

Link to comment
Share on other sites

If the Netduma was showing you that low a ping to a server in California then it was a mislocated server on our map as it is impossible to have a ping that low to a place that far away. I can't answer how/why they do support the way they do.They likely have a ping in their mind that you can play the game on without too much issue and it will be higher than what you think.

 

 

Okay that's a bit more like it. Could you please do it using ping plotter please so I can see the graph, letting it run for 10 minutes as well will give as an idea of it's fluctuations during a game.

 

https://www.pingplotter.com/download

do you want run during the game or its the same?

Link to comment
Share on other sites

  • Administrators

That's great thanks. Your ping to the server seems fairly stable, there are a few spikes here and there that you would probably notice while gaming but not a persistent thing all game. There are a few hops on your line that could be better but they're not terrible.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...