Probe Control - RemoteTech issue or user error?

[nitefallz]

I had stopped playing KSP for awhile and recently started again, updated the game, the mods, etc.   I remember previously when using the RemoteTech mod, I would remove the mk2 drone core config from RemoteTech_Squad_Probes.cfg file so I could use that as a completely autonomous probe that didn't need a signal back to KSC.  Doing this allowed me to substitute an astronaut with the mk2 drone core and still maintain full control over the spacecraft, stages, engines, etc.  

That no longer works for me.  I get the "Local Control" in red but I can't do anything other than use the flight computer, or the MechJeb functions (if i have one on the craft), unless there's a direct signal to KSC.   Not sure what changed; I didn't find any other config files referencing the mk2 drone core in  a way that I thought might hose functionality.  I reinstalled RemoteTech which added the config back and the behavior is still the same.  Only when the craft has a signal to KSC can I do anything.

 

Anyone experience this?  It's my understanding a drone/probe that's not configured in the files should have full, real-time local control over the entire craft or was that changed in the 1.2.2 update?

thanks!

[bewing]

The one thing that I can think of off the top of my head is that KSP's native CommNet stuff might be conflicting with RemoteTech. What happens if you go into your settings / Difficulty Options, and disable CommNet?

 

[nitefallz]

23 minutes ago, bewing said:

The one thing that I can think of off the top of my head is that KSP's native CommNet stuff might be conflicting with RemoteTech. What happens if you go into your settings / Difficulty Options, and disable CommNet?

 

I got excited when I saw your response, but then saw it was disabled already in the game!

[nitefallz]

It looks like it might've been the Kerbalism mod doing this. 

[nitefallz]

Definitely Kerbalism.

[Zhetaan]

Connectivity in RemoteTech is governed by ModuleSPU (SPU means Signal Processing Unit) and, according to the source, all parts with ModuleCommand must also have ModuleSPU or else they will be controllable in real time.  If deleting the Mark 2 Drone Core line from the cfg doesn't make it function without a radio link, then my first guess is that you have something somewhere that is searching for all parts with ModuleCommand and adding ModuleSPU.

If you can find it, so much the better, but it may be possible to address that with a ModuleManager patch that adds the line:

@PART[mk2DroneCore]:FOR[RemoteTech]:FINAL
{
	!MODULE[ModuleSPU] {}
}

And see whether that does the job.  If not, then you may be best off taking it up in the RemoteTech thread.

Edited June 1, 2017 by Zhetaan

[nitefallz]

1 minute ago, Zhetaan said:

Connectivity in RemoteTech is governed by ModuleSPU (SPU means Signal Processing Unit) and, according to the source, all parts with ModuleCommand must also have ModuleSPU or else they will be controllable in real time.  If deleting the Mark 2 Drone Core line from the cfg doesn't make it function, then my first guess is that you have something somewhere that is searching for all parts with ModuleCommand and adding ModuleSPU.

If you can find it, so much the better, but it may be possible to address that with a ModuleManager patch that adds the line:

@PART[mk2DroneCore]:FOR[RemoteTech]:FINAL
{
	!MODULE[ModuleSPU] {}
}

And see whether that does the job.  If not, then you may be best off taking it up in the RemoteTech thread.

Thanks for this response.  This was one of the first things I looked into.  Once I removed the Kerbalism mod the RemoteTech functionality began working as I had expected.  I appreciate the help!