Search the Community

Required to Recreate: At least 1 x Rapier Engine(+ 1 intake of your choice) attached to a craft containing at least 1x Full Methalox Fuel Tank (Liquid Fuel + Oxidizer). Steps to Recreate: Launch Craft, fly to a stable altitude within Kerbin Atmosphere, Engage Closed Cycle Mode on the Rapier Engine when your Liquid Fuel is close to running out, Wait for burnout, stay full throttle. Expected Result: Rapier Engine Burns out, Remaining oxidizer stays inside the fuel tank. Actual Result: Rapier Engine Burns Out (with half a tank of oxidizer remaining), Rapier (and everything attached to it) explodes, Fuel tanks empty. Craft destroyed. Summary: Rapier engine seems to vent all remaining oxidizer when liquid fuel is depleted, causing an explosion. Realistic? Maybe... Bug? Maybe... Annoying? Yes.

The attachment nodes on the Mk2 "Tuna Can" are not aligned with the center of the part:

see. the last part of the video

KSP Version: 0.1.0.0.20892 Operating System and version: Windows 10 CPU and GPU models, Intel Core i7 10700K @ 3.8hz, 32 GB ram, 4095mb NVIDIA GeForce RTX 3070 MSI Description of the bug. When renaming a vessel in the tracking station the vehicle's name never changes and reverts to its vab name On duna kerbal attempted to board vessel after eva and vessel spun out of control clipping below surface. Are had a lot of elevation differences In orbit around Mun attempted to board vessel after eva and vessel exploded Vehicles docked together separated but then the craft it separated from loss speed and fell vertically to surface Vehicles docked together could not separate The new maneuver nodes are very wrong much of the time, particularly with celestial body encounters. When accelerating under time warp vessel often becomes detached from maneuver path Steps to Replicate Fixes / Workarounds (if known..) None A list of ALL mods. If the list is long, please consider using a spoiler window. None Other Notes / Screenshots / Log Files (if possible..) None

KSP Version: 1.0.0.20892 Operating System: Windows 10 Pro 22H2 CPU: Intel Core i7-10700k @ 3.80GHz 3.79 GPU: Nvidia GeForce RTX 3070 Ti RAM: 32 GB DDR4 Description, expectation, observed and replication: The lower part of the shroud of an engine mount shrinks after undoing any edit in the VAB. The expected behavior is for the shroud to stay in the same shape as before the undo. The observed behavior is that it shrinks This can be replicated like the following images explain link to full imgur album: Fixes / workaround: Simply re-attach the lower part Other notes: DxDiag for devs: https://pastebin.com/iEgr95TT

OK, I am sure this has been reported before but I had to share this. KSP Center following KSP Center at KSP Center. When did KSP start using Marvel graphics engines? Version Info: 0.1.0.0.20892 OS: Windows 11 (10.0.22621) 64bit CPU: AMD Ryzen 9 5950X 16-Core Processor (32) RAM: 130992 GPU: NVIDIA GeForce RTX 3090 (24340MB) FPS: 60 SM: 50 (Direct3D 11.0 [level 11.1]) RT Formats: ARGB32, Depth, ARGBHalf, Shadowmap, RGB565, ARGB4444, ARGB1555, Default, ARGB2101010, DefaultHDR, ARGB64, ARGBFloat, RGFloat, RGHalf, RFloat, RHalf, R8, ARGBInt, RGInt, RInt, BGRA32, RGB111110Float, RG32, RGBAUShort, RG16, BGRA10101010_XR, BGR101010_XR, R16

How I built the ship: I put 3 medium docking ports on the XL engine plate in symmetry so that they weren't touching. I then built 3 segments to a space station on them, one crew segment, one solar panel segment, and one structural segment for expansion. This then had an XL tank (the middle one) and L/XL orbital engine on it for the 2nd stage. The first stage was the XL long tank with a mammoth engine and 4 of the Medium Long SRBs (because this was heavy and I am horrible when it comes to fuel efficiency). The Problem: When in LKO (100km circular orbit), I attempted to undock the parts to reconfigure them in their less symmetrical form. All seems to work normally for a varying amount of seconds (3-10 seconds maybe), I have RCS controls and am moving the detached part away and starting to rotate. Then the segment will rubber band back to its original housing on the docking port, I will get a message saying the ship is out of fuel (each segment has a near full monoprop tank), the flight log will appear as if I just ended the flight, and everything still reports operational in the parts manager. Troubleshooting: I can keep trying this process over and over on the same flight to no avail Quick loading or restarting the game also didn't help. If I have the setting for requiring comms on, then the probes and their antennae will not have an option to connect them to KSC even when directly above it and a Kerbal is onboard the crew section. I turned off this setting and have control of the probe for testing after doing so. I've tried each of the sections and they all do the same thing. There is no part collision between the segments, I made sure they had sizeable gaps (as much as I could and still fit them in a fairing on the ride up). I have also tried setting the strength of the docking ports to 0% on all the docking ports to make sure it wasn't that I was just not moving away fast enough. Even when I tried undocking and then having the part speed away as fast as possible in the few seconds (I got a whole length of the ship away which was about 2 of the medium long trusses in length), it still snaps back. The snapping back is almost like quick loading, when far enough away it is teleporting back with no applied force. If I was close enough to it, the ship did seem to wobble slightly when it bounced back (though that might just have been my imagination).

Version Info: 0.1.0.0.20892 OS: Windows 11 (10.0.22621) 64bit CPU: AMD Ryzen 9 5950X 16-Core Processor (32) RAM: 130992 GPU: NVIDIA GeForce RTX 3090 (24340MB) FPS: 60 SM: 50 (Direct3D 11.0 [level 11.1]) RT Formats: ARGB32, Depth, ARGBHalf, Shadowmap, RGB565, ARGB4444, ARGB1555, Default, ARGB2101010, DefaultHDR, ARGB64, ARGBFloat, RGFloat, RGHalf, RFloat, RHalf, R8, ARGBInt, RGInt, RInt, BGRA32, RGB111110Float, RG32, RGBAUShort, RG16, BGRA10101010_XR, BGR101010_XR, R16 Any Orbital Maneuver Expected Behavior: The burn time progress bar under the burn time status window (bottom center of screen) should reach the end (far left) when the Burn Time Remaining get to T-0 countdown. Observed Behavior: While the burn is occurring, and the view is toggled between Vehicle View and Map View, the status progress bar gets reset to the full right, then no longer finished at the far left with the total burn time reaches 0. Steps to Recreate: Plan any orbital maneuver node with a burn time duration of more than 30 seconds. Start Burn in Vehicle View, while burn is occurring switch to Map View. It also happens when starting in Map View and changing to Vehicle View. Workaround: Don't change views while performing a burn. Mods: None Logfiles: None Notes: See photos below. In KSP1 there was a burn down progress bar by the NAV ball and a Total DeltaV numerical count down. These two match. I like the Stop Burn In countdown and the 'stoplights' for the last 4 seconds, however please add the Total DeltaV numerical count down back in from KSP1. Photo 1: Started in Vehicle Mode, Stop Burn In time is 1:03, and progress bar below is reducing to the left as normal. Photos 2: Switch to Map View, Stop Burn Time has reduced nominally, however the progress bar is now full again at the start (far right). https://imgur.com/QkLEn9z Photo 3: Again switched between Vehicle View and map View. At Stop Burn In 10 seconds, the progress bar is full again (far right). Now in 10 seconds it should be all the way to the left. Photo 4: 10 seconds later at T-0, its not.

Version Info: 0.1.0.0.20892 OS: Windows 11 (10.0.22621) 64bit CPU: AMD Ryzen 9 5950X 16-Core Processor (32) RAM: 130992 GPU: NVIDIA GeForce RTX 3090 (24340MB) SM: 50 (Direct3D 11.0 [level 11.1]) RT Formats: ARGB32, Depth, ARGBHalf, Shadowmap, RGB565, ARGB4444, ARGB1555, Default, ARGB2101010, DefaultHDR, ARGB64, ARGBFloat, RGFloat, RGHalf, RFloat, RHalf, R8, ARGBInt, RGInt, RInt, BGRA32, RGB111110Float, RG32, RGBAUShort, RG16, BGRA10101010_XR, BGR101010_XR, R16 On a interplanetary flight to EVE: Expected Behavior: When planning a maneuver to intercept EVE, adjustment to the deltaV amount brings together the two intercept flags, when the two intercept flags are within the SOI of EVE, the SOI markers should be shown Observed Behavior: The SOI flags are not shown even though the intercept range is well within the SOI of EVE. (See first image below. The Intercept flag shows distance to target at 18km, well within Eve's SOI, but not SOI markers shown) Steps to Recreate: Create a EVE intercept orbit maneuver Workaround/Fix: When changing between vehicle view and Map View, it still did not show the SOI markers. Though when in Map view and rotated the view so that the intercept point were off the screen and brought back into view they got magically added. Possible and view refresh update issue? (See second image below) Mods: None Logfiles: None Notes: None

I spent an hour today driving the Rover on Duna. The idea is to get to a crater. Buy I also wanted to see how it behaves on terrain. It's buggy. -wheels float above Dunas surface -Randomly hits invisible terrain object in relatively flat terrain and spins in 360 degrees -refuses to go in a straight line and constantly fighting with maintaining control of velocity Will post a video of this on 3.3.2023

After a mun landing I made, I took off with my ship off the mun. I opened up my map view to see my apoapsis, and to my surprise, the trajectory line was missing! Luckily, I managed to save Jeb, Bob, and Tim C. Kerman from space without the line (due to my many years of ksp1 lol), but I think this but could be a HUGE issue, especially with new players and interplanetary travel. I have no clue what caused this bug, but I tried reloading and restarting the game to no avail. My ksp2 version is release (obv), and I am running windows 10 with an NVidia 3060 ti and a 3rd gen ryzen cpu.

KSP Version: 0.1.0.0.20892 Operating System and version: Windows 10 22H2 CPU and GPU models: Ryzen 5 3600X, RTX 3060 Ti, 32GB DDR4 RAM Description of the bug. Expected Behavior: When decoupling these simple structures, which are made up of 3 xs fuel tanks and 2 xs nose cones on either end, I would expect them to just fall to the ground and explode in amazing fashion. Observed Behavior: It seems they have some type of aerodynamic lift to them that causes them to shoot up and in random directions after dropping them from the craft. It is more exaggerated the faster and higher I go. Steps to Replicate: Make a plane and add little "bombs" to the wings. I think you have to have nose cones on either side of it. A list of ALL mods: I have SpaceWarp and the custom flags mod, that is all. I have numerous other bugs that all seem to have been reported. The most annoying of which is my campaigns seem to break and I no longer can save them, forcing me to delete them and start a new one. It's not a huge deal though because I am just testing stuff right now and messing around due to the WIP state of the game. But I haven't seen much reported about this issue with the aero behaving strangely. I am not sure if this is really a bug as much as it is the aero system still being worked on and tested. Here is a quick video below I recorded of the bug:

Version: 0.10 OS: Windows 10 CPU: AMD Ryzen 5 3600 GPU: NVIDIA GeForce RTX 3060 Expected Behaviour: Timewarp Observed Behaviour: Mission failed pop up Steps to replicate: Timewarp in atmosphere

What the title says. Am I doing something wrong? I activate the decoupling stage but both parts are still connected to each other even though the decoupler is gone. This never happened to me in KSP 1 so I don't think it is my problem. Is there any workaround? Has this happened to any of you?

This is something I just encountered today. My view controls suddenly don't work in flight. I'm not sure of any details for why this is happening or what I did to cause it, just all of a sudden, my view controls totally stopped working.

KSP Version Windows 11 AMD Ryzen 5 / NVIDIA Geforce GTX 1060 After loading a savegame I can't move in KSP and not select a building - see weird camera angle in video Expected Behavior Observed Behavior Load a savegame https://imgur.com/a/O6yqwHM

This vessel has no kerbals or probes, and I am unable to control it (i.e. pressing "u" results in the message "no vessel control"). However I am still able to extend/retract parts in the parts manager.

Sent my new Dream Chaser-esque spaceplane to the minty moon for grins and giggles, only to notice that the surface was almost devoid of the tiny ground scatters. I moved the camera below on accident because it isn't stopped by surfaces for some reason, and I saw a lot of these tiny scatters underground, out of sight. Underground view, erroneous scatters circled, many more, but don't have the time to find em all View from the surface, the little scatters are almost all hidden Quicksave + Quickload doesn't fix it, neither does going to map screen and back Currently, Minmus is looking a bit bland and bleak, even for Minmus standards, and I hope that once this issue is resolved, it will make the minty moon a bit more interesting to visit.

I personally prefer the control configuration of w s a d on pitch and roll with e and q on yaw. However, when I try to assign the e key to right yaw, the input is ignored.

I appear to be losing control of my rocket whenever I enter map view with SAS turned on and set to hold position. SAS also appears to lose control of the rocket, as it drifts off course instead of holding like it should have. I regain control when I exit map view, only to lose it again once I re-enter. This has messed up multiple burns that I have used map mode to monitor, not realising until too late that the vehicle was uncontrollable, and I would be grateful if it was fixed soon.

Hello, I was recreating a historical aircraft in ksp 2, when I realized that at a certain time after launch, due to a certain maneuver or because of behavior of parts, on of the prior listed reasons (I am not sure which one is the true cause) the game enters a freeze state where it becomes unplayable. There are 3 levels to this, the game either just deletes the craft but lets you revert to VAB, the game deletes the craft and freezes, forcing you to alt f4 or the game crashes entirely. I have attached an image of the game in the "game deletes the craft and freezes" type, however it seems I cannot add my Ksp2.log file.

Ships that land on the easter egg monument on Minmus are not saved by the game. Upon return to KSC, they are gone from the save. They don't appear in the tracking station nor in the save game file. They're literally gone. Landing outside the ring of the site is perfectly safe. One would expect that ships laned in the monument are persisted just like landing everywhere else. (Or if their disappearance is intentional...some kind of indication that this is the case while on the site) KSP2: v0.1 PC: AMD Ryzen 9 3900XT | Geforce RTX 3090 Founders | 32GB RAM

The title says it all

On launch, my computer will freeze, emit a sound like a buzz saw, and then blue screen of death on launch, when I have graphics on custom settings, leaning towards low, and am at recommended with RAM and CPU and in between minimum and recommended with GPU. Is it my build of the game, or what is wrong?