Search the Community

Reported Version: v0.1.5 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 | CPU: Ryzen 5 2600 | GPU: AMD Radeon RX6650xt | RAM: 32gb Navball maintains the pointing direction of the last craft after detaching from it. In the screenshot attached below the navball is pointed at the horizon, but the actual module being controlled is pointing downward. This can be solved by opening the parts manager and changing control point.

Reported Version: v0.1.4 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 11 | CPU: AMD Ryzen 5 7600X | GPU: Nvidia RTX 4070 | RAM: 32 GB DDR5 The bug has been present since the game launched. Sometimes I have to press 2-3 times on the top-right "x" button of the Parts Manager to close the window. It's not a major bug, but it happens frequently and it's annoying. Thanks!

Reported Version: v0.1.5 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 | CPU: AMD Ryzen 3200G | GPU: GTX 1050 ti | RAM: 16GB Revert to VAB and Revert to Launch buttons are for some reason enabled in the training center Included Attachments:

Reported Version: v0.1.5 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 11 Home 22H2 22621.2428 | CPU: Intel(R) Core(TM) i5-10400 CPU @ 2.90GHz 2.90 GHz | GPU: Nvidia GTX 1660 Super | RAM: 16 GB I was about to launch a rocket, when I realized I had accidentally removed the stabilizers. I had sent the image of Ferdock Kerman to the Intercept Games KSP2 General, went to the launchpad, realized the stabilizers came off, reverted to VAB, and decided to send a picture of the crew to the KSP2 general chat. I then noticed that the shading on Ferdock was different, and the shading and skin tone on Tim and Mark J also appeared to be different, as well as some kerbals in the KSC. (I.e Tim looked paler and mark more vibrant, as well as the shading was a bit different) Considering how minor this bug is, I fully expect it to not be fixed for a while since you have more important things to work on, I just kinda noticed it after reverting a flight Included Attachments:

Reported Version: v0.1.4 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 11 | CPU: AMD Ryzen 5 7600X | GPU: Nvidia RTX 4070 | RAM: 32 GB DDR5 As you can see in the image, the text for "remove flag" action is not aligned in the box. Included Attachments:

Reported Version: v0.1.5 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 11 (latest) | CPU: I9 CPU Intel | GPU: 3060 6 gb (laptop) | RAM: 16 GB Title explains the bug, here is a video, too. It does make a noise so I am assuming this is meant to happen. This is so obscure but I hope it helps for the time when interstellar comes around. Included Attachments: KerbalSpaceProgram22023-10-2717-45-00.mp4

Reported Version: v0.1.4 (latest) | Mods: none | Can replicate without mods? Yes OS: Linux Ubuntu 20.04.6 | CPU: AMD Ryzen 5 3400G | GPU: NVIDIA GeForce GTX 1080 Ti | RAM: 16GB System Specs: Description: The extra info provided for parts seems to be displaying incorrectly. The size of the text seems extremely large causing nearly all of the text to be rendered off screen. Often the text area where the text would get displayed is blank as well. Included Attachments:

Reported Version: v0.1.5 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 | CPU: Ryzen 5 3600 | GPU: rtx 3060ti | RAM: 32mb Severity: med Frequency: high Description: If I press "." to speed up time twice, and then "," to slow down twice, it all runs as expected. Now for the bug: press "." once, and use the mouse to speed up time once more. When pressing "," to slow down, the first press works, and on the second it goes to "Pause" instead. .ipsImage { width: 900px !important; }

Reported Version: v0.1.5 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 11 | CPU: I9 CPU Intel | GPU: 3060 6 gb (laptop) | RAM: 16 GB Video explains quite well but the ^ arrow does not show a window is open in the PAM if a part is opened via right click (part via flight view). But the options for the part are open. When clicking on the part in the PAM the arrow performs normally. I do this to two different parts to show it happens to everything. Included Attachments: KerbalSpaceProgram22023-10-2616-11-55.mp4

Reported Version: v0.1.5 (latest) | Mods: none | Can replicate without mods? Yes OS: windows 10 | CPU: amd ryzen 3200g | GPU: gtx 1050 ti | RAM: 16gb cant launch pls help lemme launch Included Attachments: KerbalSpaceProgram22023_10.25-20_44_06_02.mp4 .ipsImage { width: 900px !important; }

Reported Version: v0.1.5 (latest) | Mods: none | Can replicate without mods? Yes OS: NA | CPU: NA | GPU: NA | RAM: NA Icon for part groups in the action group manager all show the command pod icon, instead of their actual respective icon. This was an issue for the parts manager, but it was fixed in patch 4, so it seems like the action group manager got forgotten lol. Similarly, opening the action group manager (and resource manager in flight) still exhibit the huge lag spike when opening them that was fixed for the parts manager. Seems like these are all issues that were already solved for the parts manager, but the fixes were never transferred to the other similar systems. Included Attachments: .ipsImage { width: 900px !important; }

Reported Version: v0.1.4.1 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 11 | CPU: I9 CPU Intel | GPU: 3060 6 gb (laptop) | RAM: 16 GB When on EVA the navball changes its color pallet to "nightmode"/"space" when even on an atmospheric body like kerbin. These images were taken on Kerbin and to note is my UI is scaled at 95%. I am pretty sure this is a bug but correct me if I am wrong. Images show the UI when in a craft at the same location as when EVA'ing as a kerbal. Plane Correctly Showing Navball Set to Surface: Kerbal Incorrectly showing Navball Set to Orbit Instead of Surface: .ipsImage { width: 900px !important; }

Reported Version: v0.1.4.1 (latest) | Mods: none | Can replicate without mods? Yes OS: Microsoft Windows 11 Pro 10.0.22621 64-Bit | CPU: AMD Ryzen 9 3900X 12-Core Processor (24) | GPU: NVIDIA GeForce RTX 3090 (24340MB) | RAM: 65459 When collapsed, right mouse button drag in the area where the expanded staging UI would be results in camera not reacting, as if a "hit box" for the expanded UI is still there and preventing the camera from performing as it should. See video for more detail. Included Attachments: BUG133.mp4 BUG133-StagingUIblockscamerarotation_logs.zip

Reported Version: v0.1.4.1 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 Pro | CPU: AMD Ryzen 7 3700X 8-Core Processor | GPU: NVIDIA GeForce RTX 2060 | RAM: 32 gig Severity: (med/low). low because it doesn't impact gameplay, however could be medium, or high if issue is causing added memory load Frequency: high. reproducible v0.1.4.0.26521 While testing to see at what altitude debris/spacecraft auto deletes, I found an interesting bug. If you set as target a piece of debris before it deletes, and you set your SAS to point at it, it will remain floating in space at the distance and attitude at which it dissappeared. In the picture provided, the target indicator did not move at all in reference to the current space craft. To recreate the bug: Launch a spacecraft with discardable parts that you can release into a decaying orbit in atmosphere. Set one of those parts as target wait for the target to pass 55km in altitudde and be deleted watch indicator remain on targets last position in reference to the spacecraft I'm unsure if this object is remaining persistent in the game, or if it is actually being deleted, but a reload does remove said target (though i'm not sure if it is actually removed from the game) Included Attachments:

Reported Version: v0.1.4.1 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 | CPU: i9 9900K | GPU: 3070ti | RAM: 32GB Following Shows the issue when it's bugged (0.1.4.1) and when it isn't (0.1.2.0): Following shows it bugged but slower to give a better idea of what is happening: Credit: Thanks to Discord chat for helping me get this bug report to a point of being more simply explained.

Reported Version: v0.1.4.1 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 | CPU: i9 9900K | GPU: 3070ti | RAM: 32 GB Video Evidence: https://www.youtube.com/watch?v=Vc5sAOnTpt8 (30 Seconds) Steps to Replicate: Load TargetSpeedBasedOnRotation.json Load again to counter the spinning bug Undock one of the crafts. Target the other crafts docking port Turn off SAS Start rotating the craft around using A or D Results: Target Speed increases to around 12m/s before settling around that point. Speed drops in an oscillating way when releasing the A/D keys.

Reported Version: v0.1.4 (latest) | Mods: none | Can replicate without mods? Yes OS: Win10-20H2 | CPU: Ryzen 5800X | GPU: RTX 3080Ti | RAM: 32GB Started a fresh save on Patch 4, sent a K2 Stock rocket to be captured around the Mun. Got some odd UI spam for the camera mode, I don't think I saw this happening during Patch 3 Included Attachments:

Reported Version: v0.1.3 (latest) | Mods: none | Can replicate without mods? Yes OS: Kubuntu (via Proton Experimental, up to date at time of post) | CPU: Ryzen 5 3600 | GPU: Radeon RX 5700 | RAM: 32 GB Title: When in the VAB, the camera can be zoomed "in" past the orbit focus point. Specs: Severity: Low Frequency: Certain Description: Enter the VAB. Use the scroll wheel to zoom in. Continue to use the scroll wheel to zoom in, passing the vessel. You can go all the way to the wall on the far side of the VAB. You can even go past the wall of the VAB, but it's just a white void so I don't see much point in including a screenshot of that. The camera resets to a vaguely reasonable minimum distance as soon as you use RMB or MMB to orbit it. If you zoom past the wall and into the white void, you cannot zoom back out of it; the only way to return the camera to usability in this case is by orbiting it. Included Attachments:

Reported Version: v0.1.4 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 | CPU: AMD Ryzen 3200g | GPU: GTX 1050 ti | RAM: 16gb 3200mhz When i loaded the stock k-1 rocket onto the launch pad, it didnt show the staging sequence, but when i made my own rocket the staging did appear Included Attachments:

Reported Version: v0.1.2 (latest) | Mods: none | Can replicate without mods? Yes OS: PS1 Built In | CPU: LSI CoreWare CW33300-based core | GPU: 32-bit Sony GPU (designed by Toshiba) | RAM: 2mb A Picture Really is Worth a Thousand Words. Things to Note: When I select the menu options using the D Pad on my controller the text highlights and the detail slightly improves Background Highlight Text is a bright CYAN which is hard on the eyes. (Using Blue Filtered glasses to counter to a good degree so it will be ok until 0.1.3.0 when this is fixed) FPS overlay is completely unreadable and doesn't appear to be changing. Craft and Planet animation is changing once per 10 minutes. Oh and I saw the fps change at the same time. Thats a relief. I thought KSP2 had crashed which would have meant another bug report. Took 3 hours to get to the main menu. Luckily I also bought a copy of KSP2 for my Nintendo 64 so I did testing on that in the mean time. (Clearer text by the way) Included Attachments:

Reported Version: v0.1.4 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 11 | CPU: Intel i5 | GPU: AMD 6700XT | RAM: 16GB Hello, I have a five-year old daughter who loves to play KSP1. But, she really struggles with KSP2. Her small hands have very shaky mouse control. I have the mouse DPI turned way down, so she needs to move her hand a looong way physically to cross the screen, but even so, the VAB is basically unusable for her. The problem is that it seems to click on a part, you have to do a mouse-down and mouse-up without moving the mouse at all. For some people (young children, maybe others) that isn't possible. If you mouse-down, move a millimeter, then mouse-up, it's treated as a failed drag-and-drop. What's doubly-insulting is that it doesn't even pick the part up. She'll try ten times just to pick up a part from the menu on the left, but each time she tries to click, it's just treated as if she dropped the part back on the menu, and it doesn't get picked up as a result. So frustrating for her. Similarly, placing parts on the center of the screen is near-impossible, due to the same issue. Please fix it so that the VAB can be used by my children.

Reported Version: v0.1.3 (latest) | Mods: none | Can replicate without mods? Yes OS: Linux Ubuntu 20.04.6 | CPU: AMD Ryzen 5 3400G | GPU: NVIDIA GeForce GTX 1080 Ti | RAM: 16GB [Anth12 Edit: Adding Save Files + Video for 0.1.3.2 Repo and 0.1.4.0 Fix Confirmation] --------------------------------------------------------------- Happens When Undocking From a Craft and then Re-targetting. Video Evidence: 0.1.3.2 Bug Replication: https://youtu.be/XPd0cSTucoI 0.1.4.0 Working as intended: https://youtu.be/pUm5xS7mnO8 Steps to Replicate in 0.1.3.2: Load quicksave_6.json Undock the craft with the pod Target the craft undocked from. --------------------------------------------------------------- Specs: (Obtained from Steam via Help > System Information) Severity: Med (This feels like it's on the high end of medium. I can see it causing docking to be difficult if not impossible, as this information can be critical to performing docking maneuvers.) Frequency: High (This has happened every time I've performed docking maneuvers since version 0.1.3 came out. It wasn't happening prior.) Description: The velocity display to the left of the Navball does not appear to display the speed relative to the target when target velocity is selected. In the screenshot below I parked the lower vehicle about 3 meters away from the command pod at the top of the picture. To be sure I was right, I left them about this far apart for at least a couple of minutes. The display continued to show the command pod being 3 meters away. This tells me the velocity relative to the target should be close to zero. But as you can see in the screenshot it's showing 5484m/s. Which is close to what my orbital and surface velocities were at the time.

Nvidia: Reported Version: v0.1.4 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 | CPU: i9 9900K | GPU: 3070ti | RAM: 32GB AMD: Reported Version: v0.1.4 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 | CPU: Intel i7 4770K | GPU: Radeon RX 6600 | RAM: 24GB Navball Comparisons: Please left click on the image to see to see the difference more clearly. Original Screenshots: IngameScreenshots.zip

Reported Version: v0.1.4 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 | CPU: Intel i9 9900K | GPU: Nvidia 3070ti | RAM: 32GB Video Evidence While Moving PAM: https://youtu.be/LrEamrI8nKU Screenshot: Steps to Replicate: In the VAB grab a part that has a slider Right click the part with slider Move the Parts Manager around the screen until the distortion shows Move Slider to show distortion changing.

Reported Version: v0.1.4 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 | CPU: i9 9900K | GPU: 3070ti | RAM: 32GB Steps to Replicate: Load quicksave_58.json Press F2 Change Crafts (press [ or double click) Video Evidence: