My system RAM is 3GB and can i know which part does it say 1080p in the configuration settings? As i am unable to see that under resolution.
Thanks
3GB of RAM is considered marginal just for normal Windows use, so this is probably the cause of your problems...
1920 x 1080 60Hz is what 1080p resolution is, (normal TV HD resolution) and should be listed under Video Resolutions. With the resources that you have, this should be dropped to 1200 x 600 or lower. And you really should consider upgrading the RAM in your system to 8GB capacity...
Hey, thanks for the response. I ran the two tests you suggested.
... Net Test
Now when the 'Net Test' can't allocate a memory buffer, this shows a system issue, (such as too many back-ground tasks running, or too many networked applications running)
Try running 'Net Test' on a newly booted system with nothing else running, and consider cleaning up your Windows Hot Tray of unnecessary apps...
Otherwise, the 'Path Ping' shows no issues what so ever... So without a working 'Net Test' results to see what your sustained throughput is, its hard to say what the problem is. If its a Networking issue, it may be so intermittent that the diagnostic tests aren't catching it, or it may not even be a Networking issues at all, as the 'Net Test' initialization issues looks suspicious...
Now when the 'Net Test' can't allocate a memory buffer, this shows a system issue, (such as too many back-ground tasks running, or too many networked applications running)
Try running 'Net Test' on a newly booted system with nothing else running, and consider cleaning up your Windows Hot Tray of unnecessary apps...
Otherwise, the 'Path Ping' shows no issues what so ever... So without a working 'Net Test' results to see what your sustained throughput is, its hard to say what the problem is. If its a Networking issue, it may be so intermittent that the diagnostic tests aren't catching it, or it may not even be a Networking issues at all, as the 'Net Test' initialization issues looks suspicious...
Sorry it took me so long to reply. Holidays and everything.
I tried your suggestion about running nettest on a freshly rebooted system, but I'm still getting the message "unable to allocate performance buffer." Could the problem be Windows 8 or something? I have 8GB ram as well, if that means anything.
...
I tried your suggestion about running nettest on a freshly rebooted system, but I'm still getting the message "unable to allocate performance buffer." Could the problem be Windows 8 or something? I have 8GB ram as well, if that means anything.
8GB of RAM is plenty of memory, and many players use Win 8 to run STO, so their not the issue. It sounds like something is on your system that is conflicting with the network functionality that STO uses... Try looking over the list of conflicting apps and utilities that are not compatible with STO...
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
Hi,
The message above was the original description of my problem and was last advised to test by upgrading my RAM as i only had 3GB system RAM with a Geforce GT440 with 1GB.
But i have now discovered the source of the problem and it was the Arc client. Usually i would launch the Arc client login to it and launch STO from there and it would launch the STO "gameclient.exe" and game starts.
So now i have tested by launching the STO "gameclient.exe" directly then login and continue with the game without opening Arc at all and this has resolved the issue.
Now i am able to enjoy playing in groups and play all the "Hard" groups based missions for the reputation system or for other things and all this without upgrading my system RAM.
I hope this info will be useful for other if they come across the same issue and thanks for the fast responses and advise.
The message above was the original description of my problem and was last advised to test by upgrading my RAM as i only had 3GB system RAM with a Geforce GT440 with 1GB.
But i have now discovered the source of the problem and it was the Arc client. Usually i would launch the Arc client login to it and launch STO from there and it would launch the STO "gameclient.exe" and game starts.
So now i have tested by launching the STO "gameclient.exe" directly then login and continue with the game without opening Arc at all and this has resolved the issue.
Now i am able to enjoy playing in groups and play all the "Hard" groups based missions for the reputation system or for other things and all this without upgrading my system RAM.
I hope this info will be useful for other if they come across the same issue and thanks for the fast responses and advise.
Thanks
While this works for now, I have to advise you that ARC will become a required launcher sooner or later so you'd be right back at square one
Yes, I'm that Askray@Batbayer in game. Yes, I still play. No, I don't care. Former Community Moderator, Former SSR DJ, Now Full time father to two kids, Husband, Retail Worker. Tiktok: @Askray Facebook: Askray113
The message above was the original description of my problem and was last advised to test by upgrading my RAM as i only had 3GB system RAM with a Geforce GT440 with 1GB.
But i have now discovered the source of the problem and it was the Arc client. Usually i would launch the Arc client login to it and launch STO from there and it would launch the STO "gameclient.exe" and game starts.
...
Its most likely the case that you do not have enough RAM to run STO, and have ARC remain resident in memory at the same time. So the original diagnose appears to be correct, you need more RAM installed...
Its most likely the case that you do not have enough RAM to run STO, and have ARC remain resident in memory at the same time. So the original diagnose appears to be correct, you need more RAM installed...
Listed system requirements for STO on the ARC website still say 1GB minimum, 2GB recommended. They were apparently updated last November of 2013. Not saying that there hasn't been a pile of bloat since then, because there has - but PWE should really look at updating those if they no longer cut it.
Personally, I have never seen the game client consume more than 2GB of RAM while I was running it.
In this day and age, RAM is considered "cheap". But ARC shouldn't consume so much that a system with 50% more than the "recommended" specifications is struggling, unless a pile of other programs are running as well. If it does, then it's bloatware that is in dire need of optimisation, OR, they need to rewrite the specs (which costs 0 development time). Really, it's a launcher - there is NO reason why it should consume more than a small amount of RAM (ie not hundreds of megabytes).
Otherwise, they open the door to new players having subpar gameplay experience, and being turned off of not only STO, but all potentially all the games attached to ARC.
As you say, the diagnosis seems "correct", low memory. WHY that is the case, with well over the recommended specs, that's a whole other matter - one that should be addressed by PWE. If there isn't time to optmize STO and ARC, just fix the specs.
As you say, the diagnosis seems "correct", low memory. WHY that is the case, with well over the recommended specs, that's a whole other matter - one that should be addressed by PWE. If there isn't time to optmize STO and ARC, just fix the specs.
This would be correct if ARC and STO was the only thing running on a Windows system. But when you start adding in memory resident utilities, Anti-Virus and Firewall software, additional hardware drivers, etc. these thing start to add up quickly. (Have you looked at how many items are in your Hot-Tray recently???) This is why 4GB of RAM is recommended for 'stable' Windows use...
The last few days has been practicaly impossible for me to play the game, sometimes i can not even pass de second login. And if i get to the game, i can't move because of the lag. Here is my tests
The last few days has been practicaly impossible for me to play the game, sometimes i can not even pass de second login. And if i get to the game, i can't move because of the lag. Here is my tests
...
The 'Path Ping' results shows what your problem is. You're suffering from 'dropped packets' starting from your ISP, and in both the Seabone and Cogent backbone networks.
You should contact your ISP technical support, and ask about those 'dropped packets' in their networks, and have them talk to Seabone about dropped packets in that backbone provider.
You should also open a ticket with Cryptic/PWE to get them to kick Cogent a few more times to get the problem looked into...
Ok, thx for the help, i'll do what you suggest, unfurtunaly talking with my isp technical support is more frustrating than talking with cleverbot.
Check the Modem on your end (power cycle it) this means to shut it off for 30 secs then turn back on
Call up the ISP have them to a hit to your modem.
They can also reset the modem or walk you through it.
If you rent the modem from them they can replace it for faster newer type.
All sorts of things can effect performance. But first check with the ISP Internet Support.
disconnecting in game, severe intermittent lag. Just trying to figure it out its only been happening the last week.
From what i can tell below the ping looks ok timewise and loss wise. (bt connection from UK)
....
Well not quite... 180 ms is the recommended upper limit on network latency for reliable game play. And both of your 'Path Ping' results are showing values above this, (probably due to traffic congestion on the Cogent Trans-Atlantic link...) which would account for the intermittent lag...
(Now if we only had the 'Net Test' results to look at, to see if this is effecting your sustained connection throughput bandwidth...)
my "speedtest" is 19ms 8.59mbps up and 0.88 mbps (when i let it choose the server)
my "ping test" is 30ms and 7ms jitter from the UK to germany(it choose the server)
my "speedtest" is 19ms 8.59mbps up and 0.88 mbps (when i let it choose the server)
my "ping test" is 30ms and 7ms jitter from the UK to germany(it choose the server)
But what is your sustained network throughput to the STO servers ???? (After all, your problems are with the STO Servers, not these other test sites....)
Tracing route to 208.95.168.32 over a maximum of 30 hops
1 6 ms 6 ms 5 ms *.*.*.*
2 6 ms 8 ms 6 ms wolv-core-2b-xe-310-0.network.virginmedia.net
3 7 ms 7 ms 7 ms brhm-bb-1b-ae7-0.network.virginmedia.net
4 13 ms 11 ms 11 ms ae1.lon25.ip4.gtt.net [77.67.65.161]
5 171 ms 171 ms 172 ms xe-1-2-3.was14.ip4.gtt.net [89.149.180.198]
6 93 ms 93 ms 94 ms ash1-pr1-ae5-411.us.twtelecom.net [64.132.69.221]
7 119 ms 120 ms 120 ms orl1-ar4-xe-2-0-0-0.us.twtelecom.net [66.192.245.214]
8 122 ms 122 ms 120 ms 66-192-143-30.static.twtelecom.net [66.192.143.30]
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
Comments
3GB of RAM is considered marginal just for normal Windows use, so this is probably the cause of your problems...
1920 x 1080 60Hz is what 1080p resolution is, (normal TV HD resolution) and should be listed under Video Resolutions. With the resources that you have, this should be dropped to 1200 x 600 or lower. And you really should consider upgrading the RAM in your system to 8GB capacity...
Now when the 'Net Test' can't allocate a memory buffer, this shows a system issue, (such as too many back-ground tasks running, or too many networked applications running)
Try running 'Net Test' on a newly booted system with nothing else running, and consider cleaning up your Windows Hot Tray of unnecessary apps...
Otherwise, the 'Path Ping' shows no issues what so ever... So without a working 'Net Test' results to see what your sustained throughput is, its hard to say what the problem is. If its a Networking issue, it may be so intermittent that the diagnostic tests aren't catching it, or it may not even be a Networking issues at all, as the 'Net Test' initialization issues looks suspicious...
Sorry it took me so long to reply. Holidays and everything.
I tried your suggestion about running nettest on a freshly rebooted system, but I'm still getting the message "unable to allocate performance buffer." Could the problem be Windows 8 or something? I have 8GB ram as well, if that means anything.
8GB of RAM is plenty of memory, and many players use Win 8 to run STO, so their not the issue. It sounds like something is on your system that is conflicting with the network functionality that STO uses... Try looking over the list of conflicting apps and utilities that are not compatible with STO...
Hi,
The message above was the original description of my problem and was last advised to test by upgrading my RAM as i only had 3GB system RAM with a Geforce GT440 with 1GB.
But i have now discovered the source of the problem and it was the Arc client. Usually i would launch the Arc client login to it and launch STO from there and it would launch the STO "gameclient.exe" and game starts.
So now i have tested by launching the STO "gameclient.exe" directly then login and continue with the game without opening Arc at all and this has resolved the issue.
Now i am able to enjoy playing in groups and play all the "Hard" groups based missions for the reputation system or for other things and all this without upgrading my system RAM.
I hope this info will be useful for other if they come across the same issue and thanks for the fast responses and advise.
Thanks
Former Community Moderator, Former SSR DJ, Now Full time father to two kids, Husband, Retail Worker.
Tiktok: @Askray Facebook: Askray113
Its most likely the case that you do not have enough RAM to run STO, and have ARC remain resident in memory at the same time. So the original diagnose appears to be correct, you need more RAM installed...
Yes you are right the RAM is too low and i am in the process of upgrading my machine to either 8 or 32GB of RAM soon.
Thanks
Listed system requirements for STO on the ARC website still say 1GB minimum, 2GB recommended. They were apparently updated last November of 2013. Not saying that there hasn't been a pile of bloat since then, because there has - but PWE should really look at updating those if they no longer cut it.
http://support.arcgames.com/app/answers/detail/a_id/4009/~/(sto)-system-requirements
Personally, I have never seen the game client consume more than 2GB of RAM while I was running it.
In this day and age, RAM is considered "cheap". But ARC shouldn't consume so much that a system with 50% more than the "recommended" specifications is struggling, unless a pile of other programs are running as well. If it does, then it's bloatware that is in dire need of optimisation, OR, they need to rewrite the specs (which costs 0 development time). Really, it's a launcher - there is NO reason why it should consume more than a small amount of RAM (ie not hundreds of megabytes).
Otherwise, they open the door to new players having subpar gameplay experience, and being turned off of not only STO, but all potentially all the games attached to ARC.
As you say, the diagnosis seems "correct", low memory. WHY that is the case, with well over the recommended specs, that's a whole other matter - one that should be addressed by PWE. If there isn't time to optmize STO and ARC, just fix the specs.
This would be correct if ARC and STO was the only thing running on a Windows system. But when you start adding in memory resident utilities, Anti-Virus and Firewall software, additional hardware drivers, etc. these thing start to add up quickly. (Have you looked at how many items are in your Hot-Tray recently???) This is why 4GB of RAM is recommended for 'stable' Windows use...
C:\Windows\system32>tracert patchserver.crypticstudios.com
Traza a la direcci
Ok, thx for the help, i'll do what you suggest, unfurtunaly talking with my isp technical support is more frustrating than talking with cleverbot.
1 3 ms 5 ms 7 ms 192.168.1.1
2 6 ms 3 ms 9 ms 188-***-**-***.next-gen.ro [188.***.**.***]
3 1 ms 1 ms 1 ms 188-***-**-*.next-gen.ro [188.***.**.*]
4 3 ms 3 ms 1 ms 89.***.***.***
5 38 ms 38 ms 39 ms 10.0.228.45
6 44 ms 41 ms 43 ms 10.0.252.197
7 68 ms 53 ms 47 ms 10.0.200.53
8 40 ms 55 ms 47 ms 10.0.222.14
9 83 ms 36 ms 47 ms l0.milnit1-cr1.bbnplanet.net [195.16.160.17]
10 39 ms 50 ms 39 ms be3020.rcr21.fra06.atlas.cogentco.com [130.117.1
5.193]
11 45 ms 49 ms 42 ms be2304.ccr41.fra03.atlas.cogentco.com [154.54.74
.73]
12 67 ms 54 ms 49 ms be2261.ccr41.ams03.atlas.cogentco.com [154.54.37
.29]
13 60 ms 66 ms 60 ms be2182.ccr21.lpl01.atlas.cogentco.com [154.54.77
.246]
14 135 ms 134 ms 133 ms be2386.ccr21.bos01.atlas.cogentco.com [154.54.44
.161]
15 127 ms 129 ms 132 ms te3-4.ccr01.bos06.atlas.cogentco.com [154.54.46.
134]
16 138 ms 128 ms 145 ms 38.111.40.114
17 * * * Request timed out.
18 * * * Request timed out.
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.
Trace complete.
C:\Users\horhe>
Call up the ISP have them to a hit to your modem.
They can also reset the modem or walk you through it.
If you rent the modem from them they can replace it for faster newer type.
All sorts of things can effect performance. But first check with the ISP Internet Support.
Time will only tell!
unable to ping 208.85.168.32
tracert 208.95.168.32
Tracing route to 208.95.168.32 over a maximum of 30 hops
1 7 ms 5 ms 6 ms *.*.*.*
2 10 ms 6 ms 6 ms wolv-core-2b-xe-310-0.network.virginmedia.net
3 8 ms 7 ms 7 ms brhm-bb-1b-ae7-0.network.virginmedia.net
4 12 ms 11 ms 11 ms ae1.lon25.ip4.gtt.net [77.67.65.161]
5 92 ms 94 ms 93 ms xe-1-2-3.was14.ip4.gtt.net [89.149.180.198]
6 92 ms 93 ms 92 ms ash1-pr1-ae5-411.us.twtelecom.net [64.132.69.221]
7 119 ms 119 ms 120 ms orl1-ar4-xe-2-0-0-0.us.twtelecom.net [66.192.245.214]
8 125 ms 121 ms 120 ms 66-192-143-30.static.twtelecom.net [66.192.143.30]
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
also ran a regional ping and speedtest for referance
http://www.speedtest.net/my-result/3809317637
any advice would be greatly appreciated
Regards
From what i can tell below the ping looks ok timewise and loss wise. (bt connection from UK)
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
0 Rob-Desktop.home [192.168.1.79]
1 BThomehub.home [192.168.1.254]
2 217.32.142.3
3 217.32.142.30
4 host109-159-245-146.range109-159.btcentralplus.com [109.159.245.146]
5 213.120.162.69
6 31.55.165.109
7 acc2-xe-7-3-0.mr.21cn-ipp.bt.net [109.159.250.226]
8 core1-te0-3-0-14.ilford.ukcore.bt.net [109.159.250.154]
9 peer3-te-0-2-0-6.telehouse.ukcore.bt.net [109.159.252.55]
10 166-49-211-244.eu.bt.net [166.49.211.244]
11 be3035.ccr21.lon01.atlas.cogentco.com [130.117.14.169]
12 be2314.ccr21.lon13.atlas.cogentco.com [154.54.72.253]
13 be2495.ccr42.lon13.atlas.cogentco.com [154.54.39.133]
14 be2493.ccr22.bos01.atlas.cogentco.com [154.54.42.97]
15 te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.130]
16 38.111.40.114
17 patchserver2.crypticstudios.com [208.95.185.41]
Computing statistics for 425 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Rob-Desktop.home [192.168.1.79]
0/ 100 = 0% |
1 3ms 0/ 100 = 0% 0/ 100 = 0% BThomehub.home [192.168.1.254]
0/ 100 = 0% |
2 9ms 0/ 100 = 0% 0/ 100 = 0% 217.32.142.3
0/ 100 = 0% |
3 15ms 0/ 100 = 0% 0/ 100 = 0% 217.32.142.30
0/ 100 = 0% |
4 9ms 0/ 100 = 0% 0/ 100 = 0% host109-159-245-146.range109-159.b
tcentralplus.com [109.159.245.146]
0/ 100 = 0% |
5 9ms 0/ 100 = 0% 0/ 100 = 0% 213.120.162.69
0/ 100 = 0% |
6 9ms 0/ 100 = 0% 0/ 100 = 0% 31.55.165.109
0/ 100 = 0% |
7 13ms 0/ 100 = 0% 0/ 100 = 0% acc2-xe-7-3-0.mr.21cn-ipp.bt.net [
109.159.250.226]
0/ 100 = 0% |
8 24ms 0/ 100 = 0% 0/ 100 = 0% core1-te0-3-0-14.ilford.ukcore.bt.
net [109.159.250.154]
0/ 100 = 0% |
9 17ms 0/ 100 = 0% 0/ 100 = 0% peer3-te-0-2-0-6.telehouse.ukcore.
bt.net [109.159.252.55]
0/ 100 = 0% |
10 18ms 0/ 100 = 0% 0/ 100 = 0% 166-49-211-244.eu.bt.net [166.49.2
11.244]
0/ 100 = 0% |
11 18ms 0/ 100 = 0% 0/ 100 = 0% be3035.ccr21.lon01.atlas.cogentco.
com [130.117.14.169]
0/ 100 = 0% |
12 22ms 0/ 100 = 0% 0/ 100 = 0% be2314.ccr21.lon13.atlas.cogentco.
com [154.54.72.253]
0/ 100 = 0% |
13 112ms 0/ 100 = 0% 0/ 100 = 0% be2495.ccr42.lon13.atlas.cogentco.
com [154.54.39.133]
0/ 100 = 0% |
14 184ms 0/ 100 = 0% 0/ 100 = 0% be2493.ccr22.bos01.atlas.cogentco.
com [154.54.42.97]
0/ 100 = 0% |
15 209ms 0/ 100 = 0% 0/ 100 = 0% te3-2.ccr01.bos06.atlas.cogentco.c
om [154.54.46.130]
0/ 100 = 0% |
16 187ms 0/ 100 = 0% 0/ 100 = 0% 38.111.40.114
0/ 100 = 0% |
17 183ms 0/ 100 = 0% 0/ 100 = 0% patchserver2.crypticstudios.com [2
08.95.185.41]
Trace complete.
C:\Users\Rob>
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
0 Rob-Desktop.home [192.168.1.79]
1 BThomehub.home [192.168.1.254]
2 217.32.142.3
3 217.32.142.30
4 host109-159-245-146.range109-159.btcentralplus.com [109.159.245.146]
5 213.120.162.69
6 31.55.165.109
7 acc2-xe-7-3-0.mr.21cn-ipp.bt.net [109.159.250.226]
8 core1-te0-3-0-14.ilford.ukcore.bt.net [109.159.250.154]
9 peer3-te-0-2-0-6.telehouse.ukcore.bt.net [109.159.252.55]
10 166-49-211-244.eu.bt.net [166.49.211.244]
11 be3035.ccr21.lon01.atlas.cogentco.com [130.117.14.169]
12 be2314.ccr21.lon13.atlas.cogentco.com [154.54.72.253]
13 be2495.ccr42.lon13.atlas.cogentco.com [154.54.39.133]
14 be2493.ccr22.bos01.atlas.cogentco.com [154.54.42.97]
15 te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.130]
16 38.111.40.114
17 patchserver2.crypticstudios.com [208.95.185.41]
Computing statistics for 425 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Rob-Desktop.home [192.168.1.79]
0/ 100 = 0% |
1 3ms 0/ 100 = 0% 0/ 100 = 0% BThomehub.home [192.168.1.254]
0/ 100 = 0% |
2 9ms 0/ 100 = 0% 0/ 100 = 0% 217.32.142.3
0/ 100 = 0% |
3 15ms 0/ 100 = 0% 0/ 100 = 0% 217.32.142.30
0/ 100 = 0% |
4 9ms 0/ 100 = 0% 0/ 100 = 0% host109-159-245-146.range109-159.b
tcentralplus.com [109.159.245.146]
0/ 100 = 0% |
5 9ms 0/ 100 = 0% 0/ 100 = 0% 213.120.162.69
0/ 100 = 0% |
6 9ms 0/ 100 = 0% 0/ 100 = 0% 31.55.165.109
0/ 100 = 0% |
7 13ms 0/ 100 = 0% 0/ 100 = 0% acc2-xe-7-3-0.mr.21cn-ipp.bt.net [
109.159.250.226]
0/ 100 = 0% |
8 24ms 0/ 100 = 0% 0/ 100 = 0% core1-te0-3-0-14.ilford.ukcore.bt.
net [109.159.250.154]
0/ 100 = 0% |
9 17ms 0/ 100 = 0% 0/ 100 = 0% peer3-te-0-2-0-6.telehouse.ukcore.
bt.net [109.159.252.55]
0/ 100 = 0% |
10 18ms 0/ 100 = 0% 0/ 100 = 0% 166-49-211-244.eu.bt.net [166.49.2
11.244]
0/ 100 = 0% |
11 18ms 0/ 100 = 0% 0/ 100 = 0% be3035.ccr21.lon01.atlas.cogentco.
com [130.117.14.169]
0/ 100 = 0% |
12 22ms 0/ 100 = 0% 0/ 100 = 0% be2314.ccr21.lon13.atlas.cogentco.
com [154.54.72.253]
0/ 100 = 0% |
13 112ms 0/ 100 = 0% 0/ 100 = 0% be2495.ccr42.lon13.atlas.cogentco.
com [154.54.39.133]
0/ 100 = 0% |
14 184ms 0/ 100 = 0% 0/ 100 = 0% be2493.ccr22.bos01.atlas.cogentco.
com [154.54.42.97]
0/ 100 = 0% |
15 209ms 0/ 100 = 0% 0/ 100 = 0% te3-2.ccr01.bos06.atlas.cogentco.c
om [154.54.46.130]
0/ 100 = 0% |
16 187ms 0/ 100 = 0% 0/ 100 = 0% 38.111.40.114
0/ 100 = 0% |
17 183ms 0/ 100 = 0% 0/ 100 = 0% patchserver2.crypticstudios.com [2
08.95.185.41]
Trace complete.
Well not quite... 180 ms is the recommended upper limit on network latency for reliable game play. And both of your 'Path Ping' results are showing values above this, (probably due to traffic congestion on the Cogent Trans-Atlantic link...) which would account for the intermittent lag...
(Now if we only had the 'Net Test' results to look at, to see if this is effecting your sustained connection throughput bandwidth...)
my "ping test" is 30ms and 7ms jitter from the UK to germany(it choose the server)
But what is your sustained network throughput to the STO servers ???? (After all, your problems are with the STO Servers, not these other test sites....)
This evenings post..
regional ping and speedtest, all ok..
http://www.pingtest.net/result/107784706.png
http://www.speedtest.net/my-result/3811325087
unable to ping 208.95.168.32
tracert to 208.95.168.32
Tracing route to 208.95.168.32 over a maximum of 30 hops
1 6 ms 6 ms 5 ms *.*.*.*
2 6 ms 8 ms 6 ms wolv-core-2b-xe-310-0.network.virginmedia.net
3 7 ms 7 ms 7 ms brhm-bb-1b-ae7-0.network.virginmedia.net
4 13 ms 11 ms 11 ms ae1.lon25.ip4.gtt.net [77.67.65.161]
5 171 ms 171 ms 172 ms xe-1-2-3.was14.ip4.gtt.net [89.149.180.198]
6 93 ms 93 ms 94 ms ash1-pr1-ae5-411.us.twtelecom.net [64.132.69.221]
7 119 ms 120 ms 120 ms orl1-ar4-xe-2-0-0-0.us.twtelecom.net [66.192.245.214]
8 122 ms 122 ms 120 ms 66-192-143-30.static.twtelecom.net [66.192.143.30]
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.