Funny to think how every single trajectory screen that the shuttle had was just basically “Here are two lines and a shuttle symbol, keep the shuttle within the lines.” Really amazing video though!
Towards the end of the program they implemented the ASCENT BEARING and ENTRY BEARING displays which basically are moving maps, kind of like the Orbiter2016 MFDs. They first flew them on STS-126
Bloody incredible. Your simulation makes it all seem so simple, but it's downright terrifying to think of actually executing an RTLS Abort with crew aboard.
This is already so amazing. But think about this. They built this complicated software into the shuttle during the era of disco music. It also had to be synchronized across multiple computers with the power to detect and vote out a broken system. And it HAD to work. There was no way a human could calculate all this by looking at the instruments. It either had to work or the president was going to have to make a sad speech. My respect to the software and hardware engineers and the many people that contributed to this amazing piece of software history. And thank you for doing your part to show us this amazing piece of history.
For those reasons they had the BFS, an isolated computer running a sinplified version of the guidance equations and the OS. There is this presentation on software-induced Loss of Crew and Vehicle (LOCV) www.slideshare.net/slideshow/space-shuttle-flight-software-pass-loss-of-crew-errors-jk-orr-20150827-52150515/52150515 which details one simulated emergency where two rapid engine failures bricked all four primary computers, without the BFS it would have been fatal
Funny how the letters RTLS used to send shivers down the spines of every spaceflight fan but now those letters just mean "cool we get to see a SpaceX Booster land on land instead of at sea"
@giuliodondi not as much, the Shuttle had such a low TWR during its RTLS and such a narrow flight envelope that made RTLS hair raising I rather suspect Starship's envelope will be much larger.
Great Video in Love the size of the video because I can full screen it on my tablet and I still can't believe that was a real plan that NASA wanted to use
The Shuttle sure is a cool vehicle, but these abort scenarios are just insane. And to think that the shuttle could've been quite different, if not for that one very specific mission profile the DoD wanted (and never got to do it)
In 1971 the Shuttle baseline was quite different, with smaller wings and internal fuel tanks. Yet, it still had an RTLS abort scheme involving a combined aerodynamic-thrusting turn to reverse course. You can read about it here: ntrs.nasa.gov/api/citations/19720006189/downloads/19720006189.pdf , not sure if this would have been that much safer. All the problems with the Shuttle concept fundamentally stem from the horizontal-landing/spaceplane paradigm. But spaceplanes are cool. Also, the Vandenberg once-around crossrange requirement was not exactly imposed on NASA by the Air Force, I think they wanted it anyways for aborts, but I don't have a reference for this sadly
@giuliodondi I must confess, I saw that information in a Scott Manley video, stating that the modifications required for the shuttle to fulfill that specific mission profile had made the orbiter more complex than it otherwise had to be, especially regarding the extended hypersonic glide time requirement. It's been a good while since I've watched it, could very well be wrong
@@matthewdev I know exactly the video, the one about the 3A/3B missions. The Air Force requirement was being able to launch into polar orbits from Vandenberg. Then, in 1973, the Vandenberg launch was formalized into the 3A/3B reference mission profile, involving deployment or retrieva of a satellite and reentry in a once-around orbit. These missions did drive the aerodynamic and heat shield design, and yet there is no explicit mention of them beyond a couple papers in 1973/74. This 1977 paper here ntrs.nasa.gov/api/citations/19770026315/downloads/19770026315.pdf studies the exact reentry profile for a once- around mission from Vandenberg and yet doesn't mention the 3A/3B reference profiles. My speculation is that the 3A/3B missions were nothing more than wargame studies (because they're ludicrous and only make sense in a state of war) but the high crossrange WAS useful to NASA for once.around abort capability for the Vandenberg mission they actually were going to fly (STS-62A) . Moreover, high crossrange gives you two or three deorbit windows every day for pretty much any landing site at almost any inclination, so you can wait for weather to clear up, which they did a lot
in a 2EO situation you only get the Orbiter back if you're in the last 30 seconds or so of powered RTLS or you're in a 2EO GREEN area and within range of Bermuda or an ECAL site, or single engine TAL/ATO. Any other situation and you have to bail out
(In KSP RSS) While launching out of vandenberg (using your script) I actually had to do an RTLS abort. It was scary, it was precarious, but we made it home
@@judet2992 I was referring to KSP RSS, and there was a shuttle abort STS-51F it was an ATO (Abort to orbit) after a single RS-25 failed 5 minutes into the flight
Really late comment but I think that once you get the contingency aborts finished up that you should showcase them in a video recreating the STS-26 RTLS Test Simulation. It’d be a neat way to test it out and would fit perfectly.
Could you please demonstrate a contingency abort mid-RTLS like you said it could? (Never mind lol, just finished the vid and saw you were already planning it.)
Principia is not listed as a requirement anywhere in the readmes. FAR is a necessary requirement of RO and the Shuttle System fork, these will never work without
hello giulio i asked to raiz space but my script doesn't work when I put run shuttle or ops1 or ops3 nothing happens just a line error or something like that
1 - This is not the place to be asking for support. Go to the GitHub issues 2 - "just a line error or something like that" - am I supposed to understand what your problem is from this?
Funny to think how every single trajectory screen that the shuttle had was just basically “Here are two lines and a shuttle symbol, keep the shuttle within the lines.” Really amazing video though!
Towards the end of the program they implemented the ASCENT BEARING and ENTRY BEARING displays which basically are moving maps, kind of like the Orbiter2016 MFDs.
They first flew them on STS-126
@@giuliodondi odd idea for a mission, but what if you had one where the shuttle had to be repurposed into a passenger transport across the pacific?
@@iamarizonaball2642 the Shuttle cannot launch fully-retrograde across the Pacific, not enough deltaV even without any payload
it feels so elegant, no need to interpret lots of values and stuff just look at some icons between lines
babe wake up new Giulio Dondi just dropped
Bloody incredible. Your simulation makes it all seem so simple, but it's downright terrifying to think of actually executing an RTLS Abort with crew aboard.
This is already so amazing. But think about this. They built this complicated software into the shuttle during the era of disco music. It also had to be synchronized across multiple computers with the power to detect and vote out a broken system. And it HAD to work. There was no way a human could calculate all this by looking at the instruments. It either had to work or the president was going to have to make a sad speech. My respect to the software and hardware engineers and the many people that contributed to this amazing piece of software history. And thank you for doing your part to show us this amazing piece of history.
For those reasons they had the BFS, an isolated computer running a sinplified version of the guidance equations and the OS.
There is this presentation on software-induced Loss of Crew and Vehicle (LOCV) www.slideshare.net/slideshow/space-shuttle-flight-software-pass-loss-of-crew-errors-jk-orr-20150827-52150515/52150515 which details one simulated emergency where two rapid engine failures bricked all four primary computers, without the BFS it would have been fatal
Funny how the letters RTLS used to send shivers down the spines of every spaceflight fan but now those letters just mean "cool we get to see a SpaceX Booster land on land instead of at sea"
If humans were on board we would still shiver I think
@giuliodondi not as much, the Shuttle had such a low TWR during its RTLS and such a narrow flight envelope that made RTLS hair raising
I rather suspect Starship's envelope will be much larger.
Ive always admired anyone who can make kOS work well, great job!
RTLS is just plain crazy!
Rtls seems like something I’d do just messing around in ksp
Great Video in Love the size of the video because I can full screen it on my tablet and I still can't believe that was a real plan that NASA wanted to use
Your camera work is awesome. Great video.
Lovely lovely programming there mate
The Shuttle sure is a cool vehicle, but these abort scenarios are just insane. And to think that the shuttle could've been quite different, if not for that one very specific mission profile the DoD wanted (and never got to do it)
In 1971 the Shuttle baseline was quite different, with smaller wings and internal fuel tanks. Yet, it still had an RTLS abort scheme involving a combined aerodynamic-thrusting turn to reverse course. You can read about it here: ntrs.nasa.gov/api/citations/19720006189/downloads/19720006189.pdf , not sure if this would have been that much safer.
All the problems with the Shuttle concept fundamentally stem from the horizontal-landing/spaceplane paradigm. But spaceplanes are cool.
Also, the Vandenberg once-around crossrange requirement was not exactly imposed on NASA by the Air Force, I think they wanted it anyways for aborts, but I don't have a reference for this sadly
@giuliodondi I must confess, I saw that information in a Scott Manley video, stating that the modifications required for the shuttle to fulfill that specific mission profile had made the orbiter more complex than it otherwise had to be, especially regarding the extended hypersonic glide time requirement. It's been a good while since I've watched it, could very well be wrong
@@matthewdev I know exactly the video, the one about the 3A/3B missions.
The Air Force requirement was being able to launch into polar orbits from Vandenberg. Then, in 1973, the Vandenberg launch was formalized into the 3A/3B reference mission profile, involving deployment or retrieva of a satellite and reentry in a once-around orbit.
These missions did drive the aerodynamic and heat shield design, and yet there is no explicit mention of them beyond a couple papers in 1973/74. This 1977 paper here ntrs.nasa.gov/api/citations/19770026315/downloads/19770026315.pdf studies the exact reentry profile for a once- around mission from Vandenberg and yet doesn't mention the 3A/3B reference profiles.
My speculation is that the 3A/3B missions were nothing more than wargame studies (because they're ludicrous and only make sense in a state of war) but the high crossrange WAS useful to NASA for once.around abort capability for the Vandenberg mission they actually were going to fly (STS-62A) .
Moreover, high crossrange gives you two or three deorbit windows every day for pretty much any landing site at almost any inclination, so you can wait for weather to clear up, which they did a lot
Shows the power of the RS-25s that even with two or one they can still get the orbiter back.
in a 2EO situation you only get the Orbiter back if you're in the last 30 seconds or so of powered RTLS or you're in a 2EO GREEN area and within range of Bermuda or an ECAL site, or single engine TAL/ATO.
Any other situation and you have to bail out
@@giuliodondi yeah, but still, impressive.
holy shit your aerodynamic model handles so well, I'm definitely flying the shuttle with a joystick now
That was breathtaking and frightening to watch.
Really impressive work!
That was so cool to watch
babe its time for your daily giulio dondi guidance-posting!!!!
Really impressive work!
(In KSP RSS) While launching out of vandenberg (using your script) I actually had to do an RTLS abort. It was scary, it was precarious, but we made it home
The shuttle never did an abort, what are you talking about?
@@judet2992 he’s talking about in game
@@Keru-5829 ah nice
@@judet2992 I was referring to KSP RSS, and there was a shuttle abort
STS-51F
it was an ATO (Abort to orbit) after a single RS-25 failed 5 minutes into the flight
@@nikelinq2899 ah thanks, also I meant RTLS abort.
Tasteful Ace Combat 5 music. Though it would be rather sudden in a funny way if Ofnir and Grabacr showed up as they did. Very nice video all in all!
Impressive... really impressive.
This is so fucking awesome. Fantastic work!
Wow, that's really cool!
Really late comment but I think that once you get the contingency aborts finished up that you should showcase them in a video recreating the STS-26 RTLS Test Simulation. It’d be a neat way to test it out and would fit perfectly.
I know the video, that might be a good idea for the 2EO blue case, although it would end in a bailout
Could you please demonstrate a contingency abort mid-RTLS like you said it could?
(Never mind lol, just finished the vid and saw you were already planning it.)
impressive
Wow !!!!!!!
you're a god
I have no doubt Eileen Collins would have aced this had it been required for STS-93
please make a video of how to install your shuttle mod dependiences etc
RTLS abort aka taking the shuttle out for a spin
This is honestly incredible, I just have one question does it work with SOCK and ksrss
no, the programs are calibrated for my fork of SSS and full RSS/RO
@@giuliodondiok thanks great job though
4:25 Blooper.... 3 engines on
Guilino - maybe you wanna take a look into the Flight Sim DCS - there's PLENTY of realism in there, and communitys the nicest I know.
He plays a space simulator, not a flight simulator 💀
@@Nemo2507s Yes, and I suppose he changes that. What part are you incapable of understanding ?
Amazing to see such automated control, but why does is broken engine lit at times after it fails?
In the several takes I did, sometimes the right engine was shut down.
The first engine to fail is either the left or the right at random
Would it be possible to use the OPS1 and OPS3 scripts without far and principia? the two just eat at my resources when im playing...
Principia is not listed as a requirement anywhere in the readmes.
FAR is a necessary requirement of RO and the Shuttle System fork, these will never work without
What do you sue to get the engine flares for the SRBs?
the SSS fork has all the dependencies listed
Hi! Is EVE Raymarched Volumetrics (Early Acess) the volumetric cloiuds mod from blackrack?
Yes
@@giuliodondi Thank you!
Worm shuttle > Meatball Shuttle.
hello giulio i asked to raiz space but my script doesn't work when I put run shuttle or ops1 or ops3 nothing happens just a line error or something like that
1 - This is not the place to be asking for support. Go to the GitHub issues
2 - "just a line error or something like that" - am I supposed to understand what your problem is from this?
ok i try
How do you get your fork of sts locations to work with RSS reborn?
never tried this.
I would just keep the KK groups and static configs and throw the rest, like the Edwards and Vandenberg terrain
Broke: If Giulio Dondi kOS RTLS is so good, where is Giulio Dondi kOS RTLS 2?
Woke:
Can you add miles as well as km to the measurements? I can’t easily picture km in my head
The standard unit in KSP is km, so I don’t think kOS would even support miles
Can it do Columbia?
What do you mean?