安装 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(越南语)
Українська(乌克兰语)
报告翻译问题
https://gist.github.com/HugsLibRecordKeeper/03c80fdf7d071a5c11e6a19ed7a537f9
That said...
What seems to be happening is that the genes on a pawn has changed (for some reason or another), and a "SetAllGraphicsDirty" is being run.
"SetAllGraphicsDirty" is a vanilla rimworld function. If it is silently failing then I would suspect another mod. I'm pretty sure I don't have any empty try/catch statements or the like in code that should run.
I'd suggest doing a bit of binary testing on your modlist to try to figure out what mod combination is causing that interaction.
You could also try asking at Dub's Discord they are pretty well versed in anything performance, including weird silent errors like that.