534
top 50 comments
sorted by: hot top controversial new old
[-] merdaverse@lemmy.zip 14 points 12 hours ago
[-] HiddenLayer555@lemmy.ml 3 points 3 hours ago* (last edited 3 hours ago)

I get what you mean, but programmers in 1969 would have had their minds absolutely fucking blown by a GUI in general, let alone modern websites.

[-] bagsy@lemmy.world 3 points 8 hours ago

To be fair, there was only one moon lander, not 27 different ones that all worked slightly differently.

[-] Agent641@lemmy.world 3 points 4 hours ago

No dependencies, no frameworks, no visual studio shenanigans. No mean forum posts.

Sounds like coding heaven to me.

[-] 00Fuk2Givve@lemmy.zip 12 points 12 hours ago

Can it run doom

[-] DupaCycki@lemmy.world 19 points 14 hours ago

Just like with most open source code - I have absolutely no idea what to do with it, but I still love that it's freely available.

[-] SlurpingPus@lemmy.world 29 points 23 hours ago

The article is technically correct in that the code has been open-sourced and published, except it happened in 2016, so I'm guessing the author just decided to ride the Artemis hype.

[-] vrighter@discuss.tchncs.de 9 points 22 hours ago

i've had a copy for years.... Why is this news now?

[-] whotookkarl@lemmy.dbzer0.com 5 points 14 hours ago

Space articles get clicks when something big happens like Artemis 2

[-] Zerush@lemmy.ml 24 points 1 day ago* (last edited 1 day ago)

Adding that the Apollo 11 soft isn't much more complex as the one of an current pocket calculator, I doubt that it can even run DOOM. NASA anyway has a huge OpenSource catalogue, all their soft used is OpenSource, despite some with restricted licenses only for official uses. Same for other Space agencies, eg. from the ESA. Good sources for astronomic fans.

[-] quick_snail@feddit.nl 8 points 1 day ago

the crucial 30 lines of assembly for calculating Apollo 11's navigation trajectories.

I was never skeptical we went to the moon until now.

How the hell can you do all that in 30 lines?!?

[-] HiddenLayer555@lemmy.ml 1 points 3 hours ago

I mean, the math required is basically first year college level stuff.

Making a machine that will accurately follow that trajectory and not kill you is the hard part.

[-] Buddahriffic@lemmy.world 2 points 9 hours ago

Very efficiently.

Or for a less cheeky answer, I believe the method they used at a high level was pointing a camera at a few guide stars, so the 30 lines of assembly might have been a loop that checked those cameras for any drift of those stars and did a correction pulse of the rotation boosters to keep them centered. Oh, one of the references might have been the signal strength from home, too (signal gets weaker if the antenna isn't aligned).

Unless it was an emergency, it might only need to look at 5 pixels to determine alignment and correction.

Also, just because it's assembly doesn't mean it can't call subroutines and functions, so that 30 lines might be misleading in the way those several lines in the other reply have way more going on. That said, if it's just doing a pixel brightness comparison, that's one line to read the central pixel, then for each direction one line to read that pixel, one more to compare, one line to jump to next comparison if center is brighter, one instruction to initiate correction burn, one instruction to stop it immediately after, then one instruction to return to the start of the loop... Which comes to 22 lines total, leaving 8 for logging or maybe timing the burn. And that's assuming their instruction set didn't have anything fancy like read and compare, compare and jump, or a single instruction burn pulse.

[-] Birch@sh.itjust.works 19 points 1 day ago* (last edited 1 day ago)
import MoonPy

MoonPy.LandOnMoon()

while MoonPy.OnMoon:
    print("john madden")
[-] DupaCycki@lemmy.world 3 points 14 hours ago

Just applied to NASA with this code and they accepted me. Should have posted it under AGPL.

[-] AnnaFrankfurter@lemmy.ml 33 points 1 day ago

See ya losers I'm going to moon \s

load more comments (4 replies)
[-] KoboldCoterie@pawb.social 86 points 1 day ago

Mark my words, someone's going to make a video game with 100% historical accuracy with this.

[-] AnUnusualRelic@lemmy.world 4 points 18 hours ago

Lunar Lander wasn't good enough for you?

[-] darklamer@feddit.org 33 points 1 day ago

This code was first published 10 years ago, but I haven't seen any such game yet.

[-] fakeman_pretendname@feddit.uk 24 points 1 day ago

They'll get round to it. They're doing the graphics first. They're currently making individual 3D models of "all the stars".

[-] KoboldCoterie@pawb.social 17 points 1 day ago

"If you want to make a historically accurate moon landing sim, you must first model the universe." -Carl Sagan

[-] AnUnusualRelic@lemmy.world 3 points 18 hours ago

Don't we have the Universe Simulator already?

[-] NocturnalMorning@lemmy.world 3 points 9 hours ago

Yeah, that's how they filmed the first moon landing.

load more comments (13 replies)
[-] Cethin@lemmy.zip 24 points 1 day ago* (last edited 1 day ago)

You can automate control of your craft in KSP with a mod. All you need is to have it send the data to the Apollo computer and then send the output to the craft. It should probably work with the real solar system mod.

Now that I saw this though, I swear I saw this exact video already. Scott Manley or someone may have already done this.

[-] bl4ckp1xx13@lemmy.dbzer0.com 6 points 15 hours ago

If that works with the real solar system mod that is honestly the finest testament KSP can get for its mathematical accuracy.

[-] NocturnalMorning@lemmy.world 3 points 9 hours ago

KSP is not mathematically accurate and it can't be or it would have trouble running on computers. They split up and use simplified 2 body dynamics in the game.

We use super computers to model the n-body problem bcz of how complex it is.

[-] bl4ckp1xx13@lemmy.dbzer0.com 1 points 8 hours ago

Of course, NASA ain’t modelling actual missions in KSP.

I imagine KSP is simple Newtonian physics which is accurate at macro-scales, whereas obviously NASA is going to use Einstein’s equivalent. Far more computationally intense but really important once you scale up the small errors in Newton’s equations.

[-] NocturnalMorning@lemmy.world 2 points 7 hours ago* (last edited 7 hours ago)

Actually, we don't use relativity so much. For some stuff like light time delays, yes, but for orbit determination we use newtonian mechanics still. It's just that once you start adding more than two bodies, you have to shift to doing numerical integration to find solutions, which doesn't work for real-time stuff like video games.

For most applications, F = -GM1M2/r^2 is still a valid approximation.

Edit: And by most applications, i mean sending a satellite to a planet in our solar system. If you were trying to go to Alpha Centauri, you damn sure better use Relativity to model your trajectory.

[-] Cethin@lemmy.zip 3 points 10 hours ago

I haven't tried it, but yeah, at small scales KSP (which is just using floating point numbers) is pretty accurate. It's at large scales where it fucks up, which it does have to deal with too, being a game about traveling between planets.

I assume it probably would work though. The Apollo computers, as I'm sure you know, weren't super complex. They basically just assisted the pilot. I'm not exactly sure what math they did, but it probably just had to do with descent rate/time to impact and stuff like that. Again, this is all just guessing. I don't remember it.

[-] bl4ckp1xx13@lemmy.dbzer0.com 2 points 9 hours ago

That makes sense, floating-point precision falls apart with large numbers but is pretty good with small numbers.

Perhaps there’s a mod that can swap out the position system to use doubles instead of floats? But I’m pretty sure that’s a Unity thing with its Transform positioning system so that’d be quite a challenge to change.

[-] Cethin@lemmy.zip 2 points 3 hours ago* (last edited 3 hours ago)

Yeah, there's no way to do that. You can use doubles yourself to track things, but the engine is always going to use floats. When you send data to the engine, it has to be in float form.

IIRC, UE5 actually switched to using doubles for everything. Floating point math is faster to perform, but computers are fast enough now they decided it was worth it. It can now accurately store positions much further away without losing as much precision.

KSA is also using doubles I think, on their custom engine. They can do a cool thing where they can render multiple vehicle views at once, in totally different locations. KSP couldn't do this because of floating point error.

[-] wax@feddit.nu 3 points 1 day ago

It will be vibecoded with six-fingered physics

load more comments (1 replies)
[-] j_elgato@leminal.space 6 points 1 day ago

Wait, our own space program? Is that a thing we're supposed to have?

load more comments
view more: next ›
this post was submitted on 13 Apr 2026
534 points (99.4% liked)

Open Source

46221 readers
499 users here now

All about open source! Feel free to ask questions, and share news, and interesting stuff!

Useful Links

Rules

Related Communities

Community icon from opensource.org, but we are not affiliated with them.

founded 6 years ago
MODERATORS