T the G

As mentioned elsewhere in the thread, the Starlab is only biome-specific in Low Orbit. Once in High Orbit, only one experiment can be performed, as expected. Luckily, the automatic-experiment-resume feature seems to be working well in version 0.2.1, so you can fast-forward time to get tricky biomes like beach (takes several orbits, but eventually it's done). P.S.: To see what region you are over, you can hover over the science icon on the left panel.

Glad this is a known issue, guess I'll have to wait until the next patch to continue my mission. The solar panels stopped producing electricity as soon as the craft entered Jool's SoI. Edit: They started working again as the craft went deeper into the Joolean system, seems to be an issue near the SoI boundary.

I experienced this behaviour too, the fairing would just disappear when trying to close it at the tip, with no clipping as far as I could tell. Sadly I cannot attach a log file (perhaps due to my status as a new member?).

Yep, this bug makes low TWR craft unusable. The tips reported here (like switching to VAB/tracking station and back again) don't work for me. I am now doing a 28 (real-life) hour burn, because I really want to get to Jool with my Xenon engine. With timewarp above 1x, fuel and electricity are being consumed, but the orbit does not change. I cannot seem to attach my bug reports (generated using KSP2_BugPackager), does anyone know how? (Aside from hosting on e.g. Google Drive and adding the link here.)

Indeed, making sure the lander's engines were above the interplanetary tug's stage before undocking fixed the issue for me. Thanks for the tip.

I docked with the engines enabled, sadly I still got this bug. Here is a screenshot of before I realised the engines on the lander were still enabled.

Similar behaviour as described in this thread: I have created a zip of my save/workspace using KSP2_BugPackager, but seem unable to attach it to this post. Any hints?

I have the exact same behaviour. My craft undocked from the interplanetary tug, the two spark engines connected via a MEM-125 engine plate work fine, there is plenty fuel, BUT the DeltaV displayed on the right is zero, and I cannot create a maneuver node due to the "Cannot Create Maneuver: No Fuel" error.

Reported Version: v0.1.3.1 (latest) | Mods: none | Can replicate without mods? Yes OS: Microsoft Windows 10 Home Single Language 10.0.19045 64-bit | CPU: AMD Ryzen 5 2600X Six-Core Processor (12) | GPU: NVIDIA GeForce GTX 1080 (8072MB) | RAM: 32696 Observed when nearing the Mun's surface. Coming out of time warp under 20km always causes a short freeze (like when opening the parts manager), followed by the craft ripping itself apart. It looks as if a huge wobble has occured which tears the craft appart. Included Attachments: Comingoutoftimewarpcandestroythecraft_logs.zip