Anth

@Jeq This is the other one I changed. Thanks again for posting these bug reports

@Jeq You posted this twice by the looks of it. I hope you don't mind that I changed the titles to make one for the parachutes and one for the surviving hitting the water. 1 bug per report makes it a lot easier to search for separate issues. I also changed the videos so they start when the problem occurs.

Thanks for the information.

I appreciate your efforts but there's no need. I had this happen in the last 10 hours or so and did some testing. Looks like the other craft has to have its reaction wheels enabled and it needs to be unmanned, which both yours and @Scarecrow71's appear to have been. Thanks to you both for contributing to this. I will do more testing to make sure.

Maybe that is part of the issue. Thanks for the information. Maybe the problem is more consistently happening using a higher resolution and a lower resolution is less consistently happening.

Thanks for the information. From what you have said before, you have a Ryzen 5 3600 + RX6600, can you tell me what your resolution is?

@Vortygont Merged with this one.

@Bhenoa Merged your feedback into this one. Please remember in future there is a place for feedback and a place for bug reports. Feedback goes: https://forum.kerbalspaceprogram.com/forum/120-ksp2-suggestions-and-development-discussion Also note there is a work around that might work: Don't have KSP2 running Enter the following into Windows Explorer: %userprofile%\AppData\LocalLow\Intercept Games\Kerbal Space Program 2\Global Open Settings.json From the following picture change the highlighted line's numbers from my resolution to your resolution and then save, then start KSP2

@Joker58th I merged your bug report with this one.

@PicoSpace Its caused by the orbital decay fix in certain circumstances.

@BechMeister Thanks for doing this.

@NaughtyMonster Thanks. Added your craft file to the bug report directly. Definitely some weirdness going on there.

@NaughtyMonster Can you supply the craft file? If so can you please upload it creating a new bug report, add my name to the title and have a link to this bug report within it. The save files show the problem but there's no way to know why your problem is occurring without the craft file.

I have no idea how I missed your reply. I am so sorry about that. I fluked finding your reply while looking for another bug. All I could see was that the craft isn't displaying its trajectory because it thinks its landed which is a known bug:

@DibzNr Merged your bug report with this one.

@mattihase Merged yours with this one. I hope you don't mind me changing your save file to just the json file.

@dansiegel30 Embedded your video. (moved your other bug report with the same issue to the archive.

@dansiegel30 Moving to archive. Your newer bug report of this issue has a video.

This is fixed.

Fixed in 0.1.5.0

Weird. Inconsistent results is something I wouldn't have expected from this bug.

The idea of the grumble being a root part scares me

@NaughtyMonster and @The Aziz Do you have more information on how you assembled the crafts to start with? They were most likely bugged from a specific action. One action I have seen that could cause that is changing the root part to a surface attached part.

@Filed.Teeth Your computer should run KSP2 fine. Can you try the following: Use steam to verify the files Back up your game save files which are located: %userprofile%\AppData\LocalLow\Intercept Games\Kerbal Space Program 2\Saves\SinglePlayer Delete the Kerbal Space Program 2 folder in the Intercept Games Appdata folder located here: %userprofile%\AppData\LocalLow\Intercept Games\ Then give it another try. I can't promise anything but I hope it helps.

@ocelottagames I moved your system specs to the top and turned them into spoilers, plus I did a few changes to the formatting.