Tracing route to 208.95.168.32 over a maximum of 30 hops
1 2 ms <1 ms <1 ms 192.168.1.1
2 2 ms 3 ms 1 ms 188-173-60-129.next-gen.ro [188.173.60.129]
3 4 ms 3 ms 3 ms 188-173-48-9.next-gen.ro [188.173.48.9]
4 5 ms 1 ms 3 ms 89.121.204.189
5 44 ms 45 ms 47 ms 10.0.228.61
6 41 ms 41 ms 39 ms 10.0.252.193
7 48 ms 46 ms 47 ms 10.0.240.141
8 46 ms 46 ms 48 ms 10.0.200.62
9 45 ms 44 ms 45 ms l0.milnit1-cr1.bbnplanet.net [195.16.160.17]
10 134 ms 134 ms 134 ms vlan80.csw3.Frankfurt1.Level3.net [4.69.154.190]
11 139 ms 140 ms 141 ms ae-81-81.ebr1.Frankfurt1.Level3.net [4.69.140.9]
12 134 ms 132 ms 132 ms ae-45-45.ebr2.Paris1.Level3.net [4.69.143.134]
13 133 ms 130 ms 131 ms ae-43-43.ebr2.Washington1.Level3.net [4.69.137.5
8]
14 133 ms 133 ms 133 ms ae-72-72.csw2.Washington1.Level3.net [4.69.134.1
50]
15 131 ms 132 ms 185 ms ae-2-70.edge2.Washington4.Level3.net [4.69.149.8
0]
16 136 ms 131 ms 131 ms TWTC-level3-1x10G.Washington.Level3.net [4.53.11
4.10]
17 156 ms 183 ms 156 ms orl1-ar4-xe-2-0-0-0.us.twtelecom.net [66.192.245
.214]
18 160 ms 160 ms 160 ms 66-192-143-30.static.twtelecom.net [66.192.143.3
0]
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Japjap>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.1.1
2 70 ms 75 ms 71 ms 112.209.160.1
3 75 ms 74 ms 71 ms 119.93.255.221
4 115 ms 116 ms 101 ms 210.213.130.114
5 74 ms 74 ms 71 ms 210.213.128.53
6 72 ms 78 ms 74 ms 210.213.133.5
7 224 ms 220 ms 220 ms 38.104.84.201
8 217 ms 217 ms 221 ms 154.54.41.113
9 246 ms 258 ms 254 ms 154.54.5.65
10 277 ms 273 ms 277 ms 154.54.29.17
11 282 ms 284 ms 284 ms 154.54.31.110
12 288 ms 281 ms 281 ms 154.54.40.74
13 290 ms 284 ms 292 ms 154.54.30.14
14 293 ms 292 ms 288 ms 66.28.4.254
15 287 ms 292 ms 303 ms 38.111.40.114
16 284 ms 292 ms 284 ms 208.95.186.32
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Japjap>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.1.1
2 70 ms 75 ms 71 ms 112.209.160.1
...
70 milliseconds is a unusually high value for the 2nd hop, as the expected value should be less then 10ms...
try rebooting both your router and modem/gateway and see if this improves the condition. If it doesn't, you may need to replace the router, or have the ISP look at the modem/gateway unit...
The netcode in this game feels rather clunky..
STO needs more throughput than my connection actually has, 99% of missions I'm usually warping around with my ship throttle sliding up and down by itself, weapons unable to fire and being unable to turn my ship. STFs now commonly end with everyone vanishing, and the rewards screen popping up, along with "leaving the map in 40 seconds", I don't even look at the 20 or 10 player missions anymore, as I am unable to do anything upon warping in, leaving me unable to do the special events like crystalline catastrophe and the new mirror invasion, there is simply too much going on, and it is flooding the connection.
It would be great if things could be a little bit more optimized.. I understand that lots of data needs to be sent, but it shouldn't need me to have a 4MB line to just do missions.
No tracert, latency is fine, just a problem with actual data throughput.
and post the results, as this would provide clues if you have actually have a throughput problem with your connection.
Also substitute the 'pathing' command for the 'tracert' command, as 'pathping' will indicate if you have a 'dropped packet' problem, and where along your connection path they are occurring...
1 <10 ms <10 ms <10 ms ZyXEL [192.168.1.254]
2 1 ms 1 ms <10 ms ua-213-112-240-1.cust.bredbandsbolaget.se [213.1
12.240.1]
3 9 ms 9 ms 9 ms ti3006d400-xe7-0-0.ti.telenor.net [146.172.87.57
]
4 11 ms 9 ms 9 ms ti3006c400-ae3-0.ti.telenor.net [146.172.100.50]
5 9 ms 10 ms 9 ms ti3001c400-ae5-0.ti.telenor.net [146.172.99.125]
6 9 ms 10 ms 9 ms ti3001b400-ae0-0.ti.telenor.net [146.172.105.25]
7 10 ms 9 ms 9 ms be2001.ccr21.sto01.atlas.cogentco.com [130.117.1
4.97]
8 10 ms 10 ms 10 ms be2396.ccr21.sto03.atlas.cogentco.com [130.117.5
0.121]
9 29 ms 30 ms 29 ms be2281.ccr41.ham01.atlas.cogentco.com [154.54.63
.1]
10 29 ms 25 ms 29 ms be2187.ccr42.ams03.atlas.cogentco.com [154.54.74
.125]
11 37 ms 36 ms 40 ms be2183.ccr22.lpl01.atlas.cogentco.com [154.54.58
.69]
12 108 ms 101 ms 122 ms be2390.ccr21.bos01.atlas.cogentco.com [154.54.44
.221]
13 185 ms 221 ms 216 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
14 113 ms 107 ms 107 ms 38.111.40.114
15 103 ms 104 ms 104 ms 208.95.186.32
Seams trouble with the connection is all over at your end of the Atlantic... :P
Must say I am not adverse to you putting up a server here in the EU to get around the problem.
A test server is supposed to be used to properly test patches before patching anything....
this is my trace results my6 issuse is it gets to the the "star trek online legacy of romulus" loading screen and crashes
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\bret-meg>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 Wireless_Broadband_Router.home [192.168.1.1]
2 6 ms 5 ms 5 ms L100.TAMPFL-VFTTP-153.verizon-gni.net [108.9.176
.1]
3 9 ms 8 ms 11 ms G0-3-1-5.TAMPFL-LCR-22.verizon-gni.net [130.81.1
80.152]
4 9 ms 8 ms 21 ms ae2-0.TPA01-BB-RTR2.verizon-gni.net [130.81.199.
82]
5 41 ms 44 ms 87 ms xe-11-0-6-0.RES-BB-RTR2.verizon-gni.net [130.81.
17.112]
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 55 ms 54 ms 86 ms 0.ae2.XL4.BOS4.ALTER.NET [140.222.226.19]
11 55 ms 92 ms 56 ms 0.ge-9-2-0.GW15.BOS4.ALTER.NET [152.63.24.50]
12 55 ms 57 ms 56 ms internap-gw.customer.alter.net [152.179.134.214]
13 56 ms 55 ms 55 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.4
1]
14 71 ms 70 ms 70 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
15 62 ms 62 ms 61 ms 208.95.186.32
hoping you can shed some light on the reasons behind my
crazy rubberbanding and server disconnects since patching
today.
tracert 208.95.186.32
Tracing route to 208.95.186.32 over a maximum of 30 hops
1 7 ms 7 ms 6 ms
2 9 ms 7 ms 5 ms virginmedia.net [62.252.174.45]
3 9 ms 12 ms 8 ms virginmedia.net [213.105.159.141]
4 9 ms 9 ms 9 ms virginmedia.net [62.254.42.113]
5 8 ms 9 ms 9 ms virginmedia.net [62.254.42.118]
6 30 ms 27 ms 27 ms virginmedia.net [62.253.188.158]
7 28 ms 29 ms 29 ms atlas.cogentco.com [130.117.15.5]
8 30 ms 29 ms 29 ms atlas.cogentco.com [154.54.74.89]
9 24 ms 26 ms 25 ms atlas.cogentco.com [154.54.62.145]
10 97 ms 97 ms 99 ms atlas.cogentco.com [154.54.44.237]
11 110 ms 98 ms 97 ms atlas.cogentco.com [66.28.4.42]
12 102 ms 107 ms 107 ms 38.111.40.114
13 98 ms 99 ms 97 ms 208.95.186.32
Trace complete.
Ran a pathping too.. these were the results.. the 100% loss at 1 has
me somewhat confused though..
This explains it right here... dropped (as in lost or thrown away) packets along the Cogent backbone...
You could try the Euro Game Proxy option in the Launcher in the hopes that it directs you to a less congested path across the Atlantic, but its hit or miss, with no guarantee of improvement...
is there a real chance that a lot of the laging / diconect problems have to do with massive data trafic along the transcontinental lines due to a DDOS wave that we had ?
You could try the Euro Game Proxy option in the Launcher in the hopes that it directs you to a less congested path across the Atlantic, but its hit or miss, with no guarantee of improvement...
I shall give that try, many thanks for the quick response and advice.
EDIT - That seems to have done the trick, for now, thanks again!!
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.1.1
2 9 ms 22 ms 7 ms cpc21-bary4-2-0-gw.5-1.cable.virginm.net [81.105
.56.1]
3 8 ms 8 ms 9 ms cdif-core-2a-ae3-2259.network.virginmedia.net [6
2.252.34.85]
4 9 ms 11 ms 9 ms brhm-bb-1b-ae1-0.network.virginmedia.net [62.253
.174.81]
5 80 ms 148 ms 224 ms teln-ic-1-ae0-0.network.virginmedia.net [212.43.
163.250]
6 16 ms 17 ms 17 ms m282-mp2.cvx3-a.ltn.dial.ntli.net [213.104.85.26
]
7 14 ms 14 ms 14 ms be2317.mpd22.lon13.atlas.cogentco.com [154.54.73
.177]
8 89 ms 89 ms 89 ms be2391.ccr22.bos01.atlas.cogentco.com [154.54.44
.237]
9 284 ms 216 ms 213 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
4]
10 89 ms 89 ms 87 ms 38.111.40.114
11 88 ms 92 ms 92 ms patchserver2.crypticstudios.com [208.95.185.41]
1 <10 ms <10 ms <10 ms ZyXEL [192.168.1.254]
2 1 ms 1 ms <10 ms ua-213-112-240-1.cust.bredbandsbolaget.se [213.1
2.240.1]
3 9 ms 9 ms 9 ms ti3153d400-xe8-1-1.ti.telenor.net [146.172.85.16
]
4 9 ms 9 ms 9 ms ti3153c400-ae3-0.ti.telenor.net [146.172.100.81]
5 9 ms 9 ms 9 ms ti3002c400-ae12-0.ti.telenor.net [146.172.102.86
6 9 ms 9 ms 9 ms ti3001b400-ae1-0.ti.telenor.net [146.172.105.29]
7 10 ms 10 ms 10 ms be2001.ccr21.sto01.atlas.cogentco.com [130.117.1
.97]
8 10 ms 10 ms 10 ms be2397.ccr22.sto03.atlas.cogentco.com [130.117.5
.129]
9 29 ms 29 ms 29 ms be2281.ccr41.ham01.atlas.cogentco.com [154.54.63
1]
10 25 ms 29 ms 29 ms be2186.ccr41.ams03.atlas.cogentco.com [154.54.74
121]
11 40 ms 39 ms 39 ms be2183.ccr22.lpl01.atlas.cogentco.com [154.54.58
69]
12 104 ms 104 ms 104 ms be2387.ccr22.bos01.atlas.cogentco.com [154.54.44
165]
13 104 ms 104 ms 100 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
]
14 114 ms 106 ms 107 ms 38.111.40.114
15 104 ms 101 ms 104 ms 208.95.186.32
Once again problem is on your side of the atlantic. Been dissconected a few times today now and it is getting anoying.
If the american side of the Internet is in such a bad shape you really should consider moving servers. :mad:
A test server is supposed to be used to properly test patches before patching anything....
Unfortunately back to the rubberbanding and server disconnects, reran the tracert
and the results are the same avg 6-10ms UK side of the pond, then hitting 100+
over in the States. It's almost consistent enough to be turning into a gamebreaker.
I'm not really sure how relevant it is, but a large portion of my dc's and/or server
not responding, appear to occur during or just after map changes. I have also noticed
an increase in loading screen times for common maps.
I did a reformat tonight and then did a fresh reinstall of STO (usually I just copy the game folder to my external drive then back when I am ready for it but I want a fresh install this time.) first I tried ARC then Steam and finally one of my hard copies every time I got this message
Unable to establish connection to patch server. please check your internet connection. If problems persist, please contact Technical Support.
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.TRIBBLE.x.x
2 * * * Request timed out.
3 8 ms 6 ms 9 ms 209.236.80.77
4 5 ms 5 ms 5 ms 209.236.80.81
5 8 ms 7 ms 8 ms ellccofor.edge.secom.net [208.123.132.42]
6 8 ms 6 ms 8 ms publcowst.core.secom.net [208.117.67.3]
7 12 ms 10 ms 11 ms ae3-580.edge3.Denver1.Level3.net [4.31.9.225]
8 27 ms 25 ms 29 ms vlan51.ebr1.Denver1.Level3.net [4.69.147.94]
9 27 ms 26 ms 27 ms ae-2-2.ebr2.Dallas1.Level3.net [4.69.132.106]
10 25 ms 26 ms 26 ms ae-72-72.csw2.Dallas1.Level3.net [4.69.151.141]
11 * 26 ms 26 ms ae-2-70.edge2.Dallas1.Level3.net [4.69.145.75]
12 56 ms 55 ms 56 ms 4.68.111.102
13 55 ms 53 ms 55 ms be2031.ccr21.dfw01.atlas.cogentco.com [154.54.7.
45]
14 64 ms 63 ms 63 ms be2012.ccr21.mci01.atlas.cogentco.com [154.54.2.
113]
15 45 ms 46 ms 43 ms be2157.ccr42.ord01.atlas.cogentco.com [154.54.6.
118]
16 64 ms 65 ms 65 ms be2137.ccr21.bos01.atlas.cogentco.com [154.54.43
.194]
17 66 ms 64 ms 65 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
4]
18 68 ms 71 ms 71 ms 38.111.40.114
19 64 ms 65 ms 66 ms 208.95.186.32
Trace complete.
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
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.TRIBBLE.x.x
2 * * * Request timed out.
3 8 ms 6 ms 9 ms 209.236.80.77
4 5 ms 5 ms 5 ms 209.236.80.81
5 8 ms 7 ms 8 ms ellccofor.edge.secom.net [208.123.132.42]
6 8 ms 6 ms 8 ms publcowst.core.secom.net [208.117.67.3]
7 12 ms 10 ms 11 ms ae3-580.edge3.Denver1.Level3.net [4.31.9.225]
8 27 ms 25 ms 29 ms vlan51.ebr1.Denver1.Level3.net [4.69.147.94]
9 27 ms 26 ms 27 ms ae-2-2.ebr2.Dallas1.Level3.net [4.69.132.106]
10 25 ms 26 ms 26 ms ae-72-72.csw2.Dallas1.Level3.net [4.69.151.141]
11 * 26 ms 26 ms ae-2-70.edge2.Dallas1.Level3.net [4.69.145.75]
12 56 ms 55 ms 56 ms 4.68.111.102
13 55 ms 53 ms 55 ms be2031.ccr21.dfw01.atlas.cogentco.com [154.54.7.
45]
14 64 ms 63 ms 63 ms be2012.ccr21.mci01.atlas.cogentco.com [154.54.2.
113]
15 45 ms 46 ms 43 ms be2157.ccr42.ord01.atlas.cogentco.com [154.54.6.
118]
16 64 ms 65 ms 65 ms be2137.ccr21.bos01.atlas.cogentco.com [154.54.43
.194]
17 66 ms 64 ms 65 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
4]
18 68 ms 71 ms 71 ms 38.111.40.114
19 64 ms 65 ms 66 ms 208.95.186.32
Trace complete.
also I tried a nettest and it just times out, all other games I have install work fine WarThunder and Forsaken World those are the two I have installed so far and I connected fine.
any suggestions would be appreciated.
Edit: issue resolved itself after getting service pack 1 and some more updates installed.
my system crashs with the game trys to load local maps
the error i get as follows:
fatal error direct 3d driver return error (d3derr_invaild call)
while creating 2d render target texture size 6144 x 4096 (rtex_nxidia_intz)
i don't talk teck but my system is update. with all these crashed the new updates stink. when i uploaded these new updates i notices the graphics was not clear or sharp as before the next day i been getting thses error and crashes.
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 3 ms 2 ms <1 ms
2 9 ms 13 ms 10 ms
3 9 ms 9 ms 9 ms edge001.rtr.jk.echoes.net [72.28.2.2]
4 21 ms 20 ms 17 ms xe-11-0-0-222.nyc20.ip4.tinet.net [173.241.131.1
01]
5 19 ms 58 ms 21 ms xe-10-3-0.nyc30.ip4.tinet.net [89.149.184.185]
6 26 ms 22 ms 19 ms te0-0-0-8.ccr21.jfk07.atlas.cogentco.com [154.54
.10.89]
7 22 ms 29 ms 23 ms be2057.ccr22.jfk02.atlas.cogentco.com [154.54.80
.177]
8 28 ms 29 ms 26 ms be2096.ccr22.bos01.atlas.cogentco.com [154.54.30
.42]
9 24 ms 225 ms 216 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.
130]
10 25 ms 34 ms 35 ms 38.111.40.114
11 25 ms 50 ms 34 ms patchserver2.crypticstudios.com [208.95.185.41]
tracert results and nettest results. please help if you can. i tried everything but bypassing the router. im working on that.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Jack>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.2.1]
2 33 ms 24 ms 29 ms 174.54.184.1
3 12 ms 13 ms 11 ms te-0-0-0-15-sur02.scranton.pa.pitt.comcast.net [
68.85.44.25]
4 18 ms 17 ms 16 ms 68.85.52.229
5 23 ms 23 ms 25 ms be-1-ar03.pittsburgh.pa.pitt.comcast.net [68.85.
75.121]
6 32 ms 31 ms 31 ms he-4-14-0-0-cr01.newyork.ny.ibone.comcast.net [6
8.86.94.185]
7 31 ms 30 ms 35 ms he-0-13-0-0-pe03.111eighthave.ny.ibone.comcast.n
et [68.86.85.182]
8 32 ms 33 ms 33 ms be7922.ccr21.jfk10.atlas.cogentco.com [154.54.13
.161]
9 32 ms 40 ms 35 ms be2074.ccr21.jfk07.atlas.cogentco.com [154.54.86
.225]
10 32 ms 32 ms 32 ms be2056.ccr21.jfk02.atlas.cogentco.com [154.54.44
.217]
11 41 ms 49 ms 37 ms be2094.ccr21.bos01.atlas.cogentco.com [154.54.30
.14]
12 38 ms 38 ms 36 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
13 51 ms 36 ms 37 ms 38.111.40.114
14 40 ms 37 ms 37 ms 208.95.186.32
Black screen at the login page. Not even the server status displays.
Long wait then timeout. Same with Arc client. Same with a different computer.
Access to Gateway, ARC webpages, and speedtests are all fine. (20M down, 5M up)
Nettest times out:
contacting nettest server..timed out
Tracert has request timeouts:
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.x.x]
2 3 ms 4 ms 4 ms L100.DLLSTX-VFTTP-24.verizon-gni.net [71.123.x.x]
3 9 ms 7 ms 7 ms G0-5-0-4.DLLSTX-LCR-22.verizon-gni.net [100.41.194.242]
4 6 ms 7 ms 19 ms ae8-0.DFW9-BB-RTR2.verizon-gni.net [130.81.162.160]
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 59 ms 47 ms 47 ms 0.ae2.XL4.BOS4.ALTER.NET [140.222.226.19]
10 47 ms 47 ms 47 ms 0.ge-9-1-0.GW15.BOS4.ALTER.NET [152.63.24.46]
11 49 ms 49 ms 49 ms internap-gw.customer.alter.net [152.179.134.214]
12 46 ms 49 ms 49 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.41]
13 53 ms 67 ms 54 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
14 54 ms 54 ms 54 ms patchserver2.crypticstudios.com [208.95.185.41]
Guys, I'm having multiple BSOD's daily. About 15 minutes ago, I had one right after another. This has been going on since Tuesday of last week and increasing in progression. After playing for 2 1/2 years I've noticed that, every so many months, this happens after a maintenance patch. The last time it was this bad for me was in late 2012. Back then, you guys had an update (around October, I think) and I was having BSOD's several times a day. At that time, I gave up and came back the following patch and everything was fine.
The BSOD's ONLY HAPPEN WITH THIS GAME.
And yes, I mean a COMPLETE SYSTEM CRASH.
In late 2012, when this same event occurred, I was running Windows Home Premium 64 bit.
As of this date,
I am running a clean install of Windows 7 Ultimate 64 bit.
AMD CPU
AMD HD 6310
I have an excellent internet connection.
I have a fully updated Operating system. This includes DX, Java, .Net 4.5
I have a brand new Hard Drive (It is a spin drive not a solid state and it was bought brand new about 7 days ago.)
I just added a new memory stick (4GB, yes brand new, not used.) to see if I needed more memory. Didn't fix it.
My router was new as of 2 months ago along with my USB Wireless adapter. They are Dual Band and running on the 5 GHz line only with no Bandwidth issues.
I have a problem when getting invitations and accepting to play in groups for fleet, space or ground based play. The tech support seems to think its a local performance issue but i think its something else.
When i play in the Dyson against the Voth T-Rex there are many people there doing their stuff and if there are to many then the game will lag badly but has never crashed. The problem only happens when i am running around and then i get a pop up that someone has invited me to join and play as a team/group and i accept then after about 5 seconds the game crashes.
This only happens after i accept the invitation to play/join the group/team so please advise if anyone have come across this problem.
I have a problem when getting invitations and accepting to play in groups for fleet, space or ground based play. The tech support seems to think its a local performance issue but i think its something else.
When i play in the Dyson against the Voth T-Rex there are many people there doing their stuff and if there are to many then the game will lag badly but has never crashed. The problem only happens when i am running around and then i get a pop up that someone has invited me to join and play as a team/group and i accept then after about 5 seconds the game crashes.
...
So how much Video memory does your system have? And have you tried running at a lower screen resolution??
I have a GeForce GT 440 with 1GB RAM and have not tested yet with a lower screen resolution but will test this next.
Also would just like to point out that i had received an error message only one time and it was something about the PhysX but after that i have not received any error.
A dump was sent the last time around to the cryptic. Let me know if you need more information and thanks for the reply.
I have a GeForce GT 440 with 1GB RAM and have not tested yet with a lower screen resolution but will test this next.
...
hmmm... 1GB of Video RAM is starting to approach 'marginal' if you're running at 1080p resolution. The other significant question would be system RAM, as 4GB would also start approaching 'marginal' when running at 1080p...
Seems like I'm getting "System Not Responding" every few minutes. Sometimes, it'll take me back to the login screen and say that I was disconnected from the server.
Here's my tracert results:
Tracing route to 208.95.186.32 over a maximum of 30 hops
1 1 ms 1 ms 1 ms 10.0.0.1
2 9 ms 10 ms 10 ms 73.238.213.1
3 9 ms 11 ms 10 ms te-9-1-ur01.rankin.ms.malt.comcast.net [68.85.55.153]
4 9 ms 11 ms 9 ms te-0-0-0-7-ur05.jacksonnorth.ms.malt.comcast.net [68.86.241.37]
5 15 ms 14 ms 29 ms te-8-1-ur02.winchester.tn.malt.comcast.net [68.86.240.33]
6 28 ms 32 ms 26 ms pos-2-1-0-0-cr01.56marietta.ga.ibone.comcast.net [68.86.92.29]
7 * * * Request timed out.
8 28 ms 27 ms 30 ms te0-0-0-19.ccr21.atl02.atlas.cogentco.com [154.54.10.233]
9 28 ms 27 ms 27 ms be2051.ccr42.atl01.atlas.cogentco.com [154.54.0.161]
10 39 ms 39 ms 38 ms be2169.ccr22.dca01.atlas.cogentco.com [154.54.31.98]
11 49 ms 45 ms 46 ms be2149.ccr22.jfk02.atlas.cogentco.com [154.54.31.126]
12 51 ms 49 ms 52 ms be2096.ccr22.bos01.atlas.cogentco.com [154.54.30.42]
13 52 ms 52 ms 49 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.254]
14 52 ms 50 ms 57 ms 38.111.40.114
15 56 ms 52 ms 49 ms 208.95.186.32
Trace complete.
I'm running on a wireless connection. Connecting directly isn't really an option because the modem/router that Comcast provides can only be plugged in one spot in the house. Any help is appreciated. Thanks.
Seems like I'm getting "System Not Responding" every few minutes. Sometimes, it'll take me back to the login screen and say that I was disconnected from the server.
Here's my tracert results:
.....
Your 'Trace Route' is showing excellent network latency values, so this is simply not the information needed to pinpoint what the problem is...
The 'Net Test' diagnostic results would be useful, as it tests for sustained network throughput bandwidth. and using the 'pathping' command (which uses the same syntax as the 'tracert' command) will check if data packets are being lost or thrown away in your Internet path to the STO Servers...
Your 'Trace Route' is showing excellent network latency values, so this is simply not the information needed to pinpoint what the problem is...
The 'Net Test' diagnostic results would be useful, as it tests for sustained network throughput bandwidth. and using the 'pathping' command (which uses the same syntax as the 'tracert' command) will check if data packets are being lost or thrown away in your Internet path to the STO Servers...
Hey, thanks for the response. I ran the two tests you suggested.
PathPing Test
Tracing route to 208.95.186.32 over a maximum of 30 hops
Comments
1 2 ms <1 ms <1 ms 192.168.1.1
2 2 ms 3 ms 1 ms 188-173-60-129.next-gen.ro [188.173.60.129]
3 4 ms 3 ms 3 ms 188-173-48-9.next-gen.ro [188.173.48.9]
4 5 ms 1 ms 3 ms 89.121.204.189
5 44 ms 45 ms 47 ms 10.0.228.61
6 41 ms 41 ms 39 ms 10.0.252.193
7 48 ms 46 ms 47 ms 10.0.240.141
8 46 ms 46 ms 48 ms 10.0.200.62
9 45 ms 44 ms 45 ms l0.milnit1-cr1.bbnplanet.net [195.16.160.17]
10 134 ms 134 ms 134 ms vlan80.csw3.Frankfurt1.Level3.net [4.69.154.190]
11 139 ms 140 ms 141 ms ae-81-81.ebr1.Frankfurt1.Level3.net [4.69.140.9]
12 134 ms 132 ms 132 ms ae-45-45.ebr2.Paris1.Level3.net [4.69.143.134]
13 133 ms 130 ms 131 ms ae-43-43.ebr2.Washington1.Level3.net [4.69.137.5
8]
14 133 ms 133 ms 133 ms ae-72-72.csw2.Washington1.Level3.net [4.69.134.1
50]
15 131 ms 132 ms 185 ms ae-2-70.edge2.Washington4.Level3.net [4.69.149.8
0]
16 136 ms 131 ms 131 ms TWTC-level3-1x10G.Washington.Level3.net [4.53.11
4.10]
17 156 ms 183 ms 156 ms orl1-ar4-xe-2-0-0-0.us.twtelecom.net [66.192.245
.214]
18 160 ms 160 ms 160 ms 66-192-143-30.static.twtelecom.net [66.192.143.3
0]
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
C:\Users\me>tracert 208.95.186.32
Traza a 208.95.186.32 sobre caminos de 30 saltos como m
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Japjap>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.1.1
2 70 ms 75 ms 71 ms 112.209.160.1
3 75 ms 74 ms 71 ms 119.93.255.221
4 115 ms 116 ms 101 ms 210.213.130.114
5 74 ms 74 ms 71 ms 210.213.128.53
6 72 ms 78 ms 74 ms 210.213.133.5
7 224 ms 220 ms 220 ms 38.104.84.201
8 217 ms 217 ms 221 ms 154.54.41.113
9 246 ms 258 ms 254 ms 154.54.5.65
10 277 ms 273 ms 277 ms 154.54.29.17
11 282 ms 284 ms 284 ms 154.54.31.110
12 288 ms 281 ms 281 ms 154.54.40.74
13 290 ms 284 ms 292 ms 154.54.30.14
14 293 ms 292 ms 288 ms 66.28.4.254
15 287 ms 292 ms 303 ms 38.111.40.114
16 284 ms 292 ms 284 ms 208.95.186.32
Trace complete.
C:\Documents and Settings\Japjap>
70 milliseconds is a unusually high value for the 2nd hop, as the expected value should be less then 10ms...
try rebooting both your router and modem/gateway and see if this improves the condition. If it doesn't, you may need to replace the router, or have the ISP look at the modem/gateway unit...
STO needs more throughput than my connection actually has, 99% of missions I'm usually warping around with my ship throttle sliding up and down by itself, weapons unable to fire and being unable to turn my ship. STFs now commonly end with everyone vanishing, and the rewards screen popping up, along with "leaving the map in 40 seconds", I don't even look at the 20 or 10 player missions anymore, as I am unable to do anything upon warping in, leaving me unable to do the special events like crystalline catastrophe and the new mirror invasion, there is simply too much going on, and it is flooding the connection.
It would be great if things could be a little bit more optimized.. I understand that lots of data needs to be sent, but it shouldn't need me to have a 4MB line to just do missions.
No tracert, latency is fine, just a problem with actual data throughput.
Haven't had any problems running 4 characters through the Mirror event and Battlezone myself...
If you suspect there's an issue with throughput, you should run the 'Net Test' network diagnostics described in this thread... http://sto-forum.perfectworld.com/showthread.php?t=225155
and post the results, as this would provide clues if you have actually have a throughput problem with your connection.
Also substitute the 'pathing' command for the 'tracert' command, as 'pathping' will indicate if you have a 'dropped packet' problem, and where along your connection path they are occurring...
2 1 ms 1 ms <10 ms ua-213-112-240-1.cust.bredbandsbolaget.se [213.1
12.240.1]
3 9 ms 9 ms 9 ms ti3006d400-xe7-0-0.ti.telenor.net [146.172.87.57
]
4 11 ms 9 ms 9 ms ti3006c400-ae3-0.ti.telenor.net [146.172.100.50]
5 9 ms 10 ms 9 ms ti3001c400-ae5-0.ti.telenor.net [146.172.99.125]
6 9 ms 10 ms 9 ms ti3001b400-ae0-0.ti.telenor.net [146.172.105.25]
7 10 ms 9 ms 9 ms be2001.ccr21.sto01.atlas.cogentco.com [130.117.1
4.97]
8 10 ms 10 ms 10 ms be2396.ccr21.sto03.atlas.cogentco.com [130.117.5
0.121]
9 29 ms 30 ms 29 ms be2281.ccr41.ham01.atlas.cogentco.com [154.54.63
.1]
10 29 ms 25 ms 29 ms be2187.ccr42.ams03.atlas.cogentco.com [154.54.74
.125]
11 37 ms 36 ms 40 ms be2183.ccr22.lpl01.atlas.cogentco.com [154.54.58
.69]
12 108 ms 101 ms 122 ms be2390.ccr21.bos01.atlas.cogentco.com [154.54.44
.221]
13 185 ms 221 ms 216 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
14 113 ms 107 ms 107 ms 38.111.40.114
15 103 ms 104 ms 104 ms 208.95.186.32
Seams trouble with the connection is all over at your end of the Atlantic... :P
Must say I am not adverse to you putting up a server here in the EU to get around the problem.
A test server is supposed to be used to properly test patches before patching anything....
contacting nettest server..
Local IP: 197.78.151.92
Ping: 401.1 msec
Port: 80: 17 KB/sec 9 KB/sec 32 KB/sec 500
Port: 80: 18 KB/sec 8 KB/sec 33 KB/sec 500
Port: 443: 18 KB/sec 9 KB/sec 34 KB/sec 500
Port: 443: 21 KB/sec 7 KB/sec 34 KB/sec 500
Port: 7255: 18 KB/sec 7 KB/sec 34 KB/sec 500
Port: 7255: 16 KB/sec 8 KB/sec 36 KB/sec 500
Port: 7003: 15 KB/sec 8 KB/sec 36 KB/sec 500
Port: 7003: 17 KB/sec 6 KB/sec 33 KB/sec 500
Port: 7202: 14 KB/sec 6 KB/sec 27 KB/sec 500
It's nice to see a speed test app get all 32K of my bandwidth for once, I'll be using that nettest executable instead of speedtest.net in future.
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\bret-meg>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 Wireless_Broadband_Router.home [192.168.1.1]
2 6 ms 5 ms 5 ms L100.TAMPFL-VFTTP-153.verizon-gni.net [108.9.176
.1]
3 9 ms 8 ms 11 ms G0-3-1-5.TAMPFL-LCR-22.verizon-gni.net [130.81.1
80.152]
4 9 ms 8 ms 21 ms ae2-0.TPA01-BB-RTR2.verizon-gni.net [130.81.199.
82]
5 41 ms 44 ms 87 ms xe-11-0-6-0.RES-BB-RTR2.verizon-gni.net [130.81.
17.112]
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 55 ms 54 ms 86 ms 0.ae2.XL4.BOS4.ALTER.NET [140.222.226.19]
11 55 ms 92 ms 56 ms 0.ge-9-2-0.GW15.BOS4.ALTER.NET [152.63.24.50]
12 55 ms 57 ms 56 ms internap-gw.customer.alter.net [152.179.134.214]
13 56 ms 55 ms 55 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.4
1]
14 71 ms 70 ms 70 ms perfectworldent-4.border11.bsn.pnap.net [216.52.
61.78]
15 62 ms 62 ms 61 ms 208.95.186.32
Trace complete.
C:\Users\bret-meg>
These web articles explains the current issue with Verizon networks...
http://arstechnica.com/information-technology/2014/02/netflix-packets-being-dropped-every-day-because-verizon-wants-more-money/
http://arstechnica.com/information-technology/2014/03/level-3-blames-internet-slowdowns-on-isps-refusal-to-upgrade-networks/
http://arstechnica.com/business/2014/03/netflix-users-on-verizon-and-att-get-raw-deal-have-little-reason-for-hope/
hoping you can shed some light on the reasons behind my
crazy rubberbanding and server disconnects since patching
today.
tracert 208.95.186.32
Tracing route to 208.95.186.32 over a maximum of 30 hops
1 7 ms 7 ms 6 ms
2 9 ms 7 ms 5 ms virginmedia.net [62.252.174.45]
3 9 ms 12 ms 8 ms virginmedia.net [213.105.159.141]
4 9 ms 9 ms 9 ms virginmedia.net [62.254.42.113]
5 8 ms 9 ms 9 ms virginmedia.net [62.254.42.118]
6 30 ms 27 ms 27 ms virginmedia.net [62.253.188.158]
7 28 ms 29 ms 29 ms atlas.cogentco.com [130.117.15.5]
8 30 ms 29 ms 29 ms atlas.cogentco.com [154.54.74.89]
9 24 ms 26 ms 25 ms atlas.cogentco.com [154.54.62.145]
10 97 ms 97 ms 99 ms atlas.cogentco.com [154.54.44.237]
11 110 ms 98 ms 97 ms atlas.cogentco.com [66.28.4.42]
12 102 ms 107 ms 107 ms 38.111.40.114
13 98 ms 99 ms 97 ms 208.95.186.32
Trace complete.
Ran a pathping too.. these were the results.. the 100% loss at 1 has
me somewhat confused though..
Computing statistics for 325 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0
0/ 100 = 0% |
1 --- 100/ 100 =100% 100/ 100 =100%
0/ 100 = 0% |
2 9ms 0/ 100 = 0% 0/ 100 = 0%
0/ 100 = 0% |
3 11ms 0/ 100 = 0% 0/ 100 = 0% [213.105.159.141]
0/ 100 = 0% |
4 14ms 0/ 100 = 0% 0/ 100 = 0% [62.254.42.113]
0/ 100 = 0% |
5 13ms 0/ 100 = 0% 0/ 100 = 0% [62.254.42.118]
0/ 100 = 0% |
6 32ms 0/ 100 = 0% 0/ 100 = 0% [62.253.188.158]
0/ 100 = 0% |
7 25ms 0/ 100 = 0% 0/ 100 = 0% atlas.cogentco.com [130.117.15.5]
0/ 100 = 0% |
8 24ms 0/ 100 = 0% 0/ 100 = 0% atlas.cogentco.com [154.54.74.93]
0/ 100 = 0% |
9 14ms 0/ 100 = 0% 0/ 100 = 0% atlas.cogentco.com [154.54.62.149]
0/ 100 = 0% |
10 87ms 35/ 100 = 35% 35/ 100 = 35% atlas.cogentco.com [154.54.44.237]
0/ 100 = 0% |
11 --- 100/ 100 =100% 100/ 100 =100% atlas.cogentco.com [66.28.4.42]
0/ 100 = 0% |
12 91ms 36/ 100 = 36% 36/ 100 = 36% 38.111.40.114
0/ 100 = 0% |
13 97ms 0/ 100 = 0% 0/ 100 = 0% 208.95.186.32
Trace complete.
Thanks in advance
This explains it right here... dropped (as in lost or thrown away) packets along the Cogent backbone...
You could try the Euro Game Proxy option in the Launcher in the hopes that it directs you to a less congested path across the Atlantic, but its hit or miss, with no guarantee of improvement...
I shall give that try, many thanks for the quick response and advice.
EDIT - That seems to have done the trick, for now, thanks again!!
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>tracert patchserver.crypticstudios.com
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.1.1
2 9 ms 22 ms 7 ms cpc21-bary4-2-0-gw.5-1.cable.virginm.net [81.105
.56.1]
3 8 ms 8 ms 9 ms cdif-core-2a-ae3-2259.network.virginmedia.net [6
2.252.34.85]
4 9 ms 11 ms 9 ms brhm-bb-1b-ae1-0.network.virginmedia.net [62.253
.174.81]
5 80 ms 148 ms 224 ms teln-ic-1-ae0-0.network.virginmedia.net [212.43.
163.250]
6 16 ms 17 ms 17 ms m282-mp2.cvx3-a.ltn.dial.ntli.net [213.104.85.26
]
7 14 ms 14 ms 14 ms be2317.mpd22.lon13.atlas.cogentco.com [154.54.73
.177]
8 89 ms 89 ms 89 ms be2391.ccr22.bos01.atlas.cogentco.com [154.54.44
.237]
9 284 ms 216 ms 213 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
4]
10 89 ms 89 ms 87 ms 38.111.40.114
11 88 ms 92 ms 92 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
Nettest:
contacting nettest server..
Local IP: 81.105.57.246
Ping: 91.0 msec
Port: 80: 473 KB/sec 9 KB/sec 497 KB/sec 500
Port: 80: 537 KB/sec 10 KB/sec 569 KB/sec 500
Port: 443: 569 KB/sec 11 KB/sec 599 KB/sec 500
Port: 443: 473 KB/sec 9 KB/sec 497 KB/sec 500
Port: 7255: 569 KB/sec 11 KB/sec 599 KB/sec 500
Port: 7255: 504 KB/sec 10 KB/sec 530 KB/sec 500
Port: 7003: 446 KB/sec 8 KB/sec 469 KB/sec 500
Port: 7003: 473 KB/sec 12 KB/sec 498 KB/sec 500
Port: 7202: 478 KB/sec 13 KB/sec 508 KB/sec 500
Port: 7202: 441 KB/sec 11 KB/sec 463 KB/sec 500
Port: 7499: 520 KB/sec 12 KB/sec 548 KB/sec 500
Port: 7499: 474 KB/sec 9 KB/sec 499 KB/sec 500
Port: 80: 495 KB/sec 9 KB/sec 523 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 0 KB/sec
hit return to exit
My ISP is Virgin Media
"I'd be delighted to offer advice on women. When I have some I'll let you know..." - Cpt. Jean-Luc Picard
2 1 ms 1 ms <10 ms ua-213-112-240-1.cust.bredbandsbolaget.se [213.1
2.240.1]
3 9 ms 9 ms 9 ms ti3153d400-xe8-1-1.ti.telenor.net [146.172.85.16
]
4 9 ms 9 ms 9 ms ti3153c400-ae3-0.ti.telenor.net [146.172.100.81]
5 9 ms 9 ms 9 ms ti3002c400-ae12-0.ti.telenor.net [146.172.102.86
6 9 ms 9 ms 9 ms ti3001b400-ae1-0.ti.telenor.net [146.172.105.29]
7 10 ms 10 ms 10 ms be2001.ccr21.sto01.atlas.cogentco.com [130.117.1
.97]
8 10 ms 10 ms 10 ms be2397.ccr22.sto03.atlas.cogentco.com [130.117.5
.129]
9 29 ms 29 ms 29 ms be2281.ccr41.ham01.atlas.cogentco.com [154.54.63
1]
10 25 ms 29 ms 29 ms be2186.ccr41.ams03.atlas.cogentco.com [154.54.74
121]
11 40 ms 39 ms 39 ms be2183.ccr22.lpl01.atlas.cogentco.com [154.54.58
69]
12 104 ms 104 ms 104 ms be2387.ccr22.bos01.atlas.cogentco.com [154.54.44
165]
13 104 ms 104 ms 100 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
]
14 114 ms 106 ms 107 ms 38.111.40.114
15 104 ms 101 ms 104 ms 208.95.186.32
Once again problem is on your side of the atlantic. Been dissconected a few times today now and it is getting anoying.
If the american side of the Internet is in such a bad shape you really should consider moving servers. :mad:
A test server is supposed to be used to properly test patches before patching anything....
Unfortunately back to the rubberbanding and server disconnects, reran the tracert
and the results are the same avg 6-10ms UK side of the pond, then hitting 100+
over in the States. It's almost consistent enough to be turning into a gamebreaker.
I'm not really sure how relevant it is, but a large portion of my dc's and/or server
not responding, appear to occur during or just after map changes. I have also noticed
an increase in loading screen times for common maps.
also took the liberty of running a nettest too..
contacting nettest server..
Local IP:
Ping: 85.7 msec
Port: 80: 548 KB/sec 13 KB/sec 582 KB/sec 500
Port: 80: 543 KB/sec 14 KB/sec 577 KB/sec 500
Port: 443: 580 KB/sec 13 KB/sec 616 KB/sec 500
Port: 443: 518 KB/sec 12 KB/sec 550 KB/sec 500
Port: 7255: 575 KB/sec 12 KB/sec 610 KB/sec 500
Port: 7255: 551 KB/sec 14 KB/sec 585 KB/sec 500
Port: 7003: 447 KB/sec 10 KB/sec 473 KB/sec 500
Port: 7003: 484 KB/sec 9 KB/sec 520 KB/sec 500
Port: 7202: 439 KB/sec 10 KB/sec 466 KB/sec 500
Port: 7202: 422 KB/sec 10 KB/sec 447 KB/sec 500
Port: 7499: 478 KB/sec 13 KB/sec 507 KB/sec 500
Port: 7499: 576 KB/sec 13 KB/sec 611 KB/sec 500
Port: 80: 471 KB/sec 10 KB/sec 499 KB/sec 500
Idle NIC bandwidth Send: 1 KB/sec Recv: 1 KB/sec
hit return to exit
Regards
Unable to establish connection to patch server. please check your internet connection. If problems persist, please contact Technical Support.
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.TRIBBLE.x.x
2 * * * Request timed out.
3 8 ms 6 ms 9 ms 209.236.80.77
4 5 ms 5 ms 5 ms 209.236.80.81
5 8 ms 7 ms 8 ms ellccofor.edge.secom.net [208.123.132.42]
6 8 ms 6 ms 8 ms publcowst.core.secom.net [208.117.67.3]
7 12 ms 10 ms 11 ms ae3-580.edge3.Denver1.Level3.net [4.31.9.225]
8 27 ms 25 ms 29 ms vlan51.ebr1.Denver1.Level3.net [4.69.147.94]
9 27 ms 26 ms 27 ms ae-2-2.ebr2.Dallas1.Level3.net [4.69.132.106]
10 25 ms 26 ms 26 ms ae-72-72.csw2.Dallas1.Level3.net [4.69.151.141]
11 * 26 ms 26 ms ae-2-70.edge2.Dallas1.Level3.net [4.69.145.75]
12 56 ms 55 ms 56 ms 4.68.111.102
13 55 ms 53 ms 55 ms be2031.ccr21.dfw01.atlas.cogentco.com [154.54.7.
45]
14 64 ms 63 ms 63 ms be2012.ccr21.mci01.atlas.cogentco.com [154.54.2.
113]
15 45 ms 46 ms 43 ms be2157.ccr42.ord01.atlas.cogentco.com [154.54.6.
118]
16 64 ms 65 ms 65 ms be2137.ccr21.bos01.atlas.cogentco.com [154.54.43
.194]
17 66 ms 64 ms 65 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
4]
18 68 ms 71 ms 71 ms 38.111.40.114
19 64 ms 65 ms 66 ms 208.95.186.32
Trace complete.
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
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.TRIBBLE.x.x
2 * * * Request timed out.
3 8 ms 6 ms 9 ms 209.236.80.77
4 5 ms 5 ms 5 ms 209.236.80.81
5 8 ms 7 ms 8 ms ellccofor.edge.secom.net [208.123.132.42]
6 8 ms 6 ms 8 ms publcowst.core.secom.net [208.117.67.3]
7 12 ms 10 ms 11 ms ae3-580.edge3.Denver1.Level3.net [4.31.9.225]
8 27 ms 25 ms 29 ms vlan51.ebr1.Denver1.Level3.net [4.69.147.94]
9 27 ms 26 ms 27 ms ae-2-2.ebr2.Dallas1.Level3.net [4.69.132.106]
10 25 ms 26 ms 26 ms ae-72-72.csw2.Dallas1.Level3.net [4.69.151.141]
11 * 26 ms 26 ms ae-2-70.edge2.Dallas1.Level3.net [4.69.145.75]
12 56 ms 55 ms 56 ms 4.68.111.102
13 55 ms 53 ms 55 ms be2031.ccr21.dfw01.atlas.cogentco.com [154.54.7.
45]
14 64 ms 63 ms 63 ms be2012.ccr21.mci01.atlas.cogentco.com [154.54.2.
113]
15 45 ms 46 ms 43 ms be2157.ccr42.ord01.atlas.cogentco.com [154.54.6.
118]
16 64 ms 65 ms 65 ms be2137.ccr21.bos01.atlas.cogentco.com [154.54.43
.194]
17 66 ms 64 ms 65 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
4]
18 68 ms 71 ms 71 ms 38.111.40.114
19 64 ms 65 ms 66 ms 208.95.186.32
Trace complete.
also I tried a nettest and it just times out, all other games I have install work fine WarThunder and Forsaken World those are the two I have installed so far and I connected fine.
any suggestions would be appreciated.
Edit: issue resolved itself after getting service pack 1 and some more updates installed.
the error i get as follows:
fatal error direct 3d driver return error (d3derr_invaild call)
while creating 2d render target texture size 6144 x 4096 (rtex_nxidia_intz)
i don't talk teck but my system is update. with all these crashed the new updates stink. when i uploaded these new updates i notices the graphics was not clear or sharp as before the next day i been getting thses error and crashes.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>tracert patchserver.crypticstudios.com
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 3 ms 2 ms <1 ms
2 9 ms 13 ms 10 ms
3 9 ms 9 ms 9 ms edge001.rtr.jk.echoes.net [72.28.2.2]
4 21 ms 20 ms 17 ms xe-11-0-0-222.nyc20.ip4.tinet.net [173.241.131.1
01]
5 19 ms 58 ms 21 ms xe-10-3-0.nyc30.ip4.tinet.net [89.149.184.185]
6 26 ms 22 ms 19 ms te0-0-0-8.ccr21.jfk07.atlas.cogentco.com [154.54
.10.89]
7 22 ms 29 ms 23 ms be2057.ccr22.jfk02.atlas.cogentco.com [154.54.80
.177]
8 28 ms 29 ms 26 ms be2096.ccr22.bos01.atlas.cogentco.com [154.54.30
.42]
9 24 ms 225 ms 216 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.
130]
10 25 ms 34 ms 35 ms 38.111.40.114
11 25 ms 50 ms 34 ms patchserver2.crypticstudios.com [208.95.185.41]
Trace complete.
contacting nettest server..
Local IP: 68.70.26.142
Ping: 27.0 msec
Port: 80: 364 KB/sec 14 KB/sec 383 KB/sec 500
Port: 80: 541 KB/sec 22 KB/sec 588 KB/sec 500
Port: 443: 332 KB/sec 14 KB/sec 352 KB/sec 500
Port: 443: 547 KB/sec 23 KB/sec 598 KB/sec 500
Port: 7255: 326 KB/sec 12 KB/sec 345 KB/sec 500
Port: 7255: 306 KB/sec 12 KB/sec 325 KB/sec 500
Port: 7003: 494 KB/sec 20 KB/sec 545 KB/sec 500
Port: 7003: 648 KB/sec 23 KB/sec 681 KB/sec 500
Port: 7202: 525 KB/sec 22 KB/sec 574 KB/sec 500
Port: 7202: 338 KB/sec 14 KB/sec 368 KB/sec 500
Port: 7499: 361 KB/sec 15 KB/sec 382 KB/sec 500
Port: 7499: 672 KB/sec 28 KB/sec 742 KB/sec 500
Port: 80: 347 KB/sec 13 KB/sec 367 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 1 KB/sec
hit return to exit
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Jack>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.2.1]
2 33 ms 24 ms 29 ms 174.54.184.1
3 12 ms 13 ms 11 ms te-0-0-0-15-sur02.scranton.pa.pitt.comcast.net [
68.85.44.25]
4 18 ms 17 ms 16 ms 68.85.52.229
5 23 ms 23 ms 25 ms be-1-ar03.pittsburgh.pa.pitt.comcast.net [68.85.
75.121]
6 32 ms 31 ms 31 ms he-4-14-0-0-cr01.newyork.ny.ibone.comcast.net [6
8.86.94.185]
7 31 ms 30 ms 35 ms he-0-13-0-0-pe03.111eighthave.ny.ibone.comcast.n
et [68.86.85.182]
8 32 ms 33 ms 33 ms be7922.ccr21.jfk10.atlas.cogentco.com [154.54.13
.161]
9 32 ms 40 ms 35 ms be2074.ccr21.jfk07.atlas.cogentco.com [154.54.86
.225]
10 32 ms 32 ms 32 ms be2056.ccr21.jfk02.atlas.cogentco.com [154.54.44
.217]
11 41 ms 49 ms 37 ms be2094.ccr21.bos01.atlas.cogentco.com [154.54.30
.14]
12 38 ms 38 ms 36 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
13 51 ms 36 ms 37 ms 38.111.40.114
14 40 ms 37 ms 37 ms 208.95.186.32
Trace complete.
C:\Users\Jack>
unable to allocate performance buffer
contacting nettest server..
Local IP: 174.54.184.36
Ping: 38.0 msec
Port: 80: 1220 KB/sec 0 KB/sec 0 KB/sec 500
Port: 80: 1194 KB/sec 0 KB/sec 0 KB/sec 500
Port: 443: 1259 KB/sec 0 KB/sec 0 KB/sec 500
Port: 443: 1138 KB/sec 0 KB/sec 0 KB/sec 500
Port: 7255: 1172 KB/sec 0 KB/sec 0 KB/sec 500
Port: 7255: 1260 KB/sec 0 KB/sec 0 KB/sec 500
Port: 7003: 1313 KB/sec 0 KB/sec 0 KB/sec 500
Port: 7003: 1168 KB/sec 0 KB/sec 0 KB/sec 500
Port: 7202: 1117 KB/sec 0 KB/sec 0 KB/sec 500
Port: 7202: 1246 KB/sec 0 KB/sec 0 KB/sec 500
Port: 7499: 1239 KB/sec 0 KB/sec 0 KB/sec 500
Port: 7499: 1163 KB/sec 0 KB/sec 0 KB/sec 500
Port: 80: 1191 KB/sec 0 KB/sec 0 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 0 KB/sec
hit return to exit
Long wait then timeout. Same with Arc client. Same with a different computer.
Access to Gateway, ARC webpages, and speedtests are all fine. (20M down, 5M up)
Nettest times out:
contacting nettest server..timed out
Tracert has request timeouts:
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.x.x]
2 3 ms 4 ms 4 ms L100.DLLSTX-VFTTP-24.verizon-gni.net [71.123.x.x]
3 9 ms 7 ms 7 ms G0-5-0-4.DLLSTX-LCR-22.verizon-gni.net [100.41.194.242]
4 6 ms 7 ms 19 ms ae8-0.DFW9-BB-RTR2.verizon-gni.net [130.81.162.160]
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 59 ms 47 ms 47 ms 0.ae2.XL4.BOS4.ALTER.NET [140.222.226.19]
10 47 ms 47 ms 47 ms 0.ge-9-1-0.GW15.BOS4.ALTER.NET [152.63.24.46]
11 49 ms 49 ms 49 ms internap-gw.customer.alter.net [152.179.134.214]
12 46 ms 49 ms 49 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.41]
13 53 ms 67 ms 54 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
14 54 ms 54 ms 54 ms patchserver2.crypticstudios.com [208.95.185.41]
The BSOD's ONLY HAPPEN WITH THIS GAME.
And yes, I mean a COMPLETE SYSTEM CRASH.
In late 2012, when this same event occurred, I was running Windows Home Premium 64 bit.
As of this date,
I am running a clean install of Windows 7 Ultimate 64 bit.
AMD CPU
AMD HD 6310
I have an excellent internet connection.
I have a fully updated Operating system. This includes DX, Java, .Net 4.5
I have a brand new Hard Drive (It is a spin drive not a solid state and it was bought brand new about 7 days ago.)
I just added a new memory stick (4GB, yes brand new, not used.) to see if I needed more memory. Didn't fix it.
My router was new as of 2 months ago along with my USB Wireless adapter. They are Dual Band and running on the 5 GHz line only with no Bandwidth issues.
Please fix, thanks.
I have a problem when getting invitations and accepting to play in groups for fleet, space or ground based play. The tech support seems to think its a local performance issue but i think its something else.
When i play in the Dyson against the Voth T-Rex there are many people there doing their stuff and if there are to many then the game will lag badly but has never crashed. The problem only happens when i am running around and then i get a pop up that someone has invited me to join and play as a team/group and i accept then after about 5 seconds the game crashes.
This only happens after i accept the invitation to play/join the group/team so please advise if anyone have come across this problem.
Thanks
So how much Video memory does your system have? And have you tried running at a lower screen resolution??
I have a GeForce GT 440 with 1GB RAM and have not tested yet with a lower screen resolution but will test this next.
Also would just like to point out that i had received an error message only one time and it was something about the PhysX but after that i have not received any error.
A dump was sent the last time around to the cryptic. Let me know if you need more information and thanks for the reply.
Thanks
hmmm... 1GB of Video RAM is starting to approach 'marginal' if you're running at 1080p resolution. The other significant question would be system RAM, as 4GB would also start approaching 'marginal' when running at 1080p...
Here's my tracert results:
I'm running on a wireless connection. Connecting directly isn't really an option because the modem/router that Comcast provides can only be plugged in one spot in the house. Any help is appreciated. Thanks.
Your 'Trace Route' is showing excellent network latency values, so this is simply not the information needed to pinpoint what the problem is...
The 'Net Test' diagnostic results would be useful, as it tests for sustained network throughput bandwidth. and using the 'pathping' command (which uses the same syntax as the 'tracert' command) will check if data packets are being lost or thrown away in your Internet path to the STO Servers...
Hey, thanks for the response. I ran the two tests you suggested.
PathPing Test
Net Test