ola

I daresay that radiation is the biggest concern of all the above mentioned. The rest of them are all solvable by the ancient and true KSP maxim "add more boosters". Radiation, however, seems to be way more difficult to handle once mission durations are above a year or so. With chemical plants, greenhouses and so forth, it's possible to save up on several years' worth of LS resources. Stress is easily relievable with enough living space and "toys". Radiation seems impossible to manage, even with active shields, max passive shielding and a properly oriented craft with a huge tank at the correct end. And those RDUs don't seem to matter much. But it's a small price to pay for the enormous increase in playability.

Ascent Guidance (and other things) were broken for me as well, until I upgraded FAR to the latest unofficial release. The new version of MFI seems to have done the trick.

OK, so, after seeing this I've actually started reading articles in Journal of Guidance, Control and Dynamics. Damn you, science!

Is it just me, or is your upload on SpaceDock broken? Or is it SpaceDock in general? Will we ever know? Aaaah!

Some nice additions there, including the commented-out code. *cough cough* https://github.com/ferram4/Ferram-Aerospace-Research/compare/KSP_update Edit: this - string msg = String.Format("[{0:D2}:{1:D2}:{2:D2}] {3} failed due to aerodynamic stresses.", FlightLogger.met_hours, FlightLogger.met_mins, FlightLogger.met_secs, part.partInfo.title); + string msg = String.Format("[{0}] {1} failed due to aerodynamic stresses.", KSPUtil.PrintTimeStamp(FlightLogger.met), part.partInfo.title); is actually turning out to be one of my favourite changes thus far.

You need to get hired by Squad, if you're not already employed somewhere else. Heck, come work for us. We'd probably have a job for you.

And the way things are looking now, Squad'll need every minute of those four weeks.

There's discussion in the CKAN thread about this very issue:

I'm still seeing this, to be honest. No, I'm not. This is what I see: Downloading "https://spacedock.info/mod/198/Throttle Controlled Avionics/download/2.3.0.2" (libcurl) 3220 [1] INFO CKAN.Curl (null) - Using curl-ca bundle: (none) 3551 [8] INFO CKAN.NetAsyncDownloader (null) - Finished downloading https://spacedock.info/mod/198/Throttle Controlled Avionics/download/2.3.0.2 3551 [8] INFO CKAN.NetAsyncDownloader (null) - All files finished downloading Installing mod "ThrottleControlledAvionics 2.3.0.2" Unhandled Exception: CKAN.FileNotFoundKraken: Trying to install ThrottleControlledAvionics 2.3.0.2, but it's not downloaded or download is corrupted This happens regardless of the mod I'm trying to download from Spaceport. All files from SP end up as zero-byte length. I'll fool around a bit more to see if I get the same from non-SP mods. If so I'll just delete this post. Edit: it works fine for mods from github. I'm on Mac OS X, if that helps.

This can't be good...

I too run 64 bit KSP, but memory starts to be an issue when the KSP process starts getting over, say, 10 GB memory or so. All of a sudden all those huge tracts of memory starts taking quite a long time to traverse, and the game slows down considerably.

Lovely. Here, have some rep! *nom nom*

I can't seem to finish the first mission. I get up to 2500 metres, I stay there long enough, turn around and land at the runway. Situation: landed never goes green, and neither does biome, even though I am clearly on the runway with no speed whatsoever. Hm?

The previously launched engines all seem to need settling and their ignitor count is reset to the engine max. The centrifugal settling technique seems to work fine, however.

I have a save game which I've put >100 hrs in, all of a sudden all those probes headed everywhere and anywhere need ullage. Maybe I -should- consider turning it off...