Jump to content

[AAR] Kerbals in Space: Duna Mission


Designer225

Recommended Posts

Due to the disasterious server implosion (well, the purge is pretty violent) I lost many threads, including the ones I did for the mission to Duna. But I hoped to rebuilt the them, but due to technical reasons I can't rebuilt the first stage. So here it is: TROY Concept: Mission to Duna.

I have to skip PRE-PHASE A and rework on PHASE A. But I might as well merge them.

EDIT: Okay, I decided to skip some stuff and move on to the series. A lot of cuts is gonna be significant.

Due to the last forum failure I'm not gonna taking any chances. I will use Google Drive to backup my chapters.

  1. PREFACE: TROY Concept
  2. PROLOGUE 1: VASIMR
  3. PROLOGUE 2: Shuttle Test
  4. PROLOGUE 3: Test and Change of Plan
  5. PROLOGUE 4: Preparation
  6. CHAPTER 1: Bon Voyage
  7. CHAPTER 2: Duna Transfer
  8. ...

  1. Of Satellites and HyperEdit


Mission Status: Preparing

Jebediah: Commander

Bill: Second-in-command

Bob: Spacecraft Pilot

Kelvis: Engineer

Sherlorf: Geologist

Mallock: Doctor

Sidble: Physicist and Astronomer


CREDIT

Reaction Engines Ltd. --- Concept


EDIT: Need to reboot the mission, but I can't do it unless it have a beginning. Edited by Designer225
Link to comment
Share on other sites

PHASE A: Preliminary Analysis

Here's the whole budget plan again:

TROY SHIP:

Departure: ~4700 m/s*

Transfer (Duna): ~1033 m/s*

Duna Orbit: AEROBRAKING + ~80 m/s*

Transfer (Ike): ~300 m/s

Ike Orbit: ~110 m/s

Transfer (Duna): ~110 m/s

Duna Orbit: AEROBRAKING + ~80 m/s

Transfer (Kerbin): ~620 m/s

Kerbin Orbit: AEROBRAKING + ~200 m/s

Refuelling: 0 m/s since other vessels will refuel the ship.

*Indicates that precursor ship will do the following.

CREWED DRAGON RIDER:

Kerbin Orbit: ~4700 m/s (By FALCON 9)

Rendezvous: ???

Docking: ???

Undocking: ???

Deorbit: ~240 m/s

Landing: ??? OR BY PARACHUTE

IKE LANDER:

Orbit: ~4700 m/s

Rendezvous: ???

Docking: ???

Undocking (Ike): ???

Landing (Ike): ???

Orbit (Ike): ???

Rendezvous: ???

Docking: ???

Undocking: ???

Impact: ~120 m/s

DUNA LANDER:

Undocking: ???

Docking (MOTHERSHIP): ???

Undocking: ???

Landing: ???

Orbit: ~1750 m/s

Rendezvous: ???

Docking: ???

Undocking: ???

Waiting for ship: 0 m/s since the next ship will come to the lander.

BASE MODULES

Undocking: 0 m/s since it will float out of vicinity.

Deorbit: ~200 m/s

Landing: BY PARACHUTE + ???

TUG MODULE (Will only be used in ship construction)

Launch: ~4700 m/s

Rendezvous: ???

Tug: ???

Un-Tug: ???

Wait (2 other modules): ???

Repeat Tug & Un-Tag: ???

Impact: ~240 m/s

REQUIRED DELTA-V (Precursor Ship)

Required: ~5813 m/s

MCC (Mid-Course Correction): ~1162.6 m/s (Include Possible Impact)

Safety Margin: ~1162.6 m/s

Total Needed: ~8138.2 m/s

REQUIRED DELTA-V (Crewed Dragon Module)

Required: ~10150 m/s (In reality refueling + launching by Falcon 9 so ~4700 m/s)

REQUIRED DELTA-V (Mothership)

Required: ~7233 m/s (In reality refueling + launching so ~2533 m/s)

MCC: ~1446.6 m/s

Safety Margin: ~1446.6 m/s

Total Needed:10126.2 m/s (5426.2 m/s)

Mission Objectives:

Primary Objective (REQUIRED):

1. Get the crew returned to Kerbin safely. (CANNOT BE CHANGED)

*Failure to complete any of the goals will result in a mission failure.

Secondary Objectives (EXPECTED):

1. Get to Duna

2. Land a base on Duna

3. Land a Kerban on Duna

4. Launch a probe around Duna’s orbit

5. Get to Ike

6. Launch a probe on Ike

7. Land a Kerbal on Ike

8. When returning, get the mothership into orbit instead of impact course

9. Plant a flag on Duna

10. Plant a flag on Ike

*Note that it is expected, but NOT DEMANDED, that these goals will be met.

DESIRED Objectives:

1. Land a base on Ike

2. Visit the Magic Boulder in the orbit of Ike.

3. Perhaps launching toward Kerbin from Ike

4. Another landing mission on Duna

*These goals may be attempted, but they may be skipped in favor of the goals above.

Other Objectives:

1. Another landing mission on Ike

2. Carrying a miner unit to Ike

3. Carrying a miner unit to Duna

*These goals will be least likely to be attempted, but some might be attempted for god’s sake. Not that these goals might get promoted to any other categories above.

Spacecraft:

TROY Ship:

screenshot3.png

TROY Model Mothership:

screenshot6.png

TROY (Possibly Model) Precursor ship:

screenshot8.png

Well, that got the designs done. NEXT!

Modules:

Three modules (Recon, Habitation, and Workspace, which was known as Power Module) will be descended to the surface of Duna. New plans have been made to land the module without MechJeb first.

The Duna lander (a Dragon Rider, actually) will descent to Duna’s surface and returns. It’s not really a package deal. Take it or leave it.

The two Dragon Riders have different responsibilities: The crewed Dragon Rider will be the primary transportation to get the Kerbals from Kerbin and back. The Ike lander will serve to land on Ike, and when the crewed Dragon Rider is dead, as a reserve lander.

Two probes will be launched (with ion-power technologies, of course) to Duna and Ike from he trunks of the Dragon Riders. There they will serve as communication systems, as well as scientific probes surveying Duna and Ike.

That’s a lot of detail. Anyway, next!

Technologies:

I’m gonna use the old MechJeb and the newer MechJeb, partly because I’m forced to use them on the precursor ships (two modules have the MechJeb 1 m edition module). Chatterer will be used for communication, Leucome’s aerospike engines as main propulsion engines, and the Kerbal Crew Manifest, now rostering! (Yeah, that’s a pun...)

Engines:

As I’ve mentioned above, Leucome’s aerospike engines will be used primarily in the missioni. The Mainsail proved to be useless for the long mission, as I found out. No engines, except LV-909, Dragon-equipped engines, Mainsail, and the Leucome’s 5 meter FSA, will be used.

Ship spec:

Unknown. Will post as we go.

I'm tired of adding more BB codes, so I'll leave it as.

Changed recently. The data is no longer valid.

Edited by Designer225
Link to comment
Share on other sites

PREFACE: TROY Concept

The Troy Concept is an idea of going to Mars (which I'm using it to use it on Duna), and perhaps enabling humanity of further space exploration.

The first stage calls for departure of the 3 Percursor ships, carring base modules, and bound for Mars. Once arriving at Mars, the 3 base modules (Habitation Module, Recon Module, and Power Module) will undock from the Percursor ships, and land in groups of 3 in 3 different locations, ensuring that the covered area take up 90% of the Martian surface.

Then. the Crew ship departs, carrying crew to Mars. There they dock with Percursor ships, and in the process transfering crew to the Martian lander, then having the lander to land near the base. Then after 14 months of studies, the lander departs from Mars and docks to Crew ship. After that the lander is discarded and the crew module departs for home. After somewhat 9 months of transfer, the 2 capsule docked to the crew ship undocks, discarding the crew ship, and, after an aerobraking, docks to SKYLON for further missions.

Then again, several improvision is required for the proposal to work.

Now, I'm using it to go to Duna (and if feasible, to Ike), but several issues are needed to consider.

1: Propulsion. Of all the stock engines, only the NERVA is feasible of high efficiency, but even so requires a ton of fuel, which does not help a lot. Besides, fuel can be easily depleted. The SM-Buzzard-Ramjet is capable of long space travel, and has resources that are renewable (renewing compressed hydrogen is completely impractical). The issue is the electricity, however, and that means a lot of power sources is needed.

2. Landers: While the stock NERVA is a good engine, its weight does reduce the amount Delta-V it can use. The Radial Nuclear Engines alleviate (definition: relieve) that problem. The smaller the size, the lighter it is, and thus the more efficient it is. However, because Duna's gravity is about 30% the gravity of Kerbin, smaller engines seemed underpowered.

3. Aerobraking vs. Lithobraking: Which way is more efficient? Lithobraking eliminates the chance of breakage, but it does use a lot of fuel and requires a lot of precision on time. The aerobreaking requires less fuel, but it does require a lot of entry precision, and breakages can happen if not used properly. However, results from previous tests with the last design showed no breakage between 2. A heatshield is required, however.

4. Modules: 2 modules will be connected using Clamp-o-Tron Sr, while the other 5 or 6 or so will be connected using the normal Clamp-o-Tron. This does not ensure 100% breakage-free, however. Also, there will not be multiples of engines, nor will there be overpowered engines. The SM-Buzzard-Ramjet will be the sole ship propulsion module.

5. Crew: You will meet them in PROLOGUE 1: The Meeting.

So, several changes have been made. Not sure if this would work perfectly. NOT GUARANTEED TO FOLLOW THIS.

Edited by Designer225
Link to comment
Share on other sites

  • 2 weeks later...
  • 2 months later...
http://imgur.com/a/hC6SB

It isn't a troy mission if it isn't constructed using SSTO transports.

Yeah it really wasn't a truly TROY mission without SKYLON, but it's a bit hard to construct the SKYLON. Constructing SKYLON would either mean large SSTO with large fuel tanks, or mod parts from B9 Aerospace, which is a bit too much for my system to handle. If I do use B9, though, I expect over 70% memory usage now that I've switched to Windows 7 64-bits. :rolleyes: But I'll do my best. :)

Also, this project is not dead. I've been working on several modules now. I can't go over a specific part count, or KSP is gonna lag. I was planning to use a reusable MSTO that uses parachutes to land on Kerbin because I'm not a good Kerbin lander... lander. My landing skill will be up to the test, when I will try to land on Duna (I've last landed on the Mun and Minmus.). I'll see if a version of SKYLON can be created. Expecting longer waiting periods, though, since I have school till June.

Edited by Designer225
Link to comment
Share on other sites

  • 3 weeks later...
  • 3 weeks later...
  • 2 weeks later...

OK... since KSP 0.22 would have awesome updates (science system yay!) I would probably refurbishing some of my vehicles and hope most of my mods work with KSP 0.22... (And hope that this save would be compatible with the next version...)

Edited by Designer225
Link to comment
Share on other sites

  • 1 month later...

Preview for Prologue 1:

Gene: So, Jeb will be leading the mission, as planned. Mallock will stay on board the spacecraft for maintenance.

Mallock: WHAT? Says who?

Jebediah: I thought your engineering skills would do best there.

Mallock: Do you have to ground me onto the ship Jeb?

Gene: The plan is the plan. Now may I-

Mallock: Is this true? Or is this a joke? Or is this-

Gene/Jeb: True.

Mallock: *swears*

Link to comment
Share on other sites

  • 5 months later...

That was a long time - almost a half month before this post - but I need to reboot this. I just need to have a beginning. So I don't think I'll be working on this until the right time has come - which is soontm.

Isn't it weird that spoilers are working now, albeit looking differently?

Link to comment
Share on other sites

While I slowly build up my AAR universe, I'll be sharing you some things.

Anyway... let's- wait, where are the discs?

Hold on...

Bonus 1: Of satellites and HyperEdit

screenshot0.png

Jeb: Alright, folks, we're gonna send our second DS satellite into space!

Bill: Are you sure, Jeb, that this is gonna work?

Jeb: I'm sure. Our last teleportation test work, right?

Bill: I guess...

HyperEdit 1.2.4.2: Teleporting in 5... 4... 3... 2... 1...

*Whoosh*

Jeb: Working so- Oh lord...

screenshot1.png

no_signal_found_by_epicfail23-d2zseqv.jpg

Jeb: This is just bad.

Bill: Now what?

Jeb: What does this button do, huh?

Bill: NononononononoNO-

*Whoosh*


Some time later... (BTW, I've reverted the game state to launch so I could do it from orbit.)

AR202: Rotation to burn...

screenshot2.png

Jeb: I've never thought AI were so useful...

Bill: Come on, Jeb. I'm sure that-

AR202: Rotation complete. preparing burn...


Later...

lKj6jl7qopDMyqHdv5q5tAWx8iNiLpCNDeA1KmMYo1c=w1038-h584-no

AR202: Diary entry 5: I'm bored. Just bored.

Jeb: We heard your entry, AR202.

AR202: I'm bored! Next time please implement a secondary AI!

Jeb: Sorry. We have no available AI at this time, though. Maybe next time?

AR202: OK, but make sure I have an AI!

Bill: Fine...

Gene: OK, battery level is running low...


Much, much later...

Jeb: Do you think recording everything is a frenzy?

Gene: Maybe, but it sure is colorful.

AR202: Yeah, I have a lot of work to do now...

screenshot31.png


This is not even meant to be part of this installment. But I found this very funny. So I've made a story out of this anyway.

Anyway, expect real main-stream updates soonTM.

Edited by Designer225
Link to comment
Share on other sites

Loading from disc 1...

loading1.gif

Loading complete.

Prologue 1: VASIMR

Jeb: Alright, let's begin the VASIMR test now. AR202?

AR202: Ready as ever be, Jeb.

Bill: Are you sure this is a good idea Jeb?

Jeb: Don't worry, Bill. AR202 is right now, online. It'll have enough time to download all the data when he goes offline.

Bill: Offline? When?

Jeb: When the probe is out of any satellite reach.

AR202: May I start the launch?

Jeb: You may. 10... 9... 8... 7... 6...

AR202: Wait! Where's the secondary AI?

Jeb: Ummm... GFS's the one. Anyway... Liftoff!

screenshot38.png

Jeb: And there it goes. Anyway... Bill... can I talk to you?

Bill: Sure. Why?

Jeb: Because-

Gene appeared behind them.

Gene: Jeb, Bill. Both of you. Meet me in the meeting room.

Jeb: Looks like our conversation's been cut short.

Bill: Yup. Come on...


In the meeting room...

Gene: Welcome, everyone.

Jeb: OK, Gene. I don't know why you called us on such lovely day... Besides, we are still helping out Von Kerman's experiment...

Bill: Yeah, we were having fun there tweaking the VASIMRS...

Gene: Do not think that fact escapes me. Now quiet.

Jeb and Bill remained quiet.

Gene: Anyway, we have this meeting because you... Jebediah, Bill, Bob, Kelvis, Sherlorf, Mallock, and Sidble, you are chosen for this mission.

Kelvis: I still don't get why we are chosen.

Gene: You are chosen because you are the... what's it called... elite of the elite...

Bob: Come on, Gene... A badass, a dumb guy, a scaredy guy, a crazy guy, a detective, a mediocre doctor, and an amateur scientist is all you think would do?

Gene: Err... Maybe?

Jeb: But where are we going to?

Sidble: To the Mun? Minmus? We've gone to there, like, thousand times?

Gene: Not Mun. Not Minmus.

Mallock: OK... don't tell me this is going to be difficult...

Gene: All of you are going to Duna.

Dead silence.

Jeb: (Laughing) I thought probes were enough.

Dead silence. Again.

Gene: Yes, but... they broke down.

More dead silence.

Jeb: (Laughter contained) OK. What are the mission goals?

Gene: Thank goodness. You guys are sent to further study Duna, and its moon, Ike. We have, like, no information on Ike.

Sherlorf: What? I thought probes have orbited on Duna!

Gene: That was before ion-propulsion being researched thoroughly. Now many probes were dead. Silent.

Jeb: OK, OK. I assume that's primary objective. What's the secondary? Tertiary?

Gene: That's actually secondary. Primary is to get you guys back home alive. We couldn't afford to lose more Kerbonauts anymore. Recruitments are pretty low, actually. Tertiary is to deploy satellites and/or land on Ike. We must do Duna first, then Ike, but we must make sure you guys are gonna live through the entire thing.

Jeb: Well, let's hope ion-propulsion really is up to the task.

Wernher von Kerman broke into the meeting room.

Wernher: Jebediah and Bill Kerman, go to the mission control ASAP!

Jeb & Bill: Yessir.

Gene: Well, I guess I could end it here. Anyway, hope you guys know what you are doing soon. See you soon. Dismissed.

Everyone except Gene left quickly.

Gene: Well, that was quick.


In the Mission Control...

Jeb: How's things going, AR202?

AR202: Good. So far my wings have been opened.

screenshot41.png

Jeb: Good. Let's run some power test.

AR202 throttled to 100%

GeoSat Flight System: WARNING! Power critical!

AR202 throttled downed to 0%.

Bill: And here's your test, Jeb!

Wernher: OK, so power usage is around 6500 per second at maximum thrust, regardless of specific impulse as it affects argon usage only.

Jeb: Yep.

Bill: Something tells me that this could get crazy...

Jeb: OK, it looks like the satellite is ready to come home.

Wernher: I don't think it'll help us much...

Jeb: Come on, Wernher; you don't have to worry so much...


GFS: Heating up... 1125K... 1570K... 2247K... WARNING! Temperature have reached 2400K...

screenshot50.png

screenshot51.png

GFS: Solar panel lost. WARNING! Temperature exceeds safety level. Current temperature: 2756K

Wernher: Are you this is a good idea?

Jeb: I'm sure it's fine. I'll get to the "fine" part later.

screenshot52.png

GFS: ERROR! VW-15K inoperable. Later... Current temperature: 828K... 624K... 423K... 291K... DANGER! High altitude drop speed! High al-

Crash!

screenshot53.png

AR202: Last AWLTS signal received. Locating alternative signals...

Jeb: Thanks for capturing the last signal AR202.

Wernher: But the ship is destroyed!

Jeb: Most of it. In the event of a catastrophic failure the data system - which is located in the core of the ship - disconnects itself from the rest of the network. The part of the core that protects the data system is made of diamond, which is more sturdy than most metals, so instead of collapsing, it is buried instead. After the trouble the data system sends a weak signal to the nearest geosynchronous satellite which will pick up the signal. If we are lucky enough, we can get all the data uncorrupted without even sending a recovery team. We need to get quickly, though, as the data system only has enough for 3o days, so when it's off we'll have to manually retrieve it. Based on the current situation, we might have to dig it out - it could be buried too deep. Call in the-

AR202: Unable to find SCS signal. Locating alternative signals...

Bill: Don't tell me it's the prototype!

Jeb: Well, it is a prototype. But-

AR202: DS signal found. Downloading packages...

Wernher: Look, it's a handy device.

Jeb: Yeah...

AR202: Download complete.

screenshot54.png

Jeb: Pretty good, I guess.

Wernher: Probably...


This is just getting started. In a couple of months or years Jebediah and his crew will be going to space, to an alien world that was previously only visited by satellites.

Anyway, in case you are confused, I'm clarify a few:

GFS: GeoSat Flight System, the AI for most GeoSat satellites

AR202: The badass AI, used on some manned and unmanned ships. The main AI of the series.

#K: # degree Kelvins. Celsius = Kelvins - 273.15

VW-15K: The Big Brother counterpart of the VW-200. Will be used on the Duna mission.

AWLTS: Alternate Wavelength Location Transmission System. The one that determines the location, as well as trajectory, and other calculations, of the spacecraft.

SCS: Ship Communication System. Installed on every ship. For probes it's the command receiver, as well as status sender; for the manned ships it's both that and face-on communicators.

DS: Data system. Where plenty of data is stored. Where... well, look up.

As for the next chapter, I'm giving you this sneak peak:

screenshot79.png

Edited by Designer225
Link to comment
Share on other sites

The "Tests, Tests, and more Tests" chapter have been split into 2 chapters, due to size.

Prologue 2: Shuttle Test

screenshot19.png

Bobster: Why are we selected for the jobs?

Melcal: Yeah, why?

Jeb: Gene had thought of using us. But then he decided that losing Kerbals are kinda too much.

Bobster: Very funny Jeb. Think I can replace Bob?

Jeb: Nah. In case you aren't prepared, I had a surprise for you.

AR202: Hello, guys.

Bobster: You? Come on! How can this AI do?

Jeb: No comments.

Melcal: ...

Bobster: ...

Jeb: Prepare for launch!

Bill: 10... 9... 8... 7... 6... 5...

Bobster: (during countdown) Why didn't they get rid of this countdown noise and replace it with a women saying "It's time to go, baby."?

Melcal: Beats me.

Bill: ... 2... 1... Booster ignition and liftoff!

screenshot20.png

screenshot2.png

Bill: KSO has cleared the tower. Later... Begin gravity burn.

Bobster: Ahhhhhhhhh...

screenshot24.png

screenshot25.png


Some time later...

screenshot28.png

Bobster: Ahhh and ahhh...

Jeb: Wake up, Bobby and Melcal.

Melcal: Roger that, CAPCOM.

Jeb: That's more like it.

Bobster: Ha ha, Jeb.

Jeb: How's it going out there?

Melcal: Everything is good.

Jeb: Good. You guys are landing soon.

Bobster: Oh lord...

screenshot31.png


Much, much later...

Bobster: Seriously? Landing a ship?

Jeb: Well, not actually by you. AR202 will help do it.

AR202: Hello again.

Melcal: Artoo! We are glad to see you!

AR202: Are you guys there yet?

Silence. So silent that Bobster and Melcal can hear Jeb, over the comm, mumbling.

Jeb: (Mumbles quietly) Come on...

screenshot87.png

screenshot88.png

screenshot94.png

Bobster: It's pretty toasty here, Jeb.

Jeb: Right.

screenshot100.png

Bobster: Looks smooth here.

Melcal: I don't know... I think we may've been approaching too fast...

screenshot104.png

Bill: You guys are live.

Melcal: Whoops.

AR202: Brace yourself for-

Thump

Melcal: OW!

AR202: ... landing.

screenshot105.png

screenshot107.png

Jeb: Hmmm... needs reconfiguration of the engines. Wait here.

Bill: Hey, Jeb, where are you go- OW! *Thump* *Screech*

Melcal: That was the most natural moment of my life.

Bobster: Yup. Now what's next?


In the Experimental room...

screenshot72.png

Bill: Ouch. Maybe I should have removed my headphone before chasing you.

Jeb: Right.

Bill: Why did you run?

Jeb: You know, reconfiguration, redoing simulations...

Bill: What's this?

Jeb: Simulation on the prototype. We are scheduled to launch them soon, but we need to ensure that this works.

screenshot79.png

Bill: Hmmm. I think we could redesign a few.

Jeb: You think so?

Bill: Yeah.

Jeb: Well, thanks. Meanwhile, I gotta get ready.

Bill: Get ready for what?

Jeb: Dragon Test.

Bill: But how can we do it? Simulation? Kerbin test? Mun test? Teleportation?

Jeb: No, no, no, but yes. We are teleporting it.

Bill: But how?

Jeb: HyperEdit.

Bill: Oh no...


And that was another installment of the series. I was curious, though, on whether we should have many short chapters or few long chapters?

Anyway, sneak peak on the next installment:

screenshot159.png

Link to comment
Share on other sites

Prologue 3: Tests and a Change of Plan

Music to pair in:

screenshot108.png

Bill: Why AI again?

Gene: Like I said, we couldn't lose any of you.

Jeb: Come on, we are fine.

Bill: Yeah, Jeb's the master here.

Gene: Do not think that fact escapes me. Now get back to work, Jebediah and William.

Bill: Right.

Jeb: Ready, Artoo?

AR202: Ready as ever be. And stop. That nickname embarrassed me.

Jeb: Right. Sorry.

AR202: That's OK.

Gene: FIDO?

FIDO: We are go.

Gene: CAPCOM?

Jeb: We are go.

Gene: All right. All systems go. You may begin countdown now, Bill.

Bill: Roger that. 10... 9... 8... 7... 6... 5... 4... 3... 2... 1... and we have liftoff!

screenshot109.png

Bill: Looks good.

Jeb: Right.

AR202: Altitude report. Dragon at 32km ASL...

screenshot110.png

screenshot111.png

screenshot112.png


Later...

Jeb: Alright. You are to land back at KSP Pad, AR202.

AR202: Gotcha.

Bill: Wait! Isn't landing on Kerbin a little... risky?

Jeb: At this rate? No. KerbX has redeveloped the Dragon modules so that the engines are way more efficient than now. It even has enough to go home, but it of course doesn't have enough power or storage to support that.

Bill: Right.

Jeb: Anyway... Dragon CRS-1... do you read me?

AR202: ...

Jeb: I said: Dragon CRS-1... do you read me?

AR202: ...

Jeb: Seriously?

AR202: ... kxxxxxxxxxxxxxxxx Checking system. Flight plan prepared: 100%. Royalty level: 1%

Bill: Huh?

AR202: Just kidding. It's a real fireball in here.

Bill: Right.

screenshot114.png

screenshot118.png

Bill: The Dragon's coming too fast!

Jeb: Do you have to be some kind of a nuisance?

Bill: NO! I really meant that a disaster is gonna-

engine activates

Bill: Happen.

screenshot119.png

screenshot120.png

Jeb: Test one complete.

Bill: Now what?

Jeb: To DUNA!

Bill: NOOOOOOOOOOOOOO!

screenshot121.png

Bill: No! I'm not gonna handle this nonsense!

Jeb: Relax. I'm letting others to do now. Besides, we have to- beepOh frak. We are almost late for a meeting! We need to go to there NOW!

Bill: Something tells me it's not gonna end well.


At the meeting room...

Jeb: Now what?

Gene: Well, we have some problems with the ships.

Jeb: What's going on?

Gene: We are supposed to launch base ships to Duna soon, but Northrop Krumman isn't keeping up with all the necessities the precursor ship needs.

Bill: So?

Gene: That wasn't the worst - Relationship between Krussia and USK became icy when Krussia threatens Ukraine by stealing Krimea. Some of our cargo required for mission can only be launched upon the Prokon booster.

Bill: So what?

Gene: Well... It's a good luck that our shuttles are retrofitted and ready to go. But there's another problem with them.

Jeb: I thought Rockwell International is supposed to finish the shuttles today.

Gene: Yes. But they have noticed some defects and delayed the deployments of the shuttles.

Jeb: Frak! What about China! Err Kina!

Gene: The Kinese considered launching some of our equipment. But then... same problems Rockwell had.

Bob: Is it serious?

Gene: paused for a while Yeah. Pogo oscillation detected in Long March III, which is the only available Kinese launcher at the time.

Jeb: Great. Well, it is really bad?

Gene: Well, it will definitely jeopardize the precursor mission that's scheduled to launch soon. However, it won't really jeopardize the manned mission much, since the KLA - Kerbal Launch Alliance - had designed new boosters for heavier load. But the loss of scientific equipment does throw a monkey wrench into our plan. I don't know.

Jeb: Do we have to have a precursor before this? We don't have to, right?

Bill: Jeb's right. Most of the equipment launched in the precursor mission are not necessary. Besides, launching a crew who don't know much about Duna may actually kill them instead. Have you ever read Czokletmuss's novel?

Gene: Gee... OK, it's settled. We are postponing the precursor mission until after the manned mission is done. Then we'll discuss more about this. Understood?

Jeb & Bill: Yessir.


screenshot154.png

Fire.

screenshot155.png

Fireball. Hurling toward the planet.

screenshot159.png

When will this ever end?

Jeb: AR202, do you read me?

AR202: Woah... sorry Jeb, been daydreaming.

Jeb: Sure you did. Anyway, prepare for landing.

AR202: Yeah, right. Like I couldn't do it.

(Fill in this part based on the next few pictures.)

gbu-dFMefoJrHZXAkZzUNMIk6bw8utH0ekgU-b32Sic=w1038-h584-no

zvE0P1hcKEJwnZNoNB69Fu50baEjLv5JGSHUho-jryo=w1038-h584-no

screenshot162.png

screenshot164.png

screenshot165.png


Time has passed, and with each test, the Duna crew is closer and closer to the mission itself. The question is, what would happen?

Also, still awaiting opinions on either many short chapters or few long chapters.

And no, I have changed the settings for the Dragon lander. Too inefficient with the original (at least for me).

Edited by Designer225
Link to comment
Share on other sites

This thread is quite old. Please consider starting a new thread rather than reviving this one.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...