Инсталирайте 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)
Украински (Українська)
Докладване на проблем с превода











If you don't want to do that, you can disable the audio mods and use the console command "snd_rebuildaudiocache" which will make a new cache for whatever sounds you have right now.
Both of these require some time, either to verify and download, or calculate a new cache.
Personally, i'd verify files. while backing up any modified gameinfo or somesuch.
But i did make sure that the sounds won't have this bug. And since after 17k users you're probably the first to mention this, i'm assuming you had at one point made a custom soundcache at some point, and then installed this mod, so they no longer match.
If that is the case, disable this mod and rebuild a new sound cache, or revert to the og sound cache if possible.
Will be looking forward to an answer!
Also, from what I've been finding, could it be because of high RAM usage? If so, would it maybe make sense to just disable your mods and instead throw them into the main files instead?
And why would they. that's not how mods work.