Poppa Wheelie

Use the Cheat Menu, with Alt-F8. Spread the Longitude of Ascending Node by 120 degrees for each of your 3 satellites.

You need more than the 6867 you have, but you definitely don't need 13,060. The text for many steps of the Trip Planner is misleading. Here's how it should really read for Kerbin to Duna and return: 3400 Kerbin to LKO 930 LKO to Kerbin SOI Exit, Kerbol orbit 140 Kerbol orbit to Duna intercept, flyby 250 Duna flyby to Duna highly elliptical orbit 360 Duna high orbit to Low Duna Orbit 100 Low Duna Orbit to Duna Surface (using aerobraking, parachutes, and final landing engine assist) 1450 Duna surface to Low Duna Orbit 360 Low Duna Orbit to Duna high orbit 250 Duna high orbit to Duna SOI exit, Kerbol orbit Total: 7240 With your departure from Kerbin to Duna, and your departure from Duna to Kerbin timed appropriately, this is all you need. The Kerbol orbit you end up in after the last line of this Trip Planner should get you a Kerbin encounter. If the Kerbin Pe of that encounter is not within the Kerbin atmosphere, a very small correction burn should take care of it. Then you land on Kerbin with aerobraking and parachutes. Of course, bring a little extra.

I've had trouble with separators. For now, I'm using back-to-back decouplers

I've also had very good success using engine plates and decouplers. If I want a nosecone over a docking port, I do this: Nosecone Decoupler (arrow pointing down) Decoupler is attached to engine plate attachment node So there is a fairing here between the decoupler and the engine plate, covering the docking port Docking Port Engine plate (with attachment node facing "above")

I flew the same 300t payload to Minmus, and then to Duna. One launch.

That's how we're supposed to do this, right? ... Right? ... Oh well, too late. That's how I did it. With one launch, I flew a 300t payload to Minmus, and then flew that same payload to Duna. All screenshots: https://imgur.com/a/120d8Bt Highlights: Launch to LKO More: LKO to Minmus landing Minmus back to LKO LKO to Duna landing Burning for Duna More: By the way, I landed 20.2km from the landing location of my first Duna mission.

@Dakota, you might want to address this in the rules for this challenge

Same for K2-D2 and Maneuver Node Controller.

I've seen this problem with a couple of parts as well. I spent some time trying to create a scenario that would reproduce the problem consistently, but so far I've been unable to do so. I see in today's KERB that the dev team is also unable to reproduce this problem. @Scarecrow71, if you are able to reproduce the error consistently, please describe how to do so in your report. With that description, perhaps we can get some dev action towards a fix for this one.

I also used the small.

Yes, it was more difficult for me than my KSP1 Duna Elcano. The biggest problem was the "finger flick" bug. Here's how I described that bug in my Mission Report: And, yes, I experienced what I call the "finger flick" bug consistently and repeatedly throughout the whole journey. This is the bug where, with no input on my part, the kraken flicks a giant tentacle and knocks my rover to the right or left, sometimes spinning it out of control, sometimes messing up a tricky ascent or descent. This bug has already been reported by others through the bug reporting process. What a pain! Without this bug, there were long stretches of terrain where I could have just paid half attention and accelerated back up to speed periodically. With this bug I was constantly stopping spinouts and overcorrections - constantly putting myself back on course. There were also a couple of places where the terrain itself was more difficult than the route I took in KSP1. The poles were definitely more tricky. I also had a few sections where the ground made my wheels wobble like I was riding over cobble stones, and it bounced the vehicle up and down and slowed speed to practically nothing. Very difficult to drive through these areas, and especially to climb. And visually these areas looked like any other hilly area.

I finished a polar circumnavigation of Duna in KSP2. No parts mods, and no mods that change the physics engine, or science gathering, etc. But I did use quality of life mods. Enjoy!

I finished my Duna and Ike mission, which included a polar circumnavigation (Elcano) of Duna. A lot more screenshots in the Mission Report, but here are a few favorites:

I've been working on this mission for over a month: a couple of weeks of design and build, 1 day to launch and get to Duna, another couple of weeks doing the Duna Elcano, and 1 more day to do Ike and Kerbin return. Plus another day to put all the screenshots in order. This was my third launch that involved landing kerbals. These are my "Giant Hop" missions. On this mission I obtained over 8000 science points, plus another 3035 points for the following 3 missions: Are There Fuel Stations In Space (35): Orbit Kerbin with a X200-64 methalox fuel tank and a docking port Duna Monument (2000): Visit the Duna monument Three Is Company (1000): Land 3 kerbals on Ike Here's the mission report. Enjoy! A full set of screenshots here: https://imgur.com/a/Wn2FzAj A subset of those screenshots are used in the highlights below. Launch, Transit to Duna, and Duna Landing More: Duna Elcano Circumnavigation Some of my favorite screenshots along the way: Documentation of the Elcano: I couldn't figure out a method to mark the Map View to show where I've been. Flags do not show up on Map View. So what I have for documentation is a set of 37 screenshots, 1 taken every 10 degrees of Latitude (with the landing location represented twice): https://imgur.com/a/PTpaWhz I noticed that items dropped from my lander, such as parachutes, did show up on the Map View. They also provide a waypoint marker in flight view when they are 50km away or less. I used my dropped parachutes to show my landing location every time I went to Map View, and to guide me home as I finished up the Elcano. Anyone have any ideas on how to bring 18 to 36 items to drop during the course of an Elcano? Let's just have flags show up, please. Overall, the scenery was great, but the Elcano just took too long and required too much personal attention while running it. If I start to talk about another Elcano any time soon, talk me out of it. And, yes, I experienced what I call the "finger flick" bug consistently and repeatedly throughout the whole journey. This is the bug where, with no input on my part, the kraken flicks a giant tentacle and knocks my rover to the right or left, sometimes spinning it out of control, sometimes messing up a tricky ascent or descent. This bug has already been reported by others through the bug reporting process. What a pain! Duna to Ike, and back to Duna More: Return to Kerbin More: Mission Complete!

Musical Instrument Museum, Phoenix. Thought I was going to spend an hour here, but stayed all afternoon. Could have made a day of it. Highly recommend: https://mim.org/

Here are three methods you can try. I've used all of these. I currently use the last one (with the K2-D2 mod), but the first two methods work fine with no mods. With no mods: Put a control point that faces "up" when your current control point is facing "forward" and your engines are facing "backward" Control point can be a probe core, a docking port, a command pod, or a "Grumble" seat (oriented the right way) When you are ready to switch from "engines facing planet" to "wheels facing planet": Cut throttle Do "control from here" from your new control point, and orient SAS Retrograde You can set this switch of control points to happen with an Action Group Or this method, with no mods: When you are ready to switch from "engines facing planet" to "wheels facing planet": Cut throttle Switch SAS from Retrograde to Stability Assist Pitch nose forward to bring the wheels facing down Let the rover land from this position One more method, with the K2-D2 mod: Before you begin your regular descent, open K2-D2, select Attitude Pilot, and set the following: Set Elevation to zero degrees Set Heading to whichever direction your rover nose will be facing when it lands wheels down Do NOT press the K2-D2 Attitude Pilot Start button yet Do your regular landing, engines facing planet When you are ready to switch from "engines facing planet" to "wheels facing planet": Cut throttle Press the K2-D2 Attitude Pilot Start button

Today I visited the Duna North Pole. Six days ago I landed on the equator, and have been driving north ever since, for several real-life hours each day. Most of the driving has been pretty smooth, but some sections are tough. The entire North Pole region was very difficult driving (and staying West enough to get enough sunlight for power). Now I have to drive all the way back down to the equator. Then I'll have to decide if I'm going to do the entire southern hemisphere as well (and complete an Elcano circumnavigation), or whether I'll just return to orbit once I reach the equator. Here are a few highlight screenshots. I'll publish a full Mission Report once the mission is complete. Six days ago I landed this 3-kerbal rover on the Duna equator. And started driving North. Duna is really beautiful. Eventually I arrived at the mission objective (spoiler). I kept driving north. Until I arrived at the Duna North Pole today. When I was very close to the pole, the game suddenly told me that I could do South Pole science.

I enthusiastically agree that the issues you listed are much higher priority. I can continue to manually optimize from the starting point provided by Flight Plan.

I really enjoy the ability to edit nodes while the game is paused, but perhaps editing while pausing is what caused my initial suspicion that Flight Plan needed to move Burn Start times up before the selected creation point. However, I looked back over my screenshots, and I see that once time is taken off of Pause, the Burn Start time has indeed been moved up. So all is well on that front. I did notice, though, that with a little more manual tweaking of the Burn Start time, I still got a better predicted result (ie, closer to circular, lower Eccentricity). 1 minute 13 seconds to Ap Immediately after the node to Circularize at the Next Ap was created (with time paused), I noticed that the Start Burn time and the Time to Ap were matching. This led to my belief that the Start Burn time was locked on to the selected point (Ap in this case) After unpausing time, and then pausing again, the Start Burn time has been adjusted Flight Plan created node has projected Ecc of 0.004 With a little more tweaking of the Burn Start time, I got an Ecc of 0.002

Yes, this is what I have been doing. This MNC ability to edit a node with the game paused is fantastic! I may not be able to get to it for a few days, but I'll see if I can set up a good scenario, with screenshots, etc., and I'll report back here.

Thanks for this mod! I use it all the time. I have one possible bug, and two requests: Bug? When I ask K2-D2 to burn the next node, it begins the burn later than the burn start time. Here's what I'm expecting, versus what's happening Each second What I expect What K2-D2 Does Beep, light 1 Beep, light 2 Beep, light 3 Loud voice, light 4 Begin burn one second later Begin burn Request 1: Could we also have a Roll setting on the Attitude Pilot? And could each of the 3 (elevation, heading, roll) also be optionally selectable? I will sometimes only want 1 or 2 of the 3. Request 2: Could the K2-D2 window be hidden with the selection of F2 (Hide UI)?

Thank you for this mod! And for the combination of Flight Plan, Maneuver Node Controller, and K2-D2. I use these all the time. I've noticed one issue with Flight Plan and/or Maneuver Node Controller: If I create a node, then load a save previous to this node creation, Flight Plan and Maneuver Node Controller still have a node. Also for Flight Plan: When Flight Plan creates a node to do something at a particular point (eg, Circularize at the next Ap), the node is created right on the Ap, which will not result in the most circular orbit (possibly with the Pe still in atmosphere). When I look at the expected future results in a case like this, I do not see a circular orbit. In these cases, I manually adjust the created node, by walking backwards in time to find the "best" circularization. Could this feature of placing nodes directly on specified points be updated? I think that in every case, we don't really want the resulting node to begin its burn directly on the selected point.

Thank you for this mod! And for the combination of Flight Plan, Maneuver Node Controller, and K2-D2. I use these all the time. I've noticed one issue with Flight Plan and/or Maneuver Node Controller: If I create a node, then load a save previous to this node creation, Flight Plan and Maneuver Node Controller still have a node.

I'm loving this game! Thank you dev team! I have four feature requests for the dev team. These obviously are not really bugs, but they bug me. Can these go on the dev list, please? 1. On entering the R&D building, take me directly to the first non-complete tier For example, if I’ve already completed tier 1, and am partway thru tier 2, take me directly to tier 2 2. When a vehicle has brakes set, keep the brakes set until I unset them Right now, when I put a kerbal back into a vehicle which had brakes on, the brakes are turned off as soon as the kerbal boards. Expected behavior is that when a vehicle has brakes set, they remain set, independent of whether any kerbals are present, and independent of whether any kerbals are boarding or just finished boarding. 3. List Research Inventory "science cards" in reverse order, with most recent on top When we press the button and get new science, a window pops up showing a scrollable list of what I call "science cards" at the top, and then a summary of data and samples at the bottom. Right now, the scrollable list of science cards at the top of this window has the most recently collected science listed at the bottom of the list, meaning I need to scroll down to see what science I just got. I want this list to be in reverse order, with the most recent stuff on top. 4. The sound of walking on celestial body surfaces should sound like what the kerbal would hear inside the helmet. I’m expecting to hear something that matches what I’m seeing, that the kerbal is walking on grass, dirt, concrete, rock, regolith, powder, etc. And if there is no atmosphere, the sound needs to match, and only be coming through the suit into the helmet. Right now all walking sounds (to me) sound like the kerbal is walking on a metal floor in a small room with lots of echo.

I think it would be very useful to use positive and negative to indicate if your distance to target (at the indicated relative velocity) is increasing or decreasing.