安裝 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(越南文)
Українська(烏克蘭文)
回報翻譯問題
Since we don't have a Mac for testing, we need to rely on mac players to do the necessary backward testing for us (i.e. find the last version that did not cause the bug and the first version that introduced it.) So far, noone has answered our calls. :(
Click on "see more".
Maybe try an unpatched 3.6 base version first.
If the base 3.6 does have the bug, you'll need to install 3.5 separately. For 3.5, it might be enough to focus on 2020 versions (~ r3070 and onwards).
Remember, for regression testing you don't need to test every version. Find a version without the bug, then find a version with the bug, then test a version that's approximately in the middle, and so on.
Also mind that saves aren't backwards compatible. So I would advise to create a save with an earlier version, and use copies of that save for testing. You can use cheats to increase your level and start the war on the new testing save.
If you need any further help or advise, feel free to visit our discord.
Besides, the problem does not happen in the early days (before the war starts), and begins to happen after the war starts, and always happens after a fight.
To note, the bug goes back to at least the version that was out in March of 2020, as thats when I downloaded the mod to begin with.
Fixes
Fix the black screens on macOS and Linux, where after playing for a while textures would corrupt and the player would be unable to load or save their progress, forcing a game restart.
This was caused by the game ending up having too many opened files because it forgets to close the streamed sounds after reading them, reaching the OS limit.
Most of this investigation, reporting and testing has been contributed by @null-painter-error on Discord. Many thanks!