supertiefighter

This bug does not seem to happen when cloud quality is set to low

Reported Version: v0.1.5 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 Home 64-bit | CPU: AMD Ryzen 5 3600 6-Core Processor | GPU: Radeon RX 570 Series | RAM: 16GB When passing through Kerbin's cloud layer (going up or down), parts of the screen turn black. The black pixels stay black until reaching a certain altitude (about 12000m) or loading a quicksave. They persist when returning to KSC, entering the tracking station or VAB (although the pixels temporarily return to normal in those buildings), and when launching a new rocket. Included Attachments: 2023-10-2520-58-02.mkv .ipsImage { width: 900px !important; }

Reported Version: v0.1.3 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 Home 64-bit (10.0, Build 19045) | CPU: AMD Ryzen 5 3600 6-Core Processor | GPU: Radeon RX 570 Series | RAM: 16GB Severity: Low - Quickloading seems to fix this issue in most cases Frequency: High - I have been able to reproduce this issue consistently Description: After reverting to VAB during flight and launching again, my framerate drops significantly when a lot of terrain is visible. Looking upwards so that no terrain is on screen increases the framerate slightly, but not by much. The framerate is only lower than normal when above large land masses, not when above oceans. I have only been able to test on and around Kerbin, so I do not know if this affects other celestial bodies. Included Attachments: LKOafterreverttoVAB.mp4 Player-prev.log

After loading a quicksave near Dres, the stars disappeared and Dres appeared to be transitioning between two detail levels, but one of the models was missing. Turning the camera caused the sky to change colour, seemingly applying one pixel of the normal skybox to the entire sky. The sky returned to normal after loading the previous autosave, but subsequent quicksaves whilst still near Dres caused the issue to occur again. After leaving Dres's sphere of influence and loading a quicksave, the bug stopped entirely, and I was unable to trigger it again, even when loading the same saves that it had occurred for previously. Log file: https://www.mediafire.com/file/94viuxahfph256c/Player.log/file Specs: Windows 10 22H2 AMD Ryzen 5 3600 6-Core Processor 16GB RAM Radeon RX 570 Series Images:

After docking two ships together and deactivating one of the engines, moving the deactivated engine in the staging stack duplicated it. Quicksaves made after this cannot be loaded, loading stops at 'Creating Vessel' Video: Log: https://www.mediafire.com/file/c4q7nibv6zosw94/Player-prev.log/file Broken save: https://www.mediafire.com/file/r8dxhg6wn6xfnme/quicksave_38.json/file KSP2 version: 0.1.2.0.22258 OS: Windows 10 22H2 CPU: AMD Ryzen 5 3600 6-Core Processor 3.60 GHz GPU: Radeon RX 570 Series RAM: 16GB

Many of the lights and windows around KSC are pink Graphics settings: PC specs: CPU: AMD Ryzen 5 3600 6-Core RAM: 16GB GPU: Radeon RX 570 Series

After going EVA on the Mun and getting back in the cockpit, the kerbal portrait was replaced by a grey box. I only had one kerbal on the mission. Edit: The portrait returned to normal after opening the map

I had the same issue on Mun, also after activating timewarp whilst planting a flag. Saving through escape menu and restarting the game fixed it.

I'm excited to actually be able to use ion engines thanks to timewarp under acceleration.