-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Moving a manoeuver node forward too fast crashes the game #2188
Comments
Game version 1.7.0, Principia Version Fatou (Yeah I downloaded the latest released code and compiled it by myself... Can't wait for the new moon) |
Can you provide us with the |
This is the INFO file at the second crash, so hopefully it will be clean enough. |
I am unable to reproduce the issue in Fatou (pulling on the initial time just keeps the manœuvre at the end of the flight plan, but does not cause a crash). What is the exact commit number you used? Normally this is given in the INFO log (it comes from version.hpp, generated by generate_version_translation_unit), but yours somehow seems to be missing that information, and to have a nonsensical commit date as well:
|
I downloaded the version in release page, checked that all google dependencies are up to date, linked ksp's dll files in plugin adapter and simply clicked build. I noticed there were errors while compiling, maybe it's a problem with my visual studio or that my computer using a non-English language? Since I've noticed that before ui overhaul in fano, Principia built on my computer's version information in main panel was in garbled Chinese, and after fano it just simply doesn't show up. |
I managed to reproduce the problem and I have a journal. |
We have updated Fatou. Thanks a lot for finding and reporting this before the release was out, it would have been embarrassing... |
I misclicked the place indicated in the screenshot when there's a short flight plan, and the game just crashed. Guess it's caused by manoeuver node moving beyond flight plan limit?
It's reproducedable by me, I clicked there again and it generated identical error message.
The text was updated successfully, but these errors were encountered: