SilverWarior

This is actually an old bug when craft that are landed on dark side of the planet, moon, asteroid act as they are dicetly exposed by the sun.

It is possible that the "Set Speed Record of 2,500 m/s" contract is only checking the surface speed and not the orbital speed which is shown on your navball.

I don't think that logging of or killing the Windows GUI (Explorer) will solve this. So instead I recoemnd restarting the whole computer. Now if that doesen't help you could go and download a small program called Unlocker which is capable of forcing Windows to release the handle to just about nay file and therefore alows you to delete that file even if Windows would not allow you to do this othervise. WARNING! I recoemnd payins psecial atention of which file do you delete with that program as you can actually delete critical system files and thus crashes your system.

Is this a steam or standalone version of KSP? Also can you please use Process Explorer (https://technet.microsoft.com/en-us/sysinternals/bb896653.aspx) to monitor CPU, Memory and GPU usage during your gameplay. Some time ago I help a guy which was expiriencing similar problems but with different game. In that case the cause was the fact that for some reason games textures were saved into GPU Shared Memory (part of system ram that was made available for graphics card in order to extend its memory capabilities) instead into dedicated GPU Memory (the actual physical memory of the graphics card). This was then causing the slowdowns due the fact that graphics card Access to shared GPU memory is much slower that Access to Dedicated GPU Memory due the fact that when graphics card is accessing the Shared GPU Memory the data must go through two controllers (RAM controller and PCI Express controller). Also Process Explorer could give you nice idea of your computer utilization so you can quickly see what might be causing the slowdowns in your games (CPU, GPU, memory controller - I/O handle, high HDD utilization, etc.). I use this all the time to keep my computer running at peak eficienty by indetifying the programs that might be using most of my system resources so that I can then go and search for their alternatives when possible.

I don't think this is a graphics driver issue but rather graphics hardware incompatibility issue. Most likely the older graphics cards that those with mentioned problems have don't support the required shader level that is needed for rendering those parts. I have expirienced similar isues on my old laptop when I tried running the game that required higher shader level support that was supported by my graphics card. In a few cases I actually managed to fix this by manually changing the shader files that shipped with that specific game to forcefully lower the shader level that is required for even loading the specific shader. But this wasn't possible at all times becouse sometimes shaders had certain shading commands in them that were only available on higher shader levels. Another reason why I'm suspecting the shadder support problems is the fact that in the games changelog it specifically says that some parts shaders were redesigned to provide better visual expirience. So I asume those shaders were made with higher shading level support in mind. When I get home I Will try to check the game shaders (if I can find them) and compare them with previous version of KSP to see if my suspicions are correct.

Based on information in the KSP 1.0 change-log it is possible for heat to gradually transfer from one part of your craft to another. Also different parts have different cooling rates (take different amount of time to cool down). So I guess Stayputnik might have low heat tolerance and pretty slow cooling speed.

I guess that the reason why only some parts are affected this way is the fact that in KSP 1.0 some textures and also their shaders were updated. So it is possible that the new shaders that are used for these components require newer shading support that is not supported by that specific graphics card. In game settings there is a specific option to "Fallback part shaders" which might solve this but it might reduce game performance since the shading might be processed by the CPU instead of the GPU.

Lots of KSC buildings needs to be upgraded for you to be doing the usual stuff. For instance don't forget upgrading the CREW building or you won't be able to do any EVA's while in flight (either in space or atmosphere).

Don't start the game through launcher then but by launching the KSP.exe file instead. This however means that you will have to make yourself a new shortcut to KSP.exe because default shortcut that has been created by installer points to Launcher.exe

Based on infroamtion in this thread http://forum.kerbalspaceprogram.com/threads/116839-Heat-shield-seems-to-be-treated-as-having-0-mass the heat shield is adding the mass to the parent CoM which then somehow screws evrything up.

I agree with Claw. Using of undo functionality can cause lots of problems especially when working on large ships with lots of parts. In previous versions it caused me several game crashes, part duplications, unclickable parts, huge memory leaks, and even compleete game crashes. in one case I was even stupid enough to save the bugged ship which caused the KSP to crash every time I tried to load it.

Do you have a Steam version of KSP or a standalone purchased through KSP store. If you have Steam version then you should exit the game and let Steam client update it. If you have standalone version then I gues the best choice would be redownloading the entire game from KSP store. There seems to be bug with Launcher.exe that sometimes hangs the launcher in checking for updates. As I have written in another thread about this the most probable cause is that network component of the launcher does not cancel its wating if the data isn't recieved in certain time as it should.

I can confirm this. I have encountered this yesterday twice. It happened when I was trying to warp to my periapsis which was just above the Kerbin atmosphere but my Apoapsis was still verry high (close to the edge of Kebal SOI). Now I asume the cause for this might be the very high speed of my craft when nearing the "warp here" point (near Periapsis) so the game didn't manage to slow down the time warp in time. In my case first time the time wapr stayed at 100 and second time it stayed at 10. Worakound for this was placing the "warp here" sooner on the orbit where the craft didn't have so much speed. I'll try to do some more testing on this today to see if my teory is corect or not. I din't have enough time to do this yesterday.

I have expirienced similar isue with Launcher was being blocked by my Firewall. So I'm guessing that network component that is used for transfering data from server doesn't have any time-out set or it is set to infinite time so it causes the launcher to wait indefinitely for the data to recieve. This could lead to launcher hanging up in case of any conection problems.

KSP is installed in a folder witn full acces so no read/write limitations. Yes this is a non-steam version of KSP). I'm sure that my antivirus software (ESET Smart Security 5) isn't causing any problems or else I would see this in my AV software logs. Anywhay after quick searching of KSP forums I saw athleast one person mentioning similar problem but it was in the context of another thread regarding the KSP update. But I couldn't find any standalone thread about this ise nor any further infromation therefore I have created this thread. Now it is posible that unintsaling and reinstaling the KSP might solve this problem (I have updated it from previous version) but I decided not to try this just yet becouse now I'm still in positio to offer you guys with some more information about this. If needed I can make a Memory Dump of the KSP application once it get stuck at this bug. I can also save short stack history for each of the KSP threads.