Pilot took control from remote guidance unit

[Zil]

In career mode, I accepted a contract to rescue a kerbal from the surface of "The Mun".  I included a remote guidance unit on my lander, planning to rescue another kerbal in orbit, land on "the Mun", to rescue the kerbal there, and drill and refuel my lander, to dock at my Mun Space Station to leave the lander for future missions, to return in a capsule I had docked at the station.  So the only crew I had at launch was an engineer.  I got to "The Mun" and, upon lifting off of "The Mun", I found the rescued kerbal was a pilot and SAS would no longer give me options for anything but the level 1 pilot.  I no longer could set SAS on "Target", which is important when docking.  Which frustrated my plans!

Is there anyway to switch the remote guidance unit back on when the game gives a pilot the SAS despite the remote guidance unit having better skills?

 

Thanks for any assistance.

[mystifeid]

Seems strange. Have you actually set the station as target ? SAS target controls are not active until a target is set.

[bewing]

Welcome to the forums.

For odd problems like that, often doing a quicksave and then reloading the save will clear it up.

 

[Reactordrone]

That can also be an indicator that you're out of comms range. Rather than give you no control it gives you the pilot's control since they're independent from ground control.

[linuxgurugamer]

3 hours ago, Zil said:

In career mode, I accepted a contract to rescue a kerbal from the surface of "The Mun".  I included a remote guidance unit on my lander, planning to rescue another kerbal in orbit, land on "the Mun", to rescue the kerbal there, and drill and refuel my lander, to dock at my Mun Space Station to leave the lander for future missions, to return in a capsule I had docked at the station.  So the only crew I had at launch was an engineer.  I got to "The Mun" and, upon lifting off of "The Mun", I found the rescued kerbal was a pilot and SAS would no longer give me options for anything but the level 1 pilot.  I no longer could set SAS on "Target", which is important when docking.  Which frustrated my plans!

Is there anyway to switch the remote guidance unit back on when the game gives a pilot the SAS despite the remote guidance unit having better skills?

 

Thanks for any assistance.

In addition to what was said, remember that kerbals are stubborn and will usually refuse to let a machine work when they can screw it up 

 

[Vexillar]

Do you have any non-command seating modules?  If by chance you do [and assuming that the lack of guidance isn't for the reasons above, i.e. lack of comms signal], transfer the pilot to a seat in the back where he can't fiddle with the switches.

[mystifeid]

3 hours ago, Reactordrone said:

That can also be an indicator that you're out of comms range. Rather than give you no control it gives you the pilot's control since they're independent from ground control.

Have to admit I've never noticed that before. It took a little while to set up from scratch and possibly I'm doing something wrong but the screenshot below shows a Level 0 pilot (like one newly rescued), whose SAS skills should not extend beyond stability assist, in a pod attached to an RC-L01 Remote Guidance Unit. Minmus has been targeted and even with no commnet connection, all SAS controls are available and seem to work. EVAing the pilot and re-boarding made no difference.

One extra thing that does affect the ability to actually set a target is upgrading the tracking center from Level 1 to Level 2.

[StrandedonEarth]

It might depend on which pod the pilot is seated in, if that seat gives him the ability to control probe cores once out of comm range. Just a thought, could easily be wrong

[Vexillar]

Does your screenshot look like the one @mystifeid posted? No bars on the comms display means no probe control. 

If that's the case, is the Mun between you and Kerbin, blocking the signal??

Edited September 2, 2018 by Vexillar

[mystifeid]

4 hours ago, StrandedonEarth said:

It might depend on which pod the pilot is seated in, if that seat gives him the ability to control probe cores once out of comm range. Just a thought, could easily be wrong

Tried it a second time with only one Kerbal (pilot) in the pod. No change.

[Xainath]

Got the same problem, fixed by:

First: Check your batteries are fully charged (mine were almost depleted). My remote guide was with 0 electricity and didn't fill up til my whole set of batteries were refilled.

Second: Make your pilot go EVA, don't let him go, just a quick peek outside and make him board again.

My SAS controls where back fully working.

Hope this helps!

Cheers

Edited January 5, 2019 by Xainath