Whatever this is, it's only happened twice so far but causes extreme lag due to so many errors being made.
The only consistency I know of between these two inceidents was that I was trying to do an auto-burn to orbit the moon.
Errors are in the screenshots. I will put output log thing in comments.
| View |
I'm not seeing this problem being exhibited in the sandbox attached here.
In the future, if you could hit F2 before starting a burn to make a quick-save, then execute the auto-burn. If it exhibits the problem, hit F4 to go back to that point before the burn and upload a bug report from that quick-save. That would help track the problem down greatly.
The sandbox here is failing to restore the node chain however...due to the first planned burn having an invalid true anomaly angle...I'm not sure how it got saved that way without "orphaning" the node prior to saving.
@Mod This is a known issue that has yet to be tracked down. I will make changes to reduce the error log traffic so the log won't become so huge.
Thanks :)
Uhhhhhhhh.... MAYBE I wont upload the output... because it is apparently 1011MB...
@PhilipTarpley Alright. Can do.