Ald

Damn, @linuxgurugamer you must run on BATT-MAN batteries. I was missing this tool so much. Big thanks from me for reviving this.

One question. How do two mods interact with eachother. As I do remember "HullCamVDS" had first person view, but what happens if you add "Through The Eyes Of A Kerbal (1st person EVA) continued" to the mix? Can they coexist? I persume that there should be no conflict (C button and clicking on kerbal). But you can never be too sure. I'll check it probably, but perhaps some of you may already know the answer.

I do remember this backpack had an working antenna Sadly it is covered with a lot of dust.

I really liked the ability to select target for the dish. And the remotetech specific dishes/antennas. But yeah that would pretty much cover it. Also I'd like to remind you all, that Kerbinside had some preparations for openable new ground tracking bases.

No link = no control is included in stock pre edition. Just go to advanced options and turn off partial control.

Indeed, the spacedock version is outdated. Just take it from the source.

https://d-mp.org/ -> Download the Server -> 0.2.3.1 both client and server. I don't see any problems with it.

Ok so we stay with binary 1-0 signal presence. But why not to adapt the signal strength as a trully informative parameter? You'll know if you're reaching the limit of your vessels comm instruments, by watching the percents go down. It could just calculate the effective range, showing you when you'll pop out of range - leaving you enough time to do some preparations (such as sending a kOS program or leaving a set of maneuvers to the flight computer to be executed while you loose signal). Occulsion would be the only thing that would bust your signal from x% to 0%.

If I had to guess: RT has pointing the dishes mechanics, which stock will not have. Big +1 for RT for me RT has a flight computer, stock does not. +1 RT doesn't have such thing as signal strenght, that would be a cool thing if merged from stock in a good way RT has signal delay - if you want to punish yourself with remote control on anything further than Kerbin SOI Perhaps some tweaking in dish antennas to have relay compatibility Rewriting big chunks of code, to use stock API for communication mechanics, while keeping the callsign features of RT And keeping it unforgiving for not deploying antennas in time or messing up with the range. That is the thing I love the most +999(9) As for me, this is a no brainer. I adore RT and pretty much refuse to play without the mentioned behaviour Also I have those wild, wild dreams of integration between RT and Kerbinside ground tracking station bases (only way to emulate it with a hardcoded custom config atm). That would make the communication pretty complete for now (unless some wilder dreams appear).

The thing I mentioned will eliminate the spam and slowdown. Big lag spikes will be the garbage collector mentioned by steve_v. Try both solutions.

No, it won't, and definetly it won't break it. At least it didn't make anything go bad for my save. If you're unsure, just check it on a seperate installation of KSP (distant object + cacteye without the hook) Also from readme for "DistantObjectHook": The thing I found and belive to be the closest to explaining the issue between the two mods:

Somewhat similar

That is the DistantObject hook that resides in Cacteye. It is hard coded to a specific version of DistantObject. If DistantObject gets an update, the hook goes all funky spamming exceptions (and slowing the game), because it expects an older version of DistantObject. The fact, that versions don't mach, creates this error. You have few options with this: 1) Delete the cacteye hook dll 2) Wait for Cacteye to update the hook 3) Use an appropriate version of DistantObject that matches with the hook.

KSP64bit +/- ~23 minutes (with precached module manager patches) installed addons 123 - lots of parts and heavy graphics ModuleManager: 29814 patches applied 175 folders in GameData (3.83GB) - excluding SQUAD folder Phenom II x3 720BE ~2.8Ghz 20GB DDR3 RAM (2x4 + 2x8) Windows 7 64bit MSI Radeon 7850 2GB 1TB WD Blue HDD 8.9GB of RAM usage in main menu The load time doesn't hurt that much - I just do other things while it loads. The thing that actually hurts is the scene change times. If you want to hop between scenes frequently - that is somewhat of an annoyance. Thus I do wonder if a switch to a more modern processor (like i5/i7 skylake) would dramatically change things for me.