Not confirmed for any other planets and moons yet. This make all gravitational slingshots that use Mun almost impossible.

The gravitational range of effect of Mun shown in the map view and used in the trajectory planner is different from the one used in the actual trajectory calculation during time warp.

When in very low orbit and in 4* time wrap with SAS on, the vessel can start to rotating at fast speed when un-pause.Ĭombined with issue 9, it almost makes the game unplayable.

Adding 1m of difference between the thresholds, or simply fixing issue #9, might fix it. This is likely caused by the fact that the threshold for the two are the same (at 70,000m PE).

When in very low orbit and at the borderline between sub-orbital and orbital trajectory, one could have endlessly refreshing alternating warnings on screen showing that the viewpoint is changed to orbit and then changed to planet.

This is obviously caused by the fact that the trajectory is not calculated from the centre of rotation of the vessel.

Rotating a vessel will change its orbit, and the rate of change scales with the angular speed.

This is likely because a damping factor is not introduced in the feedback control loop for SAS. Control surfaces and nozzles will vibrate endlessly with a significant enough amplitude in some cases.

If that is true, then the calculation of the fuel tank connectivity is wrong somewhere. These two combined, means that the game could be actively reconstructing the stage sequences for the separated pieces every time a stage is triggered (that separates the vessel into multiple pieces). A brief pause happens every time a stage is triggered. In particular, this starts happen after the first time a stage is triggered after taking off, i.e., immediately after detaching the first round of boosters.ħ.1. For some vessels that launch a lander along with the orbital control, fuel cross-feed is wrongly enabled between the fuel tank of the lander and the fuel tank of the main rocket.This is exactly the opposite of what people usually do.

One can trigger the next stage during pause, but cannot plan trajectory during pause.

These are probably due to some threshold setting errors. The see-through function of payload fairing does not work correctly.

(Could be feature rather than bug) The lift provided by control surfaces feels way higher than that of KSP1, the drag feels way lower.Ī few seconds after being detached from the vessel, the physics simulation of the payload fairing pieces become wrong.ĥ.1.

(Technically not a bug) Moving up and down in VAB is bound to the middle key of the mouse, moving left and right in VAB seems to be not bounded to a key in the mouse, The aerodynamics summary shares the same F12 key with steam screenshot, and it seems to be not possible to change this in-game. A space craft launched in this way into the air again will not show any trajectory in the map view. As a result, the engine nozzle sinks into the ground before triggering the landed status, and then immediately become overlapping with the ground model, which will cause the collision physics calculator to give a super big speed to the space craftġ.1. This could be caused by that the nozzles of the engines do not have collision during flights but do have collision when on the ground. When using Flea booster and touchdown to the ground, one could be launched into air at a very fast speed (5km/s for my case).I also managed to clip Bill into the moon and he fell to the center and got shot out of the moon going 103 km/s out of the solar system and yes you read that right 103 kilometers a second not meters a second KILOMETERS a second, but hey it did show that the patched comics can handle very fast speeds and trajectories out of the kerbol system unlike the first game as that line extended FAR out into space and wasn't flipping in and out of existences like ksp 1 patched comics did alot It acted as normal for being in orbit for a bit and then deorbited very rapidly dropping from 2400 or so m/s down to 0 ina few seconds and began gaining speed downwards ripping the ship apart destroying roughly 30 or so minutes of work. I think it happens when you dock two craft together, because I was assembling an interplanetary ship in low kerbin orbit and docked two parts together when back to the ksc launched a fuel tanker to fill up empty fuel tanks and swapped back to the ship when it saw had no orbit lines. From what i can tell the orbit lines disappear because the game puts the craft into a landed state which removes all patched comics from that craft and changes the physics slightly.

Kerbal space program 2 pc reddit