Tarheel1999

You can do whatever you like BUT you shouldn't ask for support if you muck with the files or do a partial install. Doing anything but a complete install voids the warranty.

When it's ready.

The ARM grappler http://wiki.kerbalspaceprogram.com/wiki/Advanced_Grabbing_Unit

No problem

I'm pretty sure it does if you download the correct version. The OP has an update log which states that the most recent version, 2.2, is for 1.2 pre. The download page also makes this pretty clear as well. Try downloading 2.1.

You may also be able to MM the necessary module into the parts you want to have this feature.

If you search for "exception" in the output_log you will see a lot of DLLs are failing to load properly. One of them is AirbagTools.dll. This is the dll which enables the functionality of the airbags. My guess is that one of your mods is preventing those mods from loading properly Unfortunately, I can't tell from your log which mod is causing the incompatibility. KerbalKonstructs might be the problem but I can't be sure. It does state the following in the log: AssemblyLoader: Assembly 'KerKonConConExt' has not met dependency 'KerbalKonstructs' V0.9 (Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 64) AssemblyLoader: Assembly 'KerKonConConExt' is missing 1 dependencies From looking at the forum post for Tarsier Space, I would no longer recommend removing it outright as I see JPLRepo picked it up and has been maintaining it. To try and fix the problem, I would start with removing Kerbal Konstructs to see if this solves your problem. If it does, redownload KK and see if a reinstall will fix the problem. If removing KK does not fix the problem you will need to do a binary sort. Start by removing all mods again and make sure the airbags work. Then add half of your mods to the install and check again. If the airbags sill work, remove those mods and add the other half. Once you find a group of mods that cause a problem, split those mods in half and do this same thing until you find the culprit. You have a lot of mods installed so it's possible there is more than one incompatibility. Going forward I was suggest starting from scratch in 1.2 and slowly add mods as you so desire.

I took a quick look and you have a bunch of Mods that are failing to load properly. I would do two things to start: 1) Remove Tarsier Space. In the past, Tarsier was known to break other mods. I don't if this has been fixed but it had/has a bad reputation. 2) Make sure you are up to date on all your mods. When I have more time I'll take a deeper look at the logs.

Sure. If you scroll down to the logs section of the following link it will tell you where the logs are located. If you put them on Dropbox, google docs or equivalent and link them here, I'll take a look at them this weekend. You can also search them for "exception" to see if you can find the mod causing a problem.

Might be a mod incompatibility. I don't recognize the change name tag in your right click menu. Unfortunately the best way to test for this is to take a clean KSP install and just add this mod and its dependencies. You could also look for exceptions in your logs.

1.2 will not change the way multicouplers work. It will allow you to autostrut parts in flight and in the editor to increase structural rigidity. You can accomplish this now in the editor by strutting across your multicouplers.

Those are parts from the next MKS version.

In 1.1.3 docking ports are not autostrutted. They are connected in flight with a connection appromixating struts. 1.2 introduces the ability to autostrut parts which if used properly will likely address the issues you find in your designs. It will also reduce or eliminate the need to use multiple docking ports for structural purposes. It is highly unlikely that there will ever be an option to "dock" docking ports in the VAB.

Also not a bug. When you connect docking ports in the VAB, they are not docked but are connected by nodes, i.e., "coupled." Once you decouple the docking port in flight it can be "docked". That is how the game works and how it has always worked.

Your choice. It's been a long time since Rover had a save breaking update. If you run a lot of other mods that have regular save breaking changes, that is the price you pay for a heavily modded install. You can of course just play stock. Keep in mind that Rover and most other modders typically don't offer support for older versions.

Multicoupling docking ports and having multicouplers connect to multiple nodes is not the same thing. My point re multicouplers stands.

@Kerbal101 This has always been how multicouplers work. This is less a "bug" that needs to be fixed and more a limitation of the game engine.

@AlewxReading through the thread, I just wanted to make an observation. I think SpannerMonkey was referring to himself and not you. I agree that his post was ambiguous and at first blush it might come across as referring to the mod's maintainer as a "noob" but I think Spanner was saying that he lacked the ability to fix the glitches he was seeing. BTW, I really appreciate your work on Ubiozur Welding.

1.1.3 is nah gonna happen. Roverdude has already said that MKS .50 would be a save breaking update. These parts were supposed to be included in MKS but Roverdude posted them as a separate mod, at least in part, for testing because he needed MM to update before releasing MKS. I have no idea whether this will remain a separate mod as these parts are a core part of his vision for MKS.

@goldenpsp while you're up, I could use a spot of tea and a biscuit.

Copy the contents of the GameData folder to the GameData folder. It's very straightforward.

You put it in the same place it was contained in the download. It's a direct copy into the GameData folder. Just like ALL of Roverdude's mods and pretty much every other mod. Good luck.

@InfiniteAtom Roverdude released this for testing in 1.2 PRE. It will not work properly, if at all, in 1.1.3. A "beta" mod in a pre-release version is not the time or place to learn how to manually install mods. Also I'm assuming that your 1.1.3 install is your main and only install. In this case, the 1.2 pre is not for you either because it will break many of the mods you have installed there.

If you rarely use RCS for attitude, you should consider using the toggles in the right click menu to turn off yaw, pitch, and roll. They will then never fire when using the WASD keys or when SAS adjusts the craft. You can always turn them back on if you need more control.

Maybe but this has not been a PR win for Squad and was completely foreseeable. Even if their contracts were tied to the 1.2 release, I would have expected all or most of the devs to be there until after a successful release. They have all done tremendous work and have left KSP in a much better place than they found it.