So, I am constantly getting these 2 to 3 seconds where everything freezes and then all player characters move really quickly into the place they are actually located within the game. It is NOT a graphical problem as I have already tried setting everything to the lowest level and still have the same problem. Also my ping directly to the NA Square Enix servers tested through the command prompt is never above 100ms so I know for sure it is not my ping. Also, when these moments of lag are happening, I can still for example heal my party in a dungeon and for them it actually shows up and works but on my end I see no updates to the UI or the characters themselves.
That's pretty much all I can think of to explain right now so if you would like more information on something just let me know and I'll get it for you.
Strange Network Lag
Printable View
-
10-20-2013, 01:50 PMKasteusStrange Network Lag
-
10-20-2013, 01:53 PMKasteus
I guess I should also note that this does not only happen in dungeons, it is happening on my home server as well.
-
10-20-2013, 01:57 PMWipp
This happens all the time or only on peak hours ?
Also, can you post a tracert to your server IP ? (you can hide first 3 jumps) -
10-20-2013, 02:03 PMxSGxSamurai
Maybe it is a hardware issue?
-
10-20-2013, 02:09 PMKasteus
It happens all throughout the day
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Nate>tracert 184.107.107.176
Tracing route to 184.107.107.176 over a maximum of 30 hops
4 8 ms 13 ms 10 ms mcdldsrj01-ae2.0.rd.ph.cox.net [70.169.76.225]
5 * 21 ms 24 ms 68.1.5.139
6 26 ms 23 ms 22 ms te0-0-0-32.ccr23.lax05.atlas.cogentco.com [38.10
4.84.13]
7 22 ms 25 ms * be2179.ccr22.lax01.atlas.cogentco.com [154.54.41
.81]
8 * 57 ms 62 ms be2068.mpd22.iah01.atlas.cogentco.com [154.54.7.
157]
9 62 ms * 69 ms be2144.ccr21.dfw01.atlas.cogentco.com [154.54.25
.106]
10 76 ms 74 ms 84 ms be2064.mpd21.mci01.atlas.cogentco.com [154.54.5.
217]
11 84 ms 87 ms 85 ms be2158.mpd21.ord01.atlas.cogentco.com [154.54.7.
130]
12 107 ms 98 ms 99 ms be2082.ccr22.yyz02.atlas.cogentco.com [154.54.28
.10]
13 103 ms 98 ms 100 ms te4-1.mag01.yyz02.atlas.cogentco.com [154.54.40.
154]
14 103 ms 103 ms 100 ms te4-1.ccr01.yyz03.atlas.cogentco.com [154.54.45.
118]
15 100 ms 102 ms 106 ms 38.122.70.186
16 103 ms 103 ms 102 ms te8-2.cr1.mtl.iweb.com [67.205.127.121]
17 101 ms 104 ms 103 ms te7-4.dr9.mtl.iweb.com [184.107.1.110]
18 102 ms 101 ms 105 ms 72.55.128.44
19 103 ms 107 ms 104 ms 184.107.107.176
Trace complete.
C:\Users\Nate>PING 184.107.107.176
Pinging 184.107.107.176 with 32 bytes of data:
Reply from 184.107.107.176: bytes=32 time=111ms TTL=49
Reply from 184.107.107.176: bytes=32 time=106ms TTL=49
Reply from 184.107.107.176: bytes=32 time=105ms TTL=49
Reply from 184.107.107.176: bytes=32 time=104ms TTL=49
Ping statistics for 184.107.107.176:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 104ms, Maximum = 111ms, Average = 106ms -
10-20-2013, 02:50 PMGradius
Hello there! A tool that I and my FC uses to help alleviate latency in this game (since the NA servers are hosted in Montreal, making the normal latency around 100 or so) is the Leatrix Latency Fix. It makes a small change to the network settings in your windows registry and it helps makes the game more responsive. I don't know if it will help you in this case has the "fix" has mixed results. But for those of us running things like Titan, etc. it made a noticable difference in getting hit by AoE effects.
You can find some info on our guild's site: http://www.thechosenguild.net/finalf...o-help-latency -
10-20-2013, 02:53 PMKasteusI unfortunately can not see the thread on your guild site.Quote:
Originally Posted by Gradius
-
10-20-2013, 03:01 PMRaistQuote:
Originally Posted by Kasteus
Need the IP for your game server, not the www.eidos.com webserver. That server is in a subnet managed by a different company, and because it's physically in a different section of Montreal, it breaks off differently once it hits the Montreal area. Open Resource Monitor (run resmon) and find FFXIV in the networking section to see what IP's you are connecting to when in game. There will be more than one. You need the one starting with 199 for NA/EU (the one starting with 124 is a connection to Japan and is idle most the time).
You likely will still come across those struggling cogentco segments though...they've been having problems in both LA and San Jose for some time now. Interesting that it is following over to Texas too. -
10-20-2013, 03:03 PMGradius
So sorry! I didn't realize this was in our private section. Here is the link to the program if you want to give it a shot. It isn't designed for any single game specifically, but it works for many games.
Download Page -
10-20-2013, 03:34 PMKasteusMy bad, here you goQuote:
Originally Posted by Raist
C:\Users\Nate>tracert 199.91.189.46
Tracing route to 199.91.189.46 over a maximum of 30 hops
4 8 ms 16 ms 12 ms chnddsrj01-ae2.0.rd.ph.cox.net [70.169.76.229]
5 * * * Request timed out.
6 20 ms 22 ms 22 ms ae2-223.lax20.ip4.tinet.net [173.241.128.81]
7 105 ms 108 ms 105 ms xe-1-3-0.mtl10.ip4.tinet.net [89.149.184.74]
8 107 ms 105 ms 105 ms ormuco-gw.ip4.tinet.net [216.221.156.110]
9 112 ms 105 ms 108 ms 192.34.76.2
10 109 ms 109 ms 107 ms 199.91.189.234
11 111 ms 108 ms 121 ms 199.91.189.46
Trace complete.
C:\Users\Nate>PING 199.91.189.46
Pinging 199.91.189.46 with 32 bytes of data:
Reply from 199.91.189.46: bytes=32 time=109ms TTL=245
Reply from 199.91.189.46: bytes=32 time=108ms TTL=245
Reply from 199.91.189.46: bytes=32 time=112ms TTL=245
Reply from 199.91.189.46: bytes=32 time=109ms TTL=245
Ping statistics for 199.91.189.46:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 108ms, Maximum = 112ms, Average = 109ms
C:\Users\Nate>