Kim Hanson

Actually I'm just old and would like to play the release version before I die.

That's right. I haven't played since 0.1.2.0. I wanted to see what progress has been made and as far as I can tell things may have actually become worse. In the VAB, rotating and translating anything not installed on the cardinal directions is quite an adventure. I don't recall it being that difficult before. In flight an unmonitored vehicle may do almost anything. Today it decided to use up remaining fuel thus climbing it to a higher orbit before running out. All the tell tales say it was not powered. Engines were shut down, throttle was not left accidently cracked a fraction. I then remembered to shut of SAS. I like to do this when a vessel has no need for control and thus uses no electrical power for that function. Well apparently SAS was the only thing holding the craft's orientation. Once disabled it began pitching, faster and faster... and faster. I wonder what would happen if I just left it running like that? Would it eventually crash my computer? What would it look like? Would I discover some heretofore unknown effects when reaching light speed? Buggered if I know. Anyway, I guess KSP2 is not yet ready for prime time. Kindergarten seems to be about the right speed for it. I will wait a little longer and try again. Maybe around Christmas. See y'all then!

What did I do today? Increased my frustration level. Watched the game do whatever it wants. Gave up trying to control items that have no intention of being controlled. Watched critical trajectory information disappear and/or randomly change just when needed. Did I mention frustration? I think I will wait for at least two more updates in the hope that by then it becomes somewhat playable. You win this round Private Division.

Oh, I agree! If this was a RL part I would say the feedback system is flawed or still experimental. What I have found is that if your reaction wheel is over powered, it will steady down almost immediately; if it is under powered, it will take a ridiculously long time to stabilize.

I've found the best workaround for the oscillations is to disable rotations in RCS. Use only reaction wheels for rotations and only use the RCS for translations. This smooths things out tremendously but by no means is it perfect. Also saves on monopropellant.

Version: 0.1.2.0 Windows 11 Pro 12th Gen Intel(R) Core(TM) i5-12600K 3.70 GHz NVIDEA GeForce RTX 3070 No mods This has been persistent since the initial release. When orbiting a moon or planet the AP and PE can change, usually downward, especially at lower altitudes. It is as if there is an atmosphere slowing your vessel. This can really raise hob when trying to land especially with tight fuel constraints. The only temp fix I've found is to time warp. Even the minimum warp is sufficient to stop the degrading orbit.

Version: 0.1.2.0 Windows 11 Pro 12th Gen Intel(R) Core(TM) i5-12600K 3.70 GHz NVIDEA GeForce RTX 3070 No mods This has happened with 1.1 and 1.2. First on Ike then on Minmus. If a Kerbal EVAs some distance from the ship, the ship simply disappears. The distance appears to be at least 2 kilometers. I don't know if it sinks into the moon or just vanishes. So not only is one Kerbal marooned with limited oxygen, but two others have been swallowed up by the multiverse. Seems like a pretty shabby way to treat innocent little Kerbals.

Version: 0.1.2.0 Windows 11 Pro 12th Gen Intel(R) Core(TM) i5-12600K 3.70 GHz NVIDEA GeForce RTX 3070 No mods The Poodle engine has control problems. Instead of stabilizing on your intended trajectory with SAS enabled, it wobbles. Usually the direction you are pointing revolves around the intended trajectory but not evenly. Usually it favors one direction thereby pushing you off your intended course. You can control this quite well but not perfectly with manual inputs. I have not tried disabling gimbaling. That may be the best temporary fix.

Version: 0.1.2.0 Windows 11 Pro 12th Gen Intel(R) Core(TM) i5-12600K 3.70 GHz NVIDEA GeForce RTX 3070 no mods Although returning from Minmus is fairly easy, the maneuver planner suggests it is impossible. A retrograde burn will drop you back toward Kerbin and can easily be fine tuned on the fly, but the maneuver planner says you will go into a nearly circular orbit around Kerbin once you leave the Minmus SOI. If you continue burning, the planner says you will enlarge the orbit around Kerbin and eventually exit the Kerbin SOI and go into orbit around Kerbol. This of course is nonsense and no such thing will actually happen, this is just a bug in the maneuver planner for Minmus alone (are there others like this?). This has been persistent since the initial release.

I found that not going directly from flight or map to the VAB is a good temporary fix. I go to KSC first, then to the VAB. I then have no issues with the "M" key.

Version: 0.1.2.0 Windows 11 Pro 12th Gen Intel(R) Core(TM) i5-12600K 3.70 GHz NVIDEA GeForce RTX 3070 You cannot set the Communotron to toggle in the Action Group Manager. You can set it to extend and you can set it to retract, but not toggle.

If you move directly from Flight or Map to the VAB and then eventually save a vessel, pressing the "M" key will return you to the map for that last active vessel. You can lose your save if you are not careful, but mostly it's a PITA. Workaround: Go to KSC then to the VAB.

The wrench icons can persist on your screen in the VAB. They are independent of their proper location in the VAB but instead stay locked to your screen so no matter where you look the icon persists. Not only that they highlight blue when you mouse over them but are otherwise ineffective. When you do need to access a wrench icon it can be difficult to find the live one instead of the persistent one.

"Fixed issue where game switches to Fullscreen upon entering the Graphics tab in Settings" Setting/Graphics reverts to full screen upon loading. It seems this setting is not saved so that when you start a new session you must manually change it.

Furthermore, it can read one value in VAB and another on the launchpad.