Deep Space Kraken
The Deep Space Kraken is a bug in the game that is experienced in deep space. It is an error with the games physics engine, PhysX, which attacks spaceships as their velocity increases. The number of parts in your ship has a large effect on what speed the Kraken manifests itself, as well as how much it affects your ship. It primarily causes your craft to go off trajectory due to forces that shouldn't be there. The name comes from the legendary deep sea creature that supposedly attacked and sometimes destroyed sailors' ships.
The cause of this bug is extreme velocity; the bug subtly exists even in Kerbin orbit, though is mostly only noticeably experienced in Kerbol orbit due to velocity you "gain" when you transition SOI to Kerbol. A fix was implemented in 0.17, involving offloading velocity to the universe around you meaning that the focused vessel will always be at a somewhat low speed. However, the same bug under a new name, the space Cthulhu, can break apart ships when quickly warping out of high time accelerations (as of 0.17). It has been reported that Cthulhu can attack ships that are still on the launch pad when coming out of a high time warp.
Gyro Kraken is when a spacecraft will spin around and vibrate so intensely that the spacecraft will be obliterated. The rate of spinning is so extreme that it is impossible to be replicated manually.
Warp Kraken is an 0.19 bug that attacks kerbals exiting spacecraft that have just come out of a high time warp. Upon contact with the surface the bug causes the kerbal to be shot out of the solar system at an insane velocity (possibly exceeding the speed of light) while destroying all spacecraft in the vicinity. This bug has so far only been encountered on the Mun and has not been confirmed to exist in 0.20.
Deep Space Cthulhu
Deep Space Cthulhu is a fan-made term for a version 0.17 bug similar to the Kraken, except it only seems to attack when exiting high time warp speeds. Instead of adding phantom forces, Deep Space Cthulhu instead tends to detach parts from one another. In milder, yet more infuriating forms, Deep Space Cthulhu will instead detach small groups of engines, making it impossible to perform orbital burns.
The EVA Kraken is a 0.20 bug that spectacularly destroys a spacecraft if a kerbal on EVA approaches it at high speed. It only occurs in fairly specific circumstances. A kerbal must EVA from a ship and go far enough away that parts physics stops acting on the ship (200 metres). Then if the kerbal comes within 200 metres again at high speed there is a chance the ship will explode in spectacular manner, with the debris shooting off at high velocities (sometimes enough to escape low Kerbin orbit). Sometimes the unfortunate kerbal will be killed as well.
The reasons behind this form of kraken are not well understood. It is possibly due to the parts clipping into each other as physics starts to act, or another theory is that it is due to physics trying to start too quickly to keep up with the rapidly approaching kerbal. At the moment very little concrete data exists. What is certain is that it always starts as the kerbal passes exactly 200 metres from the craft, and that it only occurs when the kerbal is moving at relatively high speeds. The kerbal does not have to come from the ship it destroys. It is unknown what happens if physics starts to act on multiple ships at once.
There are good reasons to take precautions against EVA kraken as it always destroys the affected ship completely. The best prevention tactics known so far is to approach ships slowly and quicksave often.
The Wormhole Kraken has been reported to affect ships as they are leaving Kerbin's atmosphere. If there is a lot of weight below a decoupler (which is most likely also the center of mass), the rocket will clip through itself. While in Kerbin's low atmosphere, the bottom part of the link will start moving faster than the top due to the normal acceleration. Once the top of this broken part passes the actual top of the rocket, the entire rocket will obliterate itself, leaving no two pieces attached.
The Hell Kraken is a form of Kraken which was discovered during the 0.21 version. It seems to strike when a kerbonaut on EVA hits a celestial body's surface, causing the screen to turn black, with the UI remaining though. The altitude will remain at 2/3Mm which displays as "666,666m", which earned this type of Kraken Bug its name.
It has been confirmed to occur with a small unmanned rocket when crashing into Ike.
The resulting crashed world prevents any Kerbal from leaving the spacecraft via EVA and makes it impossible to launch or build new vehicles by blacking out the space center.
Quitting and then re-launching the game sometimes solves the problem, but it sometimes also deletes the vessel it occurred on.
The NaN Kraken is a form of the Kraken which can only be evoked if the orbits of celestial bodies are altered, via a mod or the alteration of the game's code. If a ship is on the surface of a planet, and another planet is suddenly moved so that the craft is within its SoI, the sudden change in gravity will cause the craft to go towards the latter at incredible speeds, and will sometimes even go through a planet to accomplish this. Please note that the gravity of the second planet does not have to be greater than that of the first, though the reason for this is unknown. This Kraken gets its name from one of the many bugs it causes; when this Kraken is acting upon a vessel, its velocity in the Tracking Station will display as "NaN".
Some players might not consider this a form of the Kraken, but rather, PhysX having a strong reaction to extreme conditions. However, it can be considered a Kraken in many respects, since it can suddenly separate a ship from launch clamps, cause launch clamps to disconnect from the ground but remain in their position relative to one another, and will automatically remove any and all connecting struts and fuel pumps, as well as distorts a Kerbal just like the Gyro Kraken and the Deep Space Cthulu.
Quickload Krakenfound in KSP version 0.22. This type of bug looks similar to the Hell Kraken, but acts differently. It can rarely happen by quicksaving before entering an atmosphere at high speeds (~10km), changing the Physical Warp to x4 once in the atmosphere, exiting the atmosphere, and then quickloading (with x4 Phys. Warp still going) to your last quicksave. The result may end up to be like the photo on the right.
The game appears to focus on "ActiveVesselScaled", with the background being either black or white emptiness. The altimeter stays at zero, you cannot switch to map view, and the GUI is bugged. For example, lets say you try to click on the Docking controls at the bottom left of the screen. The game would then continuously show the animation of switching from Staging to Docking. You cannot leave to the Space Center through the Escape key. The only way to get rid of the screen is to exit through the desktop and reload KSP.
This type of Kraken will not affect your save files or harm anything else. In the Tracking Station, your craft will be back at its last quicksave point.
This kind of Kraken was discovered in KSP version 0.22. This type of Kraken will only occur when parts somehow manage to come to rest below the surface of the sea of Kerbin. Good methods usually involve exploiting the non-buoyancy of Orange tanks. When resumed some parts may not make contact with the ground and can actually float through the ground and towards the core of the planet. When the parts get near enough to the core of the planet, they will gain extreme speeds (about 97.8% of the speed of light) and shoot out towards infinity strangely not actually hitting the far side of Kerbin when they shoot out.
This Kraken is likely caused by the planet's mass being approximated as a single point at the core rather than spaced throughout the planet, causing gravitational forces to increase rapidly as you move below Kerbin's surface.
Little is known about this type of Kraken, but it will most likely not break the save file or harm it in any way.
- (Bug fix) 'Off loading' velocity to the universe alleviated this problem, though it still exists in 'new' form.