mr_trousers

Sorry for vanishing - I've been out of town a couple weeks. Here are the ksp and output logs. I loaded the game up, loaded the craft in question, messed with the reaction wheels a bit and tried to move it around, tried to turn on SAS, then left the game. I'm not stage-locked intentionally - not actually sure what that means. Remotetech is on, and I do have a signal. As I said, I can wrest control away from the reaction wheels to some degree by messing with their settings, so it's not as if it's completely unresponsive, it's just fighting me. It is a career save. I don't have any maneuvers set up, so I'm not sure what it would be trying to point towards if I did have mechjeb somehow trying to take control. Let me know if there's any more information you need - this still has me stumped.

Not sure which log you wanted, here isModuleManager.log and MMPatch.log. I'm also not sure what I could show you in a screenshot, a video may be useful but I'm not sure how to take one of those, you won't exactly see what's happening as I describe it in the op in a still. But here's the craft, if that helps: Mechjeb is installed, but I don't believe there are any mechjeb parts on the ship, unless probe cores come with it automatically. At the least, you can see in the screenshot that mechjeb autopiloting isn't activated or anything.

I guess I'm a little confused how range is calculated, maybe you guys can explain where I'm getting it wrong. I'm using Remote Tech with the root range model activated, and as suggested, turned range of all antennae down to 0.5x. I have a small constellation of 5 relays with Communotron 16s (range 1.25 Mm) in a pentagon around Kerbin at 1.2Mm orbital altitude. I put another satellite in a polar orbit with a Communotron 16, so it can communicate with the constellation around Kerbin, and then a Reflectron KR-7 (range 45 Mm) pointed at the Mun. I then sent out a probe to orbit the Mun, also equipped with a Communotron 16 (just for maneuvers near Kerbin) and a Reflectron Kr-7, which once I got underway I pointed back at Kerbin. The Mun is at 11.4 Mm from Kerbin, so my probe should lose connection with the pentagon contellation of omnidirectional antennae satellites at around 8.75 Mm away from Kerbin - that's given by min(45,1.25)+sqrt(45*1.25), which should be the range the Communotron 16 and Reflectron KR-7 can communicate. The probe's only connection should be with the polar orbit satellite that also has a Reflectron KR-7. But what I'm seeing is that even in orbit around the moon way out at 11.4 Mm, well past the limit of 8.75 Mm, it's still communicating with all of the omnidirectional-only satellites as well. How could that be?

No idea what's going on here, but my latest probe seems to have its mind made up of where it wants to be pointing and won't take no for an answer. The probe is equipped with: A dish antenna and an omni antenna from Remote Tech (Reflektron KR-7 and Communotron 16) SCANSat Radar array DMagic's magnetometer boom Probodobodyne OKTO probe core Small inline reaction wheel Two OX-4W 3x2 solar panels A Universal Storage core with four fuel tanks strapped to it, plus a couple other fuel tanks total 48-75 "Spark" LF Engine A handful of batteries And that's it. Everything was normal for the beginning of the launch, I was headed to Minmus to do an altimetry scan. Once pretty far out there, it started acting strangely. I can't activate SAS, for starters - when I press T, it flashes on for the briefest moment before being shut off again. I can't use the reaction wheels to change the direction of the probe at all. It seems like it's fixed on one point and won't give me control. I've managed to get it to move by right clicking on the probe core and the reaction wheel and messing around with the reaction wheel setting - changing it from "Normal" to "Pilot Only" and one to "SAS Only" seems to allow me to change where it's pointing, but within a few seconds of me moving it, it starts trying to take back control and move it back to where it wants it pointed. I managed to keep it mostly under control by turning the reaction wheel power way down, but then when I activated my engine for my burn, it used the engine's gimbal to try to move it to where it wanted it to be pointed as well, ignoring my input and the fact I was trying to point at a maneuver node. It's like I'm fighting against another pilot in the ship. And even though I can wrest some control away, when I change the settings of the wheel back to "Normal" it immediately snaps back to where it wants to be pointed and I can't move it at all. Any ideas?