borisperrons

My god, that's simply brilliant!!! I read all this thread in a week and wow, what a writing!!! Kudos to you, Brotoro!!!

DUMAS abort modes 1. Transfer burn / Kerbin SOI limit: Retro burn to LKO (RBTL) In case of a major malfunction after leaving LKO preventing the mission accomplishement, the craft would discard the heatshield, dump all the unnecessary supplies and burn retrograde, using all the remaining fuel in the transfer stage and lander engines. Then, after re-circularizing the orbit, a Canopus capsule would recover the crew and return them to surface. 2. Kerbin SOI / Duna SOI: Duna fly-by, return to Kerbin (DFB,RTK) In case of a malfunction occuring while in interplanetary space, the craft would perform a nuber of correction prior and after a Duna fly-by, slingshotting back to Kerbin. Here either the TCC burns to circularize in orbit or it performs an aerocapture, depending on the remaining amount of fuel and the engines state. On-board supplies are more than enough to sustain the crew during the non-stop journey, and TCC is built to withstand the higher radiation and temperature levels of the intra-evian orbit. 3. Duna surface: ERV surface emergency recovery (ESER) In the case of damege to the lander, preventing him to leave the surface, the orbiting ERV would land at the base site, recovering the stranded crew and taking them back to orbit and to the TCC. To ensure the maximum dV for the takeoff, the ERV will remain mated to his Aither transfer stage, that would be used for inclination changes and for the de-orbit burn. This scenario is also used in case of a rover failure, were life support won't lanst enough to permit a rescue trip from a second DLREV. 4. Duna departure: ERV orbital emergency departure (EOED) In case of failure in the TCC engines or in his life support system, preventing the flight back home, the crew would board the ERV, that would bring them all the way to Kerbin. Here, after aerocapture, the crew would land in the ERV, lacking the dV to circularize the orbit and wait for a Canopus capule. This also means that the impossibility to pick up a landing zone. 5. Kerbin return: Emergency aerocapture and circularization (EAAC) The mission plan calls for the TCC engines to burn one last time, to perform a capture burn at Kerbin. In case of malfunction, the capsule would perform a light aerocapture, to achieve a high apoapsis and use the RCS to get a stable and highly elliptical orbit, were it would wait for a recovery mission. 6. Ike surface: ERV emergency surface recovery, Ike (EESRI) If the IEP remains stranded on Ike surface, the ERV would transfer to the moon, land, recover the kerbonauts, and bring them back to the TEC.

Err, not to be Mr. Picky McPick, but it should be 4-launches...

An hibrid flying-wheeled rover? In my opinion, that would be cool.

Day 278: Canopus T-18 launch KSC announcer: "...and we have liftoff!! Onboard the capsule, we say again, are the crew of the DUMAS-I mission to Duna, Jebediah, Gusdan, Dudsky and Geroly, and the pilots of the capsule, Commander Bill and Flight Engineer Corger. The four brave kerbals will set foot again on the red planet, to explore and..." ----- Bill: "... roll program terminated, all systems a-ok, standing by for staging. So Jeb, how is returning up there after all that training on the ground?" Jeb: "Oh, you know, it would be far better without all this G-force trying to squeeze the ribs out of your eyeballs. Still, you end up missing the good ol' SRBs, pushing you to the stars..." Geroly: "Ehy... dude... how... do you... can talk?... It's like... having a... bloody elephant... sitted... on my lungs..." Jeb: "Well, with the time you develop your breath, and all those nice kerbonaut tricks. But don't worry, when we'll have dropped the first stage, it would be far more bearable. Am I right, mon capitain?" Bill: "Shush. Ok Corger, ready on my mark. 3... 2... 1... Mark!" Corger: "BECO, staging confirmed, ullage go. Ready for ignition..." Geroly: "Ohy, I can breath again! Oh, sweet sweet oxigen, how I longed for thee, my deaHOLYCOWWHATTHEHELL..." Corger: "... and ignition. All systems a-ok, LES tower separation confirmed." Gusdan: "LES tower separation? We could have brought it up with us a little, right? I mean, just to stay safe, right? I mean, not that we needed more safety, this is the safest rocket in the world, the safest rocket in the world, the safest rocket in the world..." :heavy breathing: Dudsky: "Sir, I suspect that Engineer Gusdan may have a respiratory deficit caused by the takeoff acceleration. I ask permission to leave my seat to give medical aid, sir." Bill: "So, first choice, handpicked kerbals as usual, right?" Dudsky: "Sir?" Jeb: :grin: "Like myself. Only the best for the KSP!" Dudsky : "Sir, have you heard the precedent request?" ----- Corger: "Within docking range, sir. Do I have to engage the radar auto-docker?" Bill: "No, you know I don't trust those things. I'm sure you can handle this manually, Corger, so go on and don't scratch the paint from our passenger's ride." Corger: "Hard docking achieved, all contact lights green, hatches correctly lined up." Bill: "Good work." Corger: "Well, thank you, sir!" Jeb: "Ok guys, all aboard your new home!!" Dudsky : "Still I don't get why we are up there 5 days before departure, Sir..." Jeb: "Simple, my inquiring mate. We'll check out every single thing on this flying marvel, and when we're done, we'll check everything again." Dudsky: "Still, it looks all very inefficient to me. We're expending precious supplies, everything has been tested on Kerbin and no malfunction had been signaled by the on board computer." Jeb: "Well, experience teaches you that a computer can be very, very faulty, and I don't want to float endlessly in space to save some liters of oxigen..." Gusdan: "Floating WHAT?" Jeb: "Nothing, nothing, don't worry. Here take this manuals in the main cabin... NO GUS, the other hatch!!" ----- Day 283: Kerbin-Duna transfer window KSC announcer: "...Yes, mission control confirms the start of the last burn for the DTH Interplanetary Delivery Complex. Lasting 4 minutes, will propel the craft to a Duna encounter in 65 days. DIDC is the last unmanned craft to leave orbit, and next is the Tindalos-I, were the kerbonauts are preparing themselves to..." ----- Dudsky: "Geroly, what on earth are you doing? Shouldn't you be checking the engine bells alignment?" Geroly: "Drinking a cup of tea, dude! Do you want some? There's plenty of time before we depart!!" Dudsky: "Geroly, we're leaving in 20 minutes." Geroly: "See? Plenty of time!" Dudsky: "..." ----- Bill: "Have you checked the hidraulic systems?" Jeb: "Yes." Bill: "Primary and backup?" Jeb: "Natural." Bill: "Comms?" Jeb: "10/10." Bill: "Centrifuge motors?" Jeb: "All efficient and ready." Bill: "The heathshield?" Jeb: "We EVA'd two hours ago." Bill: "Just checking if you were paying attention." Jeb: "So... I think the moment arrived." Bill: "Yeah, I think so. Take care of you and of the boys, and bring back a red rock for the kids." Jeb: "Nah, you'll take one yourself when you'll visit. Besides, I don't guarantee for the total safety of Gusdan..." Bill: "I'm not asking for miracles, Jeb!!!" :laughs: ----- Bill: "We cleared the hatch, Jeb, you're free to maneuver. Godspeed!!" Jeb: "Thanks pal!! Ok, aligning for the burn. Last check guys, have you peed? Because this time I won't return at home just after departure..." Dudsky: "No need for: we have lavatory facilities on board..." Jeb: "Dudsky, it was just... I didn't mean it for... You... Oh, the maneuver node. Ok, all ready for ignition in 3, 2, 1... Jeb: "Ignition succesful!! NEXT STOP, DUNA!!!" ----- Corger: "Sir, are you all right?" Bill: "Mhm? What... Oh, yes Corger, yes. Why are you asking?" Corger: "You stared out of the window in silence for the best part of 10 minutes..." Bill: "Ah... I'm a little... absent." Corger: "Worried for the guys?" Bill: "No, not so much. Jeb is a skilled pilot, and apart from their evident deficiencies, his crew is really the best KSP can offer... No, I was just thinking... We three, me, Jeb and Bob, we have always sticked together, since the start of the space program. Yes, we are best pals, but let's face it, they're the good ones... They were the first on the Mun, while I went with up with the second mission; they landed on Duna, while i stayed in orbit to just wait for them... Now, Bob directs the Munar outpost, Jeb is going again to Duna, and I still fly things around Kerbin. It's just, you know, sometimes you feel useless..." Corger: "If I can say my opinion, sir, you're not being really objective. You're the most skilled capsule pilot we have, and half of KSP pilots were trained by you. Also, since I'm flying, I never seen someone to dock so efficiently and precisely, even Commander Jeb is lousy at it compared to you, KSC doesn't validate a new design if it's not tested by you... I don't think that you have to plant a flag on something to be good at something..." Bill: "... Maybe you're right Corger... Who knows... Now, too much talking, and too little action. Plot me a Homann transfer to Spacelab 1, we have science to do!!" Corger: "Aye aye, sir captain!!" Bill: :smile: "One day, Jeb, one day..."

Well, I think that if yoy bring along an MMU along with the lander and use it to hop around, that should count as another rover, since it works pretty the same way. Also, you can design an unmanned rover with roughly the same mass (to say, a cubic probe body, 4 small wheels and a fixed solar panel) so you can have the same points, although in a very less stylish way.

Yes, completely forgot it. So, the achievements. Mission execution 3 - I'm writing a mission report, and I plan to fly the missions all the way down to day 1000 Crew mobility 2 - I'll land 3 rovers, with a total capacity of 9 kerbals, versus only 8 surface personnel. Base mobility 3 - The base itself it's towable by the rovers, and i'm using a wheeled lander. Crew safety 2 - I'll explain all the contingency plans in a dedicated entry in the mission report. Mission robustness 2 - As explained in the flight plan above, i've got non critical launches and contingency launch windows, to be prepared for eventual launch failures.

Since you asked for it... Here we are, 5 kerbals, 4 launches MOR-KOR rendezvous mission!!! Mission plan: Phase one launches Two Munar Kickers, one to return the crew capsule from the Mun, and one to bring the first there. Phase two launches Another Munar Kicker, and the Crew Capsule-Lander Ok, now all down in the mathematical hell of counting the points. (I can hear the voice of my high school teacher, saying that one day logarithms would have been useful...) Launch mass: [100/(99,883*3 + 103,663)]* 1.4= 0.35 Normal staging: 2 5 kerbals : 3.32 Total: 2.324 Well, I could have done worse.

Well, seeing you roving along Munar surface and collecting all those biomes made me think. "Andrea, you really suck at driving, in real life and in KSP. You have only one way to make this working: SPAM LANDERS ON EVERY KODDAMN SINGLE FLAT AREA AT YOUR DISPOSAL." Also, I always fiddled with the idea of visiting both the bodies in a single mission. As I said, I really suck at maths Thanks for the check out!

That cross-feeding direct ascent giant!!! I didn't noticed it, but now that you made me thinking of it I see it's pretty much the same concept. Comrade Chelomei would be proud of it!! Congrats for the 100% reusable rocket!! A very elegant and small design, I have to say.

In the life of a KSP player, it comes the moment when he projects something so darn big, complex and dangerous to fly that he cannot help but saying "Holy crap, what I've just created??" (at least, an italian KSP player with tuscanian ascendancy). For me, that moment arrived with the the Holycrapturn-I. I used Kerbal Engineer and the Docking Alignment plugin. Do you remember when i said that I expected the rocket to explode any moment? Well, when i focused a landing site on the Mun to take a shoot of the spent descent stage left here, the Kraken ate it, the rover and the flag. I knew something would have happened. Anyway the points!!! Launch Single launch - 1.8 Flight plan Mun - 0.9 Minmus - 0.2 Free return trajectory - 0.1 Total - 1.2 Kerbals in space 11 kerbals = 11 points Kerbals in command pod 0.7 points base 3 kerbals left in orbit - 0.33 Total - 1.03 Kerbals landed 0.3 points base 8 kerbals landed - 0.88 Total - 1.18 Rovers 0.5 points base 4 manned rovers - 1.1 Total - 1.6 Science 0.5 points base 12 biomes visited - 3.6 Total - 4.1 Landings 0.6 points base 4 two stage manned landers - 0.7 Total - 1.3 Return Water landing - 1 Landing within 100 km of KSC (didn't misured it exactly, but I'm pretty sure to have landed nearer than that) - 0.1 Total - 1.1 Debris 1 point base NO DEBRIS!!! Survival 1 point base Just for this time, everybody lives!! Total score 1.8 * 1.2 * 11 * 1.03 * 1.18 * 1.6 * 4.1 * 1.3 * 1.1 * 1 * 1 = 270,89 (Double checked the result, but if someone check it again, it would be the most appreciated. I suck at maths.) Indeed, a funny challenge. I visited the Mun and Minmus after a long time, I designed that monstruosity and I finally made a Kerbin system grand tour (inb4 NOOB, inb4 do you even orbit , inb4 OP cant inb4). Thanks MagiMaster!!!

DUMAS 1 crew announcement Now that all the hardware of Phase 1 is in orbit and thet the transfer widow is nearing, KSC announces the first crew ever of a permanent surface base on another planet. Since the high complexity of the experimental hardware and, particularly, of the state-of-the-art closed cycle life support system, it has been decided that the first inhabitants of the base should be skillful in engineering and mechanics before being scientist. This way, they can extensively test the systems on site, and develop simple procedures to be easily followed by the subsequent scientific crews. The kerbonauts chosen for the mission are: Jebediah Kerman A hero of kerbality, famous for his courage, piloting skills and appetite for snacks. He commanded a number of ground breaking missions, including the Olympos mission to Duna, the first kerballed landing on the planet. KSC is sure that his experience in long duration missions and his charisma will come in handy in case problems should arise. Gusdan Kerman A higly skilled engineer, if a bit shaken by the idea of spaceflight. Part of the original DUMAS project, he was head designer of the DLREV. Knowing much more about that piece of equipment than anyone on Kerbin, it was decided that it was more efficient to ignore his protests and train him as a kerbonat than training a kerbonaut in DLREV engineering. During training it was assigned to the Avalon SSTO crew #2, with Jeb. Since then, the test pilot decided that his mission would be to ensure that this engineer won't kill himself searching for operation manuals outside the airlock. Dudsky Kerman Expert in complex bio-mechanical recycling systems, he will be in charge of the DTH life support systems. Also, he will be responsible for the teleoperation of remotely controlled hardware, controlling the reentry of the unkerballed surface modules. A picky and rigorous kerbal, he is famous for the precision requested from his crew mates and by his hasty manners in relating with other people. Geroly Kerman The most skilled mechanical engineer in the space program, by many. As he loves to say, he's "gifted with the MkGiver hand": he has the capacity of repairing nearly everything, given the right tools and enough time (usually, a wrench and half a minute); well remembrered is his performance on training, were he repaired a hull breach using silver paper, a couple of aid-bands and some leftover porridge. In contrast with Dudsky's behaviour, he's a very easy-going one, famous at KSC for his semi-illegal parties on top of the VAB. Jeb is confident that, if sentient life ever existed on Duna long enough to develop some sort of pub or night club, Geroly will find it out in the first 42 minutes after their landing. The most keen eyed may have noticed the lack of a medic in the crew. This because the boffins at R&D developed a full automatic medical system, the Medical Crew Assistance System (MCAS), complete of a HAL 9000-proof AI. This system has been implemented on both the Tindalos Exploration Complex and the Duna Towable Hab.

Ok, all Phase 1 launches succesful: next stop, Duna!! http://forum.kerbalspaceprogram.com/threads/65308-DUMAS-Duna-Permanent-Outpost-Mission-Architecture-Challenge-Report

DUMAS, Phase 1 launches Day 10: DTH #1 Launch Reusable strap-on boosters separation Orbital insertion burn Sustainer deorbit burn Day 47: DTH #2 Day 84: Galatea NTR DTH Interplanetary Delivery Complex Day 121: DLREV #1 Day 158: Tindalos 1 Cruise Stage, "Yog-Sototh" Day 195: Tindalos 1 Lander, "Mi-Go" Day 232: GRS-D Day 269: Tindalos 1 Crew Compartment, "Arkham" Tindalos Exploration Complex 1

This is my entry fo the Duna Permanent Outpost Mission Architecture Challenge by sturmstiger: http://forum.kerbalspaceprogram.com/threads/31510-Duna-Permanent-Outpost-Mission-Architecture-Challenge I've already posted the mission concepts, presented the hardware and the launch planning in this post on the original thread: http://forum.kerbalspaceprogram.com/threads/31510-Duna-Permanent-Outpost-Mission-Architecture-Challenge?p=888093&viewfull=1#post888093

Congrats for the official release!! I've been using the dev version for a while, and it's really wonderful. As Czo said, if you're going to expand it, you'll be a hero for us KSP players. Just a little question, has something changed from the last dev version? And downloading and substituting the old one with this would cause some compatibility issue?

Planned launches timetable 10- DTH #1 47- DTH #2 84- Galatea NTR 121- DLREV #1 (Non critical launch. if one of the previous launches fails, it goes up on this launch window. The base will be static for a cycle.) 158- Tindalos 1 Cruise Stage 195- Tindalos 1 Lander 232- Contingency Launch Window (If not needed, launch of GRS-D) 269- Tindalos 1 Crew Compartement 283- [transfer window K->D] Tindalos 1 / NTR + DTH / DLREV #1 / GRS-D 306- Supplies Package #1 343- Emergency Return Vehicle 380- Tindalos 2 Cruise Stage 417- Tindalos 2 Lander 454- Tindalos 2 Crew Compartement 491- DLREV #2 (Non critical launch) 511- [transfer window K->D] Tindalos 2 / ERV / SP #1 / DLREV #2 528- Supplies Package #2 565- Tindalos 3 Cruise Stage 602- Tindalos 3 Lander 638- Tindalos 3 Crew Compartement 676- IEP (Non critical launch) 713- DLREV #3 (Non critical launch) 723- [transfer window D->K] Tindalos 1 739- [transfer window K->D] Tindalos 3 / IEP / SP #2 / DLREV #3 861- Tindalos 4 Cruise Stage 898- Tindalos 4 Lander 935- [transfer window D->K] Tindalos 2 935- Tindalos 4 Crew Compartement 967- [transfer window K->D] Tindalos 4 (KSC <-> LKO, LDO <-> Duna transfers not shown) Flight plan VERY prone to changes.

DUna Mobile Advanced surface System MKII (AKA Vincit Qui Patitur) Mission concepts Mission planners (at least, the ones who survived the gulag) learned their lessons from the errors made on the first failed attempt at estabilishing a permanent base on Duna: a crawler base that was too much heavy and too asymmetrical for a safe launch, the overreliance on few nuclear tugs, the problem with sending fuel to LDO, the difficulty of a parachute landing on Duna...... The new DUMAS will overcome those problems with an overall redesign of the mission harware and of the execution, while mantaining the same core mission: estabilish a fully mobile surface base, with room for 8 kerbals on long term missions, and of a reliable supply train from Kerbin. A firm point is the safety of the crew: several contingency plans had been devised to ensure the survivability of the crew in the worst possible scenarios. The payloads are far smaller, and are designed to be launched mated to an expendable transfer stage where possible, or to be part of a self propelled complex. The difficulty of fuel transport invalidated the concept of an orbiting station with reusable landers: instead an expendable interplanetary complex capable of landing has been designed. Some things had to be discarded: for example, the Duna Atmospheric Exploration Vehicle (DAEV). Some argue that if it was named Duna Atmospheric Vehicle for Exploration (DAVE) the Kongress would have saved it, being a far too cool named thing to be cancelled. Mission hardware Ouranos IR Lifter This is essentially an Ouranos I lifter stripped down of the Aither upper stage and with reusable strap on boosters. It has a 25 tons to LKO payload capacity. Its short construction time means a greater number of launches, to counterbalance the lighter payloads. Aither Upper Stage This will be used as a trasfer stage to propel the lighter payloads to Duna, such as the DLREVs or the Supplies Packages. Duna Towable Hab A very flexible piece of equipment, each segment house 4 kerbals, with 150 days of provisions, comm device and autonomous electrical supply. The basic plan calls for 2 hab to be sent, but the extended mission could include more segments to expand the system. Duna Long Range Exploration Vehicle This long range rover had been ereditated directly from the first DUMAS plan with very little modifications. His role is indeed very different: it now has the role of towing the DTH around the surface, since this is not self propelled. DLREV and DTH towing test In this image we see the engineer Gusdan and the test pilot Bill testing on the field the complex. Galatea NTR A greater simplified version of the NUTS, this transfer stage will be used to transport the first two DTH to Duna, and as an orbital fuel depot for the IEP. Ike Exploration Package Another piece of hardware from DUMAS MKI. Designed to bring 2 kerbals on Ike and returning them to LDO in safety. Emergency Return Vehicle This contingency system (still in redesign phase) can land to recover some stranded kerbal on Duna or Ike, refuel at the orbiting Galatea and bringing them back to Kerbin. GRS-D (Geographical Radar Satellite - Duna) Altough the subsatellites released by the Olympos mission sent back invaluable data about atmospheric composition and gravitational properties, Duna surface has never been extensively mapped. To fill this knowledge gap about the planet, a new version of the Almak-T radar surveillance satellite has been re engineered for Duna service. The information collected by the probe will help the mission planners to direct long range explorations towards target of major scientific interest. Tindalos Exploration Complex Te original DUMAS plan called for two separate Interplanetary Crew Vehicle, two reusable landers and a Duna station to dock all of them. This design proved to be impossible with the new lifter: an Ouranos IR can't even take an ICV to orbital height, and assembling it in orbit would consume too many launch windows to be a feasible option (not counting the landers and their transfer stages). So the mission planners designed an expendable interplanetary vessel, to be launched in three parts, capable of landing 4 kerbals and returning them home, all on his own: the Tindalos. It's composed of: Tindalos cruise stage This will accelerate the complex out of Kerbin SOI, make the necessary course corrections, and raise the periapsis after aerobraking, before being ditched. Tindalos Lander This is a far more interesting piece of hardware: after detatching from the orbiter, the craft will perform a parachute assisted powered landing near the DTH. The wheels ensure the mobility of the lander, thus giving the DUMAS a full mobility to explore the planet without limits. Tindalos Crew Compartement Another marvel of kerbal engineering: this orbiter, after rendezvous with the lander in Duna Orbit, will return to kerbin, aerobrake and wait a crew return vessel in orbit, since it has no chutes, to save weight. To ensure the crew won't suffer from muscolar atrophy and bone weakening after the long trip at 0g, a state of the art inflatable centrifuge has been added at the design. Mods used Landertrons, KW rocketry, AIES, KER, ASET ALCOR pod, PorkWorks Inflatable Habitats.

Don't worry, we all are on a giant 31st December hangover, I guess. Happy new year to you too, and good luck with your moving!!

Woah! First of all, very nice works you make!! Second, I've got a little request: can you please design a patch for my Canopus space program? It's a Constellation style project, aimed to estabilish a permanent munar base and a temporary presence on Duna. I'd like it to read "Canopus Program" and "Lumen Scientiae", but for all the other details, I leave it to you. Take all the time you need, since I won't be needing for a while (exams period). Thanks in advance for your kindness

I don't think so, the save turned out to be corrupted the day before 0.23 came out. It basically decided to stop working.

So, it looks like my challenge save got corrupted. Damn. But it's not a great loss for me: flying the missions turned out to be a nightmare, and i started to fear the moment I had to turn on KSP and play the missions. So I think I'll reboot my space program, starting again with DUMAS Project Mk2: more sensible, more efficient, less explosive!!! Now with 29% more snacks!!! Stay tuned.

I agree with Weegee: engine bells are built to with stand very stressful situations, so i guess they will be able to survive a re-enter, although if only half shielded. Also, Tac life support is pretty good, and avoiding the recicle part adds to the realism: today, we don't have a practical close circuit recycling sistem (ISS relies on supply launches for life support) so for me your approach is totally fine.

Ah ah ah ah!!!! Well sir, that's a pretty darn good way to save the day!!!

Well, just do it . A launch window to another planet doesn't open and close in a single day. For example, Maven had a 20 days launch window. It's a period of time, you can launch on the end of it, and still have and encounter with Duna (although you'll need a bit more dV, and maybe a midway correction burn).