Varsi

User manual says explosives can be attached without tools. And isn't H the attach key? Someone can tell if I'm wrong about that. Can't test this out myself right now.

At least the easiest way to check what mod is causing it (if any, could be something else too I guess) is to make a copy of your KSP folder and start removing mods one by one to find out what is causing it. Someone wiser might know more about this and if it can be fixed with MM patch or something.

This could be due to some other mod. TweakScale for example can cause such issues.

Probably out of this mods scope too. KoS should be able to do this but would need some understanding on how to do that.

Did action groups work with flight computer delay? That probably would be the only way to do this. Don't have time to try it myself and not quite sure how action groups work when detaching parts of a ship.

1.6.9 was the last version for 1.0.5 (mostly working). You can get it here. If you are already using it then there's something else wrong and would need to know more to figure it out.

Actuallly. It seems the distance info and such won't show up in tech tree the way I said to do it so not quite sure if the antennae would even work. Anyway... If you don't want the whole mod you'd have to figure out a way to go around it. The mod author meant to have all the functionality in use.

You could install Remote Tech, then delete everything but "parts" folder and "RemoteTech_Antennas.cfg" in RemoteTech folder.

DP-10 is in a silly place under "Flight Control" I tend to move it Basic Science myself to actually be able to use probes early on. //Edit Maybe the mod designer thought early probes should be thrown to space on a ballistic trajectory and then activated with flight computer but I'm not that hardcore.

You can think of it like trying to call someone who doesn't have a phone. Sure you might send signal somewhere but who ever you are calling won't be answering. The disappearing crafts is definitely a bug that came with 1.1. I had that too but don't know if it has been fixed in later builds. Using Remote Tech is very risky for now as it's currently being fixed by some very nice people and isn't quite there yet.

Communications need to work in both directions so do you have a dish antenna targeted at what ever is targeting your probe? In the image there is a cone coming at the probe but not one going back.

Half a year is "just around the corner" I'm sure. We did get fixes from others so maybe it wasn't that critical anyway. Fixing everything for 1.1 might take quite a while tho with all the changes in stock game.

I do hope they were just waiting for 1.1 release. This never got properly fixed for 1.0.5 after all.

You could try to just copy the KSP to another computer and see if it's stable there. If it's anything hardware related you should be fine then. If you get problems even after that then it'd be a broken installation of the game or mods.

4GB of memory and integrated graphics card (which uses the same memory). People are having trouble with modded KSP memory usage even when they have a whole 4GB of memory free for just the KSP and you are running operating system and such with just that 4GB. So my bet would be memory running out. I do assume you can follow memory usage somehow on macs as well.

No such limit. Any antenna can connect with another as long as both have the range to reach each other. Of course no omni will reach from Kerbin to Minmus other than KSC itself.

Dish antennae have a cone which is pointed at the target. Seems KSC (which has long omni range) is inside this cone. You can toggle the cone display from bottom right corner (that cone icon). So could this be the case? Or do you get connection even when KSC is at the far side of the planet (This could still happen if some other satellite around Kerbin had a cone pointed at minmus). //Edit Another option is that if you use dish antennae to connect satellites around Kerbin to each other then one of those cones might sometimes be pointed at minmus.

Something very different happening in your game. Definitely does not sound normal behavior.

T is probably to stop the Kerbal from spinning when dragging parts. Very annoying.

Ok... It wasn't actually that hard. Here are the values I changed in RemoteTech_Settings.cfg. Latitude = -0.008611111111111111 Longitude = -166.9688888888889 Height = 450 Body = 16 I got slightly confused by the body id not being 9. The correct way to do this would be to create MM patch so these changes would stay even if you update Remote Tech but what are the chances of that happening since It's not even fixed for 1.0.5 yet?

I've been interested in these alternate starting locations so decided to test this myself as well. And you're right. RT doesn't work with Laythe Space Program out of the box. Or rather it does work but the Ground Station is still on Kerbin (or Bin in this case) so making connection might be somewhat challenging. The fix would be to move ground station to Laythe. Ground stations are defined in RemoteTech_Settings.cfg but figuring out the right parameters is beyond me.

The version number in 1.2.4 file name was wrong and instead said 1.3.4. Was mentioned a couple of pages ago in this post.

Try the modified dll by FancyMouse he mentioned earlier post on this page (and has been mentioned on every page for the past for months). Hopefully it works for you. //Edit Seems the link to the file in the old post doesn't quite show correctly but try to manage

I could be wrong but I think modulemanager reads configs in alphabetical order. So if the RealismOverhaul folder is read before RemoteTech then the values from RemoteTech configs would overwrite those of RO. Maybe you could try creating some zzz folder in gamedata and copy the RO_RemoteTech.cfg there. See if that would help?

Scroll up a bit. Check what FancyMouse said and test his fix. You can imagine how old this gets when there are multiple bug reports at github and the same gets asked a few times on each page for the past 4 months or so. The other issue with Science Alert at the same time did cause some confusion. "Active Vessel" -target has been confusing a lot of people. I avoid using it myself. Every network should be built always pointing satellites at each other from both ways (usually I do this by having proper cones pointed at planets and moons).