Poppa Wheelie

Although this video is about 1.5 hours long, I really enjoyed it. It's about the Apollo Guidance Computer, how it worked, and how the crew interacted with it. It describes what was really happening with all of those 1202 alarms that were going off during the lunar landing descent. And here's a 15 minute video from Scott Manley where he interacts with some people who have recently gotten an original one of these computers working again.

Here's how to re-root the subassembly on PC (I don't know about console): While your mouse still has "control" of the subassembly, press 4 Now left click the part that you want to be the new root part of the subassembly You should now be able to attach the subassembly at the point (part) that you wanted.

I think this is it:

Yes, this is what I've been doing. It's inconvenient to have nothing in the VAB (or SPH) though.

Yes, it flies. Yes, it has the correct propellant. See in the photo that it has Liquid Fuel. Once in orbit, the correct dV numbers show up.

I ran some tests a few days ago, looking to collect dV and fuel requirements for an upcoming Eve mission I'm planning. With the ship below, I did the following: Cheat the vessel to Low Eve Orbit in Sandbox mode Run the sequence of steps shown in the spreadsheet, from bottom to top, starting with "Raise Ap to 64Mm" and ending with "Hohmann transfer to target". I had MechJeb do all the burns. In some cases I halted executing before it was finished, because I had reached the target and there was still dV remaining in the burn. In every case: MechJeb burned more fuel than the Rocket Equation calls for. Look at column E of the spreadsheet. This is what the Rocket Equation calls for given the dry mass of column H and the dV of column D. I spot checked some of these using this URL, which agreed with my numbers: https://faxmachinen.com/ksp/fuel.html. Now look at columns E and N. E is the amount of fuel that should be required to burn the dV called for in column D, but column N is the fuel actually used. They differ by quite a lot. MechJeb always started the burn "late", past the burn time divided by 2 time. Even on the relatively short, low dV burns. Do I have a MechJeb issue? If so, do I need to report it on a different forum, with logs, etc.? Or is this expected behavior?

I did a little research, and found a few people asking the same question, but I never saw an answer. I've addressed some of the "try this" items I've found, specifically: Make sure the root part is not below the Nerv engines in the staging stack. They are not. Make sure the dV calculating tool at lower right is set to vacuum. It is. Turn the MechJeb dV calculator on. It is. Is also shows zero. KER info window in lower left also shows zero You can see plenty of fuel in the tanks Is this just standard behavior, and I just need to work around it? Or do I have an issue here? Here's a much simpler craft, which I did in case other parts were somehow contributing to the issue.

Did Elvis even notice? He was too busy crying in the chapel.

There are several good videos that show getting early game science. Most involve these methods, which I also followed to get early science in my career game: Build a kerbaled rover of some kind as early as possible and get science from the KSC (each building is a "biome", and your vehicle often [maybe always] must be touching the building) Build a science aircraft and get flying low, flying high, landed (and possibly splashed down) science for all or most of the biomes on Kerbin Max science from each rocket launch by getting flying low, flying high, in space low, and in space high science over each different biome (as your flight allows), and then by landing in biomes that you don't already have landed or splashed down science for Good luck!

OP asked for our individual methods. I was trained in computer science and mathematics. As a mathematician, I would follow PEMBAS, in which case I get the result of 9, as follows: 6/2(1+2) = 6/2*(1+2) [math notation] = 6/2*3 [Parentheses first] = 3*3 [Multiplication and Division have equal priority and are evaluated left to right] = 9 As a computer scientist, I would not leave this to chance (or to the programming language, or to the compiler/interpreter writer's discretion). I would use additional parenthesis to implement the PEMBAS order of events, as follows: result = (6 / 2) * (1 + 2)

Your aerobraking screen shot shows 54ms of dV at 38km ASL. You had at least this much (probably a little bit more) before reentry began. The 46ms you had upon landing is not vacuum dV. I think your "total vacuum delta-v spent" should be no more than 5114 - 54 = 5060.

I saw the ground shadow of a station orbiting Minmus. First time I've ever seen the shadow of something in orbit, and first time I've captured an image of the shadow. 8 images:

Steps Taken: Revert KSP Recall in CKAN to v0.2.2.3 Launch Game with CKAN Start game > Resume Saved > [Selected Career Save] Load this save: LOADMETA file SFS file Test Escape, Save Game... (to create a new named save): successful Reload the same save, then Escape, Space Center: successful Reload the same save, then Escape, Tracking Center: successful Reload the same save, then Escape, Quit to Main Menu: successful Quit the game, all the way out Update KSP Recall in CKAN to v0.2.2.4 Launch the Game with CKAN Start game > Resume Saved > [Selected Career Save] Load the same save as step 4 Test Escape, Save Game... (to create a new named save): Unsuccessful. The Quicksave As... window to specify a filename for the save appears, but upon hitting the Save button the game freezes. Another Escape and we're back in the game, clock running again, etc. Escape, Space Center: Unsuccessful. Game is frozen. Escape unfreezes and we're back in the game Escape, Tracking Center: Unsuccessful. Same as for Space Center Escape, Quit to Main Menu: Unsuccessful. I get the intermediate window asking if I'm sure that I want to Exit to the Main Menu, but upon hitting Exit to Main Menu from here the game freezes. Escape unfreezes, and we're back in the game. but the only way to quit the game is with Task Manager (Windows 11). This is what I did at this point: quit the game with Task Manager Do you need new logs or ModuleManager.ConfigCache?

Me too. KSP.log ModuleManager.ConfigCache Player.log

I've done this challenge with Monoprop only here: But I've never tried SRB only, so I thought I would give that a shot. So here we go, SRB only, no monoprop. Full album here: https://imgur.com/a/tut1Eem Liftoff to LKO Transfer Burn Mun Landing Flag Return Burn Reentry

I've used a few SSTOs in my career save, shuttling crew. These were difficult, because I don't have Rapier yet, and I was always hauling a heavy Nerv engine with me. Several weeks ago, with a couple of LKO rescues coming up, I reevaluated mission requirements, and realized I don't need that Nerv engine. The mission of my SSTOs right now is LKO rescues, and crew transfers to and from my LKO station. So I built an SSTO for my first rescue, then realized it had non-stock parts. Here's my latest, "Jackie Cochran". All stock parts. Seven seats, two Whiplash engines and an aerospike Dart. Small cargo bay, outfitted for this mission with a claw and solar panels. I did test the parachutes, and the front two need to be further forward, but it will land intact with parachutes. Here's the rescue mission. My "F1" screen capture isn't capturing everything, so I switched to Windows-Alt-PrtSc (Xbox screen capture) somewhere in the middle of the mission. Ascent to orbit (5 images) Rendezvous and Rescue (5 images) After transferring Johnsy, it was time to head home (13 images) Here's the whole album. Most of these photos are already included above, but there are a few extras. https://imgur.com/a/cfMWTZC

Mods are not required. The "stock" way to store several crew reports is to EVA, take the crew reports from a command pod (right click the pod and Take Data), and then put them back in the pod (right click and Store Data).

Put both of our names on the entry. Thanks @swjr-swis!

That part is a "MK1 Drone Core", Manufacturer "Kerbal Standard". I thought I was using a stock part, but I just searched through my save and see that this is actually from the Airplane Plus mod. It has the following resources and capabilities which would have to be duplicated if using a stock probe core: Mass: 0.1t Electric Charge: 20.0 Pitch Torque: 10.0 Yaw and Roll Torque: 3.0 Requires: Electric Charge, 0.4/sec SAS: Stability Assist Prograde/Retrograde Hold Radial, Normal Attitude Hold Maneuver Hold Target Tracking

@AllenLi, your sixth mission photo shows that you should get 1110 points on the leaderboard, not 1010.

The real challenge is to get the most dV into LKO as possible. @AllenLi got 1110m/s into LKO. I think that's the standard to beat. I got 2759m/s into LKO with this: Full album (15 images): https://imgur.com/a/7odzAhK Highlights: I didn't attempt to go anywhere from here. With this dV we could wait for the opportune time and do all kinds of gravity assists to anywhere. Or, if we didn't want to wait, we can still get a Jool encounter or get well beyond Eeloo's orbit

Wow! I'm super-impressed by the 14 - 16t solutions from @QF9E and @camacju! I have a lot to learn about thinking smaller when the challenge is all about minimal mass. Question for you pros: What was your process for building your booster stages? There was no obvious way to sum up stage dV to the 3200m/s called for in the dV Map. Do you have a method or rules of thumb you could share? My process was trial and error until I got something to work. Here is my submission in the "amateur" category. 47.018t at launch. Full Report: https://imgur.com/a/tE0SCca

Using only stock engines? I think the O-10 "Puff" is the only stock monoprop engine.

It can be done in Chrome with even fewer steps, as follows: Right click the image in the Imgur album Select "Copy Image Address" Inside your forum post, right click and select "Paste" As I did here:

Yeah, especially at the beginning.