king_shredder

I did some more testing using the F8 surface teleport feature and I have visited every body in the kerbolar system (Except Laythe. Too many oceans) and applied non-physical time warp on the surfaces. This bug also happens on Moho Gilly Mun Minmus Ike (Got teleported *just* below the surface. There is really no handler for being out of bounds) Every time, the vessel is in the "In Orbit around X" while falling to the core. After Ike, the bug suddenly stopped happening. Even on bodies where it previously did occur. Then I switched to a vessel on Eeloo again, and the bug is still there. Very weird. I would conclude that the bug happens more reliably when one switches to a another vessel. The Vessel one currently focuses on can fix itself *eventually*.

Oh, absolutely Especially if I would tunnel through Kerbins atmosphere in a single time step!

Reported Version: v0.2.1 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 | CPU: Intel Core i5 | GPU: Nvidia GeForce GTX 1070 | RAM: 16GB Severity: low Frequency: med Description: Occasionally, when a time warp is aborted, kerbals in a vessel start panicing (as much as they can) and sometimes do not even calm down after a while. I would guess that an abrupt stop of the time warp is sometimes wrongly interpreted as an extremely high-g event.

Thank you for combining these two reports. They may be related. Btw: I tried switching vessels some more, and had not the same happen with other planets like Duna or Jool. I can provide the save file if needed, as I am going to wait for the next update anyway.

The same happes on Dres for me as well. I have not tested other planets and moons

Reported Version: v0.2.1 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 | CPU: Intel Core i5 | GPU: Nvidia GeForce GTX 1070 | RAM: 16GB Severity: high Frequency: ? Description: I switched from a vessel in map view back to the KSC. The runways and a large part of the KSC is covered by terrain. See video. Note: This happened after I was looking at eve. Eves atmosphere is following my vessel in map view. See screen shot. I have reported this bug separately. Included Attachments: bandicam2024-01-3022-07-51-765.mp4

Reported Version: v0.2.1 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 | CPU: Intel Core i5 | GPU: Nvidia GeForce GTX 1070 | RAM: 16GB Severity: high Frequency: high Description: To recreate: Have a rover on the surface of eeloo. Time warp. Stop time warp. The rover is now inside eeloo on its way to Eeloo's core. See attached video. Also: Why is Valentina inside the vessel? I did not send her to Eeloo. A kill sphere inside the planet seems to be missing, but perhaps I am teleported below it. Included Attachments: bandicam2024-01-3021-56-12-489.mp4

Reported Version: v0.2.1 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 | CPU: Intel Core i5 | GPU: Nvidia GeForce GTX 1070 | RAM: 16GB I had a vessel in orbit around eve. Then I switched to a vessel in tylo orbit.... The game first displayed the wrong (i.e. previous vessel) in Tylo orbit before it eventually loaded the correct vessel. Creepy side-effect: Now eve follows me around where ever I go, and the Sun appear unusually dark in map view. See image. I generally noticed that swicthing between vessels causes major visual problems. Included Attachments:

Reported Version: v0.2.0 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 | CPU: Intel Core i5 | GPU: Nvidia GeForce GTX 1070 | RAM: 16GB I noticed that the game does not unload the scene when switching between flying/tracking station/mission control which I think is smart. But: after I landed my rover on a hill on eeloo and switched to R&D after applying brakes (i thought) i could see (Thanks to the buggy menu background) that the rover was rolling away. In fact, It could have crashed and exploded while I was in this menu and be completely unaware of that. I can even rotate the camera with the left mouse button while in the menu! I wonder if the explosion sound would play. I would say this is a bug and that the physics of crafts on planetary surfaces should be frozen while the screen is covered with menus. Concerning the menu background bug: This is probably my own fault to some degree as I set the display resolution manually in a config file, since I am playing on a widescreen monitor and ksp2 only supports a limited number of default resolutions (why? ) Reproduce by: Setting resolution to widescreen by editing C:\Users\THEUSER\AppData\LocalLow\Intercept Games\Kerbal Space Program 2\Global\Settings.json ("ScreenResolution":"3440x1440" in my case) drive a rover across any planet swich directly to R&D menu and scroll all the way to the right: The craft is displayed and camera controls are working, craft may be rolling! Included Attachments: .ipsImage { width: 900px !important; }

Reported Version: v0.2.0 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 | CPU: Intel Core i5 | GPU: Nvidia GeForce GTX 1070 | RAM: 16GB As can be seen in the attached image, the planet renderer can mess up loading of sections of the terrain. This is only noticable at high altitudes. Does the renderer somehow think the rocket is at ground level and these sections can remain unloaded? The glitch only affects far away terrain and *eventually* the holes close up partially when the rocket gets near those surface coordinates. I am unable to reliably reproduce this bug. Included Attachments:

I might add that this may not just be a visual glitch. I wondered yesterday why my engines won't start even though I have more than enough air intakes. Still the engine choked each time, but apart from that nothing else was particularly weird. When I switched to map view and looked at kerbin the atmosphere was missing... After a quicksave in orbit it was back again. I don't think this was a coincidence, but maybe there is a possibility that I made some other mistake when building the craft, I can't rule that out completely. In some other rare cases the atmosphere renders for the reentry, but there is no drag. This is fixed by quickloading enough times. Of course, this may be a different issue

Reported Version: v0.2.0 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 | CPU: Intel core i5 | GPU: Nvidia GeForce GTX 1070 | RAM: 16GB In an orbit around planets/moons without an atmosphere, the terrain (craters) is illuminated well before the sun actually rises. Geometrically this should be impossible. When a planet has an atmoshphere this is probably just not as noticeable I guess. Could this have to do with the fact that terrain above sea level is ignored for this calculation? Just a very naive guess Included Attachments:

Reported Version: v0.2.0 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 | CPU: Intel i5 | GPU: Nvidia GeForce GTX 1070 | RAM: 16GB There is a whole (extensive) and dense forest under the map at the KSC. Also, the Framerate suffers immensely when going near those hills next to the runway, but if one considers the screenshot I took it is not that surprising that the framerate goes down Included Attachments: