-
Notifications
You must be signed in to change notification settings - Fork 21
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
Jumping to high timewarp levels from off-rails will alter the active vessel's orbital elements #170
Comments
I guess this happened to me too, but not nearly often enough to identify why it was happening. If I were to take a guess, I'd say this might have to do with the One way to verify such a theory in the presence of this bug would be to set Edit : yep, can confirm this is the issue. I can reproduce it consistently by putting a 1500 part vessel in orbit while having the max dt per frame at 0.12, and engaging max timewarp speed. |
Awesome. I'm not too familiar with the Timewarp system but the problem is not limited to "autoWarpTo" - which I think you confirmed? You can also trigger it by clicking the max warp button in the UI. |
Yeah, I wrote that before testing, but this is reproducible no matter the method used to engage timewarp. I need to do some proper debugging, but I suspect this won't be so easy to fix (just like with other similar KSP issues involving update/fixedupdate being wrongly assumed to be in prefect sync). |
…12.5] Fix active vessel orbit moving randomly when engaging timewarp while under heavy CPU load.
Fix included in 1.32.0 |
https://www.reddit.com/r/KerbalSpaceProgram/comments/189fr5b/this_glitch_is_occurring_when_i_try_to_go_to_duna/
I've seen this happen so often that using 5x timewarp first is just muscle memory now. If we could fix this one it would be a huge benefit.
On the other hand, the workaround is not difficult. So either you learn the workaround or you learn to install KSPCF. I think the former is probably easier but it's the principle of the thing...
The text was updated successfully, but these errors were encountered: