Horizon206

Reported Version: v0.2.0 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 | CPU: Intel i5-8400 | GPU: GTX 1050 Ti | RAM: 16GB As seen in the video attached below, the kerbal gets flung outwards once they run/jump into the lower part of the LT-2 "Wombat" landing legs while landed on Moho. The landing legs in question were all properly extended, had Auto Friction Control enabled, and Auto Suspension disabled (the Spring and Damper Strengths were set to 1.55 and 2.00 respectively). On flatter terrain the kerbals can easily be flung a few dozen meters away from the craft, but the velocity at which they are flung isn't constant. This bug persists through quicksave+quickload, although I have not tried it on other crafts nor on other landing legs. Included Attachments: 2024-01-19-05PM.mp4

Reported Version: v0.2.0 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 | CPU: Intel i5-8400 | GPU: GTX 1050 Ti | RAM: 16GB When I re-entered Kerbin at a very high speed (I've tested 9.6-7 km/s at various periapsis altitudes), my HS-I Deluxe heat shield almost immediately melts (no big surprise there), and then my craft then seems to stop producing any drag, and the re-entry effects & heating stop functioning properly on most parts, although the re-entry sound effects persist. When re-entry heating is turned off, the capsule re-enters fine, so I suspect that this has something to do with the HS-I Deluxe heat shield getting destroyed and then the parts still thinking that they are connected to the heat shield. This bug persists even if I reload using the quicksave that I linked in this bug report. However, if I reload from another quicksave that was taken later on (where the re-entry capsule had already separated from the upper stage), the heating works as expected. On top of the buggy quicksave, I've also linked the file of the craft used and a video of the buggy quicksave with heating turned on, the buggy quicksave with the heating turned off, and the non-buggy quicksave (with heating turned on). Included Attachments: Buggyre-entry.mp4 (bug happens starting 1:35) Kerplorer3.json quicksave_140.json

Reported Version: v0.1.5 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 | CPU: Intel i5-8400 | GPU: NVIDIA GTX 1050 Ti | RAM: 16 GB Severity: Low Frequency: High Relevant graphical info: Three monitors, game resolution set at 1920x1080 with V-Sync turned off. Upon starting the game, the window mode of the game (for a lack of a better name, the option that is either Fullscreen, Borderless, or Windowed) is often different upon relaunching the game compared the window mode that the previous instance of the game was on. While I am not 100% sure what the cause is, I am pretty certain that it has to do with both the window mode of the game's previous instance and the way that you closed that previous instance of the game. On top of this, I also see that those two aforementioned factors also determine what monitor my game appears on upon launching it; sometimes the game only launches on the leftern-most monitor as opposed to the central monitor, which is my primary monitor that I always play the game on and also where the launcher appears. While I have already filed a separate bug report on this, I only looked at the closure methods in that bug report, but it appears that the game's window mode also has a role in this, so I decided to track that as well while doing this bug report. Below is a chart of the combinations of all the factors and the reproducible results of each combination. Keep in mind that the ones with an asterisk ( * ) proceed to convert to Fullscreen after the startup credits fade away. The monitor that the game appeared in is located in brackets for each combination; the game's previous instance was always on the central monitor. "Exit" option in the main menu "Close Game" option in the game's escape menu "Close Window" option when right-clicking the game's icon in the taskbar Termination in the Task Manager Fullscreen Borderless* (center) Borderless* (center) Windowed* (left) Windowed* (left) Borderless Borderless* (center) Borderless* (center) Borderless* (left) Borderless* (left) Windowed Windowed (center) Windowed (center) Windowed (center) Windowed (center) Windowed (Minimized) N/A N/A Windowed (left) Windowed (left) When the game is on Fullscreen or Borderless and is closed via the Taskbar & Task Manager, the game is is minimized before closure in order to access the Taskbar / Task Manager. Because of this, I hypothesize that when the game is closed while minimized, it defaults to starting on the left monitor. Otherwise, it will start on the monitor that it was last played on. As for the window mode issue, it seems that Windowed works as intentional, but upon relaunch, Borderless turns into Fullscreen after the startup credits and Fullscreen relaunches as either Borderless or Windowed (probably depending on if the previous instance was minimized when closing) and turning into Fullscreen only after the startup credits. And again, this is all reproducible on my computer/setup, but I'm not sure if this issue is reproducible for other people. I probably rambled here for way too long, but hopefully this all helps!

Reported Version: v0.1.5 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 | CPU: Intel i5-8400 | GPU: NVIDIA GTX 1050 Ti | RAM: 16 GB When starting up the game in a setup consisting of three monitors, despite the launcher being in the central monitor (which is monitor number 2 in the display settings and is set as the primary monitor), the game launches on the left monitor (which is monitor number 3 in the display settings). This can be fixed by changing the game to "Windowed" mode, dragging the window to the central monitor, and then switching the game back to "Borderless" or "Windowed". Upon relaunching the game, the game only appears on the central monitor again if the game was previously exited via the in-game "Exit" option on the main menu or via the "Quit Game" option in the game's escape menu. However, if the game was closed via the "Close window" button accessed by right-clicking the game's icon on the taskbar (which is often how I personally exit from fullscreen games) or via termination in the task manager, the game will once again appear on the left monitor upon relaunch. Edit: While writing this bug report, which covers a different but similar issue, I realized that I had only tested this bug in the "Borderless" optioning the graphics settings. Upon looking a little more into it, I found out that this bug probably has to do with the fact that the game window is minimized while the game is being closed.

I experienced this too, for me it happened when my game crashed upon launching the craft, then it was stuck in the ground upon reloading the game. My encounter of the bug happened in a different way, but it sounds to me like the same bug.

I have 2 questions about the challenge: 1. Are QoL mods like Kerbal Engineer Redux and Editor Extensions Redux allowed? 2. Are there any limitation reguarding part offsetting / clipping?