LordFerret

I still have v0.90 installed. However, I've been devoting my time to the new v1.0.2 instead. At some point this coming week, I'll be hopping back into v0.90 to bring all my Kerbals back home. I'll make a few last notes about the crafts I've built, backup my screenshots... then the rest goes off to the archives.

Thank you for researching this. Your data goes right into my notes file.

You need a good anti-virus, obviously. AVG or Avast are free and sufficient. But, first, removing the bugs, start with Malwarebytes - let it scan and clean, then load up SpyBot - scan and immunize your system and keep it updated. All of these things are free, and they work... so does smart browsing.

As if the Devs and Maintainers don't already have enough to do... I visited the Wiki page for KSP, hoping to find some answers on key bindings and new parts, but I find it is very much-so out of date. So I guess this is a request for one more thing to be added to the To-Do List ... please update the Wiki.

Being so many people in the past have had problems with the Updater/Patcher, I've never bothered with it, I just download a fresh copy (zip). It took me forever to get my hands on v1.0, likely because their servers were so busy with so many hitting it for the new version. When I saw the news of the v1.0.1 update, I tried to download that but ran into troubles ... twice I tried to download it. The first time, the download timed-out at about 80% (grrrrr), and there was no recovering from it. The second time, it died about 10% in. The reason was because they put up the v1.0.2 update lol. From what I'm reading and understanding, updating or patching likely isn't going to help you any with your existing game - as the changes have a drastic impact on the parts and their properties. Your best bet is a fresh install (in my opinion).

Download the demo and try it if you're unsure about investing in it.

If you'll look in the picture, on the left, you'll see the rocket (fallen over). It consists of an Mk1 pod, a Service Bay (with Goo and Thermometer inside), and a Science Jr. ... the capsule had an Mk16 parachute on top, and one Mk2-R radial mount parachute on its back side (not seen in the picture). Total mass = 1.4 tons (not counting the fuel tank, engine, or pilot). The rate of descent is pretty slow, on the order of about 3m/s. I've never had a building explode from landing on it. This is also the first time I've ever had a Kerbal get stuck on a building ladder as such.

Bah, my bad. I forgot about that in Career mode, stuff needing upgrading ... I play a Science game and it's all lit up from the git-go.

The Reliant engine lacking a gimbal can be part of the problem, it's a major annoyance for me anyway. Need for keeping a reign on your thrust and ascent velocity (and G's) is also an issue. Fins do help. I find sometimes that SAS can help (a little), but more often than not (for me) SAS just seems to fight with itself. You should check out the boat-load of tips in GoSlash's thread here. I've asked for a Mod to sticky it, wish someone would.

KSP Version: Win 8.1 64-bit, non-Steam, build id = 008422015.05.01 at 21:02:12 CEST Branch: master What Happened: Very early in the new game, just installed, maybe the 5th flight? Launched a small rocket "Progress-1" towards the KSC complex. Approaching the complex at a few hundred meters in altitude, I shutdown the engines and staged (dropping the engine and fuel tank) ... and then after a few moments I deployed the chutes in an effort to (try to) land on my target. When the ejected engine and fuel tank hit the ground an explosion was heard - and then a fraction of a second later the explosion began repeating endlessly and the game froze. There was no exiting the game, Esc did nothing... I pressed the 'Windows key' and got to the main Win 8.1 screen and then attempted to go back to the desktop... at that point, the system displayed a message that KSP was not responding. I had the system force the close of KSP. No crash file was created. Screenshot: I did not get a screenshot (sorry). Files: persistent craft output_log System: ASUS laptop, i7-4500U cpu @ 2.4ghz, 8gb mem, Intel embedded graphics with additional Nvidia Geforce GT 745M card.

Huh? Why are you questioning or even debating this?

If you knew you were 100km north of the KSC, then all you needed to do was keep an eye on your bearing via the Navball and head south hugging the coastline while keeping an eye out for the mountains to the west of KSC. Once you got close enough, you'd have seen the KSC, because it does have lights - the launchpad is lit, as well as the runway.

Version 1.0.2 Leave it to me to find an odd quirk with a ladder... on the roof of the VAB no less. So I landed on the roof of the VAB and did some science. I decided to head up top, and I found a ladder to take me there - or so I thought. When I approached the ladder, I got that familiar friendly 'Grab' message, so I did. That allowed me to climb the ladder. But, once I got to the top, the 'Climb Out' message appeared and I wasn't allowed to climb up any farther... so I opted for 'Climb Out', thinking it would take me to the roof. Mistake. I was left in a position as seen in the picture below. There was no 'Let Go' (although it did appear now and then), no more 'Climb Out' (repeated selection did nothing), and an occasional switch between 'Climb Out' and 'Grab' as I struggled to get free. I even tried activating the Jet Pack, but all that did was burn fuel and take me nowhere. I tried to select and switch back to the capsule - no go... a message told me I couldn't switch while in atmosphere (at least it was correct lol). I tried Esc too - no go... the menu would come up, but all that was allowed was to Resume or Revert. After a few more futile attemps at escaping, I reverted the flight back to Launch (half expecting the game to crash, but it didn't). No damage done, just odd, really odd.

The download for 1.0.1 from the Store failed twice, both times pretty much in the middle of the download - after taking forever to get there. 1.0.2 doesn't show at the Store. I think I'm just going to set this all aside for a while.

The Launcher is a pain in the butt because it gives no connection status what-so-ever... just "Updating", when it isn't. If the connection times-out, you'll never know it.

One launch is all it took. Off.

I kind of have the impression at this point that the whole aero revamp was for the benefit of planes, which most people here appear to focus on. It certainly hasn't helped me any with rockets. Still fun to tweak with though.

Batteries, science experiments... and even a light - so I can see what the heck I'm clicking on out there in the dark. Anyone tried fitting a Kerbal in there yet? I don't have the external command seat yet, but I'm dying to know ..... what if? lol

Nothing fancy here, playing a vanilla science game. So far, so good... but very wobbly rockets... SAS likes to fight itself. :/ So far, I've sent manned probes (orbited only) for science to Mun and Minmus, and unmanned probes (two of them) to Duna. Took pictures, but haven't uploaded them yet. At least I still have Jeb, Bob, Bill, and Val still, plus a load of new faces put to work as well.

It appears the community has come up with what will likely be the only answer to this ... see the results here.

I posted this in the Unmodded Installs Support section... seems the general consensus is the situation of the Service Bay and parts placement around it. At this point I don't think there can or will be a fix for it ... so the advice posted here by several is the way to go - keep stuff (chutes, etc) clear of the Service Bay. Marking thread as "Answered".

After reading the results of xxserilviaxx and Speijker above, I'd say it definitely involves the Service Bay. I can reproduce it, already have twice now (as stated in OP), but I can't for sure say 'reliably'. While I did not do a quicksave/quickload test, as I said - exiting the game and then reentering did seem to fix it... but I've not really tested that out thoroughly. So far, with another flight I did late last night, the chutes all successfully deployed. As for an .sfs file, I posted a link to the persistent.sfs which was saved right after the problem occurred; It was after saving it that I reentered the game to find it mysteriously 'fixed'. Correct, no fairings are used other than the auto-fairing of the new heat shield, and no other cargo bays / Service Bays other than what's seen. The rest of the rocket was the lifter stage. No, I did not use the Offset or Rotate tools while assembling in the VAB. Both radial chutes were placed manually, but the Angle Snap was active.

I did some searching on this last night, and there isn't much to be found. I got the impression however that some suspected the ALSA daemon was having a time-out issue with the sound card. One source I read made suggestion about updating the sound card's drivers (check the OEM's site), but there was no real follow-up on the success of that (or not). So, I'm wondering now if your computer is a laptop, and if so, could this be related to power management?... left sitting idle, in order to conserve power (even while running connected to a power source, plugged-in), laptop power management schemes can spin down drives and turn off displays and other resource utilization. Maybe take a look at that if the case applies? Next time you run into this, check the status of the ALSA daemon and see what state it's in as well as the status of the sound card itself.

I find Mun far more fun to rover around on than Minmus... visiting anomalies. That was in 0.90, but I'll continue the trend in 1.0

From what I've read, they're expecting perhaps a 15-meter impact crater (of what depth?)... would be interesting to see what manner of ejecta it throws up, but I don't think we've anything with power/resolution enough to view it at this point. :/