Good start but much to do.

[boolybooly]

There is a lot to like in KSP2 launch version and I enjoyed getting Jeb to land on the Mun and back to Kerbin by the skin of his flight suit. Graphics are lovely. Fuel balance seems interestingly different from KSP1 but there are bugs interfering with gameplay.

 

I have to say I noticed quite a few things that deserve fixing. I am sure intercept devs know this but I will try to be useful by itemising the ones that I encountered as a player and which stuck in my memory.

Firstly the Kraken is alive and well and living in low Mun orbit. I noticed creeping PE and AP values in low Mun orbit below 20km, also apparent tank draining after lift off to return from Mun, even in timewarp, when engines were shut down by pressing X, which continued until above an altitude of about 20km. This cannot be atmospheric drag from a light atmosphere as the engines were shut down, so there is a bug in the midst of low orbit calcs.

Could not double click the Mun to focus on it in map, unlike Kerbin and unlike the tutorial advice, had to right click and select focus for the Mun.

Also the ship just exploded spontaneously in low orbit when applying time warp during a fairly swift rotation and then coming out of timewarp. Just blew apart, spaghettified. Luckily I was able to reload. Fairings (interstage scallop type) also repeatedly jumped about as they drifted away after separation.

I got a vessel recovery tutorial message on landing on the Mun. Surely you should not be able to recover a vessel from the Mun (I didnt try) and the message should only apply on Kerbin?

The navball is illegible at 1080p. Cannot read the numbers properly, they are too small and are pixelating. I would comment there is a lot of navball display area being wasted with thick black empty borders, which we dont need and the navball could probably be >10% bigger if these were removed, the other indicators in the central roundel optimised (moved out and slimmed) and the numbers  on the navball given a larger font too. The peripheral shading/dithering on the navball to indicate spherical shadow doesnt work very well as it is obviously pixel sized black dots when the shade of the ball hue needs to be greyed. Wrong effect is being used here imho.

EVA input control settings have the jetpack RCS down button hard coded to left CTRL. You cannot change it to any other value. I usually set mine to  E and up to Q. You can change the up key from left SHIFT but for some reason not the down key. Looks like an oversight. 

That will do for now, looks like you have plenty to do but I will try to help. 

Edited February 24, 2023 by boolybooly

[Fluke]

28 minutes ago, boolybooly said:

The navball is illegible at 1080p.

Definitely agree. Lots of pixelation.