I think the Kraken ate Kerbin after my probes summoned it

[DopeGhoti]

Let me preface this by saying that I know I have a veritable mountain of mods installed, and I know it could be any or all of them interacting in a way to cause this problem in a highly non-orthogonal way. I'm already going to be removing mods one by one to see if I can cause this to unhappen, and will update as I progress in this. I post mainly in hopes someone has seen something similar, or already knows the cause.

KSP: 0.24.2 32-bit Windows and Mac OS

Problem:Jumping into unmanned craft (i. e. probes) from the tracking center yields a very broken state (see picture linked below)

Mods Installed:Quite a few, still trying to narrow down the precise cause. Currently installed:

• Active Texture Management
  
• Aligned Currency Indicators
  
• Atmospheric Trajectories
  
• Blizzy's Toolbar
  
• Chatterer
  
• Deadly Re-Entry Cont'd
  
• DMagic Orbital Science
  
• Ferram Aerospace Research
  
• Final Frontier
  
• Fine Print
  
• Fusebox
  
• HotRockets
  
• Kerbal Alarm Clock
  
• Kerbal Contruction Time
  
• Kerbal Engineer Redux
  
• Kronal Vessel Viewer
  
• MechJeb 2
  
• Procedural Fairings
  
• Remote Tech 2
  
• ScanSAT
  
• ScienceAlert
  
• StageRecovery
  
• Station Science
  
• StillBetterThanSpyware
  
• TAC Life Support
  
• Universal Storage
  
• USPI mods (Karbonite, MKS, etc.)

Reproduction Steps: Not terribly certain on exact steps to reproduce, but involve as a commonality thus far the following:

• Send a manned craft into LKO (e. g. 200Km) low-eccentricity orbit.
  
• Separate an powered, antennae-festooned (at least one omnidirectional antenna, activated) unmanned probe, controlled through RT2.
  
• Switch to the probe, adjust attitude to antiradial (I'd be shocked if this were a necessary step).
  
• Switch back to launch vehicle.
  
• De-orbit and land
  
• Repeat all of the above with two more probes which are within communications range for RT2's network status tracking
  
• Go at the KSC to the Tracking Center. Select one of your unmanned probes, confirm that it is functioning as expected with regard to RT2 (e. g. making and breaking connections as orbits process
  
• elect Fly!.
  
• See something such as what is pictured here: https://i.imgur.com/S8EI5UX.jpg - to wit: a broken, partially-rendered and untextured Kerbin. A "craft" consisting of what appears to be only a fairing and a small rocket engine, thrusting constantly.
  
• Observe that no control inputs have any effect.
  
• Switch back to KSC. Manned and new flights appear as normal. Unmanned flights eventually appear as above.
  

Logs:

Output_log can be found here.

KSP.log can be found here.

[liviner]

It's the Eye of Kraken!

[Heathcliffe]

This exact thing is happening to me too! Very aggravating after spending a long time doing everything perfectly in hard mode.

My shared mods on your install are:

• Chatterer
  
• Deadly Re-Entry Cont'd
  
• DMagic Orbital Science
  
• Ferram Aerospace Research
  
• Fine Print
  
• Kerbal Engineer Redux
  
• Remote Tech 2
  
• StageRecovery
  
• Station Science
  
• TAC Life Support
  

I'll be trying this with a few less mods installed and see what happens....

[Heathcliffe]

Actually, this has been happening to me with manned craft too! No real pattern spotted yet, but always when switching between KSC and the craft. Appears to be irreversible without a save state to reload.

EDIT: It seems like my issues were resolved by uninstalling RealChute. Sorry that doesn't really help ya...

Edited October 16, 2014 by Heathcliffe

[BudgetHedgehog]

That used to be a problem with SmokeScreen (HotRockets) before it got upgraded.