Search the Community

After Leaving Mun under "ground view" and switching to "chase" the camera view becomes disconnected and no view will track the craft. The controls do not function properly and the craft spins out of control way off in the distance and there is no way to reset the view - loading a saved game does not fix this Ryzen 9 5800X Crosshair VIIIDH X570X Strix RTX3090OC 32GB(4x8GB) 980Pro 1TB SSD

The Kerbals remain listed as in flight after going EVA at landing. It recovered the ship but there is no way to recover the kerbals that are now stranded there. Ryzen 9 5800X Crosshair VIIIDH X570 Strix RTX3090OC 32GB(4x8GB) 980Pro 1TB SSD

I have a 980 pro, so most of the loading times were pretty fast in the game, but when I tried reverting to VAB from splashdown it just stopped. The progress bar went to around 2/3 and froze for 10+ minutes, after which I killed the process through task manager.

I noticed a few times when Time Warping [was using to do a landing in the day] it would yeet another craft that is in orbit. 1st time it yeeted it up high then forced a collision course with Kerbin. 2nd time it was yeeted into an orbit around Kerbol.

This problem only happens when the game is paused and fixes when going back to 1x time warp

After bailing from a vessel, recovering the kerbal, and reverting to vab soft locks on the confirmation screen but the game doesn't crash.

I left a space plane in a stable Kerbin orbit. Switched to another vessel, switched back, and the Pitch and Yaw controls (roll was normal) on the spaceplane were all inverted. SAS didn’t like that either.

Whenever I time warp or leave and return to a craft all the decouplers have separated and all the parts are floating away.

While trying to set up an encounter with a space station I noticed in map view that the station was not moving through its orbit at all. I switched to the tracking center and it was still not moving despite my other stuff orbiting as you would expect. Switching to the bugged craft resolves the issue and it was gone when I switched away from it to the original ship. I am not quite sure yet how to reproduce this bug consistently

A list of bugs I noted when building and flying around in my first built airliners, jet aircraft. Control Surfaces on Angled Wings rotate off-axis in flight How to reproduce: Attach any Wing to a craft, e.g. HPW-1000 "Evolution" Rotate the wing using the translation tool, for example upwards as seen on this image Launch craft and play with the controls Wings don't change mass when adjusting its size I mean...seriously? This was a feature in KSP 1 with the procedural fairings, so it shouldn't bee to hard to implement to make a wings mass depend on its span, thickness, width etc. How to reproduce: Build any wing and watch the vessels total mass when changing its dimensions Reverse thrust animation is broken when using action groups When Action Group is toggled, the reverse animation of the J-90 "Goliath" Jet engine plays, then goes back to its base state (showing that the engine is not reversing), while the engines deliver reverse thrust. I'd need to check if this happens with the other jet engines too. When using the right-click menu to toggle the reverse thrust, everything works. How to reproduce: Attach J-90 "Goliath" Jet engine to aircraft Assign an action group to the action "Cycle Mode" Launch craft, activate engines, throttle up Enable the assigned action group and watch the animation play, then go backto its first frame Another bug, related to this: While the reverse animation is playing, the thrust produced by the jet engine is not updated. Check right-click menu to see the thrust value.

This happens with every ship I leave in orbit at 1x timewarp, it just spins (and accelerates the spinning) forever. SAS and RCS do nothing.

KSP Version: 0.1.0.0.20892 Unmodded stock steam release Launched via stock launcher Subject: VAB - Orientation change, causes parts mounted on radial attachment points to pivot upon snapping to unrotated parts in other construct built in other orientation. Expected teams required: Gameplay Features: VAB // Orientations Behaviour Expected: When constructing something in horizonal alignment, then attaching a radial attachment point with a Docking port on it, and then rotating that construct into a vertical alignment, before trying to attach it to a vertically aligned secondary ship, with a side mounted docking ring, should connect the two docking rings as expected. Observed: The docking node on the selected (and earlier rotated ship) will pivot 90 degrees out of alignment with the selected ship and prevent the nodes from connecting. Reproduction Recreated in fresh empty campaign, but occurs in all instances. Probability: 100% (10/10 repro's) Steps: Start with a horizontal cockpit (Ref: shipA) and ensure the workspace is in horizontal orientation mode Attach a fuel tank behind it Attach a radial attachment point (Ref: radialA) below the fuel tank Attach a docking port (Ref: dockA) to radialA. Select the cockpit, and rotate the entire construct 90 degrees into a vertical alignment. Change the workspace into vertical orientation mode Place a new fuel tank somewhere as a secondary construct. (Ref: shipB) Attach a radial attachment point (Ref: radialB) to the side of the fuel tank on ShipB. Attach a docking port (Ref: dockB) to radialB. Pick up shipA, and attempt to connect it to shipB by attaching dockA with dockB. ERROR: When dockA snaps to dockB, dockA will pivot 90 degrees into the wrong orientation. Workaround: After the part (dockA) has snapped into the wrong orientation, pick it up (dockA), rotate it into the correct orientation, and reattach it to radialA. Then attempt to connect the two constructs together again and they will snap together as expected. Image/Video: https://imgur.com/a/UnikOQ7 Logfile: https://pastebin.com/aBAz7wrn Probably irrelevant but attached OS details regardless: Operating System: Windows 10, i7-6700k, GTX1070, 32gb Ram

System Info KSP Version: KSP2 Build ID 10624168 Operating System and version: Windows 11 / Version 22H2 CPU and GPU models: AMD 5800X / NVIDIA RTX 3700 / 32GB RAM Mods Installed: None Description of the Bug Expected Behavior: After crashing vehicle, reverting to the VAB or Launch will get rid of the crashed vehicle window. Observed Behavior: After I crashed one of my planes, neither revering to launch or reverting to VAB would get rid of the crashed vehicle state. Instead my vehicle would appear on the runway perfectly intact, then the same crash window would show, and I would lose control of my vehicle because the game thought it had crashed. Being not actually crashed, the plane would slowly roll down the runway as per usual. Steps to Replicate: I reproduced this crashing the same plane again on takeoff after restarting my game. Here is a copy of the workspace: https://drive.google.com/file/d/1CGyZ2T4Y-bNiDsGNJ3czSQR0n01TTkI8/view?usp=share_link Fixes / Workarounds: Restarting the game Recording of behavior: https://imgur.com/a/PMy2c45 This recording shows revert to launch and revert to VAB reproducing this issue

Hej, KSP2 is currently no longer playable for me. I tried reinstalling the game and restarting the campaign. Everything didn't work. I try to explain the problem with screenshots. I see the same picture no matter where. The picture is in the foreground! Solution: Delete the "Intercept Games" folder in the LocalLow folder! Best regards

Every time you quick load, EVA, reboard, switch crafts, etc. an extra game paused/unpaused message will appear. The number of messages seems to correlate with the number of scene changes per play session. For example after doing an EVA on Minmus two scene changes occurred (leaving the craft and reboarding) which lead to three messages appearing.

Here's what it looks like: copying 2 parts rotate once Rotate once more

Version: 0.10.0.20892 OS: Windows 10 CPU: AMD Ryzen 5 3600 GPU: NVIDIA GeForce RTX 3060 Expected Behaviour: I dont know anymore... Observed Behaviour: Controling ship but all I can see is VAB + Nav ball etc. Steps to replicate: Not sure, but i was making ship in VAB, went to name it, ended up on map screen focused on one of my satelites, went to VAB (through menu). Workaround: Press alot of buttons.

Version: 0.10.0.20892 OS: Windows 10 CPU: AMD Ryzen 5 3600 GPU: NVIDIA GeForce RTX 3060 Expected Behaviour: When Delete key is pressed part should be deleted Observed Behaviour: When delete key is pressed part is delted AND messege pops up saying flight mode has changed Steps to replicate: Not entirley sure, but i launched an empty rocket (so couldnt be controled) and then reverted to VAB Workaround: I have no clue but it isnt game breaking so im not fussed.

Keybinds are gone when i restart the game. They Show in the options as if they are still bound but they dont work. happens for me when i bind "full throttle" to "forward thumb mouse button" and "cut throttle" to "backward thumb mouse button" Copied here from the KSP Discord Bug Forum

KSP 2 Version: 0.1.0.0.20892 Operating System and version: Windows 10 CPU and GPU models, any other system information which could be relevant: Intel i7, MSI GeForce RTX 2070 6 gigs VRAM, 32 gigs ram Description of the bug. Expected Behavior: Ability to load crafts, see previously seen crafts, and launch crafts Observed Behavior: Launch button does not work. saved crafts become invisible and inaccessible Steps to Replicate: Launch craft, Fixes / Workarounds: Close and relaunch game A list of ALL mods: N/A Other Notes:

I'm on the first publicly release version of KSP 2, and my game will not let me load a save or enter a new campaign. The game worked relatively well for me for a while, then at some point recently, it will not let me load into a game. I can get to the title screen, try to load into a game, and the game will freeze on pumping sim once. After 15 minutes or so on this screen, my screen will change into this odd black and white screen, and the only user interaction that works is f12 to bring up or hide the aerodynamics overlays. Nothing else works (including esc.). I'm on windows 10, and my computer has an NVDIA GeForce GTX 1660 Ti (graphics card), an Intel Core i5-9400F CPU @ 2.90GHz (processor), and 8 GB of installed RAM. No mods, I haven't found any workarounds that worked for me (though some people had some very creative ones on discord that didn't do the trick for me, like changing OS language to British English and deleting the AppData folder for the game (serious). I have seen other people have this same issue, and for all of them the screen they reached was identical. I have attached an image of it to this post, although it looks slightly brighter than this in person. I believe this is related to the wider issue of people being stuck on pumping sim once, but I don't know for sure how.

Version: 0.1.0.0.20892 System description: OS: Windows 10 (10.0.19045) 64bit CPU: AMD Ryzen 5 2600X Six-Core Processor (12) RAM: 16334 GPU: NVIDIA GeForce GTX 1070 (8081MB) SM: 50 (Direct3D 11.0 [level 11.1]) Description: Expected Behaviour: That the entire manoeuvre node GUI is displayed at any angle of view when close to a planet. Observed Behaviour: That the Radial Out arrow disappears at some view angles (seemingly when it is close to overlapping the center circle of the node GUI), when close to Kerbin. Steps to replicate: Put a vehicle into orbit of Kerbin (365km was used in my example images) Go into the Map view. Create a manoeuvre node on your vehicle’s trajectory. Click on the node so that the 6 arrows adjustment GUI is displayed. Rotate the camera, so that the angle of view to the node is approximately the same as that in the angle in the image below. 6. While holding the right mouse button move the mouse up and left, so that the angle is similar to that in the image below. Notice that the blue Radial Out arrow has disappeared. Other Notes: The issue only seems to occur when the node is close to a planet. I burned so that the vehicle was on an escape trajectory of Kerbin and placed a node on its trajectory, at about 2000km, which was not affected by this issue.

Version: 0.1.0.0.20892 OS: Windows 11, version 10.0.22621 my pc specs: 16gb ram, nvidia gforce GTX 1660Ti, intel core i5-9400F CPU 2.90GHz Bug description: the game freezes and the Memory usage jumps to 95-100% usage, ive waited for up to ten minutes but the only way out is closing the game through task manager. this happens most times i enter any loading screen Performance issues: when i am able to launch something the game runs constantly at 10-15FPS, however my GPU is only being 30-60% utilized, and my CPU is only being used 50% Steps to replicate: i dont know how to replicate this as it it always how it is for me Fix: the only way i know to get around the memory issue is to make a new campaign. i have not been able to fix the performance issue

When rotating a craft in the VAB, engines and RCS will follow the rotation and keep their actions true to the craft, however SAS will remain facing north. If you rotate your craft by 180 degrees for example, pressing W will cause the RCS and Engine gimbals to try and tilt you forward meanwhile the SAS will oppose it. Here is a video I made demonstrating the bug to hopefully assist my explanation. KSP Version: early access release OS: Windows 10 Build 19044.2604 CPU: Intel i7-9700 GPU: NVIDIA GeForce GTX 1660 Ti RAM: 16 GB Mods: None

KSP Version : 0.1.0.0.20892 Operating System and version : Windows 11, 22H2 version, build 22621.1265 CPU and GPU models : I5 12400F, 3060 Ti FE Description of the bug : the ToggleFlightUI key (changed for F1 in my game) doesn't work at the launch, I must reassign on the same key in settings to make it work Expected Behavior : the key should work and hide the hud Observed Behavior : the key don't work and don't hide the HUD, until the reassign Steps to Replicate : just launch the game, éventually with a custom assign (F1) if the problem don't appears with the default assign Fixes / Workarounds (if known..) : workaround is "reassign the key" A list of ALL mods. If the list is long, please consider using a spoiler window : actually Space Warp and Custom Flags, but the problem existed before their install Other Notes / Screenshots / Log Files (if possible..) : nope.