Steam 설치
로그인
|
언어
简体中文(중국어 간체)
繁體中文(중국어 번체)
日本語(일본어)
ไทย(태국어)
Български(불가리아어)
Čeština(체코어)
Dansk(덴마크어)
Deutsch(독일어)
English(영어)
Español - España(스페인어 - 스페인)
Español - Latinoamérica(스페인어 - 중남미)
Ελληνικά(그리스어)
Français(프랑스어)
Italiano(이탈리아어)
Bahasa Indonesia(인도네시아어)
Magyar(헝가리어)
Nederlands(네덜란드어)
Norsk(노르웨이어)
Polski(폴란드어)
Português(포르투갈어 - 포르투갈)
Português - Brasil(포르투갈어 - 브라질)
Română(루마니아어)
Русский(러시아어)
Suomi(핀란드어)
Svenska(스웨덴어)
Türkçe(튀르키예어)
Tiếng Việt(베트남어)
Українська(우크라이나어)
번역 관련 문제 보고
All the Steam Friends and Steam Public networking goes via Steams Peer to Peer API in order to allow play between machines that may be behind NATs / firewalls. The documentation states that while they try to establish a direct connection between machines, but if this fails they can also resort to routing messages via their own backends. I suspect that if this happens round trip latency might increase.
With all of that said, we still have work to do on improving the networked experience. See this post for a technical overview of what currently affects network performance in the game.
We are currently looking into graphics performance stuff and have some good fixes just implemented. This will probably roll out as a specific update so we can see if it helps people with slowdown situations. With the current network setup this has direct implications on networked performance as well.
After that, looking at our backlog and plan, improving the networked experience is pretty high priority.
We regularly do pre-update testing between Sweden and California (thanks Billy!) to ensure that things stay solid.
I heard someone played a game between Tennessee and New Zealand that also worked...
10/10, would buy again !