Zainstaluj Steam
zaloguj się
|
język
简体中文 (chiński uproszczony)
繁體中文 (chiński tradycyjny)
日本語 (japoński)
한국어 (koreański)
ไทย (tajski)
български (bułgarski)
Čeština (czeski)
Dansk (duński)
Deutsch (niemiecki)
English (angielski)
Español – España (hiszpański)
Español – Latinoamérica (hiszpański latynoamerykański)
Ελληνικά (grecki)
Français (francuski)
Italiano (włoski)
Bahasa Indonesia (indonezyjski)
Magyar (węgierski)
Nederlands (niderlandzki)
Norsk (norweski)
Português (portugalski – Portugalia)
Português – Brasil (portugalski brazylijski)
Română (rumuński)
Русский (rosyjski)
Suomi (fiński)
Svenska (szwedzki)
Türkçe (turecki)
Tiếng Việt (wietnamski)
Українська (ukraiński)
Zgłoś problem z tłumaczeniem
Turns out it was actually an OpenAL problem, it just wasn't fixed be reinstalling. The problem was that the game only found the x64 version of the OpenAL32.dll, and the fix was downloading the x32 version and putting it in the game folder. I found this out via the program Dependency Walker
PowerShell can't fix problems, but its output might help highlight the problem.
If nothing works, I'd suggest you search that error code online.
I don't think I can explain how to run the game through PowerShell any more easily. If you're not sure, please check how to run a program (or .exe) through PowerShell online.
If, at your own risk, you decide to follow the instructions provided there, please let me know whether it works or not. The first step redirects you to the Microsoft website, so it's safe. The second you can skip since it's about Microsoft Visual C++ Redistributable package. The third, IDK.