Poppa Wheelie

That's correct.

I really like this for planetary transfer planning: https://alexmoon.github.io/ksp/ It was built for KSP1, but also works for KSP2. However, keep in mind that this tool assumes the first year is Year 1, while KSP2 assumes the first year is Year 0.

How accurate is the trunk?

The showers in the Ramstein AB gym (1996 - 1999) had only one control: a push button. Pushing the button gave you about 30 seconds of shower (preset temperature and pressure). After 30 seconds the shower flow stopped. Take however long you want to lather up. Press the button again for another 30 seconds at a time to rinse off.

Nope, sorry. It doesn't work fine. In the "solution" I showed above, it worked because the decoupler and fairing blew up and were destroyed when they hit the runway behind the vehicle. If I look at the Tracking Station after they've blown up, I see 3 objects: Test Rig-1, Default Name-2 (the second ship), and Default Name-3 (the decoupler facing Test Rig-1. In orbit, the fairing and decoupler continued flying behind the second ship (Default Name-2). Since they never blew up, I don't get a Default Name-3 for the first decoupler which is sitting there. I also have no control over the second ship. So, back to square one. I don't know how to work around this.

I want a different type of multi-player experience than has been discussed so far. I want to be able to put 2 people into 2 different seats in the same command pod in IVA. We'll cooperate that way. With VR would be even better.

This same scenario has been reported for returning to Kerbin from Duna. I don't know if there are other planets with the same issue.

@FreeSpaceIndustry, would you please configure this mod for CKAN, which now supports KSP2? Thank you!

@bbepis, would you please configure this mod for CKAN, which now supports KSP2? Thank you!

@Halban, would you please configure this mod for CKAN, which now supports KSP2? Thank you!

I would like this, too. Until then, I use an Engine Mount above the Heat Shield.

I posted a response to the same thread you linked to. I think this should work for you.

I think I have the workaround for this. Bottom Line: Use two decouplers - one at the bottom of the fairing facing the Engine Mount, and one below that facing away from the Engine Mount. I tried separators here, no luck. It only worked for me with two decouplers. We have situations where a single decoupler below, and facing, the Engine Mount works fine. The stock K2 rocket, for example, uses this configuration to get to the stage 3 engines. My guess is that we introduce the problem when we have control nodes on both sides of the decoupler. Do you have a probe core under your decoupler? I reproduced the problem with a test rig on the runway. This test rig is to demonstrate that my exact scenario could be reproduced, and fixed. I needed the exact parts you see here, in this order, and I needed to start with 2 kerbals on the right side and move 1 to the left side before decoupling. I didn't know what was breaking, so I reproduced the sequence of events. Even so, I think this is the same problem as you are having, and I think the solution demonstrated below should work for you. Here's a demonstration of the solution, using the same test rig on the runway Finally, I put a ship in orbit and tested the same solution there. It worked fine. I wanted to make sure that it would work for the In Orbit state just as it did in the Landed state. No screenshots of that, but it worked.

Success! Using the Parallel Lines Method as it should be done (sorry that I misunderstood), I actually had an encounter upon leaving the Duna SOI, without the need for a correction! However, 31 m/s applied at the An or Dn (I don't remember which, but it was not too far along the orbit after leaving Duna), I got a very nice, zero degree inclination, 84km Pe with Kerbin. Some screenshots:

Aha! OK, I'll try this from the same save and report back.

I used the “Parallel Lines Method” demonstrated by @Starhawk earlier, and I am satisfied that: This is the most efficient method This method is repeatable Thanks again, Starhawk. This is the method I will use until the game is fixed. I learned a whole lot from the entire exercise. More details of the tests I ran, for those who are interested:

@Starhawk, this is great! I will check it out later today. What external launch window planner did you use? This one, or something different? https://alexmoon.github.io/ksp/

I would like to be able to put labels on some (or all, if I want) of my parts on a specific vehicle in the VAB. I might have labels like: "lander decoupler", "Booster tank 2", "Transfer stage cockpit", etc. This would be useful when trying to find the right part if it was displayed in the VAB Parts Manager and Kerbal Manager. It would also be very helpful if these labels were displayed on the Crash Report.

This bug has been reported, and discussed elsewhere in these forums. I'm pretty sure it's universal for everyone attempting a return from Duna. I would be interested in hearing from anyone who has NOT seen this bug when returning to Kerbin from Duna.

Thanks for the test, results, and analysis @Starhawk. Since we're specifically talking about the "can't see projected or actual trajectory until after departing the SOI" issue for Duna to Kerbin (and any other planets this may affect), then all options right now are "two burn" options. I'm interested in the following 3-way comparison. Assume I have determined transfer window date, phase angle, and dV requirement from other tools. Option 1, "Shot in the Dark" or "Flying Blind" option: Depart Duna on the transfer window date. Use best guess for placement of the maneuver plan to achieve required phase angle. Use best fast-finger method to begin and end the burn on time, and to use the exact amount of dV required. After leaving the Duna SOI, build and execute a "correction" maneuver plan to get the results you actually need. Option 2, "On Time Duna Burn" option. Depart Duna on the transfer window date. Use best guess for placement of the maneuver plan to achieve required phase angle. Burn only enough dV to barely exit the Duna SOI. As soon as possible after leaving the Duna SOI, build and execute a "correction" maneuver plan to get the results you actually need. Option 3, "On Time Correction Burn" option. Depart Duna so as to leave the SOI shortly before the transfer window date. Use best guess for placement of the maneuver plan to achieve required phase angle. Burn only enough dV to barely exit the Duna SOI. As soon as possible after leaving the Duna SOI, build a "correction" maneuver plan and place it as close to the transfer window date as possible. Execute this "correction" maneuver to get the results you actually need If you, or anyone else, wants to run this test and post results, that would be great! If not, I'll give it a go after I finish the Eve weekly challenge (I can't get the game to recognize that my Eve lander/ascender has separated from the mothership).

I believe we are supposed to see different values in the VAB and the launchpad. In the VAB we are shown vacuum dV. On the launch pad we get "sea level Kerbin atmosphere" dV.

I also want a dedicated screenshot key. Actually, I want two: To take a screenshot of everything currently on the screen (as F1 used to do for KSP1) To take a screenshot as if F2 has already been pressed -- no UI elements would be included in the screenshot. This still needs to be done with a single key press. By the way, if you are on Windows you can use the XBox controls to take a screenshot (but it requires a multiple key press): Windows-Alt-PrintScreen will take the screenshot of the currently active window Some other similar combination will take a screenshot of all monitors on a multi-monitor system (I think it's Alt-PrintScreen Screenshots are stored at Videos > Captures

Has anyone determined a workaround for this? Some way to edit the save file? Anything else? I have the same issue with both Decouplers and Separators. But only in the case where I have a command pod on both sides. I've already successfully decoupled booster stages with no issues. I see the same symptoms as described above: Visually, it looks like the separation worked as planned But as far as the game goes, it is still looking at one ship Both kerbals show in the cockpit camera view No result from ']' and '[' All stages still show in the staging view Tracking Station only shows one ship Save and Load do not correct anything Everything explodes after a short time warp I have one more symptom: I no longer have control of the vessel (with SAS or WASD) Or, sometimes, I only have control of one of the two halves

I would like to be able to spawn right outside one of the VAB doors, as if I just rolled the vehicle out of the building instead of rolling it all the way to the end of one of the runways.

Since we'll have to use this "burn to leave the SOI and then make corrections" method for at least the near future (hopefully not for too much longer), and since it can sometimes take quite a while to actually exit the SOI, is it a reasonable approach to time the initial escape burn so that we are exiting the SOI right before the transfer window time? If, for example, it will take 5 days to exit the SOI, then do the escape burn 5 days before the transfer window time. I haven't tested this out yet, but it seems like this should minimize the dV requirement of the correction.