phoenix_ca

Yep. I actually narrowed it down fast. B9 Aerospace is causing the CTD. http://forum.kerbalspaceprogram.com/threads/66020-B9-0-23-fixes/page13

If realism-crazy-people come in here and start demanding that every resource have its own part, I'm going to shoot someone. Besides, your description is a bit off. Water and wastewater aren't in the same tank, they're in two "tanks" in the same part. Abstraction. But it works.

Well. B9 Aerospace causes a hard crash while loading, but it's not the only thing doing it. Removing it from the broken install with all the mods doesn't fix it. Still get a crash. This makes all of NO sense. Edit: Or not. Gods dammit. This is the most confusing thing I've ever had to deal with in KSP.

Yeah. That's from DevHelper. I tried removing it but it didn't change anything. I'm going to try a new copy of KSP, install mods a few at a time by copying them from the broken install, and look at the KSP.log file each time. Hopefully, something will come up. If not, I have an even more confusing problem on my hands. I'd wager its a problem with a plugin. I'm only a little way in but it seems like the effect might be cumulative between various plugins.

If you had it installed previously, you should have deleted the FerramAerospaceResearch folder first, then installed the new version. Just overwriting the folder is a bad way to update any mod.

Nice. Now if only I could wrangle KSP into actually starting. >.<

Well. This is brilliant.

Would you consider using Gaius' TweakScale plugin for the hubs? http://forum.kerbalspaceprogram.com/threads/72567-0-23-5-Goodspeed-Aerospace-Parts-TweakScale-plugin-v2014-4-1B/page8 It'd save a fair bit of part spam in the VAB. Actually quite significantly by removing two thirds of the parts necessary. 5 parts for 15 different variations is a good deal.

Yeeeah. That plugin is more interesting than all the parts combined. >.>

2,000 calories is a pretty high estimate. You need to be pretty active for that to be accurate. One can live on a fair bit less. Not well by our zomg-so-wealthy-we-can-waste-food standards but still.

If you suspect that, it'd probably be of great help to figure-out just which of your mods is clashing with it.

Yeeeaaaahhh, except that didn't work. O.o WEIRDNESS. Besides this was all just me being silly. Easy solution to get what I wanted was to use workspaces. I'm way to used to running KSP under Windows, which lacks the very concept of workspaces (and I gave up on them with OS X when Apple stomped all over their older system that worked quite well...jerks). Edit: Naturally, I've run into other trouble. Seemingly random crashes when loading on start. It's very confusing because absolutely nothing has changed with my KSP install. It just...loads a bit, and then boom. Crashes with nothing useful. My KSP.log is flooded with these lines: [EXC 06:32:09.871] NullReferenceException: Object reference not set to an instance of an object Right after Module Manager finishes, the log is just full of these. Multiples after every load entry. I have absolutely no idea what the hell this is coming from. Here's a full version of a failed start: http://pastebin.com/vBXD35qX What's annoying is it really was just working. I got a successful start and figured I'd be done. Now, this. Out of nowhere.

Bah no. I just killed KDE with a vengence by wiping-out my Ubuntu partition and starting over again. -.-

It's almost definitely a KSP thing. Maybe I can use workspaces to get around it. Installing KDE for Ubuntu has created it's own raft of problems...reminding me why I avoid it in the first place. Aside from being a really heavyweight desktop environment, a lot of my applications are stuck using KDE interfaces in the default Unity environment. *sigh* Yeah. Looks like it's time for me to wipe this Ubuntu install again with a clean one. Lots of fun with GParted again I'm sure when Ubuntu inevitably installs GRUB on my EFI partition when I don't want it to. -.-

No actually. The reason I want to get this is because I want fullscreen on a single monitor, but I also want the ability to alt-tab out of KSP to other applications while it's running, so I can do things like watch something with VLC while letting MJ do a very long burn and such. I have the same problem with Windows and OS X versions of KSP and am (perhaps wrongly) extending the same logic that running the game in a sort-of faked fullscreen mode will give me back that ability. Unit: Not that I know of. Unity isn't all that customizable. You really have to fight with it. Anyway starting a KDE session instead of Ubuntu's Unity/GNOME thing does the job. It's way, way, way more customization than I need but still. Now if only I could get a driver to work for my backlight so I can actually change the screen brightness.

By default, command modules cannot store duplicate reports. Are you sure that the reports are being taken in different situations?

I'd just chalk that up to Windows' fairly poor, tacked-on permissions system that barely works right half the time. Windows wasn't built with adequate permissions management in mind. Other OS' were, leading to OS X and popular linux distros today having comparatively robust permissions management.

After reading the whole readme and config files from top-to-bottom...twice...or three times, honestly I've lost count at this point, I still am not clear on exactly how to manage things. I want to use two IVA suit colours, the blue for generic kerbals, and the orange for Bill, Bob, and Jeb. The former seems easy: All I need to do is slap the blue kerbalMainGrey and kerbalMainNRM PNGs in the Default folder. For the latter, the issue is making sure both the suit texture and normal files get applied. I assumed (though this isn't clear at all from the config files if I'm doing this right) that putting a folder in /TextureReplacer/Suits called "KSP_Dark_Orange_IVA_suit" which contains both the correct normal and texture files in that folder, then specifying the suit name in the config for Bill, Bob, and Jeb as KSP_Dark_Orange_IVA_suit. But as I said, I have no idea if that'd work. It's all based on assumptions. The config just isn't specific enough on the subject of custom suits, especially since all the actual PNG files are named the same as each other. Differentiating them and making sure the correct normal file is used isn't straight forward. What's not clear is the terminology refering to "Suit Texture". The texture is actually the kerbalMainGrey PNG, not a folder/directory. It'd be clearer if this section were more specific. From the examples you gave in the above post, it seems I'm going about it the right way, but that's not specifying the texture, that's specifying the name of the directory in the Suits folder that contains both the texture and the normal files. It's also clear in the last part because you say specifically "suit directory" not texture. Edit: The config that comes with Texture Replacer is much, much more clear. I would suggest you keep your config more in line with this paragraph:

Unfortunately no, I'm using Ubuntu's Unity (GNOME; "Unity" how's that for confusing when talking about a Unity3d application) environment. I suppose I could slap KDE on here too and just switch to it for KSP but if there's a way to do it with GNOME that'd be nice. And yes, that's what I'm talking about. A window that fills the native resolution of the screen its on.

ATI is dead. >.>

@WaveFunctionP: It might help you if you create a script before recording, or have a point-form list of specific topics you want to cover in what order. Mostly it'd probably help you with making sure you have the specifics and particular values right, so that you don't spend time wondering whether or not you're right in the recording. That and something wierd is happening when I try to download your experimental version as a zip. I get a lot of duplicate folders, one with capitalization, one without, for almost each folder, and the files are spread between the duplicates. If you'd be kind enough to package the thing as a zip on your end that'd be handy.

These are pretty nifty. My only request would be to add some sort of shield or fairing around the bays, for use with FAR. As it is, you can use something like procedural fairings to cover it up, but that'll only last until you jettison them, so it's not ideal for any long missions that'll go through both space and atmosphere. Perhaps you could add a shield part that would go around the bays so that the things inside are covered but accessible via doors or something. So what was the fix for your problem?

Or the same sentence. That makes more sense now.

You, sir, seem to have a wildly insane bug on your hands. Or some unexpected behaviour.

I vaguely recall someone mentioning that antimatter from collectors wasn't using ALL_VESSEL logic. The same logic that drives Monopropellent in stock KSP.