安装 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(越南语)
Українська(乌克兰语)
报告翻译问题








Before I got mine working right I was getting an error weather loading an old save or making a new game that essentially said that the game was having trouble making a seed (the word 'story' was used) and that one of my mods may be the cause.
As you said, it gives the error "Failed to create a working story".
But for whatever reason, despite trying everything I could think of to get the DLL noticed by Steam Proton on Linux, it just will not load properly. Is there anything I can do to get it working on there? DOS2 on Linux without the script extender has loading times in the range of at least 15+ minutes, which is exceedingly painful, so figuring out how to get the DLL to properly hook is pretty frickin vital to play on Linux using Steam Proton.
Given how the game works fine once actually loaded, I'm loathe to toss D:OS2 into my "Only works on Windows" category, but the 15+ minute load times REALLY make me tempted to do exactly that. Any method to get Proton to notice the script extender and actually utilize it wuld be appreciated.