Sitting Duck

Old news, but I can definitely confirm this. I tested a new rover out on Eeloo, and every 1000m it wanted to spin out (or did)... This happened every kilometer for 49km because I am an idiot. So this occurred nearly 49 times in a row. RECOVERY: I finally tried immediately turning on SAS and selecting Prograde each time this happened (and then disabled SAS), which really helped with recovering from the events. Note that I had a reaction wheel inline with the rover.

Can confirm. Having many files in the Saves folder on Load or Save has the game going "Wait, wait! I need to count all of these files, grab info and thumbnails from all of them, and then display them! Okay, now you can have your game back." Is this really necessary? To correct this I had to select all of my quicksaves and throw them into a backup sub-folder to get them out of the root, but honestly deleting them is a better step. I really despise it when developers decide for you that "quicksaves don't fit our vision of how you should play our game." It's obtuse, non-customer-focused, and frustrating, and can lead to a corrupted save destroying your hours of effort. (See Oxhorn's live, randomly destroyed play-through of Jedi: Survivor). So I really appreciate that KSP2 allows for manual, auto, and quicksaves -- especially with the current state of the game. But maybe quicksaves should be limited in some way. Ten, or a bit more? Or let us configure that? And then rotate back around and re-use them once the limit is reached. FWIW: Reported Version: v0.2.0 (latest) | Mods: Yes | Can replicate without mods? Yes OS: Windows 10 | CPU: Ryzen 9 5900x | GPU: EVGA 3090Ti | RAM: 32Gb at 3600

I will definitely not use this as an easy way to send kerbals on one-way missions to the outer planets and easily recover them when I run out of fuel. But I might do it For Science!

I don't have ready access to an external fileshare. I'd suggest building something simple and then use the cheat menu to teleport it to Eeloo (and others), then do some science, save, and check through that. Or just wait until you get that far in the game.

Cool mod! Very nice work. So, a small issue: Is it just me, or is Eeloo actually missing from the list? I've done science there, even transmitted some back to Kerbin, but there's nothing listed below Jool in my list as I'd expect, and Eeloo doesn't appear anywhere else in the list. See screenshot. EDIT1: Changed the mod's settings to force Eeloo to show up. The mod doesn't seem to think I've been to Eeloo. Current Settings (issue appears): Show only visited planets: YES Show only unlocked experiments: YES Discoverables display mode: CENSORED I can see Eeloo listed when: Show only visited planets: NO EDIT2: Also, I've similarly been to and have done science at Pol and Laythe, but they don't show up either, even though they should—same issue as with Eeloo. Only Vall and Tylo appear as they should, even though I've visited and done science at all of Jool moons and all other planets and moons except for Bop. All other planets / moons appear as they should.

Related: I've had trouble trying to steer anything with wheels, and dug into the keybinding, including resetting my changes to default. Wheels (at least for rovers, so far) are hard-locked to WASD, which is on the entire opposite side of the keyboard for me (I am a lefty). There are no binding options in the Inputs to affect anything wheeled. I'd be fine with editing the bindings in game files, if that's what it took, but there's nothing to be edited for this.

To me it's unintuitive because we would not stop our ascent or descent in the real world to switch between ladder sections unless there was a good reason. And when we can align the ladder rungs in the game, there is no appearance of a good reason to be forced to stop. We would simply continue down the next rung. And also because many of the players of KSP2 also played KSP1. This is a given.

Confirmed this issue as well, it caught me off-guard and I really had to work at it to work around this when climbing down or especially UP the ladders, since the resolution is not intuitive. Regardless of whether other people find this annoying or not, it should be fixed.

Reported Version: v0.2.0 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 | CPU: Ryzen 9 5900x | GPU: EVGA 3090Ti | RAM: 32Gb at 3600 I can confirm that this happens every single time I load the game. That's it--quit and reload the game, and then it's as though I have not gone through and changed 90% of the default key bindings (I'm left-handed). Once I go to Settings and just click Input, the issue resolves. This has been an issue since Day 1. I even reported it directly to an engineer in Feb/March 2023, who opened a bug for this.

Just chiming in with the masses. I am guessing that my PC stats will not matter, by now. I landed on Gilly and planted the flag to receive this Flag Pol achievement. FWIW I had watched a player on YouTube the day before plant a flag on Minmus to receive this achievement...

Just throwing my support in for this one, since I can replicate it. This is really annoying, and happens to me regardless of what I'm attempting to intercept. The issue isn't just with the approach markers: When those actually do appear, they often block inclination indicators for targeted orbiting bodies, which just disappear and reappear when they feel like it. As all of these markers move around, their connecting lines also criss-cross each other and overlap other markers at random when planning a maneuver or actually perform one. It all makes for a really visually confusing, non-usable mess. Not that it helps, but my specs are: Reported Version: v0.2.0 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 | CPU: Ryzen 9 5900x | GPU: EVGA RTX 3090Ti | RAM: 32GB

Reported Version: v0.2.0 (latest) | Mods: none | Can replicate without mods? Yes OS: Win10Pro | CPU: AMD Ryzen 5900X | GPU: EVGA 3090Ti | RAM: 32GB @ 3600 Title: Keostationary Orbit mission description says "geostationary" Specs: NOT INCLUDED. This is a text correction issue, not a gameplay issue. Severity: LOW Frequency: 100% Description: I was glad to see you titled this mission Keostationary Orbit instead of Geostationary (I suggested this in the forum many months ago). However, the Description section body text says "geostationary orbit" instead. That's it! Something super-critical for you. Included Attachments:

Marketing will always be the enemy of "well-informed". While there are great things about KSP2, the promotional video for KSP2 so far is nearly the best thing about it, and only served to distract from the shortcomings of even a "good grief this is too soon" alpha release of the game into Early Access. I know someone who very recently was jettisoned by Intercept (more than likely by C-level decree). While this friend could not relay anything sensitive to me, I at least had somewhat of an insider's view to inform me, so I had no qualms about allowing my brother (not my friend) to gift the Early Access game to me. Even so, it's been a very disappointing release, still is, and is even more so now in some ways. I really, truly hope the best for this game: for the sake of the people who work so hard on it, for the entire community surrounding KSP, and for the people who have shelled out what is universally considered to be far too much for an alpha-level Early Access release that still has a long, long way to go. Perhaps when we hit v0.1.5, the game might reach a level where the fun outweighs the frustration.

Thanks! Yeah I have that installed, but it just doesn't have the kind of control I want that the KSP1 maneuver panel has, at least not for what I'm doing at the moment. I'll give it another go.

Rude, unhelpful, spiteful, and counter-productive. Try to remember that there are people on the other end of your commentaries, and that you are not them, are not there with them, and are not subject to the specific challenges, trials, and limitations they are faced with.

Seconded! This is a very useful feature in the KSP1 maneuver panel, and since we don't have that yet in KSP2... We are eventually going to get a maneuver panel in KSP2, right?

Wow, that ship is like a blowtorch in reverse. Nice! I can hardly wait to (perhaps accidentally) subject kerbals to those flight stresses. Only because I know they'll be absolutely, perfectly safe.

I've been running this since before Patch 1 and haven't experienced this problem. Just tried again and confirmed not an issue with the scaling set to 80% (2560x1440p). I'm wondering if one of your other settings is having an impact on this. Let me know, and I can post details of my visual setup. Basically, though: I'm at 2560x1440 (on monitor #1 of 3), running Windowed with the following Steam (KSP2) Launch Options, which disables the launcher and lets me move my mouse outside the KSP2 window in Windowed mode: "D:\GAMES\Steam\SteamApps\common\Kerbal Space Program 2\KSP2_x64.exe" %command% -popupwindow

That is a LOT of fixes. Thanks very much, everyone, for your hard work!

As the game stands right now, you're likely running into several issues: Your CPU is fine, above the minimum spec, but the GPU is borderline, if not below the minimum spec. Seems likely to me that you're bottlenecking at the GPU. It's not a surprise that you're seeing low frame rates, since many people with faster rigs have reported the same. The game has not been graphically optimized yet in the way Intercept is aware it needs and has stated that they're planning for. Right now, the game is just not where we'd like it to be, and likely won't be any better in that regard if/when the Patch comes out on Thursday 3/16. Optimization wasn't on the published list of fixes this time around, and IMO won't be on the next, either. (I could be wrong.) When you have many parts in your build, and/or you're looking at something that's currently graphics-intensive (like Kerbin) you'll take a hit to FPS. The game will be better in time, but at the moment with the hardware you have, there unfortunately isn't much you can do to improve the performance that you haven't already done. Waiting is something we all have to do at this point for a better experience. Again, unfortunate, but it is what it is.

Hopefully you're referring to this (#2 in screenshot). You'd think the boosters would align and clip on correctly, but no, they just swallow the bracket and hide them. This is something that vexes me in both KSP1 and KSP2. 1) Perfectly aligned boosters (the way they should look). 2) Engines overlap the mounts even though they are correctly aligned. 3) So when attaching something like a booster to the mounts, try attaching it further down until it pops out and connects to the surface of the mount as it should. 4) Then use the adjustment tool to move it vertically on the mount to where you want. Make sure it's aligned and attached at this point, otherwise moving them with the tool won't help.

Don't know how you came up with Earrestrial, but: Terra = Latin for "ground" = Earth. We are Earth people, from Earth like everything else on Earth. In English we use the word Terrestrial (as in the screenshot), not Earrestrial. Kerbal = derived from "Kerbin" (possibly vice-versa, either works) Kerbol (the sun) = derived from "Kerbin" or "Kerbal" and SOL, which is the Latin name of our Sun. SOLar system. Ker is obviously being used as a root name. Kerbin kerbal Kerbol Kerman So: KERestrial rather than TERRestrial, because that's inline with how the game rolls. At least to me. It's a suggestion and nothing more.

Or am I just being super cheesy? (Apologies, intended this for KSP2 Suggestions and Development Discussion)

For every game I own, I re-bind All The Keys, and it's very apparent in KSP2 when I launch that the keys sometimes don't work, period. (I use the numkey pad for flight and EVA). To fix, I pause the game and go to Settings > Input and click Apply Settings, and the keys work again. Anyone know if there's something else going on here that I'm not aware of (other than a bug)?

Yep, my bad: used the wrong term. I used a decoupler. My next step is to try an actual separator.