ebaydan777

so the original signal does not need to come from KSC? I always thought KSC needed to send to a RemoteCommand which then would send off to 3-4 RemoteControl's orbiting kerbin every 90 degrees. Then on the moon another command to receive from the Command on Kerbin, and Controls to the rest of the mun..

ok so I should just have 1 on my space station (problem is i cant move it and its orbiting to close to kerbin to always be in contact. So should i just remove the remotecommands and only put controls around kerbin, or have 1 command mixed in there too. And would that 1 be the one that I would point at KSC and at my future moon remotecommand, also with a few controls to continue to the route around the mun too. p.s. thank you for all the help, just new to it.

all the remotecommand modules onboard have 3 kerbals on as well, the ones with only remotecontrol are simple probes. But i still dont understand. Do i have too many remotecommands and they wont signal to each other, do I need to replace all those with just remotecontrol modules and only leave one remotecommand? I am confused =/

Hey everyone. I need some help, PLEASE. I am currently using this probe: http://kerbalspaceprogram.com/interplanetary-mapping-satellite-v1-1/ and carrying a RemoteTech Remote attachment as well as the extendable antennae and the RF one. I sent that up after I sent 4 probes up that had both RemoteControl and RemoteCommand modules on them, I thought that this way I could do both. Now I point 2 satellites I have on each probe, where ComSat I points to KSC and the other goes to ComSat II then that probe goes obviously one back to ComSat I and the other dish to ComSat III. And ComSat III would point back at II and also IV. I had this at an altitude of 2868.75km above Kerbin and in 4 quads around Kerbin. I saw no blue line pointing at anything, the only thing I had was my 5th probe with only the RemoteControl attachment that was closest to ComSat III and had a blue line to that device. Why is this occuring?? http://imgur.com/01RABAZ thanks for your time and help!

ok so...I get this when I go to launch. My mechjeb button is Red, I have a RemoteCommand on there and a remotetech macrodish sr. I also have mechjeb 2.0.8 on board (AR202 case). But everytime I launch and try to use my mechjeb panels, it doesn't launch, even if i manually hit space. Why is this? It's almost like remotetech has disabled my mechjeb from operating. Here's my setup up top: http://imgur.com/xMi2j6B And here's the error on the launchpad. Not so much an error but mechjeb stuck: http://imgur.com/Br5TBwT

Well I started at 350km kerbin orbit. I was trying to get to the moon. It sets up the plane alignment and then does a few other things. Then it gets to Hohmann transfer and the nodes state -68years countdown and does not warp. This is the same for whatever target I choose. I then have to manually warp and eyeball on my map screen till im close enough to the target to disengage the rendezvous and re-engage it, sure enough it sees im close enough to the target and sets up what I assume is matching velocity. So that gap in between, theres a bug there somewhere.

hey guys, problem with the rendezvous autopilot in 2.0.8. It gets you to match the planes and set up for hohmann transfer and then says u have 69 years to get close, and no warp. i ended up just warping myself to the meetup spot, then disengaged autopilot and re-engaged, fixed to close approach...