安装 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 spent at least 3 hours trying various configurations. At least it made me optimize the code somewhat :D.
I think what happened with Uncle, is that he caught my mods mid-update on workshop, and I will not know better until he comes back with more information.
- 1.5 or 1.6
- What mods are enabled
- What errors do you see if you enable DevMode and press Console
I just tested and it seems to work fine on my end:
1) RimTek DigiPal-equipped pawn: https://i.imgur.com/JgzRsZr.png
2) Hurt by shooting: https://i.imgur.com/9VqfwIb.png
3) No errors: https://i.imgur.com/vGGOEsR.png
Just in case, if it's Workshop weirdness, try to unsub and resub to the mods, and relaunch your game.
The only idea I have is that maybe the fact that I updated Core and underlying mods synced with your activity on PC and workshop messed it up for you locally.