W2D2

Same here. After returning to KSP 2 with new hopes (being at patch 1.2.0 and all) I hoped I could get to MOHO. I built a big-ass rocket ... Pressed "Launch".... anticlimax.... nothing Rocket has multiple stages and is something completely different than what alex built, yet same issue. (BroTip: Alex if you put a wheel at the back, you are probably going to need canards to get off the ground. Scott Manley has a great tutorial on SSTOs)

I'd like to amend to this bug. Also have the issue with throwing away a fairing. When you grab it you cannot put it in the trash. (v1.2.0). When you move the mouse it lights up the red "trash" option but you cannot throw the part away when the mouse isn't moving. If you succeed in throwing it away it glitches th UI and leaves the fairing edit icon in screen So please take a look at fairings in general. The bugs are very obvious.

I think the bug is highly likely the priority order of part actions. Burning engine, then decoupling -> explosions Decoupling, then burning engine -> happy staging

Just dropping this because it could be the reason we are spinning out of control... I'm going to be testing the setting when I have some game time...

I've seen that low-quality effect when my laptop wasn't plugged in. I think it's the game coping with dropped frame rates when my 3070 mobile GPU can't handle the load on battery power. I'd turn on the FPS measurements and take a look at your frame rate. I'd turn off pc power balancing mode and put it on high performance. I'd check my drivers and update if available. I'd plug in power if it's a laptop. My 2cts

I'm in Fullscreen and windowed mode at the same time. Something is wrong but it doesn't make the game unplayable for me. I'd call it a cosmetic bug...

Looking at your pics it seems that you are not yet staged correctly. The engines haven't fired up. either fire them up manually or press space bar to go to stage 4. That said I have yet to stage anything without exploding

Yup kind of sounds like the bug I just experienced, here's my similar account. Finally after fighting all the bugs to get to the Mun... this alone is stupid because on KSP1 it was a breeze, in KSP2 it's stupidly hard bacause you fly blind with manouvre node dragging that's as coarse as a freight train and impossible to fine tune. Also no idea what will happen in the target SOI... no idea on burn time... no idea on TWR.... but back to the issue at hand... Got into an orbit at 80km or so. Lowered periapsis to 15km and then my ship started to spin like a cotton candy machine. Spinning was straight on an axis, so going directly over the north and south of the navball. Pressed 2x warp to straighten out the ship (glad this 'feature' still exists) and when going back to 1x warp it starts rotating again. Things that could be happening are... Medium reaction wheel bug? Mun physics somehow getting mixed up with Kerbin? Anyway I thought, lets get rid of my lower stage (which was way overkill to get me there), however the decoupler didn't decouple the ship, parts flew off and I blew up .... :-( Other than that, the game has tons of potential and the graphics are great. Waiting for the first updates :-)

There is a limit to dV (17238 for NERV)(58k for Ion) I’d guesstimate approx. half is feasible with a payload and a TWR of just under 0.5. So aim for 8k-10k dV. This thing will weigh as much as a small moon and be just fast enough to be under 10min burns source: https://wiki.kerbalspaceprogram.com/wiki/Cheat_sheet

Method used by many: Launch in pieces and construct in space above landing site. Add boosters with decouplers to your design for landing (chutes if there was an atmosphere). Add sturdy landing legs. As stated use throttle limit to balance. Once landed decouple and shoot off boosters to never never land. Turn off all reaction wheels to prevent the Kraken from exploding base components. P.S. Assembly on surface sucks unless you have a tested and tried system for aligning docking ports.

Gilly. Basically anything that can land on Minmus can land on Gilly. Gilly has the lowest gravity so you can land and take off with an EVA jet pack.

Ok I came here bacuse I had the same question. I then accidentally developed a possible method at Pol which works on 100% stock . I had to edit this post once I figured out the science. In your left bottom widget there is orbit info showing periapsis and apoapsis info. There is a second tab in there giving you more info like inclination which is highly likely not zero. I believe you want this to be zero 0. You have your LAN value (longitude of ascending node) which tells you where your ascending node is in degrees which is an angle from a reference direction which I believe to be the direction of travel of the moon/planet (still not 100% sure if this is the case). So the way to do this is to zoom out until you are above the orbit. Make sure the orbited planet/sun is on the left, and your spacecraft orbiting the planet/moon on the right. Up should be the orbital path of the planet/moon. The number of degrees is measured counter clockwise around the planet/moon you are orbiting. 0 degrees is basically the point on your orbit that intersects with the orbit of the planet/moon you are orbiting. Now eyball the location of the ascending node and warp there. Then burn normal or anti-normal to correct the inclination. The LAN will shift with every burn so you will need to correct in multiple burns to get inclination down to zero,. Alternative Method: Zoom out until you see your elliptical orbit and the orbit of the planet/moon. Move your camera to squash down the planet/moon orbit into a line. Imagine that line going though the planet. Where your orbital lines cross that line should be the ascending/descending node. (Because your orbit will still be seen as an elipse you get two points. This method only has a limited resolution but I use this to figure out a good enough correction when entering an SOI (when inclination adjustments are still cheap) Hope this is a solution for your question, and I explained it sufficiently....