[The Wheels on the bus go round and round but turn in wrong directions]

So of course right after I post my question I find the answer: I had a probe core mounted in the center, and didn't change the control point. Once I set the docking port as the control point, everything worked just fine. I'm leaving this up in case anyone else runs into this conundrum. 

[The Wheels on the bus go round and round but turn in wrong directions]

I have a set of tanks aligned horizontal to the ground, on wheels for a base I'm building. I want to land it, then drive it around to dock with the core. I put the wheels on in mirror symmetry in the SPH, but when I take it for a test drive, the wheels turn in opposite directions. I.e., when I want to go left, the wheels on the right side turn to the left the way they should, but the wheels on the left side turn to the right. So the beast ends up going nowhere. What am I doing wrong? 

[KSP not recognizing motorized wheels on base]

I have a contract for a base on Gilly and it requires that the base be on motorized wheels. So I built the base, and regardless of whether I take it out to the launch pad or the runway (to check to make sure I've met all of the requirements of the contract), the program won't recognize that there are motorized wheels on the base. The beast even starts rolling around. I've tried all three versions of the motorized wheels. There's batteries and solar panels galore to provide power.  What am I missing??? 

[KAS: Object that I moved before is now too heavy]

On 9/24/2020 at 9:19 AM, jimmymcgoochie said:

Does the entire vessel highlight when you hold G or H and hover the cursor over the docking port? Do you get an error when holding H and hovering over the port saying the part is a root part.

If Yes to either of those: hold H, hover over the part the port is attached to and then ‘detach’ the whole vessel from the port. That should cause the port to detach and it should then behave as expected.

Your solution worked perfectly. I'd attached the the docking port to what normally would have been debris - it was just a bunch of fuel tanks and an engine that I'd decoupled earlier, and had no command part associated with it. I figure the port became the root part when I docked a vessel to it. Thank you very much for your assistance!

[Duna? Or Mars???]

I think I've been playing KSP too much. This morning the Windows splash screen on my computer showed a gorgeous picture of Mars, from NASA, and my first thought was, "Whoa! Why is Microsoft showing me a picture of Duna????" LOL

[KAS: Object that I moved before is now too heavy]

Thanks for the suggestions. I’ve been offline for several days so I’ve just now seen your posts. I’m still a day or two out before I can give them a try. I’ll post the results. Many thanks!

[KAS: Object that I moved before is now too heavy]

11 hours ago, Superfluous J said:

Is the docking port in use? you need to undock before you grab it, or it tries to grab everything "away from" the root part of the craft you're interacting with.

The only other thing I can think of is that maybe you had other Kerbals around before, and now your engineer's alone. But this sounds more like the first thing.

No, I undocked from the port, and all of the previous times I worked on it (disconnecting from the original, attaching it to the transport vehicle, then reattaching to the new vehicle) had only the one Kerbal to move it. When I try to grab the port, even though I have only the port highlighted in green, when I hit 'G' to grab, the entire ship it's now connected to lights up in green. 

[KAS: Object that I moved before is now too heavy]

Earlier in my game, I was able to use an engineer to grab/detach a docking port from one vehicle, attach it to another, move to a third vehicle, and attach it. Now, I want to move the same docking port, using the same engineer, in the same mission, to another location on the vehicle. But when I try to grab the docking port, I get a 'too heavy' message, as it seems to think that I'm trying to grab the entire vehicle. Restarting the game didn't change anything, and I'm trying to figure out what is different, and (most importantly) if there's a way to 'fix' it so I can detach the docking port and move it. Any suggestions/explanations will be welcome.  

["Unknown Parts Module" error after removing Docking Port Alignment Indicator mod]

3 minutes ago, steve_v said:

You suspect correctly.

Thanks for the quick response... you've seen this before?

["Unknown Parts Module" error after removing Docking Port Alignment Indicator mod]

A while ago I installed the "Docking Port Alignment Indicator" mod, but did not find it very useful, so I've uninstalled it. Now all of my ship files in the VAB that have a docking port on them appear in the 'Open' menu with the error message "Unknown Parts Module" under the part count and cost line. If I select and load one of these files, I get a 'Confirmation Needed' window stating that the vessel has the following problem: "<vessel name> is missing part module ModuleDockingNodeNamed" with OK and Cancel buttons. If I hit OK it loads the vessel, and in the Open menu that vessel no longer appears with the Unknown Parts Module error. 

I suspect this is an harmless error message I'm seeing, but I'm hoping someone with more experience and knowledge can validate that for me before I go further. 

[Is there a way to rename a game?]

5 hours ago, Superfluous J said:

You need to rename it in 2 places. That folder in saves should be changed "so if you named it "my sapce program" change it to "my space program" and then within that folder, find your persistent.sfs file and open it in a text editor. One of the first lines of that will be:

	Title = my sapce program

Change it there as well.

The only potential problem is, if you load a quicksave from before the change the change may revert or something else weird might happen. So either don't do that, or edit the quicksave.sfs file just like you did the persistent.sfs file.

Source: None. I've done it myself with no issues.

Thank you!! I'll give it a shot. Much obliged!!

[Is there a way to rename a game?]

I've been playing a career game for several months, and only now noticed that when it comes up in the menu, there's a misspelling in it's name. Is there a way to change the game's name without screwing up everything?

I found (what I believe is) the game's folder under C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program\saves, but it looks like there's lots of other folders and files that also have that same name as a prefix. 

 

[Cannot delete maneuver node (Control Locked)]

1 hour ago, Superfluous J said:

"Control Locked" means you don't have control of the ship. Generally this means you don't have a pilot on board, and no communications to Kerbin.

I expect all the extra stuff you did only allowed your ship to orbit long enough to re-achieve communications.

Interesting ... I'll start keeping an eye out for that. This is the first time I've flown a ship without a pilot, just AI, and I don't have any commsats set up, so that might very well be it. But in the past there's always been at least one pilot on board. Thank you very much!

[Cannot delete maneuver node (Control Locked)]

In the past I've seen this message sporadically after completing a maneuver, but usually it goes away after I unselect the node, then re-selecting it and trying again. Today it is NOT going away. I've cleared the Input Locks; and I've tried restarting the game, no luck. I need to resolve this move on. 

 

Update: After restarting the game two more times and clearing the Input Locks, I was FINALLY able to get the control node to delete. But this keeps happening, and I'd like to be able to avoid having to clear the input locks each time. Any suggestions?

 

[Space Bar failing to stage]

22 hours ago, Boyster said:

Sadly sometimes it happens, especially when you trying to stage fairings/decouplers, things get wonky.

My suggestion is go with Action Groups and ignore spacebar.

Its more reliable and never fails, so transfer your staging to 1,2,3  buttons etc and it will be as responsive as it can get.

And with the new cool updates you can then edit your action groups in flight so you dont want to worry about that.

Hmmm.... I'll give that some thought. Thanks for the suggestion.

At least the problem I'm seeing doesn't seem to be personal. Much obliged.

[Space Bar failing to stage]

On 9/5/2020 at 10:57 AM, BadOaks said:

That sounds really frustrating. The only thing I can think of is the "insert" key. Is it possible you're pressing that? Or otherwise turning off staging mode (the staging icons go away)?

Thanks for the suggestion, but that's highly unlikely ... on my keyboard, for some reason, the Insert function requires the Fn + PrtSc keys... 

[Space Bar failing to stage]

A mild rant and a desperate plea for help: I've been playing in career mode for several weeks - not a great or super experienced player but enough to know that staging with the space bar is supposed to work consistently, and I'm getting REALLY tired of it not working mid-game, mid-burn, or at random points in a mission. I've not touched the key bindings for staging; I've ensured that I'm not in warp when I try to stage; there's no purple light in the lower left corner; I've ensured I've not pressed Alt-L, and even when staging fails and I try pressing Alt-L it doesn't start working. I've rebooted and started a mission fresh from the VAB, gotten into orbit no problem, set up my maneuver node, warped to the node, stopped the warp well in advance of the node, started my burn, and when it's time to stage mid-way ... nothing. I have to manually decouple, then manually activate the engine. Of course, if I'm planning to decouple during a landing or re-entry sequence, it's even more disruptive. Restarting the game from scratch, or rebooting SOMETIMES resolves it temporarily, but I shouldn't have to reboot in the middle of a game just to get staging to work. Is this just an on-going bug - I've seen it in both 1.9 and 1.10, and seen it on numerous threads elsewhere as I've tried to find a solution. What the HECK is going on? What have I missed? What else can I try to fix this?