Quadnick

I uploaded it to utoob

Thank you. I have more to report on this problem that hasn't been mentioned yet. When I reloaded my save to try again, something very strange happened during the process. The other ship started spinning again, so I switched to it to enable SAS. After doing so, I switched to map view and noticed the other ship's orbit was rapidly increasing. It would have gone indefinitely if I did not switch back to it. I have video of this, but don't see a way to add it. Can videos only be added when creating a bug report post?

Reported Version: v0.2.0 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 | CPU: Intel i7-10700 | GPU: NVIDIA 2080 Super Mobile | RAM: 32 GB DDR4 This is the second time I've done a rendezvous, and the second time the ship I'm meeting up with has its SAS disabled once I get near. It then begins to spin wildly and ruins the encounter. In the video attached, you can see the moment at ~0.07 when the other ship loses SAS and begins to spin. There are two other points of irritation in this clip that could be their own reports, but I will include them here anyway. One is that it is much too difficult to switch between ships on the map screen when they are near each other. At 0:36, the ship I'm trying to click on is called Monument Molester, and you can see that the UI shows that that is the vessel I have my mouse on. But yet when I click on it in order to control it, the ship that actually gets selected is the one I'm already controlling. This is why I say "please" at that part of the video. Time is an issue, but yet I'm having to struggle with the UI to click on the correct vessel. The other annoyance is with the camera. If I toggle free camera at any point, it then begins to toggle on by itself at random times. Even after I've pressed the "home" key to reset my camera. It happens more than once in this video, but you can see an example of at 1:01 when I switch back to the smaller ship. I'm just stuck looking all around until I press "home" again to reset it. It will happen again after that, but the rest was cut out of the video for length and size purposes. Included Attachments: KSPRendezvousRetardation.mp4 .ipsImage { width: 900px !important; }

Thanks. I searched before posting, but "fairing" was not a keyword I thought to look for. I should also add that it seems loading an autosave is the only way I've found to fix this. Loading one of my own saves doesn't do it.

I came here to report the same issue.

Reported Version: v0.2.0 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 | CPU: Intel i7-10700 | GPU: NVIDIA 2080 Super Mobile | RAM: 32 GB DDR4 I was in the Tracking Station, deleting debris to free up my frame rate, when I clicked on some debris that was reported to be close to the ground. So instead of deleting it, I wanted to wait and see it crash and disappear from the list. But as I watched, I noticed that the reported altitude kept fluctuating; reducing and gaining hundreds of meters of height, till it eventually went into the negatives. I also noticed that the debris was reported to be in orbit, even though it was said to be less than 1000 meters from the surface, and had a velocity of 0 m/s. I'm about 90% sure the debris was the small solid fuel boosters I used to get me off the ground. There was 8 pieces, 3 of which were deleted before the video starts, and that corresponds with the amount of boosters used. I used that many boosters, and even more stages, because the Dv calculator told me I needed over 10k for a round trip to the Mun. Which I found out later was way off. But that's for a different bug report. Both video and craft .json are attached. Included Attachments: KSPInaccurateDebrisData.mp4 PenetratetheMun.json

Reported Version: v0.2.0 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 | CPU: Intel i7-10700 | GPU: NVIDIA 2080 Super Mobile | RAM: 32 GB DDR4 Sometimes when I load or reload my save, I get a bunch of floating panels coming from every decoupler on my craft. I'd mark it as a low priority, since the problem was just fixed by loading my most recent autosave. Included Attachments: .ipsImage { width: 900px !important; }