I did have some rubberbanding today, which is not normal. My connection is mobile broadband via a rooted android handset, but my connection is LTE, so it's normally faster than the landline options I have in my area. But that is not the norm; typically, my connection is fast and strong. One unusual thing about today, though, was that I managed to play one toon for several hours non-stop. I think I had a continuous play session of about five or so hours. I finally stopped it when I hit a bug that would not allow me to complete a patrol mission, and when I dropped the mission, I could not take on any other missions, or leave that sector of space. I closed the client, rebooted my PC, and reconnected with no issue. I completed the mission, and when I transwarped to ESD, immediate CTD. I reloaded the launcher, verified all files, then started the client again. I started with the last toon I played, it loaded ESD, but I didn't have time to get off the transporter pad before it crashed again. That is the typical behavior the game has had since the launch of Season 8. Usually, any play session lasts only a few seconds after I try to load a social zone. If I'm out in sector space, no issues. If I'm running a mission (that doesn't involve a social zone), no issues. Try to go to ESD, K7, or DS9 to change ships? Immediate CTD. When Season 8 launched, my Romulan toon was on New Romulus, in the staging area. He was unplayable for weeks. I managed to get him off the surface once, and out into sector space, but the promises of Q drew him back. CTD.
My Klingon toon, now that I think about it, has never crashed. Hmm. Maybe I can play after all.
i haeve teh fancay signaetures!!!!!!!1 i am teh l33t usar!!!!!!1
Hello, I've been lagging and getting disconnected a lot the past 2-3 days here is my tracert:
1 <1 ms <1 ms <1 ms fritz.box [192.168.TRIBBLE.x]
2 96 ms 35 ms 37 ms rdsl-stgt-de81.nw.mediaways.net [213.20.56.140]
3 57 ms 26 ms 29 ms xmwc-stgt-de04-chan-23.nw.mediaways.net [195.71.
229.205]
4 57 ms 25 ms 25 ms rmwc-stgt-de01-chan-1.nw.mediaways.net [62.53.1.
64]
5 38 ms 73 ms 37 ms rmwc-brln-de02-xe-0-0-2-0.nw.mediaways.net [62.5
3.1.41]
6 92 ms 57 ms 39 ms rmwc-brln-de01-chan-5-0.nw.mediaways.net [62.53.
1.112]
7 49 ms 70 ms 49 ms xmws-frnk-de07-chan-0.nw.mediaways.net [62.53.5.
176]
8 49 ms 105 ms 67 ms ge-3-0.ir1.frankfurt-he.de.xo.net [80.81.192.182
]
9 81 ms 60 ms 122 ms ae1d0.cir1.amsterdam2-nh.nl.xo.net [207.88.15.74
]
10 126 ms 68 ms 57 ms ae1d0.cir1.london2-eng.uk.xo.net [207.88.15.70]
11 136 ms 142 ms 167 ms vb1042.rar3.nyc-ny.us.xo.net [207.88.13.202]
12 146 ms 146 ms 184 ms ae0d0.mcr1.cambridge-ma.us.xo.net [216.156.0.26]
13 147 ms 147 ms 148 ms ae1d0.mcr2.cambridge-ma.us.xo.net [216.156.1.14]
14 134 ms 133 ms 133 ms 209.117.103.10
15 135 ms 134 ms 134 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.4
1]
16 135 ms 138 ms 142 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
17 134 ms 134 ms 134 ms 208.95.186.32
Hello, I've been lagging and getting disconnected a lot the past 2-3 days here is my tracert:
...
any help would be appreciated.
Your network latency is within acceptable limits (according to the 'Trace Route), but that doesn't rule out the possibility of packet drop...
substitute the 'pathping' command for the 'tracert' command and post the diagnostic results, as this will show if you are a victim of dropped packets...
I should have known better than to say that my KDF toon has never crashed. As soon as the doors opened from the transporter pad on Qo'nos, CTD. This only happens in the social zones. Something is definitely wrong there that only began with Season 8. And, while I was typing this, the launcher was verifying files in the background ... and crashed. Ticket number 14179083.
i haeve teh fancay signaetures!!!!!!!1 i am teh l33t usar!!!!!!1
here my complete log of tracert and pathping. Would be graet if anybody could have a look on it.
C:\Windows\System32>tracert 208.95.186.32
Routenverfolgung zu 208.95.186.32 ?ber maximal 30 Hops
1 <1 ms <1 ms <1 ms fritz.box [192.168.TRIBBLE.x]
2 66 ms 26 ms 26 ms rdsl-stgt-de81.nw.mediaways.net [213.20.56.140]
3 25 ms 24 ms 25 ms xmwc-stgt-de04-chan-23.nw.mediaways.net [195.71.
229.205]
4 60 ms 24 ms 26 ms rmwc-stgt-de01-chan-1.nw.mediaways.net [62.53.1.
64]
5 38 ms 38 ms 115 ms rmwc-brln-de02-xe-0-0-3-0.nw.mediaways.net [62.5
3.1.43]
6 38 ms 37 ms 39 ms rmwc-brln-de01-chan-5-0.nw.mediaways.net [62.53.
1.112]
7 49 ms 48 ms 53 ms xmws-frnk-de07-chan-0.nw.mediaways.net [62.53.5.
176]
8 49 ms 56 ms 51 ms ge-3-0.ir1.frankfurt-he.de.xo.net [80.81.192.182
]
9 49 ms 48 ms 48 ms ae1d0.cir1.amsterdam2-nh.nl.xo.net [207.88.15.74
]
10 54 ms 98 ms 55 ms ae1d0.cir1.london2-eng.uk.xo.net [207.88.15.70]
11 143 ms 142 ms 142 ms vb1042.rar3.nyc-ny.us.xo.net [207.88.13.202]
12 146 ms 146 ms 146 ms ae0d0.mcr1.cambridge-ma.us.xo.net [216.156.0.26]
13 151 ms 146 ms 148 ms ae1d0.mcr2.cambridge-ma.us.xo.net [216.156.1.14]
14 158 ms 158 ms 158 ms 209.117.103.10
15 158 ms 158 ms 156 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
04]
16 169 ms 160 ms * perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
17 157 ms 157 ms 158 ms 208.95.186.32
Ablaufverfolgung beendet.
C:\Windows\System32>pathping 208.95.186.32
Routenverfolgung zu "208.95.186.32" ?ber maximal 30 Hops
Berechnung der Statistiken dauert ca. 425 Sekunden...
Quelle zum Abs. Knoten/Verbindung
Abs. Zeit Verl./Ges.= % Verl./Ges.= % Adresse
0 Meiner.fritz.box [192.168.TRIBBLE.TRIBBLE]
Berechnung der Statistiken dauert ca. 425 Sekunden...
Quelle zum Abs. Knoten/Verbindung
Abs. Zeit Verl./Ges.= % Verl./Ges.= % Adresse
0 Meiner.fritz.box [192.168.TRIBBLE.TRIBBLE]
Looks like the biggest issue is the Frankfurt gateway of xo.net from your ISP (mediaways.net) at 100% packet drop, with some further congestion in the boston pnap.net hub...
You should complain to your ISP at that huge packet drop at that Frankfurt gateway...
Could it also be a issue that i have CPU and board temperatures of 200-210 degree F?
Sounds like your system needs a case fan... However, if this was a system problem, you would expect to see dropped packets on all nodes on the connection, which is simply not the case here...
After today's maintenance, which did not address any crashing issues (according to the patch notes), the client crashed while still in the Cryptic loading screen, issuing ticket number 20653032. The dump for that ticket is still in progress as I type this.
i haeve teh fancay signaetures!!!!!!!1 i am teh l33t usar!!!!!!1
I verified files, relaunched the client, and played for about 15 minutes before CTD, generating ticket number 14662149. I was browsing the exchange on ESD with my newest toon. I think I'm going to give up on it for awhile and go play guitar.
i haeve teh fancay signaetures!!!!!!!1 i am teh l33t usar!!!!!!1
So been having lots of issues with STO since returning after about a year away. Trying to eliminate as many possible causes as I can till I find the route cause an get it fixed. Already done driver updates on Chipset, Graphics, Audio and LAN as well as as many variations of game/launcher settings as I can think of, also an uninstall from Steam and re-install from Arc didn't help either. Next port of call is checking all the networking, to that end below are my Tracert and Pathping results if someone could have a look over and see if anything stands out it would be much appreciated.
TRACERT
Tracing route to 208.95.186.32 over a maximum of 30 hops
1 19 ms 8 ms 12 ms dial-92-52-XX-X-orange.orange.sk [92.52.XX.X]
2 1 ms <1 ms <1 ms 192.168.102.13
3 2 ms 2 ms 1 ms DNI-198-189.orange.sk [213.151.198.189]
4 2 ms 2 ms 1 ms te0-0-0-6.ccr21.bts01.atlas.cogentco.com [149.6.26.45]
5 10 ms 10 ms 10 ms be2224.ccr21.muc01.atlas.cogentco.com [154.54.36.9]
6 15 ms 15 ms 15 ms be2230.mpd21.fra03.atlas.cogentco.com [154.54.38.97]
7 22 ms 22 ms 22 ms be2261.ccr21.ams03.atlas.cogentco.com [154.54.37.29]
8 32 ms 32 ms 30 ms be2277.mpd21.lon13.atlas.cogentco.com [154.54.62.145]
9 97 ms 99 ms 99 ms be2386.ccr21.bos01.atlas.cogentco.com [154.54.44.161]
10 98 ms 100 ms 105 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.134]
11 106 ms 107 ms 107 ms 38.111.40.114
12 97 ms 97 ms 100 ms 208.95.186.32
PATHPING
Tracing route to 208.95.186.32 over a maximum of 30 hops
Seems like your ISP is having some serious problems with network traffic, with 100% Packet drop very close to your entry into their network... I suggest you contact them and present them with this information...
Thanks for the quick reply grouchyotaku. That's a result I was not expecting as other MMOs I play, Guild Wars 2, Age of Conan & DCUO are all working as normal, STO was the only one giving me grief.
Would the Packet Loss cause the main issue I'm having where on rolling a new Fed Char I'm not getting the Intro Movie but dropped straight into the world with just the UI and everything else is just black? All the NPCs are moving and I can as well according to the mini-map I just can't see anything.
I really thought this was an issue caused by something else and checking the networking was just so I could have it checked off on the list of things I've tried to help narrow things down if i had to contact support.
Would the Packet Loss cause the main issue I'm having where on rolling a new Fed Char I'm not getting the Intro Movie but dropped straight into the world with just the UI and everything else is just black? All the NPCs are moving and I can as well according to the mini-map I just can't see anything.
....
Without knowing how the STO Client software is structured, this is hard to say, but its not outside the bounds of reality that this could be the cause...
Hi again grouchyotaku, this is just a quick thank-you post because taking your advice as a starting point I am now able to play normally again it seems. It's a strange fix, if I try and run wired directly into the router games a no-go but if switch over to the wireless game is happy.
I think it may possibly be due to my upload speed, when wired directly SpeedTest shows D/Load at 100MBps but only 0.9MBps Upload where as on wireless D/Load drops to 15MBps but upload jumps up to 11MBps.
So thanks again and hopefully having this solution posted can help anyone else having the same kind of issue.
Played a little guitar, ate dinner, and decided to take another crack at it. Jumped on my Romulan toon this time, played for 15-20 minutes. Started on New Romulus, no crash; jumped into sector space, it's all fine. Transwarp to Qo'nos, and set up some DOFF missions; a little lag, but nothing to worry about. Slid into Q's Winter Wonderland, and completed two races! Then I was standing under the big gazebo, collecting snowballs, and CTD. Ticket number issued is the same as the last one: 14662149.
i haeve teh fancay signaetures!!!!!!!1 i am teh l33t usar!!!!!!1
Tried again. Verified files, launched client. Selected toon at character select screen, client crashed during initial loading. I was given the same ticket number as before: 14662149.
i haeve teh fancay signaetures!!!!!!!1 i am teh l33t usar!!!!!!1
I been having disconnect problems since today, speedtest/ping/trace all looks fine. Looks to me it's a problem introduced with yesterdays patch, I did not have any problems before this patch. I mainly disconnect when loading a mission.
C:\WINDOWS\system32>tracert 208.95.186.32
Tracing route to 208.95.186.32 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.178.1
2 5 ms 5 ms 5 ms 10.244.144.1
3 7 ms 6 ms 6 ms land-rc0001-ds102-vl202.core.as9143.net [213.51.
148.194]
4 9 ms 10 ms 8 ms tb-rc0001-cr102-ae10-0.core.as9143.net [213.51.1
57.201]
5 12 ms 30 ms 11 ms asd-tr0610-cr101-ae5-0.core.as9143.net [213.51.1
58.154]
6 10 ms 10 ms 10 ms adm-b5-link.telia.net [80.239.167.229]
7 12 ms 10 ms 11 ms cogent-ic-130765-adm-b3.c.telia.net [213.248.85.
110]
8 11 ms 11 ms 12 ms be2303.mpd22.ams03.atlas.cogentco.com [154.54.74
.101]
9 25 ms 25 ms 21 ms be2275.ccr21.lon13.atlas.cogentco.com [130.117.5
1.253]
10 94 ms 95 ms 92 ms be2387.ccr22.bos01.atlas.cogentco.com [154.54.44
.165]
11 95 ms 92 ms 94 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.
130]
12 92 ms 104 ms 93 ms 38.111.40.114
13 91 ms 92 ms 91 ms 208.95.186.32
I been having disconnect problems since today, speedtest/ping/trace all looks fine. Looks to me it's a problem introduced with yesterdays patch, I did not have any problems before this patch. I mainly disconnect when loading a mission.
...
Try substituting the 'pathping' command for the 'tracert' command, as 'Trace Route' does not have the ability to show packet drop on your connection to the STO server...
And what does your 'Net Test' results look like, as this would show if you could sustain the required throughput on your network connection to the STO network...
I gave the game some time away, hoping that a couple of patches/server maintenance would correct this issue. It did not. I launched the game, played maybe five minutes, CTD, ticket number: 14662149, same as before. I guess I am going to have to wait to play until such time as the patch notes indicates they have at least attempted to address further crashing issues. Because as it stands, this game is unplayable for me.
i haeve teh fancay signaetures!!!!!!!1 i am teh l33t usar!!!!!!1
Im getting the crashes now. The game worked fine till this past friday when they worked on the system after that I can log in and after five minutes the game crashes and a fatal error occurs corupt pig file detected then it states different files ech time it happends.
I dont know what else to do dont look like anything on my part geuss I should feel lucky that I can still log in even if for only 5 minutes. Ive been a paying member since 2010 and as of late im really thinking of dropping my sub and just going f2p after all if there system dont support mine why should my wallot support them?? I would be greatful for any suggestions on how to fix this.
8 99 ms 105 ms 102 ms be2134.mpd21.mci01.atlas.cogentco.com [154.54.6.38]
9 101 ms 105 ms 107 ms be2158.mpd21.ord01.atlas.cogentco.com [154.54.7.130]
10 92 ms 91 ms 93 ms be2140.ccr22.bos01.atlas.cogentco.com [154.54.43.186]
11 91 ms 91 ms 92 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42]
12 99 ms 92 ms 103 ms 38.111.40.114
13 90 ms 89 ms 90 ms patchserver2.crypticstudios.com [208.95.185.41]
Latest read at 10pm PST (I hope those * good news but unlikely) excluded my isp.
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
5 * 63 ms 60 ms be3000.ccr21.sjc03.atlas.cogentco.com [154.54.11
.45]
6 * 60 ms 60 ms be2047.ccr22.sjc01.atlas.cogentco.com [154.54.5.
113]
7 67 ms 61 ms * be2165.ccr22.sfo01.atlas.cogentco.com [154.54.28
.65]
8 104 ms 104 ms 104 ms be2134.mpd21.mci01.atlas.cogentco.com [154.54.6.
38]
9 105 ms 119 ms 114 ms be2158.mpd21.ord01.atlas.cogentco.com [154.54.7.
130]
10 104 ms 103 ms 102 ms be2140.ccr22.bos01.atlas.cogentco.com [154.54.43
.186]
11 * 117 ms 118 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
12 97 ms 101 ms 107 ms 38.111.40.114
13 112 ms 117 ms 111 ms patchserver2.crypticstudios.com [208.95.185.41]
Just checked it again, to be sure. Beamed myself out of ESD as soon as the client loaded, and all was well, until I realized I had left something undone. I decided to try my luck at Starbase 39. Five seconds in, CTD, same ticket number.
i haeve teh fancay signaetures!!!!!!!1 i am teh l33t usar!!!!!!1
Here's mine. Looks like something is bottlenecking in the alter.net neck of the woods, wherever that is.
Tracing route to 208.95.186.32 over a maximum of 30 hops
1 10 ms 1 ms 1 ms myrouter.home []
2 8 ms 9 ms 10 ms L100.TAMPFL-VFTTP-127.verizon-gni.net []
3 16 ms 20 ms 19 ms G0-13-4-6.TAMPFL-LCR-21.verizon-gni.net [130.81.
138.128]
4 8 ms 10 ms 9 ms so-2-0-0-0.TPA01-BB-RTR1-verizon-gni.net [130.81
.28.212]
5 80 ms 56 ms 66 ms 0.ge-4-3-0.XL3.BOS4.ALTER.NET [152.63.16.34]
6 60 ms 58 ms 58 ms 0.xe-10-2-0.GW15.BOS4.ALTER.NET [152.63.21.138]
7 147 ms 147 ms 148 ms internap-gw.customer.alter.net [152.179.134.214]
8 69 ms 62 ms 59 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
04]
9 110 ms 107 ms 107 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
10 97 ms 110 ms 108 ms 208.95.186.32
Hi there, my game crashes whenever I beam into a base or facility. Planet surfaces are fine and mining works fine, space and battles work fine, but as soon as I beam into a base the game client stops working. Anyone else had this problem? I will add that it is a recent problem and that all files verify with no problem.
I believe I have fixed the crashing issue. In the middle of the night it came to me: when Season 7 launched, I had a similar issue. At that time, I was using the Steam client. I fixed the issue then by uninstalling the Steam client, and installing the standalone client. This time, I did the reverse: I uninstalled the standalone client, and installed the Steam client. I have had no issues for several days. This tells me there is probably something wrong with the way the client handles large updates. Something was corrupted when I installed Season 8, and no amount of patching and verifying files could fix that. I had to start all over with a fresh install.
Edit: now that I think about it, I think it was Season 6, not 7, where I had the initial issue, because I took a great deal of time off from the game at that point, too.
i haeve teh fancay signaetures!!!!!!!1 i am teh l33t usar!!!!!!1
I don't know if this is the right section. Every time I play Star Trek Online the game crashes my PC, I don't know if its my PC or the game itself I have uninstalled and reinstalled the game and it still does the same thing. Can not put a ticket up in game for that same reason. I have the required specs to run the game. Can anyone suggest any help ? Thanks.
Comments
My Klingon toon, now that I think about it, has never crashed. Hmm. Maybe I can play after all.
1 <1 ms <1 ms <1 ms fritz.box [192.168.TRIBBLE.x]
2 96 ms 35 ms 37 ms rdsl-stgt-de81.nw.mediaways.net [213.20.56.140]
3 57 ms 26 ms 29 ms xmwc-stgt-de04-chan-23.nw.mediaways.net [195.71.
229.205]
4 57 ms 25 ms 25 ms rmwc-stgt-de01-chan-1.nw.mediaways.net [62.53.1.
64]
5 38 ms 73 ms 37 ms rmwc-brln-de02-xe-0-0-2-0.nw.mediaways.net [62.5
3.1.41]
6 92 ms 57 ms 39 ms rmwc-brln-de01-chan-5-0.nw.mediaways.net [62.53.
1.112]
7 49 ms 70 ms 49 ms xmws-frnk-de07-chan-0.nw.mediaways.net [62.53.5.
176]
8 49 ms 105 ms 67 ms ge-3-0.ir1.frankfurt-he.de.xo.net [80.81.192.182
]
9 81 ms 60 ms 122 ms ae1d0.cir1.amsterdam2-nh.nl.xo.net [207.88.15.74
]
10 126 ms 68 ms 57 ms ae1d0.cir1.london2-eng.uk.xo.net [207.88.15.70]
11 136 ms 142 ms 167 ms vb1042.rar3.nyc-ny.us.xo.net [207.88.13.202]
12 146 ms 146 ms 184 ms ae0d0.mcr1.cambridge-ma.us.xo.net [216.156.0.26]
13 147 ms 147 ms 148 ms ae1d0.mcr2.cambridge-ma.us.xo.net [216.156.1.14]
14 134 ms 133 ms 133 ms 209.117.103.10
15 135 ms 134 ms 134 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.4
1]
16 135 ms 138 ms 142 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
17 134 ms 134 ms 134 ms 208.95.186.32
any help would be appreciated.
Your network latency is within acceptable limits (according to the 'Trace Route), but that doesn't rule out the possibility of packet drop...
substitute the 'pathping' command for the 'tracert' command and post the diagnostic results, as this will show if you are a victim of dropped packets...
here my complete log of tracert and pathping. Would be graet if anybody could have a look on it.
C:\Windows\System32>tracert 208.95.186.32
Routenverfolgung zu 208.95.186.32 ?ber maximal 30 Hops
1 <1 ms <1 ms <1 ms fritz.box [192.168.TRIBBLE.x]
2 66 ms 26 ms 26 ms rdsl-stgt-de81.nw.mediaways.net [213.20.56.140]
3 25 ms 24 ms 25 ms xmwc-stgt-de04-chan-23.nw.mediaways.net [195.71.
229.205]
4 60 ms 24 ms 26 ms rmwc-stgt-de01-chan-1.nw.mediaways.net [62.53.1.
64]
5 38 ms 38 ms 115 ms rmwc-brln-de02-xe-0-0-3-0.nw.mediaways.net [62.5
3.1.43]
6 38 ms 37 ms 39 ms rmwc-brln-de01-chan-5-0.nw.mediaways.net [62.53.
1.112]
7 49 ms 48 ms 53 ms xmws-frnk-de07-chan-0.nw.mediaways.net [62.53.5.
176]
8 49 ms 56 ms 51 ms ge-3-0.ir1.frankfurt-he.de.xo.net [80.81.192.182
]
9 49 ms 48 ms 48 ms ae1d0.cir1.amsterdam2-nh.nl.xo.net [207.88.15.74
]
10 54 ms 98 ms 55 ms ae1d0.cir1.london2-eng.uk.xo.net [207.88.15.70]
11 143 ms 142 ms 142 ms vb1042.rar3.nyc-ny.us.xo.net [207.88.13.202]
12 146 ms 146 ms 146 ms ae0d0.mcr1.cambridge-ma.us.xo.net [216.156.0.26]
13 151 ms 146 ms 148 ms ae1d0.mcr2.cambridge-ma.us.xo.net [216.156.1.14]
14 158 ms 158 ms 158 ms 209.117.103.10
15 158 ms 158 ms 156 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
04]
16 169 ms 160 ms * perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
17 157 ms 157 ms 158 ms 208.95.186.32
Ablaufverfolgung beendet.
C:\Windows\System32>pathping 208.95.186.32
Routenverfolgung zu "208.95.186.32" ?ber maximal 30 Hops
0 Meiner.fritz.box [192.168.TRIBBLE.xx]
1 fritz.box [192.168.TRIBBLE.xx]
2 rdsl-stgt-de81.nw.mediaways.net [213.20.56.140]
3 xmwc-stgt-de04-chan-23.nw.mediaways.net [195.71.229.205]
4 rmwc-stgt-de01-chan-1.nw.mediaways.net [62.53.1.64]
5 rmwc-brln-de02-xe-1-0-8-0.nw.mediaways.net [62.53.5.16]
6 rmwc-brln-de01-chan-5-0.nw.mediaways.net [62.53.1.112]
7 xmws-frnk-de07-chan-0.nw.mediaways.net [62.53.5.176]
8 ge-3-0.ir1.frankfurt-he.de.xo.net [80.81.192.182]
9 ae1d0.cir1.amsterdam2-nh.nl.xo.net [207.88.15.74]
10 ae1d0.cir1.london2-eng.uk.xo.net [207.88.15.70]
11 vb1042.rar3.nyc-ny.us.xo.net [207.88.13.202]
12 ae0d0.mcr1.cambridge-ma.us.xo.net [216.156.0.26]
13 ae1d0.mcr2.cambridge-ma.us.xo.net [216.156.1.14]
14 209.117.103.10
15 border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.104]
16 perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
17 * 208.95.186.32
Berechnung der Statistiken dauert ca. 425 Sekunden...
Quelle zum Abs. Knoten/Verbindung
Abs. Zeit Verl./Ges.= % Verl./Ges.= % Adresse
0 Meiner.fritz.box [192.168.TRIBBLE.TRIBBLE]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% fritz.box [192.168.TRIBBLE.xx]
0/ 100 = 0% |
2 24ms 0/ 100 = 0% 0/ 100 = 0% rdsl-stgt-de81.nw.mediaways.net [2
13.20.56.140]
0/ 100 = 0% |
3 25ms 0/ 100 = 0% 0/ 100 = 0% xmwc-stgt-de04-chan-23.nw.mediaway
s.net [195.71.229.205]
0/ 100 = 0% |
4 33ms 0/ 100 = 0% 0/ 100 = 0% rmwc-stgt-de01-chan-1.nw.mediaways
.net [62.53.1.64]
0/ 100 = 0% |
5 50ms 0/ 100 = 0% 0/ 100 = 0% rmwc-brln-de02-xe-1-0-8-0.nw.media
ways.net [62.53.5.16]
0/ 100 = 0% |
6 42ms 0/ 100 = 0% 0/ 100 = 0% rmwc-brln-de01-chan-5-0.nw.mediawa
ys.net [62.53.1.112]
0/ 100 = 0% |
7 51ms 0/ 100 = 0% 0/ 100 = 0% xmws-frnk-de07-chan-0.nw.mediaways
.net [62.53.5.176]
0/ 100 = 0% |
8 --- 100/ 100 =100% 100/ 100 =100% ge-3-0.ir1.frankfurt-he.de.xo.net
[80.81.192.182]
0/ 100 = 0% |
9 56ms 0/ 100 = 0% 0/ 100 = 0% ae1d0.cir1.amsterdam2-nh.nl.xo.net
[207.88.15.74]
0/ 100 = 0% |
10 62ms 1/ 100 = 1% 1/ 100 = 1% ae1d0.cir1.london2-eng.uk.xo.net [
207.88.15.70]
0/ 100 = 0% |
11 141ms 1/ 100 = 1% 1/ 100 = 1% vb1042.rar3.nyc-ny.us.xo.net [207.
88.13.202]
0/ 100 = 0% |
12 144ms 1/ 100 = 1% 1/ 100 = 1% ae0d0.mcr1.cambridge-ma.us.xo.net
[216.156.0.26]
0/ 100 = 0% |
13 145ms 0/ 100 = 0% 0/ 100 = 0% ae1d0.mcr2.cambridge-ma.us.xo.net
[216.156.1.14]
10/ 100 = 10% |
14 157ms 18/ 100 = 18% 8/ 100 = 8% 209.117.103.10
0/ 100 = 0% |
15 163ms 10/ 100 = 10% 0/ 100 = 0% border11.te8-1-bbnet2.bsn.pnap.net
[63.251.128.104]
1/ 100 = 1% |
16 163ms 11/ 100 = 11% 0/ 100 = 0% perfectworldent-4.border11.bsn.pna
p.net [216.52.61.78]
2/ 100 = 2% |
17 158ms 13/ 100 = 13% 0/ 100 = 0% 208.95.186.32
x
Thank you
Looks like the biggest issue is the Frankfurt gateway of xo.net from your ISP (mediaways.net) at 100% packet drop, with some further congestion in the boston pnap.net hub...
You should complain to your ISP at that huge packet drop at that Frankfurt gateway...
Sounds like your system needs a case fan... However, if this was a system problem, you would expect to see dropped packets on all nodes on the connection, which is simply not the case here...
TRACERT
Tracing route to 208.95.186.32 over a maximum of 30 hops
1 19 ms 8 ms 12 ms dial-92-52-XX-X-orange.orange.sk [92.52.XX.X]
2 1 ms <1 ms <1 ms 192.168.102.13
3 2 ms 2 ms 1 ms DNI-198-189.orange.sk [213.151.198.189]
4 2 ms 2 ms 1 ms te0-0-0-6.ccr21.bts01.atlas.cogentco.com [149.6.26.45]
5 10 ms 10 ms 10 ms be2224.ccr21.muc01.atlas.cogentco.com [154.54.36.9]
6 15 ms 15 ms 15 ms be2230.mpd21.fra03.atlas.cogentco.com [154.54.38.97]
7 22 ms 22 ms 22 ms be2261.ccr21.ams03.atlas.cogentco.com [154.54.37.29]
8 32 ms 32 ms 30 ms be2277.mpd21.lon13.atlas.cogentco.com [154.54.62.145]
9 97 ms 99 ms 99 ms be2386.ccr21.bos01.atlas.cogentco.com [154.54.44.161]
10 98 ms 100 ms 105 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.134]
11 106 ms 107 ms 107 ms 38.111.40.114
12 97 ms 97 ms 100 ms 208.95.186.32
PATHPING
Tracing route to 208.95.186.32 over a maximum of 30 hops
0 Alisdair-PC [92.52.XX.TRIBBLE]
1 dial-92-52-32-1-orange.orange.sk [92.52.XX.X]
2 192.168.102.13
3 DNI-198-189.orange.sk [213.151.198.189]
4 te0-0-0-6.ccr21.bts01.atlas.cogentco.com [149.6.26.45]
5 be2224.ccr21.muc01.atlas.cogentco.com [154.54.36.9]
6 be2228.ccr21.fra03.atlas.cogentco.com [154.54.38.49]
7 be2261.ccr21.ams03.atlas.cogentco.com [154.54.37.29]
8 be2182.ccr21.lpl01.atlas.cogentco.com [154.54.77.246]
9 be2386.ccr21.bos01.atlas.cogentco.com [154.54.44.161]
10 te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.134]
11 38.111.40.114
12 208.95.186.32
Computing statistics for 300 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Alisdair-PC [92.52.XX.TRIBBLE]
0/ 100 = 0% |
1 3ms 0/ 100 = 0% 0/ 100 = 0% dial-92-52-XX-X-orange.orange.sk [
92.52.XX.X]
0/ 100 = 0% |
2 --- 100/ 100 =100% 100/ 100 =100% 192.168.102.13
0/ 100 = 0% |
3 --- 100/ 100 =100% 100/ 100 =100% DNI-198-189.orange.sk [213.151.198
.189]
0/ 100 = 0% |
4 2ms 0/ 100 = 0% 0/ 100 = 0% te0-0-0-6.ccr21.bts01.atlas.cogent
co.com [149.6.26.45]
0/ 100 = 0% |
5 10ms 0/ 100 = 0% 0/ 100 = 0% be2224.ccr21.muc01.atlas.cogentco.
com [154.54.36.9]
0/ 100 = 0% |
6 15ms 0/ 100 = 0% 0/ 100 = 0% be2228.ccr21.fra03.atlas.cogentco.
com [154.54.38.49]
0/ 100 = 0% |
7 22ms 0/ 100 = 0% 0/ 100 = 0% be2261.ccr21.ams03.atlas.cogentco.
com [154.54.37.29]
0/ 100 = 0% |
8 32ms 0/ 100 = 0% 0/ 100 = 0% be2182.ccr21.lpl01.atlas.cogentco.
com [154.54.77.246]
0/ 100 = 0% |
9 97ms 0/ 100 = 0% 0/ 100 = 0% be2386.ccr21.bos01.atlas.cogentco.
com [154.54.44.161]
0/ 100 = 0% |
10 123ms 0/ 100 = 0% 0/ 100 = 0% te3-4.ccr01.bos06.atlas.cogentco.c
om [154.54.46.134]
0/ 100 = 0% |
11 104ms 0/ 100 = 0% 0/ 100 = 0% 38.111.40.114
0/ 100 = 0% |
12 98ms 0/ 100 = 0% 0/ 100 = 0% 208.95.186.32
Seems like your ISP is having some serious problems with network traffic, with 100% Packet drop very close to your entry into their network... I suggest you contact them and present them with this information...
Would the Packet Loss cause the main issue I'm having where on rolling a new Fed Char I'm not getting the Intro Movie but dropped straight into the world with just the UI and everything else is just black? All the NPCs are moving and I can as well according to the mini-map I just can't see anything.
I really thought this was an issue caused by something else and checking the networking was just so I could have it checked off on the list of things I've tried to help narrow things down if i had to contact support.
Without knowing how the STO Client software is structured, this is hard to say, but its not outside the bounds of reality that this could be the cause...
I think it may possibly be due to my upload speed, when wired directly SpeedTest shows D/Load at 100MBps but only 0.9MBps Upload where as on wireless D/Load drops to 15MBps but upload jumps up to 11MBps.
So thanks again and hopefully having this solution posted can help anyone else having the same kind of issue.
Vek.
C:\WINDOWS\system32>tracert 208.95.186.32
Tracing route to 208.95.186.32 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.178.1
2 5 ms 5 ms 5 ms 10.244.144.1
3 7 ms 6 ms 6 ms land-rc0001-ds102-vl202.core.as9143.net [213.51.
148.194]
4 9 ms 10 ms 8 ms tb-rc0001-cr102-ae10-0.core.as9143.net [213.51.1
57.201]
5 12 ms 30 ms 11 ms asd-tr0610-cr101-ae5-0.core.as9143.net [213.51.1
58.154]
6 10 ms 10 ms 10 ms adm-b5-link.telia.net [80.239.167.229]
7 12 ms 10 ms 11 ms cogent-ic-130765-adm-b3.c.telia.net [213.248.85.
110]
8 11 ms 11 ms 12 ms be2303.mpd22.ams03.atlas.cogentco.com [154.54.74
.101]
9 25 ms 25 ms 21 ms be2275.ccr21.lon13.atlas.cogentco.com [130.117.5
1.253]
10 94 ms 95 ms 92 ms be2387.ccr22.bos01.atlas.cogentco.com [154.54.44
.165]
11 95 ms 92 ms 94 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.
130]
12 92 ms 104 ms 93 ms 38.111.40.114
13 91 ms 92 ms 91 ms 208.95.186.32
Trace complete.
C:\WINDOWS\system32>
Try substituting the 'pathping' command for the 'tracert' command, as 'Trace Route' does not have the ability to show packet drop on your connection to the STO server...
And what does your 'Net Test' results look like, as this would show if you could sustain the required throughput on your network connection to the STO network...
I dont know what else to do dont look like anything on my part geuss I should feel lucky that I can still log in even if for only 5 minutes. Ive been a paying member since 2010 and as of late im really thinking of dropping my sub and just going f2p after all if there system dont support mine why should my wallot support them?? I would be greatful for any suggestions on how to fix this.
9 101 ms 105 ms 107 ms be2158.mpd21.ord01.atlas.cogentco.com [154.54.7.130]
10 92 ms 91 ms 93 ms be2140.ccr22.bos01.atlas.cogentco.com [154.54.43.186]
11 91 ms 91 ms 92 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42]
12 99 ms 92 ms 103 ms 38.111.40.114
13 90 ms 89 ms 90 ms patchserver2.crypticstudios.com [208.95.185.41]
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
5 * 63 ms 60 ms be3000.ccr21.sjc03.atlas.cogentco.com [154.54.11
.45]
6 * 60 ms 60 ms be2047.ccr22.sjc01.atlas.cogentco.com [154.54.5.
113]
7 67 ms 61 ms * be2165.ccr22.sfo01.atlas.cogentco.com [154.54.28
.65]
8 104 ms 104 ms 104 ms be2134.mpd21.mci01.atlas.cogentco.com [154.54.6.
38]
9 105 ms 119 ms 114 ms be2158.mpd21.ord01.atlas.cogentco.com [154.54.7.
130]
10 104 ms 103 ms 102 ms be2140.ccr22.bos01.atlas.cogentco.com [154.54.43
.186]
11 * 117 ms 118 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
12 97 ms 101 ms 107 ms 38.111.40.114
13 112 ms 117 ms 111 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
Tracing route to 208.95.186.32 over a maximum of 30 hops
1 10 ms 1 ms 1 ms myrouter.home []
2 8 ms 9 ms 10 ms L100.TAMPFL-VFTTP-127.verizon-gni.net []
3 16 ms 20 ms 19 ms G0-13-4-6.TAMPFL-LCR-21.verizon-gni.net [130.81.
138.128]
4 8 ms 10 ms 9 ms so-2-0-0-0.TPA01-BB-RTR1-verizon-gni.net [130.81
.28.212]
5 80 ms 56 ms 66 ms 0.ge-4-3-0.XL3.BOS4.ALTER.NET [152.63.16.34]
6 60 ms 58 ms 58 ms 0.xe-10-2-0.GW15.BOS4.ALTER.NET [152.63.21.138]
7 147 ms 147 ms 148 ms internap-gw.customer.alter.net [152.179.134.214]
8 69 ms 62 ms 59 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
04]
9 110 ms 107 ms 107 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
10 97 ms 110 ms 108 ms 208.95.186.32
Trace complete.
Edit: now that I think about it, I think it was Season 6, not 7, where I had the initial issue, because I took a great deal of time off from the game at that point, too.