Capt. Hunt

same here. I would play it so much more if I could use my fancy HOTAS.

I'd like to know why half of my craft launch as Fly Safe-47 instead of the name I set for the craft? Also, they occasionally just change mid-flight to Default Name-38.

you will soon learn that Kari Kerman is a very enthusiastic character. This message isn't entirely out of character for her.

The mk 1 pod has an integrated heatshield. Although I agree that it might be kinda confusing for new players.

I'm seeing the same thing.

I've seen this too. It will also change the name of your craft to Default Name.

this is why you shouldn't ever just install "tons of mods" all at once. Your best bet is to go through them one by one until you find the culprit.

Reported Version: v0.2.0 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 | CPU: AMD Ryzen 7 3700X | GPU: AMD Radeon RX 6600XT | RAM: 32 gb DDR5 Whenever I load a saved craft, the vessel name resets to "Fly Safe" instead of the name I entered for the craft. Craft name is also not always persistent during the mission. It'll start as whatever you name it, but by the time you stage off the rest of the launch vehicle, what's left of your craft becomes "Default Name ###" Included Attachments: NewWorkspace.json

Absolutely. At the vary least, the AP and PE nodes of the planned orbit should show their altitudes automatically. Right now, plotting a precise orbit involves a lot of back and forth because you have to mouse over the node to see the number. I know you should be able to pin the popup on screen, while you're doing it, but I haven't been able to get that to work reliably.

KSP1 had this, why can't KSP2?

I'm coming back to KSP2 for the For Science update, but I'm rather disappointed to see that the game still doesn't really support HOTAS controls. You can set a single joystick, but it is very difficult to do and overrides keyboard input. I know @Nate Simpson mentioned wanting HOTAS support in one of the early interviews, has there been any development progress on that front? I miss being able to fly my ships with my stick and throttle like in KSP1.

Same here, I'm so used to flying KSP1 and other games with HOTAS that it just doesn't feel right to play with WASD.

Still waiting for the HOTAS fix, but this is awesome so far.

I posted about the same issues a week ago. Thank you for at least verifying that I'm not the only one having this problem. I filed a bug report on the PD support page, you might as well do one as well.

yeah, I'm sure that the devs will release a new Module Manager sooner or later that will supersede both of these plugins.

This is something I just encountered today. My view controls suddenly don't work in flight. I'm not sure of any details for why this is happening or what I did to cause it, just all of a sudden, my view controls totally stopped working.

doesn't the scroll wheel already control zoom?

oh, that's actually pretty cool. That would keep Jeb from flying every rocket like in KSP1. It would be nice if they at least had a scroll bar on the list though, so it was clear that your Kerbals weren't just missing.

Kerbals that you recover cannot be used again, they seem to disappear from your crew roster, and can't be placed in new spacecraft.

I found the Private Division support page and posted these bugs there.

well, I don't know what to say, I can use EVA just fine.

What? If you hang around this forum enough, you'll find that to be a pretty common mistake. Anyway, I'm sure that there's an easy answer that you're not thinking of, that's how most of these things go.

is this KSP1 or 2? In KSP1, you have to upgrade the astronaut complex in order to do EVAs

I'm having trouble getting my HOTAS to work in game. I seem to be having multiple problems here. I went through the input settings and first off it was only reading the axe on my stick, it wouldn't even pick up my rudder pedals or my throttle, both of which work fine in KSP1. It did read the buttons on both my stick and throttle though. it would only let me set inputs in one direction. For example, I would pull the stick back to set pitch up, it would flash pitch down for a split second, but before I could move the stick it would close the window and set pitch down to stick up as well. This seemed to happen with both axis moves and button presses on any bi-directional command, the only times it would let me set both directions was with the keyboard. I tried the second tutorial to test my controls and it wasn't reading inputs at all, this may be related to problem two.

it might be a corrupt file. Delete that part and run a force verify through Steam.