Ravlain

Thanks, I'll remember that for the future.

800km?

@MajkI've literally just solved this myself, managed to get the advanced bio experiment back from 180km, 60km periapsis using 3 stacked heat shields. First one fails at around 72k, second around 52k and third doesn't reach overheat. I will admit I used SmartAss to keep it aligned, I'm not good enough to keep things straight without more than stability assist

Aaaargh!! Never mind, PEBKAC detected. Somehow MJ orbit altitude had reset to 100km so first stage was shutting down when apoapsis got that high.

Hi, I've just started running an RP1 game, latest version, and I've hit a bizarre problem when I complete the 2 initial programs and start the light satellites program. Everything was normal up to this point, but after taking the new program most engines I have used apart from the Aerobee have begun to stop with about 10% or more fuel left. This is happening with A4, XLR 41 and the NAA-75-110 amd A6 configuration. All these engines were performing as expected before the program change, but now all stop in simulation and launch, no failure shown. This has now happened on 2 game starts at the same point. Has anyone got any idea how to fix this?

Oops my bad, Alt-x is correct.

Alt-z resets trim.

Have you got trim set accidentally? I think it's Ctrl-x or Alt-x to zero trim.

I'm finding that frequently the DV and numeric burn time show 50% of the correct figures, while the bar at the bottom is correct, so remaining time 0 is when half the bar is empty. This doesn't happen all the time though.

Some additional information for this. After experimenting with editing the save to change the name and state of the craft after release I found that the probe initially has the correct 'Orbiting' status on release, and only changes to 'Landed' when you switch control to it. Hope this helps nail down this annoying bug.

I think the error is the message, I had the message, but switching SAS/RCS back on left the probe controllable (but in a landed state).

KSP Version - 0.11 Operating System and version - Windows 10 64-bit CPU - Ryzen 3650X GPU - NVidia RTX 3600 12Gb Description of the bug. Expected Behavior - Separating a probe from launcher with probe core should leave both in the same flight state. Observed Behavior - Separating a probe from launcher with probe core sets the new probe to Landed, no orbit lines etc are available. Steps to Replicate - Launch a rocket with 2+ probe cores (eg multiple comsat launcher) to orbit. Once in orbit stage away the comsat, the released satellite will be in Landed state. Fixes / Workarounds (if known..) A list of ALL mods. None Other Notes / Screenshots / Log Files (if possible..)

Seems almost random to me, sometimes they work ok, other times revert to default with no indication until my rocket won't turn on launch.

Can confirm this, save and reload needed to get commnet connection after dropping a probe.

Had the decoupler issue with one I built myself as well.

A detailed orbit information window like KER/Mechjeb to give inclination, orbital period to at least the hundredth of a second and other essential parameters for relay networks and such should be added sooner rather than later.

Downloading

Eagerly awaiting the first giant leap for Kerbalkind

Isn't that what the workspaces allow you to do? I'm probably going to build a set of launchers in individual workspaces for each size, then different payloads can be built in the appropriate workspace to drop onto the launcher as needed.

Can't vote None (This field is required)

@kerbnub Go into Scatterer settings (Alt-F10 or Alt-F11 I think) and turn off TAA. Not sure why it's default on 0.772 as it seems totally broken.

@BombaatuTurn off TAA in scatterer settings.

Have you enabled the surface feature finder from the Alt-F12 menu ?

Probably better off removing KerbalRenamer, it seems to cause assorted problems with other mods , and I think @OhioBobis dropping it from the pending update of GPP for that reason. Just delete the KerbalRenamer folder from under the GPP folder.