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








Thats the full crash log. The crash has happened to me 4 times now. It seems to occur when my Defense shield finishes charging. I have a base that was generating about 15Gw of power and also have a mod that provides capacitors so I can dump a large amount of power into my grid as a buffer for heavy load situations. About 2 or 3 Gw in maybe 30seconds or so. If I get into a scrap and take a large amount of shield damage the shields charge up using all the capacitors power then my guess is the caps fill up and because of how the game calculates the drain / charge time it overflows your scripts calculations. The capacitors are always floating at around 99% charge when idle.
Anyway, thats my best guess. About all that I can help on this error. Would love to continue to use this script. Up till this issue it was a staple of my builds. But right now, I've got it on ice till the CTD thing is resolved. :-/
Thanks for looking into it. Good luck ('-')7
Googled: "System.OverflowException TimeSpan overflowed because the duration is too long" and received the following StackOverflow response by Juan Redondo (https://stackoverflow.com/a/60740007):
Analysing error location in InformationPanel.GetTime():
Analysing error location in InformationPanel.PaintInformation():
Upon analysis, the variable "charge" is checked for 0, but the whole algorithm in "seconds" is set to 0 if the "charge" variable is 0. This is a problem if TimeSpan.FromSeconds() cannot handle 0.
Possible solution #1:
Possible solution #2:
Solution #2 seems better, as seconds should be able to be 0. By using solution #1, seconds will never be below 1.
Thanks for quick and concise error report
Locking the thread until the issue arises again.