Cheesywotsit

Yeah I am done with this game, this is by far and away one of the buggiest releases yet. After having spent a week or more playing BF1 and Dishonored 2 I decided to come back to play KSP again and continue with my Career save. I sped forward a few days till KSP Alarm told me to look at my retunr from IKE craft, Clicked the link to be told that a craft with that name no longer existed. Okay I thought maybe I did something with that ship prior to me going off to play the other games and forgot about it. Looked through my ship list and Kerbel list to find, no Kerbel assigned but 3 Kerbels now listed as KIA. I know for a fact I haven't lost ANY Kerbels. I tracked this down to maybe a bug with a contract to rescue one of the KIA ending before the craft returned and the game deleting the entire craft (really annoying if not also highly annoying.) Fast forward to my next KSP Alarm event, a departing ship for Dres, load the ship to find that it never loads, locks the computer with half the ship missing, a whole load of weird image effects and then crashes to desktop. Againa this ship worked perfectly before my little break. Decided to try loading the saved ship in the VAB to now find that ALL my saved ships from this Career have gone, everything, ever single one of them is missing, they are on my HD, under the save game folder but the game will simply not display them. This game is now a total and utter mess, I've gotten 1,000 hours out of it so I am happy I got more than my monies worth but I am done with trying to work round these flaws and faults. When it was small simple stuff it was fine but deleting and destroying entire sections of a career and rendering everything I had done worthless and with no explainable or good reason... yeah not worth the hassle any more.

Not sure about the x64 version but the 32bit version does have some weird memory issue going on somewhere. Like I said the strange thing is their is no set of circumstances that seem to cause it to happen.

With each new version I always remove (delete) the old game folder and then redownload the latest version. 1.2 is bad, plain and simple. The issue is the same as the old out of memory issue but that would usually hit during transitions, i.e launching or recovering vessels switching between vessels the issue with 1.2 is the game just closes to desktop without notice at ANY time, sometimes with a crashdump sometimes without, their is no repeatable cause. The x64 version is more stable in that issues only seem to occur during transitions (same as previous over modded versions) however I have only two mods, Kerbel Alarm and Mechjeb. Decided to do some investigation the results show that this game has a significant memory leak somewhere. I decided to monitor memory usage in the background while playing the game, I reloaded a return from the Mun mission and kept an eye on the memory usage from the 32bit version by the time I got back to Kerbel (a ten minute flight) my memory usage for the game was at 2.7Gb but what worried me and confirmed this game version has a very bad memory leak was what happened when I landed the craft. I opted to leave the craft doing nothing alt tabbed out to take one last look at memory usage to find it at 2.8Gb but what worried me more was as I watched memory usage it was going up in front of my eyes by around 0.05gb every few seconds and it continued to rise for the three or so minutes I watched it. I recovered the vessel, checked memory usage (down to 2.6Gb) and decided to reload a different craft and leave it sitting on the launch pad. This time round very little change in memory usage, it went up over time but by a tiny tiny amount I then launched the craft and got it staged and in to space with no real changes in memory usage. So it seems that 1,2 has a memory leak that only comes in to effect under specific conditions but when it hits it's bad.

Sorry if I am the one to buck the trend but so far this is the most unstable Kerbin I've played. Stock 1.2, not a single mod at all (the usual cause of crashes) and so far I've had two crashes similar to the 32bit memory cap crash. The first just dropped me straight to desk top while landing on the Mun I had the check to run a test on a Science bay which the game decided it didn't like. So I restarted the game in 64bit mod and ended up with the game crashing in a quite an amazing fashion after trying to recover the craft back on Kerbin. The game sat at the black loading screen and point blank refused to allow me to do anything else, alt+tab didn't work was going to force close it via ctrl+alt+tab but as I went to do that the typical Windows this program has stopped working box popped up. So yeah lots of improvements but no where near a stable game.

Okay so after very much head scratching, removing, reinstall mods and testing testing testing it seems my mistake was rather too simple, turns out I have two relay networks, my early network called Gnat in a Kerbinsync orbit, which had a range of to around just outside Kerbin system and my newer second network called Spider. Which was a Kerbol wide network. Now I assumed or at least I was pretty sure that I placed everything correctly, and that I interlinked the two networks, a double safety should Kerbinsync orbit fail on either of the networks, a total of ten probes surely at least one would be in LOS of mission control? Turns out though that I hadn't. My Spider network was self contained and slowly over time the probe sitting over Mission control had moved out of LOS. Hence failure of the comm device. I installed Remote XF, adjusted my probes and now it all seems to be working, so, uh yeah user error here.

No Stone Blue I don't have Science Alert installed I did but it didn't work with 1.05 I then had some issues so wiped my KSP and did a full reinstall minus Science Alert

Got a small issue, I don't seem to be able to transmit any science data back from manned craft. In fact from ANY craft. Keep getting told I have no comms device on this vessel, problem is I do two huge ones in fact attached, powered and linked to my Kerbin relay network and well in range.