...talking to players is like being a mall Santa. Everyone immediately wants to tell you all of the things they want, and you are absolutely powerless to deliver 99% of them.
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168
2 30 ms 22 ms 19 ms cpe-76-190-160-1.neo.res.rr.com [76.190.160.1]
3 9 ms 10 ms 10 ms tge1-8.grfdoh1-rtr1.neo.rr.com [24.164.104.125]
4 10 ms 10 ms 10 ms tge9-2.clvhoh1-rtr1.neo.rr.com [24.164.107.130]
5 13 ms 14 ms 14 ms tge0-9-0-1.clevohek02r.midwest.rr.com [24.164.11
7.128]
6 14 ms 14 ms 14 ms be25.clevohek01r.midwest.rr.com [65.29.1.32]
7 21 ms 22 ms 22 ms ae10-0.cr0.dca20.tbone.rr.com [107.14.19.14]
8 19 ms 20 ms 20 ms ae-2-0.c1.nyc90.tbone.rr.com [66.109.1.49]
9 53 ms 53 ms 52 ms te0-16-0-23.ccr41.iad02.atlas.cogentco.com [154.
54.10.209]
10 58 ms 62 ms 63 ms be2177.ccr22.dca01.atlas.cogentco.com [154.54.41
.206]
11 65 ms 66 ms 67 ms be2149.ccr22.jfk02.atlas.cogentco.com [154.54.31
.126]
12 74 ms 73 ms 69 ms be2096.ccr22.bos01.atlas.cogentco.com [154.54.30
.42]
13 74 ms 72 ms 68 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.
130]
14 74 ms 86 ms 69 ms 38.111.40.114
15 74 ms 74 ms 77 ms patchserver2.crypticstudios.com [208.95.185.41]
...talking to players is like being a mall Santa. Everyone immediately wants to tell you all of the things they want, and you are absolutely powerless to deliver 99% of them.
Been having the same issues since the Day after the Winter event came online.. Tried to submit a ticket but got no feedback if the ticket went through.. I ran this when the system was having a difficult time. I have found that before changing maps if I try to load the launcher webpage in a browser and the "Perfect World" logo does not display in the upper left corner I will get disconnected. But that does not stop the times when I get server not responding.
Tracing route to launcher.startrekonline.com [208.95.185.44]
over a maximum of 30 hops:
1 3 ms 1 ms 1 ms 192.168.1.1
2 47 ms 26 ms 19 ms cpe-071-075-160-001.carolina.res.rr.com [71.75.160.1]
3 15 ms 24 ms 15 ms cpe-024-074-252-177.carolina.res.rr.com [24.74.252.177]
4 23 ms 32 ms 42 ms ae18.rlghncpop-rtr1.southeast.rr.com [24.93.64.4]
5 29 ms 27 ms 27 ms ae-3-0.cr0.dca10.tbone.rr.com [66.109.6.80]
6 25 ms 88 ms 26 ms ae-2-0.pr0.dca10.tbone.rr.com [66.109.6.169]
7 80 ms 80 ms 82 ms te0-16-0-23.ccr41.iad02.atlas.cogentco.com [154.54.10.209]
8 81 ms 79 ms 89 ms be2112.mpd22.dca01.atlas.cogentco.com [154.54.5.234]
9 84 ms 87 ms 87 ms be2151.mpd22.jfk02.atlas.cogentco.com [154.54.40.74]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 50 ms 40 ms 41 ms forums.startrekonline.com [208.95.185.44]
Tracing route to launcher.startrekonline.com [208.95.185.44]
over a maximum of 30 hops:
1 1 ms <1 ms 1 ms 192.168.1.1
2 42 ms 27 ms 29 ms cpe-071-075-160-001.carolina.res.rr.com [71.75.160.1]
3 28 ms 14 ms 15 ms cpe-024-074-252-177.carolina.res.rr.com [24.74.252.177]
4 30 ms 22 ms 23 ms ae18.rlghncpop-rtr1.southeast.rr.com [24.93.64.4]
5 28 ms 31 ms 27 ms ae-3-0.cr0.dca10.tbone.rr.com [66.109.6.80]
6 38 ms 28 ms 41 ms ae-2-0.pr0.dca10.tbone.rr.com [66.109.6.169]
7 78 ms 79 ms 91 ms te0-16-0-23.ccr41.iad02.atlas.cogentco.com [154.54.10.209]
8 78 ms 92 ms 89 ms be2113.mpd21.dca01.atlas.cogentco.com [154.54.6.170]
9 87 ms 98 ms * be2151.mpd22.jfk02.atlas.cogentco.com [154.54.40.74]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 42 ms 50 ms 60 ms forums.startrekonline.com [208.95.185.44]
Tracing route to launcher.startrekonline.com [208.95.185.44]
over a maximum of 30 hops:
1 1 ms <1 ms 1 ms 192.168.1.1
2 47 ms 38 ms 48 ms cpe-071-075-160-001.carolina.res.rr.com [71.75.160.1]
3 41 ms 15 ms 25 ms cpe-024-074-252-177.carolina.res.rr.com [24.74.252.177]
4 21 ms 23 ms 23 ms ae18.rlghncpop-rtr1.southeast.rr.com [24.93.64.4]
5 29 ms 27 ms 30 ms ae-3-0.cr0.dca10.tbone.rr.com [66.109.6.80]
6 27 ms 28 ms 27 ms ae-2-0.pr0.dca10.tbone.rr.com [66.109.6.169]
7 99 ms 79 ms 79 ms te0-16-0-23.ccr41.iad02.atlas.cogentco.com [154.54.10.209]
8 82 ms 78 ms 79 ms be2177.ccr22.dca01.atlas.cogentco.com [154.54.41.206]
9 99 ms 87 ms * be2149.ccr22.jfk02.atlas.cogentco.com [154.54.31.126]
10 103 ms 92 ms 92 ms be2094.ccr21.bos01.atlas.cogentco.com [154.54.30.14]
11 91 ms 114 ms 96 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42]
12 111 ms 51 ms 50 ms 38.111.40.114
13 40 ms 40 ms 41 ms forums.startrekonline.com [208.95.185.44]
Trace complete.
C:\Users\CyborgNC>
EDIT: Fired up a VPN out of the midwest and no connection issues..
Tracing route to launcher.startrekonline.com [208.95.185.44]
over a maximum of 30 hops:
1 53 ms 68 ms 55 ms 10.132.1.1
2 * * * Request timed out.
3 55 ms 55 ms 57 ms ae2.er2.ord7.us.above.net [208.184.110.229]
4 54 ms 63 ms 53 ms ae4.cr2.ord2.us.above.net [64.125.20.41]
5 66 ms 56 ms 57 ms ae5.cr1.ord2.us.above.net [64.125.28.233]
6 85 ms 71 ms 116 ms ae6.cr1.lga5.us.above.net [64.125.24.33]
7 78 ms 106 ms 87 ms xe-1-1-0.mpr3.bos2.us.above.net [64.125.25.41]
8 82 ms 92 ms 83 ms 208.184.110.70.IPYX-072053-002-ZYO.above.net [20
8.184.110.70]
9 86 ms 80 ms 82 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
04]
10 77 ms 91 ms 87 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
11 80 ms 88 ms 90 ms www.startrekonline.com [208.95.185.44]
While I appreciate that "everything looks good" on your end. Is there ever going to be acknowledgement that when you guys do whatever it is you did in the last week to your code, chunks of your playerbase suddenly cannot maintain a connection to the game?
Of course not. It's always our problem, and not STO's flawless servers and software.
It's just pure coincidence that thousands of us tend to have major connection problems simultaneously.
I am currently at Server Not Responding in WW for over 400secs and I have not been kicked...which is really annoying because I cannot do anything :mad:
I had no problems an hour ago, I log in to do my races for the day and pow...Server issues. My network is fine, my internet connection is functioning perfectly- Now at 700 secs not responding
i was a SNR for a cpl hundred sec and no kick so i closed out. then tried to re connect and no dice. keeps saying "connection to log in server timed out". i know its not on my end cuz i was just in game lol. any ideas cryptic???
The problem is with te3-2.ccr01.bos06.atlas.cogentco.com. There is a significant amount of packet loss coming from it.
It is not a problem with anyone's computers but rather one of the backbones. Cryptic/PW should get on it because they have a lot more influence; Cogent will not care if we complain.
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
...
Try replacing the 'tracert' command with the 'pathping' command, as unlike 'Trace Route', 'Path Ping' will show if you have a dropped packet issue, and where it is occurring...
The problem is with te3-2.ccr01.bos06.atlas.cogentco.com. There is a significant amount of packet loss coming from it.
It is not a problem with anyone's computers but rather one of the backbones. Cryptic/PW should get on it because they have a lot more influence; Cogent will not care if we complain.
Though keep in mind that compared to the likes of Netflix, YouTube and Hulu, PWE is a very small fish in a very large pond... Cogent happens to host Netflix Servers, and you can bet that complaints from Netflix will have priority over complaints from PWE...
Though keep in mind that compared to the likes of Netflix, YouTube and Hulu, PWE is a very small fish in a very large pond... Cogent happens to host Netflix Servers, and you can bet that complaints from Netflix will have priority over complaints from PWE...
Yes, but, PWE is a customer. I am not. If I were to call their NOC, they would not even give me the time of day. Presumably, PWE has some sort of SLA that guarantees a certain level of service.
Yes, but, PWE is a customer. I am not. If I were to call their NOC, they would not even give me the time of day. Presumably, PWE has some sort of SLA that guarantees a certain level of service.
And this is the reason why STO Users with connection issues should be posting their 'Trace Route' and 'Path Ping' diagnostics on the PWE Tech Support Forum... To expect PWE to yell at Cogent to 'FIX IT' without any evidence what the issues are just isn't going to work...
Packet drop up and down the Cogent backbone. This should be posted in the networking section of the PWE Tech Support Forum so that PWE can kick Cogent a few more times with it... Packet drop of 5% - 15% might be acceptable for a TCP/IP connection, but above that...
Packet drop up and down the Cogent backbone. This should be posted in the networking section of the PWE Tech Support Forum so that PWE can kick Cogent a few more times with it... Packet drop of 5% - 15% might be acceptable for a TCP/IP connection, but above that...
I wouldn't be able to live with myself if I allowed 15% packet drop on my networks (other than traffic shaping) and I know of no SLAs that would allow for that.
Well it could be a DX11 problem indeed , correct me if im wrong but i really think it is
because everytime you load into a area/map then the game is patching , so it means your getting those data about that specific map straight from the STO servers.
And indeed if the DX11 is glitching and loading to long it will lose connection.
Im gonna try tommorow to play whole day on DX9 and look if there is any difference.
i tried all 3 versions of DirectX today. still didnt solve my issue. still dc 1 to 5 minutes into the game no matter where im at or doing in it. But i must say its saved me 100$ this weekend lol.
So far so good.
Saturday I played about 3 hours and today about 3 hours.
Haven't been dc'd as of yet.
I remember a thread where a dev had said playing in dx9 mode is recommended. Being that some things don't crossover so well to dx11. Could cause errors etc.
This was a support thread for S8, when it first got patched.
I could buy the problem was on my end IF the constant DC's had not started the gaming session following downloading the Wonderland patch.
In all the time playing STO up till that point I'd been DC'd perhaps twice. Now it happens at least four to five times an hour. Game Server, Login Server, Account Server, error after error after error.
I can stream 1080p video without a hitch while surfing the Internet and streaming music. Yet even if I shutdown every program I still DC constantly with STO.
I was going to ask the wife for a subscription for the holidays. That's off the table until this gets fixed. Like domvina said, I've had very few DCs prior to the wonderland update. Coincidence? Maybe. But given the history of post content patches, my money is staying in my pocket for now.
Tracing route to 208.95.186.32 over a maximum of 30 hops
1 28 ms 27 ms 28 ms cpe-075-183-016-001.triad.res.rr.com [75.183.16.
1]
2 15 ms 12 ms 14 ms te-14-0-0.gnboncsg-rtr1.triad.rr.com [24.28.229.
17]
3 19 ms 20 ms 18 ms ge-3-1-0.rlghncpop-rtr1.southeast.rr.com [24.93.
64.178]
4 22 ms 22 ms 27 ms 107.14.19.44
5 37 ms 24 ms 24 ms ae-2-0.pr0.dca10.tbone.rr.com [66.109.6.169]
6 79 ms 78 ms 78 ms te0-16-0-23.ccr41.iad02.atlas.cogentco.com [154.
54.10.209]
7 78 ms 78 ms 77 ms be2113.mpd21.dca01.atlas.cogentco.com [154.54.6.
170]
8 84 ms 86 ms 84 ms be2149.ccr22.jfk02.atlas.cogentco.com [154.54.31
.126]
9 * 90 ms 91 ms be2094.ccr21.bos01.atlas.cogentco.com [154.54.30
.14]
10 90 ms 90 ms 89 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.
130]
11 39 ms 33 ms 34 ms 38.111.40.114
12 37 ms 37 ms 38 ms 208.95.186.32
Trace complete.
"Great War! / And I cannot take more! / Great tour! / I keep on marching on / I play the great score / There will be no encore / Great War! / The War to End All Wars"
— Sabaton, "Great War"
Tracing route to 208.95.186.32 over a maximum of 30 hops
1 28 ms 27 ms 28 ms cpe-075-183-016-001.triad.res.rr.com [75.183.16.
1]
2 15 ms 12 ms 14 ms te-14-0-0.gnboncsg-rtr1.triad.rr.com [24.28.229.
17]
3 19 ms 20 ms 18 ms ge-3-1-0.rlghncpop-rtr1.southeast.rr.com [24.93.
64.178]
4 22 ms 22 ms 27 ms 107.14.19.44
5 37 ms 24 ms 24 ms ae-2-0.pr0.dca10.tbone.rr.com [66.109.6.169]
6 79 ms 78 ms 78 ms te0-16-0-23.ccr41.iad02.atlas.cogentco.com [154.
54.10.209]
7 78 ms 78 ms 77 ms be2113.mpd21.dca01.atlas.cogentco.com [154.54.6.
170]
8 84 ms 86 ms 84 ms be2149.ccr22.jfk02.atlas.cogentco.com [154.54.31
.126]
9 * 90 ms 91 ms be2094.ccr21.bos01.atlas.cogentco.com [154.54.30
.14]
10 90 ms 90 ms 89 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.
130]
11 39 ms 33 ms 34 ms 38.111.40.114
12 37 ms 37 ms 38 ms 208.95.186.32
Trace complete.
So substitute the 'pathping' command for the 'tracert' command, and see if you're suffering from packet drop issues on your connection... as 'Trace Route' won't show packet drop...
I just spent 15m trying to log in after being DC'd. Constant issues with connecting to the Gamer server, the Login server, the Account server. Everytime one server let me in another would kick me out. Here's the tracert:
tracert 208.95.185.41
Tracing route to patchserver2.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.1.1
2 37 ms 12 ms 19 ms cpe-024-074-032-001.carolina.res.rr.com [24.74.32.1]
3 12 ms 9 ms 17 ms cpe-024-074-252-193.carolina.res.rr.com [24.74.252.193]
4 20 ms 18 ms 20 ms ae18.rlghncpop-rtr1.southeast.rr.com [24.93.64.4]
5 23 ms 23 ms 28 ms 107.14.19.44
6 22 ms 29 ms 24 ms ae-2-0.pr0.dca10.tbone.rr.com [66.109.6.169]
7 89 ms 112 ms 84 ms te0-16-0-23.ccr41.iad02.atlas.cogentco.com [154.54.10.209]
8 83 ms 85 ms 84 ms be2113.mpd21.dca01.atlas.cogentco.com [154.54.6.170]
9 96 ms 93 ms 93 ms be2150.mpd21.jfk02.atlas.cogentco.com [154.54.31.130]
10 98 ms 99 ms 99 ms be2095.ccr21.bos01.atlas.cogentco.com [154.54.30.38]
11 97 ms 99 ms 99 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.134]
12 35 ms 41 ms 33 ms 38.111.40.114
13 37 ms 34 ms 34 ms patchserver2.crypticstudios.com [208.95.185.41]
I will give Cryptic one potential "out" on this issue because I did see something similar in a different game many years ago. One of the Internet nodes between the primary IP provider in my state and the neighboring states and the game's server location went down due to poor weather. With that node down game play became nearly impossible due to massive lag and constant DC's for all players in those states. This situation looks a lot like it did that time.
Unfortunately a fix only happened when the node was finally brought back online after nearly a month.
Comments
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168
2 30 ms 22 ms 19 ms cpe-76-190-160-1.neo.res.rr.com [76.190.160.1]
3 9 ms 10 ms 10 ms tge1-8.grfdoh1-rtr1.neo.rr.com [24.164.104.125]
4 10 ms 10 ms 10 ms tge9-2.clvhoh1-rtr1.neo.rr.com [24.164.107.130]
5 13 ms 14 ms 14 ms tge0-9-0-1.clevohek02r.midwest.rr.com [24.164.11
7.128]
6 14 ms 14 ms 14 ms be25.clevohek01r.midwest.rr.com [65.29.1.32]
7 21 ms 22 ms 22 ms ae10-0.cr0.dca20.tbone.rr.com [107.14.19.14]
8 19 ms 20 ms 20 ms ae-2-0.c1.nyc90.tbone.rr.com [66.109.1.49]
9 53 ms 53 ms 52 ms te0-16-0-23.ccr41.iad02.atlas.cogentco.com [154.
54.10.209]
10 58 ms 62 ms 63 ms be2177.ccr22.dca01.atlas.cogentco.com [154.54.41
.206]
11 65 ms 66 ms 67 ms be2149.ccr22.jfk02.atlas.cogentco.com [154.54.31
.126]
12 74 ms 73 ms 69 ms be2096.ccr22.bos01.atlas.cogentco.com [154.54.30
.42]
13 74 ms 72 ms 68 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.
130]
14 74 ms 86 ms 69 ms 38.111.40.114
15 74 ms 74 ms 77 ms patchserver2.crypticstudios.com [208.95.185.41]
How about your firewall software? Could it be interfering in some way?
I'm just running through a list of problems I've encountered personally in the past.
Thanks for the help, I know dX'ing tech issues over the internet is a thankless task.
EDIT: Fired up a VPN out of the midwest and no connection issues..
Of course not. It's always our problem, and not STO's flawless servers and software.
It's just pure coincidence that thousands of us tend to have major connection problems simultaneously.
I had no problems an hour ago, I log in to do my races for the day and pow...Server issues. My network is fine, my internet connection is functioning perfectly- Now at 700 secs not responding
It is not a problem with anyone's computers but rather one of the backbones. Cryptic/PW should get on it because they have a lot more influence; Cogent will not care if we complain.
Try replacing the 'tracert' command with the 'pathping' command, as unlike 'Trace Route', 'Path Ping' will show if you have a dropped packet issue, and where it is occurring...
Though keep in mind that compared to the likes of Netflix, YouTube and Hulu, PWE is a very small fish in a very large pond... Cogent happens to host Netflix Servers, and you can bet that complaints from Netflix will have priority over complaints from PWE...
Yes, but, PWE is a customer. I am not. If I were to call their NOC, they would not even give me the time of day. Presumably, PWE has some sort of SLA that guarantees a certain level of service.
And this is the reason why STO Users with connection issues should be posting their 'Trace Route' and 'Path Ping' diagnostics on the PWE Tech Support Forum... To expect PWE to yell at Cogent to 'FIX IT' without any evidence what the issues are just isn't going to work...
http://techsupport.perfectworld.com/
over a maximum of 30 hops:
1 192.168
2 cpe-76-190-160-1.neo.res.rr.com [76.190.160.1]
3 tge1-8.grfdoh1-rtr1.neo.rr.com [24.164.104.125]
4 tge9-2.clvhoh1-rtr1.neo.rr.com [24.164.107.130]
5 tge0-9-0-1.clevohek02r.midwest.rr.com [24.164.117.128]
6 be25.clevohek01r.midwest.rr.com [65.29.1.32]
7 ae10-0.cr0.dca20.tbone.rr.com [107.14.19.14]
8 ae-2-0.c1.nyc90.tbone.rr.com [66.109.1.49]
9 te0-16-0-23.ccr41.iad02.atlas.cogentco.com [154.54.10.209]
10 be2176.ccr21.dca01.atlas.cogentco.com [154.54.41.54]
11 be2148.ccr21.jfk02.atlas.cogentco.com [154.54.31.118]
12 be2094.ccr21.bos01.atlas.cogentco.com [154.54.30.14]
13 te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42]
14 38.111.40.114
15 patchserver2.crypticstudios.com [208.95.185.41]
Computing statistics for 375 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Isabella []
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0%
0/ 100 = 0% |
2 12ms 0/ 100 = 0% 0/ 100 = 0% cpe-76-190-160-1.neo.res.rr.com [7
6.190.160.1]
0/ 100 = 0% |
3 11ms 0/ 100 = 0% 0/ 100 = 0% tge1-8.grfdoh1-rtr1.neo.rr.com [24
.164.104.125]
0/ 100 = 0% |
4 11ms 0/ 100 = 0% 0/ 100 = 0% tge9-2.clvhoh1-rtr1.neo.rr.com [24
.164.107.130]
0/ 100 = 0% |
5 13ms 0/ 100 = 0% 0/ 100 = 0% tge0-9-0-1.clevohek02r.midwest.rr.
com [24.164.117.128]
0/ 100 = 0% |
6 12ms 0/ 100 = 0% 0/ 100 = 0% be25.clevohek01r.midwest.rr.com [6
5.29.1.32]
0/ 100 = 0% |
7 22ms 0/ 100 = 0% 0/ 100 = 0% ae10-0.cr0.dca20.tbone.rr.com [107
.14.19.14]
0/ 100 = 0% |
8 21ms 0/ 100 = 0% 0/ 100 = 0% so-1-1-1.a0.alb75.tbone.rr.com [66
.109.1.49]
1/ 100 = 1% |
9 60ms 2/ 100 = 2% 1/ 100 = 1% te0-16-0-23.ccr41.iad02.atlas.coge
ntco.com [154.54.10.209]
0/ 100 = 0% |
10 61ms 5/ 100 = 5% 4/ 100 = 4% be2176.ccr21.dca01.atlas.cogentco.
com [154.54.41.54]
0/ 100 = 0% |
11 67ms 42/ 100 = 42% 41/ 100 = 41% be2148.ccr21.jfk02.atlas.cogentco.
com [154.54.31.118]
0/ 100 = 0% |
12 73ms 1/ 100 = 1% 0/ 100 = 0% be2094.ccr21.bos01.atlas.cogentco.
com [154.54.30.14]
2/ 100 = 2% |
13 --- 100/ 100 =100% 97/ 100 = 97% te4-4.ccr01.bos06.atlas.cogentco.c
om [66.28.4.42]
0/ 100 = 0% |
14 78ms 3/ 100 = 3% 0/ 100 = 0% 38.111.40.114
37/ 100 = 37% |
15 72ms 40/ 100 = 40% 0/ 100 = 0% patchserver2.crypticstudios.com [2
08.95.185.41]
Trace complete.
Packet drop up and down the Cogent backbone. This should be posted in the networking section of the PWE Tech Support Forum so that PWE can kick Cogent a few more times with it... Packet drop of 5% - 15% might be acceptable for a TCP/IP connection, but above that...
I wouldn't be able to live with myself if I allowed 15% packet drop on my networks (other than traffic shaping) and I know of no SLAs that would allow for that.
This is apparently not a limited problem :
https://twitter.com/search?q=cogent%20packet&src=typd
because everytime you load into a area/map then the game is patching , so it means your getting those data about that specific map straight from the STO servers.
And indeed if the DX11 is glitching and loading to long it will lose connection.
Im gonna try tommorow to play whole day on DX9 and look if there is any difference.
Saturday I played about 3 hours and today about 3 hours.
Haven't been dc'd as of yet.
I remember a thread where a dev had said playing in dx9 mode is recommended. Being that some things don't crossover so well to dx11. Could cause errors etc.
This was a support thread for S8, when it first got patched.
Anyways that's my 2 ec.
Hope it helps someone .
I'm not saying it is your problem, but it's not on our end, as evidenced by the tracerts posted in this thread.
Here's what I've done: I've passed along your tracerts to the team and requested, that if possible, to forward them along to the Cognet.
While I wish there was more we could do in the immediate, I will continue to monitor the tracerts posted in this thread and forward them along.
Cheers,
Brandon =/\=
In all the time playing STO up till that point I'd been DC'd perhaps twice. Now it happens at least four to five times an hour. Game Server, Login Server, Account Server, error after error after error.
I can stream 1080p video without a hitch while surfing the Internet and streaming music. Yet even if I shutdown every program I still DC constantly with STO.
Tracing route to 208.95.186.32 over a maximum of 30 hops
1 28 ms 27 ms 28 ms cpe-075-183-016-001.triad.res.rr.com [75.183.16.
1]
2 15 ms 12 ms 14 ms te-14-0-0.gnboncsg-rtr1.triad.rr.com [24.28.229.
17]
3 19 ms 20 ms 18 ms ge-3-1-0.rlghncpop-rtr1.southeast.rr.com [24.93.
64.178]
4 22 ms 22 ms 27 ms 107.14.19.44
5 37 ms 24 ms 24 ms ae-2-0.pr0.dca10.tbone.rr.com [66.109.6.169]
6 79 ms 78 ms 78 ms te0-16-0-23.ccr41.iad02.atlas.cogentco.com [154.
54.10.209]
7 78 ms 78 ms 77 ms be2113.mpd21.dca01.atlas.cogentco.com [154.54.6.
170]
8 84 ms 86 ms 84 ms be2149.ccr22.jfk02.atlas.cogentco.com [154.54.31
.126]
9 * 90 ms 91 ms be2094.ccr21.bos01.atlas.cogentco.com [154.54.30
.14]
10 90 ms 90 ms 89 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.
130]
11 39 ms 33 ms 34 ms 38.111.40.114
12 37 ms 37 ms 38 ms 208.95.186.32
Trace complete.
— Sabaton, "Great War"
Check out https://unitedfederationofpla.net/s/
So substitute the 'pathping' command for the 'tracert' command, and see if you're suffering from packet drop issues on your connection... as 'Trace Route' won't show packet drop...
tracert 208.95.185.41
Tracing route to patchserver2.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.1.1
2 37 ms 12 ms 19 ms cpe-024-074-032-001.carolina.res.rr.com [24.74.32.1]
3 12 ms 9 ms 17 ms cpe-024-074-252-193.carolina.res.rr.com [24.74.252.193]
4 20 ms 18 ms 20 ms ae18.rlghncpop-rtr1.southeast.rr.com [24.93.64.4]
5 23 ms 23 ms 28 ms 107.14.19.44
6 22 ms 29 ms 24 ms ae-2-0.pr0.dca10.tbone.rr.com [66.109.6.169]
7 89 ms 112 ms 84 ms te0-16-0-23.ccr41.iad02.atlas.cogentco.com [154.54.10.209]
8 83 ms 85 ms 84 ms be2113.mpd21.dca01.atlas.cogentco.com [154.54.6.170]
9 96 ms 93 ms 93 ms be2150.mpd21.jfk02.atlas.cogentco.com [154.54.31.130]
10 98 ms 99 ms 99 ms be2095.ccr21.bos01.atlas.cogentco.com [154.54.30.38]
11 97 ms 99 ms 99 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.134]
12 35 ms 41 ms 33 ms 38.111.40.114
13 37 ms 34 ms 34 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
Tracing route to patchserver2.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
0 Serenity [192.168.1.2]
1 192.168.1.1
2 cpe-024-074-032-001.carolina.res.rr.com [24.74.32.1]
3 cpe-024-074-252-193.carolina.res.rr.com [24.74.252.193]
4 ae18.rlghncpop-rtr1.southeast.rr.com [24.93.64.4]
5 107.14.19.44
6 * * *
Computing statistics for 125 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Serenity [192.168.1.2]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 17ms 0/ 100 = 0% 0/ 100 = 0% cpe-024-074-032-001.carolina.res.rr.com [24.74.32.1]
0/ 100 = 0% |
3 16ms 0/ 100 = 0% 0/ 100 = 0% cpe-024-074-252-193.carolina.res.rr.com [24.74.252.193]
0/ 100 = 0% |
4 20ms 0/ 100 = 0% 0/ 100 = 0% ae18.rlghncpop-rtr1.southeast.rr.com [24.93.64.4]
0/ 100 = 0% |
5 26ms 0/ 100 = 0% 0/ 100 = 0% 107.14.19.44
Trace complete.
Unfortunately a fix only happened when the node was finally brought back online after nearly a month.
Looks like 'Path Ping' gave up when trying to enter the Cogent backbone...
That first 1% packet loss is within acceptable limits, but once again, were seeing packet drop up and down the Cogent backbone...