QwertyHpp

Reported Version: v0.1.4 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 11 | CPU: Intel i9-9750H | GPU: RTX3060 | RAM: 32GB Found a possible bug where if the brakes were enabled before a Kerbal enters the vessel, they are disabled after they've entered (see video). Also tested with a capsule & a wheel on Kerbin (see images) Included Attachments: images.zip KerbalSpaceProgram22023-09-0122-28-55.mp4 brakes.json

I think I came across this one too - it seemed like instead of showing a warning if your fairing was clipping another part like it used too - it just removes the sections of the fairing that are clipping with other parts instead

Yeah I think my previous install after the update was a little corrupt. They are bigger now after reinstalling

Yup definitely the most recent. After posting this report I did come across a bunch of other issues - so uninstalled, rebooted and reinstalled which did fix most issues - however, this one still remains. Seems to be focusing on the structural part behind the button (got another video that shows this more clearly just can't add to reply)

This is an issue I've had too since at least 1.3: (Happens any time a vessel is reloaded) Potentially an issue with Intel iX-9750H CPU's? As this is a very persistent issue that I haven't seen reported much anywhere else

Reported Version: v0.1.4 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 11 | CPU: Intel i9-9750H | GPU: RTX3060 | RAM: 32GB Often when trying to click on fairing buttons (view/edit) they will go away if you move you mouse too far away (while still hovering over them). Video: video-Copy.mp4 Craft File: Fairings.json

Huh weird I thought I did add one when I made the report... Whats the best way to provide it btw? Don't see any option to embed a file in this reply/when editing the original report

There were a couple of quick-save reloads, never went back to the VAB or KSC though

Thanks for the tips! Looking at it now the image & description probably wasn't too clear but this was from a single play-through from launch headed to Moho, and instead of touching down the craft just kept going through the surface

Reported Version: v0.1.3.2 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 11 | CPU: Intel i9-9750H | GPU: RTX3060 | RAM: 32GB The edge of the crater (which didn't have a collider at the bottom) has a wavy pattern to it. Might just be a part of the geology of Moho, but logging it just in case - appears too regular. Save File: autosave_1.json Screenshot From Save:

Reported Version: v0.1.3.2 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 11 | CPU: Intel i9-9750H | GPU: RTX3060 | RAM: 32GB Fell through a crater, see image: Probably a duplicate Included Attachments:

Reported Version: v0.1.3.2 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 11 | CPU: Intel i9-9750H | GPU: RTX3060 | RAM: 32GB Occasionally after returning to Kerbin from (at least) Dres, the parachute remains deployed and the vessel cannot be recovered. Have to take one of the Kerbals EVA to get rid of it and recover the vessel. Included Attachments:

Reported Version: v0.1.3.2 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 11 | CPU: Intel i9-9750H | GPU: RTX3060 | RAM: 32GB Sent a couple capsules into LKO, one after the other. After returning to the first launched vessel from switching away to launch the second one, the engine plate fairings that had been decoupled with the decoupler were visible again (see screenshot). Video Evidence: KerbalSpaceProgram22023-08-3109-22-29-Copy.mp4 Save File: autosave_2.json Screenshot:

^

Yup same issue here - near impossible to rendezvous