Foozle

Wow! So, what was the issue, out of curiosity? --- JW (and much, much more) here I come! --- Eventually

Yep, happened to me last night launching a mun fly-by using Procedural Fairings. All was well until I tried to stage the fairings, then kaboom. Didn't realize at the time what was causing it, thought I must have accidentally clipped some parts. I'm running 1.3, BTW.

So THAT's why my fairing exploded last night! Had no idea it was related. Uh, "can confirm"...

That sounds oddly familiar. I had trouble with the standalone download of WBT a little while back. Same symptoms, too, now that I think about it. Got around it by just using the most recent version of WBT in the WBI mods themselves instead. That tuned out fine. Caveat: I'm still on 1.3 so your mileage may vary. And the version of the standalone WBT was different as well. Still might be worth trying though...

Congratulations! It's gorgeous. And to all those folks still using 1.3 (like me), it works there too. Because Textures Unlimited works in 1.3.

I'm on OSX, actually. But I use a lot of mods and performance gets very laggy above 9GB.

Everyone who can afford that much memory, anyway I would love to run full Ven's but had to trim it down to just the new parts. Too many mods, too many mods...

True enough, cribbing the configs was very straightforward. I would suggest that early-game 3-Kerbal pods (Tantares, Contares Union) might be fair game too. Early Soyuz was contemporaneous with Gemini...

Here we go... KSP loaded successfully, no crash... check. VAB category present... check. Parts are accessible *OOOH, SHINY! * ahem, check. This thing is gorgeous. And it works in 1.3, just as you said it would. Kottabos, where art thou? You ain't gonna wanna miss this...

Sometimes the WBI downloads, based on their respective ages, have different versions of the various supporting folders. This is because angel125 keeps rolling out improvements, and good on 'im. It also means when you install a WBI mod, if you just overwrite everything you may be replacing one of those supporting folders with an older version. Which can cause problems. In my experience that's the most common cause of "why can't I reconfigure anymore?" problems. So when you're installing WBI mods, check the version files and file dates of the supporting folders in the archive to make sure you're not overwriting something new with something old.

Alas, I think licensing issues prevent distributing improved Squad normal maps. A batch process for doing that using open source tools, however... Hmm. And it would work for mods, as well.

Ah, OK. Good to know. It wasn't a request, BTW, rather I was hoping to make an alternate config myself. Maybe not so easy after all, though. But don't worry about that, just follow your muse-- it's already leading you in a very good direction!

Ah, OK. Good to know. I'm a bit leery of dll files compiled for versions higher than what I'm running-- they tend to be rather crashy. Will let you know how it goes.

Sounds plausible. The Vinci has always worked fine with Kemini for me as well. For the official release, that is very sensible. Still, going to keep my own config to personalize my experience I wonder if as extras, more explicit instructions and examples would be a good idea, e.g. "README_How_to_Kemini_Your_Own_Command_Pod.txt" and "Boilerplate_Kemini_config.cfg.ZZZ" Customizing a command pod for Kemini is very easy. But many folks may not realize that.

Both, really, since high memory usage ends up degrading performance in KSP. Especially those pesky garbage collection freezes...

Wonderful idea, looking forward to trying this out. And from the config file, looks like it wouldn't be too hard to adapt this to LH2 either. Hmm...

This is very nice, indeed. And widely applicable which is just as important. A lot of mods could benefit from it. Do you have any plans for a 1.3-compatible version, or would that require work beyond a simple recompile? I ask because I'm still on 1.3, waiting for more of the mods I use to be updated to 1.31. I already have a 1.3 version of TST and would very much like to be able to try out the Webb.

In BDB it's called the "Vinci" capsule rather than "Gemini" If it's useful, here's a config that will add Kemini to all command pods with two or greater crew capacity. That way all suitable pods have Kemini baked in no matter what mod they came from.

find . -regex '.*\.dds' Yes. As I said, it's my habit.

Tried it, compatibility issues with too many mods I'm using. I also avoided RO/RSS, Deadly Reentry, and other mods in the hardcore realism category for the same reason. Will probably try the realism path someday with a more reasonable load order. But this is not a reasonable load order-- it's an "Oooh, shiny!" load order. There are a fair number of mods missing that you might expect to see, because they broke something and got tossed as a result. Or because they're just too big for what they bring to the table. I shifted to memory/performance friendly environmental graphics mods for that reason. The hardest part of this load order wasn't keeping memory use low-- it was figuring out a group of mods that don't break each other. And aside from a few minor quirks, these mods work together pretty well.

I use grep by habit because grep/sed regex is more powerful than command line globbing.

Caveat: Still Running KSP 1.3 (on OSX). Not going to update until more of the mods I use are compatible 1.31. It's getting there. The game becomes very laggy at anything above 9GB or thereabouts, so having 32GB RAM doesn't actually help much. The utility I use is ImageMagick, an open source image modification suite, in particular, the mogrify command: mogrify <filename> -verbose -resize 50% -filter Mitchell -sharpen 1 <filename> This reduces the filesize of an image file by 75%, and the sharpening (high-pass filter) helps offset the quality loss-- somewhat. It works on dds, tga, and png, but not mbm. So to shrink all the dds files in a directory tree, find . | grep "\.dds" | xargs -P 4 -n 4 -I {} mogrify {} -verbose -resize 50% -filter Mitchell -sharpen 1 {} The xargs part is just to distribute jobs across all the cores, which speeds processing. If you're on a PC you'll have to figure out your own scripting approach. This works just fine on the Squad folder as well (dds files), which saves a few hundred MB all by itself. The quality loss is noticeable, but to me is worth the trade-off because more mods. I could probably script something to only shrink high-res files, but have been happy enough with the results (and lazy enough) not to bother. For mbm files, there's another utility: The current version is on Github: https://github.com/krupski/MBM_Utilities Use "mbm2png" to convert. You can then shrink the pngs, but mbm files are so large this saves a lot of space even if you don't. Last, for parts mods I delete the cfg, mu, and image files for every part I don't want. Ditto for Spaces. This also helps with VAB clutter. Here's a mod listing. Some of the really big parts mods are trimmed down to save space, e.g. Contares, FASA, Ven's They play surprisingly well together, but I do get a crash every 6 hours or so mainly on scene transitions. And yes, it does take a very long time for the game to load.

Generally between 7GB and 9.5GB, depending on what I"m doing. I use about 200 mods, but shrinking the image file dimensions by 50% (reduces the space they use by 75%) helps a lot.

Well, with Kerbal Konstructs you can always make your own. Kerbin-side Complete (which depends on Konstructs and is part of Kerbin_Side continued) provides a couple of hangars next to the runway, but also a lot of other things such as extra buildings, bases, aircraft carriers, all over Kerbin. Which may or may not be overkill for your needs. Also KSC++, which may still be overkill for what you're asking...

This might do what you're looking for. Haven't tried it myself though...