BananaDealer

Yeah, QS can wreck havoc when they're not connecting "properly". Avoid connections where the blue line is on the edge of a corner (if it goes past a corner, you're in big trouble).

I think something like that was suggested before. Not sure on whether it went anywhere...

Like I said, you only ever need one version of the C++ redist (either 32bit (x86) or 64bit; versions from different years notwithstanding). I'm not excluding AVG preventing things from being ran in your KSP folder, even when whitelisted (as anti-virals can be weird sometimes). I do hope you're not now running without an anti-virus however...

You can't have "both" Visual C++ versions. Either one or the other. Otherwise things get wonky. Uninstall both and reinstall the x86 one.

The .dll is supposed to be in the root /GameData folder of your install. Make sure you have the correct Visual C++ redist. Your system may be 64bit but you still need the 86bit one. Other than that, make sure a firewall or anti-virus isn't blocking either the .dll or KSP altogether. Win8 is a bit picky when it comes to running "unknown" things... Also make sure you have the latest .NET Framework version.

Hmm... Interesting...

Might be a good idea to have a direct link to the download on the OP, rather than to have to go to a separate site. I get the idea you want to have your own thing, but from a product stand point, ease of access generally means better... um... sales, downloads in this case... Also a change log in the OP. That's pretty much a must-have. As well as version numbering in the title (and maybe last date of update) so people can easily figure out whether there's been an update or not.

Great... More maintenance... Well, better get on that...

Oh, sweet! Is this definitely gonna break craft files?

Get well soon, dude!

I have... And as I said, I'm not actually sure that it's LOD causing the loading issue- might just be something gone wrong with the vessel that's freaking out KSP...

I thought LOD was compatible with the latest ATM...

My game outright doesn't want to load without LOD due to the 2210 textures I got on, even on Eight Res and with Aggressive Texture Management. And I'm not actually sure it has trouble loading due to LOD. It might be something to do with the craft in question getting somehow broken. I've got a thread about it, here: http://forum.kerbalspaceprogram.com/threads/77313-Station-failing-to-load Crashes (in VAB) however are definitely due to LOD.

Also, Lack, could I maybe ask you to make a 6-nozzle version of your engines (with thrust relatively the same as the Skipper, maybe somewhat less)? Preferably 2.5m in size. I kinda want one for my Soyuz-alike.

Finally got around to updating the Taurus mission! Also, OSS-02 "Galactica" Launched: 20/04/2014 Launch System: Shuttle MET: 3 Hours 20 Minutes (At 00:19 PM BST; 23/04/2014) Status: On return to Kerbin. Crew: Jerny Kerman- Mission Commander Eddos Kerman- Mission Engineer Kirdon Kerman- Mission Specialist Mission Description and Parameters: After the crash of the "Orca", the Cabana Corporation's Space Exploration Program needed a new Orbital Supply/Service Shuttle. The "Galactica" was built in the wake of the "Orca" incident, both suffering from the massive public support pull-back and benefiting from the heightened safety requirements. The "Galactica" is also the first OSS to feature the newly developed "Articulated Robotic Manipulator", "A.R.M." for short. To allow for the manipulator's safe operation, the layout of the shuttle's payload bay was changed to have supply mounting equipment only on one side. A specialised tethering mechanism was also added to help secure both the "A.R.M." and the normal payload of the shuttle. The objective of "Galactica"s' maiden flight was to deliver the "Atlas" Z-0 Truss piece to "Horizont" Station, as well as test the "A.R.M."s' capability of performing an unassisted mating of station components. Mission Log: The ascent of the flight was somewhat shallower than originally planned. The shuttle's orbit was partially circularised using leftover fuel in the external tank, before it was drained and decoupled on a reentry trajectory which would leave it to burn up somewhere over the desert. The rest of the circularisation burn was performed using on-board fuel. Transfer window to an orbit to match the Station was done after two periods of the parking orbit of 250km. While on approach to "Horizont" Station, the Station dropped out of all communication channels without any explanation. When ordered to pursue the anomaly, the "Galactica" reported not being able to acquire a visual image of the Station, even though guidance equipment reported it being there. Upon asking for further instructions, the crew of "Galactica" were ordered to transfer to a 200km orbit, scuttle the "Atlas" Truss and then return to the Space Centre.** Documentation: ** Yes, this is what I'm going with.

Yeah, for some weird reason the backup doesn't work as well... I'm suspecting some part on it got its parameters changed and the game is getting confused...

Hey, at least it's not your entire damn station that you've been working on for the past couple weeks...

Dammit, Lack! Stop breaking the game!

Aw... Well, good luck on your other projects! Please continue development of your Bingo cockpit for B9's HL fuselages...

Yeah, I've noticed that as well. Currently that's pretty much preventing me from loading my main station. It's chugs at about 3GB RAM usage and then KSP just freaks out and crashes...

I don't know, I'm still getting a lot of loading and crash issues with 2.2. Granted, I'm on 2204 textures as of this post, so I'm guessing it's expected... Most of the issues are when I'm in editor, the game runs pretty solid otherwise. I'm currently experiencing some nonsense trying to load my main station (the game just outright refuses to load and freezes, even on the lowest res settings) but I can't say for sure that's due to LOD or something else...

Sorry there's been no recent updates, I'm currently having issues with stuff loading properly...

The small blanket array gets stuck quite a lot at times. Most recently on my Asteroid Observation Laboratory (check my News Network in a couple hours if you wanna know more) where it just stood in its' "neutral" state, while the array on the other side of the AOL rotated normally... It's not a big deal as just pulling it back in and extending it again seems to fix the issue...

They do get stuck quite often though...

What's this? A working release? Just as my asteroid redirecting project was getting into Stage III? Thank you, sirkut.