Instale o Steam
iniciar sessão
|
idioma
简体中文 (Chinês simplificado)
繁體中文 (Chinês tradicional)
日本語 (Japonês)
한국어 (Coreano)
ไทย (Tailandês)
Български (Búlgaro)
Čeština (Tcheco)
Dansk (Dinamarquês)
Deutsch (Alemão)
English (Inglês)
Español-España (Espanhol — Espanha)
Español-Latinoamérica (Espanhol — América Latina)
Ελληνικά (Grego)
Français (Francês)
Italiano (Italiano)
Bahasa Indonesia (Indonésio)
Magyar (Húngaro)
Nederlands (Holandês)
Norsk (Norueguês)
Polski (Polonês)
Português (Portugal)
Română (Romeno)
Русский (Russo)
Suomi (Finlandês)
Svenska (Sueco)
Türkçe (Turco)
Tiếng Việt (Vietnamita)
Українська (Ucraniano)
Relatar um problema com a tradução
Either I'm missing something and this is going to require a support ticket with Valve directly, or something is broke on Valve's end and they're handing out client versions with broken elements. I'm not sure either way because I haven't been using sprays much lately and that makes it hard to establish a timeline on when the problem started. Without a timeline, you can't be certain if the break corresponds to a specific patch or not.
So yeah, that's where I'm at but I can see from only having 2 responses in 4 hours both suggesting tier 1 troubleshooting isolation this is not a bigger issue.
*sigh* ...I just hate dealing with software tech support when things are this cut-and-dry. Hopefully they have some sort of SLA I can use as leverage if the ticket doesn't move anywhere. Sure, I'm no software specialist but I do work with routing engines with similar logic. Code is code, configurations are fallible.
Thanks for the effort though, guys.