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









"So, I turned on debugging, and it started working"
Isn't that the definition of a heisenbug?
https://imgur.com/a/pvXoBvy
If you replace <LogDebug xsi:nil="true" /> with <LogDebug>true</LogDebug> in the ring config for the planet (or use /ringast logdebug from the chat console and save), the mod should log where it sees the planet as being in the appropriate RingAsteroidComponent log in Storage\3102127379.sbm_BylenRingAsteroids . I wonder if the coordinates for the planet aren't being properly initialized when it is a long way away from the player?