安裝 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(越南文)
Українська(烏克蘭文)
回報翻譯問題
But I understand they won't be patching it. I believe the problem was caused by a change in windows or perhaps even directX. If so i imagine a fix could be to place the library(DLL) that worked correctly in the directory of the game.
After Clockwork Empires, Gaslamp Games stopped posting updates on twitter (it's been a year now) and went silent on their forum. A wiki posting explained that after Dec 2016, staff reportedly moved on to other projects, and is practically defunct because of that. I think Clockwork Empires was not successful enough to maintain the company. It might be operating with a skeleton crew (to maintain the company website and stuff), I don't know specifics. It's a safe bet that unless the company is revitalized, it's defunct enough to stop any further development for current or future projects. I would've liked a more official annoucement on their status though, but it is what it is.
The other game is Diablo 1, but only if I use a mouse clicker program (used for auto attacking). The clicker program worked fine before I updated Windows 10, but after the update the mouse cursor will occasionally jump around every few seconds if you hold the left mouse button down. Luckily I found a work around using a different program, X-Mouse Button Control.
I'm glad putting the game in windowed mode fixes the issue in DoD, but I wonder how many other games experience this problem.
"xinput1_3.dll" being changed, But I downloaded an archieve from 2010 and placed that old dll in DoD install directory where "Dungeons of Dredmor.exe" would look for it before going to C:\Windows\System32\ But it didn't work. In fact the file is the exact same size.
Well I don't think it being broken is any fault of the the developers. Microsoft broke this somehow but I'm out of ideas 'how'.