Upvote Upvoted 3 Downvote Downvoted
Casual matchmaking auto-defaults to Virginia
posted in Q/A Help
1
#1
0 Frags +

So for some reason ever since the mystery update for TF2 I am always getting routed to Virginia US servers (130 ms), despite having my custom ping selected to 95 ms. I'm not catching Madrid, Luxembourg or Stockholm servers, only Virginia.

How to fix?

So for some reason ever since the mystery update for TF2 I am always getting routed to Virginia US servers (130 ms), despite having my custom ping selected to 95 ms. I'm not catching Madrid, Luxembourg or Stockholm servers, only Virginia.

How to fix?
2
#2
0 Frags +

Bump

Bump
3
#3
23 Frags +

Move to Virginia

Move to Virginia
4
#4
6 Frags +

epic meme, upvoted

epic meme, upvoted
5
#5
2 Frags +

What is the output of tf_datacenter_ping_dump?

What is the output of tf_datacenter_ping_dump?
6
#6
1 Frags +

Hi mastercoms, I have the same problem as Fuxx. Here's the dumped data:
[SDR Ping] Ping data is current as of Sat Sep 16 22:28:05 2017. Pending refresh: 0, Sent initial fix: 1
ams: 93ms, status 1
atl: 147ms, status 1
bom: 166ms, status 1
dxb: 259ms, status 1
fra: 55ms, status 1
gru: 313ms, status 1
hkg: 308ms, status 1
iad: 138ms, status 1
jnb: 213ms, status 1
lax: 186ms, status 1
lhr: 47ms, status 1
lim: 256ms, status 1
lux: 51ms, status 1
maa: 179ms, status 1
mad: 18ms, status 1
man: 400ms, status 1
mwh: 195ms, status 1
okc: 221ms, status 1
ord: 245ms, status 1
scl: 320ms, status 1
sea: 245ms, status 1
sgp: 245ms, status 1
sto: 63ms, status 1
sto2: 67ms, status 1
syd: 373ms, status 1
tuk: 245ms, status 1
tyo: 297ms, status 1
vie: 56ms, status 1
waw: 100ms, status 1
eat: 181ms, status 3

Hi mastercoms, I have the same problem as Fuxx. Here's the dumped data:
[SDR Ping] Ping data is current as of Sat Sep 16 22:28:05 2017. Pending refresh: 0, Sent initial fix: 1
ams: 93ms, status 1
atl: 147ms, status 1
bom: 166ms, status 1
dxb: 259ms, status 1
fra: 55ms, status 1
gru: 313ms, status 1
hkg: 308ms, status 1
iad: 138ms, status 1
jnb: 213ms, status 1
lax: 186ms, status 1
lhr: 47ms, status 1
lim: 256ms, status 1
lux: 51ms, status 1
maa: 179ms, status 1
mad: 18ms, status 1
man: 400ms, status 1
mwh: 195ms, status 1
okc: 221ms, status 1
ord: 245ms, status 1
scl: 320ms, status 1
sea: 245ms, status 1
sgp: 245ms, status 1
sto: 63ms, status 1
sto2: 67ms, status 1
syd: 373ms, status 1
tuk: 245ms, status 1
tyo: 297ms, status 1
vie: 56ms, status 1
waw: 100ms, status 1
eat: 181ms, status 3
7
#7
2 Frags +

See if

steamdatagram_client_force_relay_cluster mad

fixes it.

EDIT: this command was removed in the steam datagram update a few days ago. not sure how to fix it then.

See if
[code]steamdatagram_client_force_relay_cluster mad[/code]
fixes it.

EDIT: this command was removed in the steam datagram update a few days ago. not sure how to fix it then.
Please sign in through STEAM to post a comment.