Steam官匹高Ping优化指南（SteamNetSockets乱跳优化）
众所周知，网易UU加速器提供Steam商店免费加速。但默认的进程模式只会劫持Steam的进程因此得选择路由模式代理Steam商店的同时，网易UU加速器也会代理掉SteamNetSockets，但还是会导致连接港服还乱中继到日韩、新加坡的问题
先说优化的效果对比：
比如说没有强制状态的时候，本来是可以直接到新加坡，走了个香港转发多了1ms
使用了net_option SDRClient_ForceRelayCluster sgp 就可以直连啦
那么话不多说，上教程。适用于Dota2及CSGO等Steam官匹！
打开游戏的控制台，status可以看到所有人的ping值情况，
正好查的时候发现有个很好用的命令，如果你玩东南亚经常连到印度金麦，东京，甚至是澳大利亚可以用以下指令强制sdr的指向的服务器，(括号内不要复制)
net_option SDRClient_ForceRelayCluster sgp (新加坡)
如果速度一般，或者你平时中继香港比较好
net_option SDRClient_ForceRelayCluster hkg (香港)
群里也有人会去欧服玩，如果不幸连到了瑞典斯德哥尔摩，可以使用
net_option SDRClient_ForceRelayCluster fra(法兰克福)
net_option SDRClient_ForceRelayCluster par (巴黎)
最后的最后，如果你想回归不强制的设置，只需要
net_option SDRClient_ForceRelayCluster 0
以后发现新方法了会编辑更新
更新，服务器ip
[#972597635 SDR server steamid:90256452095244316 vport 1 'server'] Discarding inactive session sgp#74 (103.10.124.117:27042). ConnectionShutdown
[#972597635 SDR server steamid:90256452095244316 vport 1 'server'] Discarding inactive session hkg#429 (103.28.54.184:27029). ConnectionShutdown
显示ping服务器时间
net_print_sdr_ping_times
得到的SDR请求为
SDR relay network status: OK. Relays: 23 valid, 0 great, 2 good+, 6 ok+, 15 ignored (100 100 100)
SDR ping location: hkg=37+3,hkg4=39+3/37+3,sgp=73+7/68+3,seo=98+9/74+3,tyo=/83+3,maa2=103+10/99+3,bom2=124+12/117+3,dxb=/145+3,syd=161+16/162+3,fra=198+19/196+17,iad=252+25/245+18,gru=/357+18
Measured RTT to 34 SDR points of presence.
(This list may include POPs without any gameservers)
hkg: 37ms via direct route
hkg4: 37ms via hkg (front=37ms, back=0ms) 2ms faster than direct ping of 39ms
sgp: 68ms via hkg (front=37ms, back=31ms) 5ms faster than direct ping of 73ms
seo: 74ms via hkg (front=37ms, back=37ms) 24ms faster than direct ping of 98ms
tyo: 83ms via hkg (front=37ms, back=46ms)
maa2: 99ms via hkg (front=37ms, back=62ms) 4ms faster than direct ping of 103ms
bom2: 117ms via hkg (front=37ms, back=80ms) 7ms faster than direct ping of 124ms
dxb: 145ms via hkg (front=37ms, back=108ms)
syd: 162ms via hkg (front=37ms, back=125ms)
hel: 164ms via hkg (front=37ms, back=127ms) 2ms faster than direct ping of 166ms
sto2: 172ms via sto (front=172ms, back=0ms) 2ms faster than direct ping of 174ms
sto: 172ms via direct route
sea: 176ms via hkg (front=37ms, back=139ms) 6ms faster than direct ping of 182ms
eat: 180ms via hkg (front=37ms, back=143ms)
lax: 188ms via hkg (front=37ms, back=151ms) 95ms faster than direct ping of 283ms
ams4: 191ms via sto (front=172ms, back=19ms) 27ms faster than direct ping of 218ms
waw: 192ms via sto (front=172ms, back=20ms) 106ms faster than direct ping of 298ms
lhr: 196ms via sto (front=172ms, back=24ms) 77ms faster than direct ping of 273ms
fra: 196ms via sto2 (front=174ms, back=22ms) 2ms faster than direct ping of 198ms
mfr1: 199ms via sto2 (front=174ms, back=25ms)
par: 202ms via sto2 (front=174ms, back=28ms) 8ms faster than direct ping of 210ms
vie: 202ms via sto (front=172ms, back=30ms)
dfw: 215ms via mdf1 (front=215ms, back=0ms) 63ms faster than direct ping of 278ms
mdf1: 217ms via direct route
dfw2: 220ms via direct route
mad: 223ms via sto (front=172ms, back=51ms) 2ms faster than direct ping of 225ms
ord: 228ms via sea (front=182ms, back=46ms) 36ms faster than direct ping of 264ms
iad: 245ms via sea (front=182ms, back=63ms) 7ms faster than direct ping of 252ms
atl: 248ms via sea (front=182ms, back=66ms) 3ms faster than direct ping of 251ms
lim: 307ms via sea (front=182ms, back=125ms) 55ms faster than direct ping of 362ms
scl: 336ms via sea (front=182ms, back=154ms) 7ms faster than direct ping of 343ms
jnb: 352ms via sto (front=172ms, back=180ms) 25ms faster than direct ping of 377ms
eze: 356ms via sea (front=182ms, back=174ms)
gru: 357ms via sea (front=182ms, back=175ms)
Obtained direct RTT measurements to relays in 34 POPs. Closest 15 are:
hkg: 37ms
hkg4: 39ms
sgp: 73ms
seo: 98ms
maa2: 103ms
bom2: 124ms
syd: 161ms
hel: 166ms
sto: 172ms
sto2: 174ms
sea: 182ms
ams: 198ms
fra: 198ms
msj1: 198ms
par: 210ms 呃呃
页:
[1]