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










I'm not sure how would i fix that though
However, blue screens may actually be that you are forcing too much processing power to your computer. Just go to the settings and lower some values, some texture qualities, some range to see objects, then you should see less blue screens.
Also keep your computer cooled.
I can try to do that in the next Project _however_
that's not why kenshi crashes AFAIK. (take it with a grain of salt)
it crashes because either a filepath is broken (written incorrectly or not existent at all)
or if another mod creates again a modrecord (specially with a broken filepath).
a good rule of thumb is to paste the last part of the kenshi log and let chatgpt figure it out from there.
It does show all mod conflicts where a record is created twice or more therefore overwriting all fields.
give me more ideas of what you would like to see in a project like that, maybe after 2 KenshiPatcher patches in the weekend i will program it