Doing It Constellation Style

septemberWaves · February 16, 2017

The Constellation program was a proposed mission architecture designed by NASA with the goal of returning to the Moon and eventually sending humans to Mars. This is a large-scale challenge dedicated to recreating the ideas proposed for the Constellation program, and then extending it for other purposes. You will be scored based on how you replicate the original Constellation spacecraft as well as how you execute the missions. You should do the first four challenges in the order (1, 2, 3, 4) or (1, 2, 4, 3) before moving on to the others (if you have challenge entries from before the December 2018/January 2019 update you can start from wherever you left off).

This challenge is somewhat inspired by @Xeldrak's Doing It Apollo Style, and @Death Engineering's Doing It Gemini Style challenges.

Thanks to @Martian Emigrant for making the mission patches.

The Constellation Mission Packs Discussion Thread has some good resources that can be incredibly useful references for Constellation-style vehicles. There are a number of links in the first post of that thread, and the vehicles people have designed for it are likely to be helpful for providing ideas as well. Also, this video is helpful for gaining some insight into the Constellation Mars mission profile, as is this, more "kerbal" video (I very much recommend watching both of these videos if you have the time, they're an excellent source of inspiration).

This delta-v map may be helpful to people. I will provide approximate values for Mios and Richell in this thread once I have figured them out.

Rules

You technically only need to complete the Objective listed in each challenge in order to qualify for completion. Doing so will earn only the minimum amount of points however, and is not really the point of this challenge.
You must provide screenshots or a video as evidence of your entry.
Stock and modded entries will be considered on separate leaderboards. Regarding modded entries, most mods are allowed so long as they're reasonably close to stock balance and are not cheaty. Entries with entirely stock parts are part of the "stock-alike" category even if you are using visual mods, information mods (MechJeb components are permitted), utilities like Stage Recovery, official DLCs (currently this only includes Making History), and/or planet mods. Life support mods are also considered part of the "stock-alike" category but will receive a note that life support was used.
You don't need to stick with the real Constellation naming scheme; using your own names for vehicles is perfectly acceptable so long as they are reasonably recognizable as analogues of the Constellation vehicles.
No cheating, of course. The only exception is if you are doing this challenge in career or science mode, in which case you may cheat in funds and science points to be able to accomplish this challenge. And do not look for loopholes in any of these rules, as doing so will be considered cheating and will invalidate your entry - essentially, if there is a need to explain why your mission should be valid based on a technicality, it is not valid.
All spacecraft launches must be flown legitimately. Mechjeb or other autopilots are acceptable (no space program has pilots do everything manually, after all), but every vehicle must be launched from a launch site or runway on Kerbin (this does not necessitate use of the KSC specifically; other launch sites are acceptable).
I'm not strict about part clipping. You can't do things like clipping functional parts or fuel tanks entirely inside each other, but doing some part clipping for the sake of aesthetics (or to do things like removing an extra couple of centimeters from a ship so it fits properly in cargo bays or fairings) is valid.
Difficulty settings must be Normal or harder, except for commnet which is not required to be turned on (but must abide by this rule if you choose to use it). There are also exceptions if you are using Kerbalism, in which case I will allow up to 95% shielding efficiency (compared to default of 90%) and 2000 days maximum time between solar storms (don't confuse this with the minimum time setting; minimum time should remain at 100 days or less).
A surface sample is a minimum-size stock ore tank filled completely with ore on the desired celestial body. An atmospheric sample is a stock "Stratus-V Roundified Monopropellant Tank" (this must be kept empty and locked, and cannot be used to store any monopropellant at any point during the mission) which must enter the target body's atmosphere at least 2km below space, at which point the sample is considered to be successful. Any sample can be returned to Kerbin either as cargo with your crew, or with its own separate re-entry and landing system.
When a vehicle should be "derived from" another vehicle (such as landers derived from Altair), this means it should be of similar design. You can add stages, you can remove stages, you can modify existing stages, as long as it is visually clear that the new design is based on the previous one. Some examples might be an ARM consisting of an Altair vehicle with no stage separation and asteroid-surveying equipment instead of extra fuel, a Bop/Pol lander which consists solely of an Altair upper stage with added electrical and landing systems, or a Laythe Ascent Vehicle consisting of a Duna Ascent Vehicle with a more powerful engine and drop tanks.

Optional challenges 6, 8, and 9 involve celestial bodies added by @Xenonclave's Xen's Planet Collection mod. The thread for it can be found here. Unfortunately this mod has not been updated since KSP version 1.2, but you are still welcome to try these challenges using the earlier version (you don't need to do every part of this challenge in version 1.2, but reverting will almost certainly require vehicle redesigns); if Xenonclave updates the mod at any time, or if someone else gets permission to update it, please let me know so I can test out the planets in the current game version and update this challenge thread accordingly.

Challenge 10 requires the Kerbal Komets mod by @Angel-125, the thread for which can be found here.

The score system works like this: you have a general score and a mission-specific score, as well as the optional science bonus. For each individual mission, your total score is the general score plus the mission score.

General Score

Launch Vehicles: Only use analogues of the Constellation-specific launch vehicles (Ares I, Ares IV, and Ares V) for all launches from Kerbin (not including satellite launches). (+10)
Ares I: Your Ares I analogue has one solid rocket motor on the first stage* and one liquid rocket engine on the second stage. *For stock entries you are allowed to use a cluster of several first-stage solid rocket motors, so long as they all ignite at the same time and have the same burn time. (+5)
Ares V: Your Ares V analogue has 5 liquid rocket engines and two solid rocket boosters on the first stage, and one liquid rocket engine on the second stage. (+5)
Stage Recovery 1: The solid first stage of the Ares I can land safely in the ocean with parachutes. You must demonstrate at least once that this works, but need not do it on every flight. (+3)
Stage Recovery 2: The SRBs on the Ares IV and V can land safely in the ocean with parachutes. You must demonstrate at least once that this works, but need not do it on every flight. (+4)
Asparagus Staging: Use asparagus staging on any vehicle. Note that fuel tanks which are jettisoned once empty do not count as asparagus staging if they do not have their own engines. (-50)
Orion: Orion is launched on the Ares I rocket and has space for at least three kerbals for stock entries, or four kerbals for modded entries. (+6)
Crew Safety: Orion includes a solid-fueled launch escape tower. (+4)
Crew Mobility: All surface modules have functional ladders. (+1)
Crew Survivability: Any kerbal dies (or runs out of life support supplies if you're using a life support mod). (-50 per kerbal)
Life Support: Use a life support mod (+25)
We're Doomed: Specifically use Kerbalism as your life support mod; difficult settings must be Normal or harder. (+5 added to the +25 for Life Support)
Thawed: Use the Deep Freeze mod, or similar mods that pause life support mechanics. (-50)
Larger Than Life: Use a scaled-up version of the Kerbol system with a scale factor of at least 2 (day length cannot be reduced below 6 hours but may be increased). For mission duration points, I advise the use of Kronometer to adjust the game clock when Kerbin's day/year is extended. (+(5+scale factor))
Commnet: Do everything with commnet enabled at the default (normal mode) settings or more difficult. (+10)
Kerbals are green enough already: Use RTGs or nuclear reactors on any crewed vehicle; or use nuclear engines on any crewed vehicle aside from interplanetary transports. This only applies when crew are actually present. (-20 for each vehicle)
Reasonably Accurate: Don't do anything too ridiculous (i.e. anything which is so drastically beyond the the theoretical capabilities of Constellation technology that I have to actually complain about it). Doing so will lose you some points. (-30)

Science Bonus

This is a separate score to the ordinary scores, which judges you by the amount of science points you can collect in a mission. There are three categories:

Stock-only: Collect as many science points from your target celestial body as possible using only stock science experiments.
Stock + DMagic: DMagic Orbital Science is a popular enough mod to warrant its own category; collect as many science points from your target celestial body as possible using only stock experiments and experiments from the DMagic Orbital Science mod. The exception to this is the SIGINT experiments, which are prohibited because their size makes them frankly ridiculous to include as part of any crewed mission.
Mad Science: Use as many science-adding mods as you like to gather as many science points as possible.

There are also certain rules you must follow for your science score to be valid:

Science returns must be set to 100% for all categories, in order to keep scores balanced with each other.
For the asteroid mission, collect the science data only from Kerbin orbit when you are near the asteroid, and for the komet mission collect the science data only from solar orbit when you are near the komet. In all other missions you cannot use data from solar orbit or from Kerbin to contribute to the score; your data must come exclusively from celestial bodies which are the targets of the mission.
Your science experiments must be sent to the target celestial body on a crewed vehicle, and must return to Kerbin with your crew (they cannot be transmitted). This rule exists to prevent you from using the commsats that some tasks require as a means of science collection; do not do this, it will invalidate your entry to this category.
You can only collect science data from places your kerbals have been to. For example, if you are exploring the Joolian moons but are not sending kerbals to Vall, you cannot send a probe to land on Vall and collect science for the science bonus.
You cannot use a lab to increase your science yield.
Do not do anything too ridiculous to collect science data. By this, I mean things like collecting a near-Kerbin asteroid and bringing it with you to Duna for asteroid sounding experiments, or sending a kerbal deep into the atmosphere of Jool for lower atmosphere science (I am sure you can understand the kind of thing I mean). This kind of thing is too extreme for the Constellation program. This rule is waived for the Mad Science category for the sake of people who want to maximize science gains; however, you will lose the points for reasonable accuracy from your general score.

Mission 1: Munar Sortie

A large part of the purpose of the Constellation program was to return to the Moon. In KSP this equates to a Mun mission.

Spoiler

Objective: Using the Orion spacecraft and the Altair lander, send four kerbals (three for stock entries) to the surface of the Mun and return them safely to Kerbin. (+20)
Kerbin Orbit Rendezvous: The Orion spacecraft and the Altair lander are launched separately and dock in Kerbin orbit before transferring to the Mun. (+8)
Accurate Altair: The Altair Munar Lander includes a descent module and an ascent module, and has space for all four kerbals (three for stock entries). (+7)
Fuel Cells: The Altair lander is powered by a fuel cell. (+2)
Descent Module: The Altair descent module is left on the surface of the Mun, and includes: airlock, fuel and engines for landing, landing legs, power storage (at least 1000 electric charge). (+4)
Kerbin Departure Stage: The Mun transfer burn is done using the upper stage of the rocket that launched the Altair lander. (+3)
Altair Orbital Insertion: The orbital insertion burn at the Mun is done using the engines and fuel system of the Altair lander. You should design the lander to include enough additional fuel in the descent module to accomplish this task. (+3)
Mun Rover: Bring along a rover with seats for at least half the crew. (+3)
Surface Sample: Return a surface sample from the Mun to Kerbin. (+8)

Completing this challenge will earn you this mission patch:

Mission 2: Asteroid Rendezvous

"The public wants us to have mastered the problem of dealing with asteroids. So being able to have astronauts go out there and sort of poke one with a stick would be scientifically valuable as well as demonstrate human capabilities." - Chris McKay, Constellation deputy scientist, on the potential value of using the Constellation infrastructure for an asteroid rendezvous mission

Spoiler

Objective: Send a fully crewed Orion spacecraft and an Asteroid Research Module to rendezvous with a Near Kerbin Asteroid (NKA) - this is defined as any asteroid which passes through Kerbin's SOI - and then return the crew safely to Kerbin. (+20)
Kerbin Orbit Rendezvous: The Orion spacecraft and the ARM are launched separately and dock in Kerbin orbit before transferring to the asteroid. (+5)
Asteroid Research Module: The ARM is derived in some way from the Altair lander (it should be visually similar), and includes a grabbing unit to attach to the asteroid. It should be able to undock from the Orion spacecraft when near the asteroid, and land on the asteroid using its own propulsion systems. (+8)
Asteroid Science: The ARM includes a functional drill, ore tanks, and some sort of science equipment for surveying the asteroid. (+5)
Crew Comfort: The ARM includes habitation space for all of the kerbals on the mission. (+5)
Moderate Duration: The total time the crew spend in space is less than 20 Kerbin days. (+6)
Taking Things Literally: As per the quote used to introduce this challenge, poke the asteroid with a stick. (+2)
Surface Sample: Return a sample of the asteroid to Kerbin. (+8)

Completing this challenge will earn you this mission patch:

Mission 3: Crewed Duna Mission

The ultimate goal of the Constellation program was to send a crewed mission to Mars. The KSP equivalent, of course, is Duna. This will be a much larger mission than the previous two challenges, requiring more launches, more planning, more kerbals, and more time.

Spoiler

Objective: Land 6 kerbals (5 for stockalike entries) on Duna and return them safely to Kerbin. (+30)
Extra Crew: Use an upgraded version of your Orion spacecraft that contains two extra kerbals. Alternatively, use two Orion spacecraft for the crew. (+8)
Scheduled Transfers: Excluding support satellites, send all Duna payloads within just two consecutive transfer windows. Launch the uncrewed payloads to Duna in the first transfer window, and send the crew to Duna in the second transfer window. (+6)
Careful Planning: Send a satellite to orbit Duna and choose a landing location with a high ore concentration. (+5)
Constellation Constellation: Send at least three relay satellites to orbit Duna, and one to orbit the Sun, to ensure that the crew have a connection to Kerbin at all times. These satellites may either be transported all at once or individually, and they do not need to be identical. Depending on your desired landing location you may need more than three satellites for full coverage; points are only achieved if the crew has a constant connection to Kerbin. (+4)
Cargo Lander: Use a standardized lander for both the Duna habitat and the Duna ascent vehicle. The lander should be able to make a parachute-assisted propulsive landing on Duna. (+8)
Transfer Stages: Use separately-launched chemical or nuclear transfer stages for the uncrewed payloads (habitat and ascent vehicle) (does not include support satellites). (+5)
Heat Shielding: Cargoes landed on Duna are protected by a fairing during atmospheric entry. (+3)
Surface Habitat: Send a habitation module to Duna which has space for all of the crew and an airlock (airlock does not count as part of living space). The habitation module should await the crew in Duna orbit and be used to land them on the surface. (+10)
Hab Lab: Habitation module includes a science lab (lab space does not count as part of living space). (+4)
Duna Ascent Vehicle: A single DAV is used with space for all of the crew. It must have sufficient power systems and must be able to rendezvous and dock with the Duna Transfer Vehicle. (+9)
ISRU: The fuel tanks for the DAV are filled using ore mined and refined on Duna. (+7)
Surface Mobility: Include a rover with space for at least three kerbals. (+3)
Surface Mobility 2: The rover fulfills the previous requirement and is pressurized. (+2)
Duna Transfer Vehicle: Your crewed DTV is solar powered and has sufficient habitation space (at least 2 seats per kerbal). It should be assembled in orbit using multiple launches and a modular design. (+5)
Nuclear DTV: Your DTV is propelled by 3 nuclear thermal rockets, and includes one drop tank that is jettisoned after the trans-Duna injection burn. (+5; does not stack with Chemical DTV or Ion DTV)
Chemical DTV: Your DTV is propelled by several (3 to 5 ideally) chemical rocket stages that are jettisoned when out of fuel. (+5; does not stack with Nuclear DTV or Ion DTV)
Ion DTV: Your DTV is propelled by an ion drive which does not jettison fuel tanks or engines. (+5; does not stack with Nuclear DTV or Chemical DTV)
Spacecraft Shipment: Your Orion spacecraft is transported to Duna and back whilst docked to the DTV, and is used to re-enter and land back at Kerbin. If you are using two Orion spacecraft, you must do this for both of them. (+2)
Mission Time: Your crew spend at least 1 Kerbin year on the surface of Duna, and are back on Kerbin in no more than 5 Kerbin years since they were launched. (+6)
Surface Sample: Return a surface sample of Duna's surface to Kerbin. (+12)
Atmospheric Sample: Return a sample of Duna's atmosphere to Kerbin. (+5)

Completing this challenge will earn you this mission patch:

Mission 4: Mun Base

To extend operations on the surface of the Mun, you have to assemble a Mun base.

Spoiler

Objective: Land modules of a Mun base on the Mun using Altair descent stages, and then send 4 kerbals (3 for stockalike entries) to the base for an extended duration mission. (+30)
Base Size: Score for the number of modules you add to the base. (+5 for each module, capped at +25)
Crew Quarters: Include plenty of habitation space (at least 2 seats per kerbal, not counting labs or airlocks). (+8)
Science Module: Include a science lab and science equipment. (+8)
Total Mobility: Include a pressurized rover with space for the whole crew. The lander used for the rover does not count as a base module unless it also has another function. (+8)
Pressure Preservation: All modules containing kerbals (except the rover) have a dedicated airlock. (+3)
Careful Planning: Send a scanning satellite to orbit the Mun ahead of time, and choose a landing site with high ore concentration. (+4)
Phone Home: Make sure your Mun base has a constant commnet connection to Kerbin (either by being on the Kerbin-facing side of the Mun or by launching relay satellites). (+3)
Power Systems: Mun base modules are powered by solar panels and have enough power storage to maintain functionality when the base is in darkness. (+9)
Anomaly Survey: Choose a base location within visual range of any Munar anomaly, and plant a flag near it. (+3)
Long-term Stay: The crew stay at the Mun base for at least one Munar orbit per base module (for example, if your base has three modules your crew must remain there for three Munar orbits). (+4)
Crewed Mission: When sending crew to your Mun base, add all relevant points from the Munar Sortie challenge (points which apply for this new mission, not your previous Munar Sortie attempts).

Completing this challenge will earn you this mission patch:

Mission 5: Crewed Dres Mission

Following previous asteroid rendezvous missions, you must send a crewed mission to the largest object in Kerbol's main asteroid belt: Dres.

Spoiler

Objective: Land 6 kerbals on Dres and return them safely to Kerbin. (+30)
Extra Crew: Use an upgraded version of your Orion spacecraft that contains two extra kerbals. Alternatively, use two Orion spacecraft for the crew. (+8)
Scheduled Transfers: Launch the uncrewed payloads (satellites and landing vehicles) to Dres in the first transfer window, and send the crew to Dres in the second transfer window. (+6)
Careful Planning: Send a satellite to orbit Dres and choose a landing location with a high ore concentration. (+5)
Constellation Constellation: Send at least three relay satellites to orbit Dres to ensure that the crew have a connection to Kerbin at all times. (+4)
Lander Coherence: Use Altair-based landing vehicles. Dres is similar to the Mun in terms of delta-v requirements, so you should require few modifications from the original Altair design. (+8)
Transfer Stages: Use separately-launched chemical transfer stages for the uncrewed payloads (not including satellites). (+5)
Surface Operations: Include two uncrewed cargo landers for surface modules. (+5)
Surface Habitation: Include plenty of habitation space (at least 2 seats per kerbal, not counting labs or airlocks). (+8)
Science Module: Include a science lab and science equipment. (+8)
Surface Mobility: Include a rover with space for at least three kerbals. (+3)
Surface Mobility 2: The rover fulfills the previous requirement and is pressurized. (+2)
Pressure Preservation: All modules containing kerbals (except the rover) have a dedicated airlock. (+3)
Power Systems: Surface modules are powered by solar panels and have enough power storage to maintain functionality when the base is in darkness. (+9)
Interplanetary Coherence: Use an interplanetary spacecraft based on the same design as the one used for the Duna mission (either identical in design or modified for the higher delta-v requirement). It should be assembled in orbit using multiple launches and a modular design. (+10)
Spacecraft Shipment: Your Orion spacecraft is transported to Dres and back whilst docked to the interplanetary transport, and is used to re-enter and land back at Kerbin. If you are using two Orion spacecraft, you must do this for both of them. (+2)
Mission Time: Your crew spend at least 1 Kerbin year on the surface of Dres, and are back on Kerbin in no more than 8 Kerbin years since they were launched. (+6)
Surface Sample: Return a surface sample of Dres to Kerbin. (+16)

Completing this challenge will earn you this mission patch:

Mission 6: Extended Duna Mission

After the success of the first crewed Duna mission, there is now additional funding to expand upon the Duna exploration infrastructure in the next mission to the red planet. You are tasked with sending two more cargo payloads to Duna, and have several additional objectives on top of the previous mission parameters.

Spoiler

Objective: Conduct a second mission to Duna involving two extra cargo payloads (one for the large rover, one for the moon lander). (+30)
Basic Requirements: Add all points from the original Duna mission section that also apply to this second mission (points are judged by this mission, not previous Duna mission attempts).
Change of Scenery: Land in a different biome than the previous mission. (+4)
Mobile Base: Send a large crew rover to the surface of Duna. It must be solar powered, have sufficient habitation space for all crew members, and have an airlock. It is not a replacement for the original habitation module, but should be equipped for long-duration surface excursions. (+10)
Landing Systems: Land the large rover in the same way as the other payloads to Duna's surface. You should use a similar cargo lander, but may make modifications if necessary. (+6)
Anomaly Survey: Send your crew to any Duna anomaly in the large rover and plant a flag near it. (+3)
Moons of Duna: Using a modified Altair lander, land four kerbals on the surface of Ike either before or after the Duna surface excursion (if you have XPC installed you have to land them on Nyke as well using the same vehicle). (+10)
Moon Lander: Your Ike lander is derived from the original Altair design, but is solar powered. The two-stage design is recommended but not required, as Ike requires only about 2/3 the delta-v of the Mun. (+7)
Moon Mobility: Bring a rover to Ike with seats for at least 2 kerbals (you don't need one for Nyke if you have XPC installed). (+4)

Completing this challenge will earn you this mission patch:

Mission 7: Laythe, and the Jool system

The primary goal of this mission is to explore Laythe. Jool's other moons are secondary targets for research. The only requirement for earning the badge is the primary objective (secondary and tertiary objectives are not required) but the other tasks are worth attempting. Work In Progress

Spoiler

Phase 1: Satellites

Constellation Constellation: Send at least three relay satellites to orbit Jool, at least three to orbit Laythe (possibly more depending on intended landing site), one to orbit the sun (anywhere beyond the orbit of Duna), and at least two to orbit each Joolian moon (aside from Laythe) you intend to land crew on, to ensure that your kerbals have a constant connection back to Kerbin. (+15)
Careful Planning: Send a satellite to orbit each Joolian moon you intend to land crew on, and choose a landing location with high ore concentration. (+3 for each moon)

Phase 2: Uncrewed Payloads

Payloads in this phase should be sent to the Jool system in a transfer window after the satellites are sent, but before the crewed phase of the mission. Payloads which require landing on a Joolian moon must be successfully landed,, and payloads that are intended to await the crew in orbit of Jool or its moons must be positioned in their desired orbits, before the crew are to be launched from Kerbin.

Surface Habitat: Send a habitation module to Laythe which has space for all the crew and sufficient supplies for them to spend most of their time in the Jool system on Laythe's surface. The habitation module should await the crew in orbit of Laythe, and be used as their landing vehicle much like in the Duna mission(s). (+6)
Hab Lab: Habitation module includes a science lab (lab space does not count as part of living space). (+4)
Laythe Ascent Vehicle: Two LAVs are used, each with space for half of the crew. Each must have sufficient power systems and be able to rendezvous and dock with the Jool Transfer Vehicle under its own power. It must be a vertical rocket, and cannot be a spaceplane or use airbreathing engines (this kind of technology is beyond the capabilities of the Constellation program). The LAVs should be derived from the Duna Ascent Vehicle but do not need to be identical. They must be landed on Laythe before the crewed phase of the mission begins. (+12)
Mobile Base: Send a large rover to Laythe. It must have sufficient power systems (fuel cells are suggested) and space for all crew members. It must be pressurized and must have an airlock. It is not a replacement for the habitat, but should be equipped for long-duration surface excursions. (+10)
It can swim?: The large rover is amphibious. (+10)
Cargo lander: Similar to the Duna mission, you should use standardized cargo landers for all payloads landed on Laythe. The landers should be derived from the Duna ones (but they do not need to be identical to those). They should be able to land on the surface of Laythe (water landings are not valid) using either parachute-assisted propulsion, or parachute-only methods (no wings, but steering fins are permitted). (+8)
Heat Shielding: Cargoes landed on Laythe are protected by a fairing during atmospheric entry. (+3)
Tylo Infrastructure: If you plan to explore Tylo, send a 2-kerbal lander to orbit Tylo. The lander should be derived from the Altair lander. (+12)
Tylo Surface Mobility: Your Tylo lander includes a rover which can transport both crew members short distances across the surface of Tylo. (+8)
Vall Infrastructure: If you plan to explore Vall, send a 2-kerbal lander to orbit Vall. The lander should be derived from the Altair lander. (+8)
Vall Surface Mobility: Your Vall lander includes a rover which can transport both crew members short distances across the surface of Vall.(+4)
Bop/Pol Infrastructure: If you plan to explore Bop and Pol, send a 2-kerbal lander to await the crew in orbit of whichever inner moon (Laythe, Vall, or Tylo) you intend to explore last. The lander should be derived from the Altair lander, and must be capable of transporting the crew to the surface of both Bop and Pol from an inner moon where the interplanetary transport will await, and returning after the surface excursions on both moons have been completed. (+8)
Bop/Pol Surface Mobility: Your Bop/Pol lander includes either a rover or a monopropellant flyer (not both) capable of transporting one crew member short distances across the surface of Bop or Pol. The lander must be capable of transporting this vehicle to the surface of both moons. (+7)
Transfer Stages: Use separately-launched chemical or nuclear transfer stages for all uncrewed payloads in this phase of the mission. (+5)

Phase 3: Crewed Exploration

Once all other mission components are in place, it is time to send kerbals to explore Laythe (and, potentially, other Joolian moons). I would advise assembling the Jool Transfer Vehicle while Phase 2 payloads are on their way to the Jool system; this is probably how it would be done in a realistic situation.

The general mission profile is as follows: send your crew in the Jool Transfer Vehicle to the Jool system and land them on Laythe using the Laythe habitat as a landing vehicle, while the JTV awaits in Laythe orbit; next, remove all crew members from Laythe and explore Vall and Tylo (these are optional) in either order (if exploring both), using the JTV to transfer the crew between moons; next, leave the JTV in orbit of the most recently explored moon, and send two kerbals to land on Bop and Pol (you must land on both); finally return the crew to Kerbin.

Primary Objective: Send eight kerbals (six for stock entries) to the Jool system, land them on the surface of Laythe, and return them safely to Kerbin. The crew should spend the majority of their time in the Jool system on the surface of Laythe. (+40)
Secondary Objective - Tylo: After the surface excursion on Laythe, land two kerbals on the surface of Tylo. (+20)
Secondary Objective - Vall: After the surface excursion on Laythe, land two kerbals on the surface of Vall. (+16)
Secondary Objective - Outer Moons: After the surface excursions on chosen inner moons, land two kerbals on both Bop and Pol using the same vehicle. (+16)
Tertiary Objective - Surface Samples: Return a surface sample to Kerbin from each moon you land kerbals on. It is acceptable to use autonomous landers to obtain the samples, but these probes must be transported to the Jool system as cargo on the Jool Transfer Vehicle. Samples must be returned to the JTV for analysis during the return trip. (+8 for each moon)
Tertiary Objective - Atmospheric Samples: Return atmospheric samples of Jool and Laythe to Kerbin. The Jool sample should be obtained by dipping an autonomous probe into Jool's upper atmosphere; this probe must be transported to the Jool system as cargo on the Jool Transfer Vehicle. Samples must be returned to the JTV for analysis during the return trip. (+12)
All Objectives: Successfully completing all primary, secondary, and tertiary objectives will earn you some extra points. (+10)
Jool Transfer Vehicle: The Jool Transfer Vehicle uses a similar design to previous interplanetary transports (upgraded if necessary) and has sufficient habitation space (at least two seats per kerbal). It should be assembled in orbit using multiple launches and a modular design. (+16)
Artificial Gravity: Your Jool Transfer Vehicle includes some sort of centrifuge (it does not need to actually function as one if you do not have a mod for that, but it has to at least resemble a centrifuge). (+8)
Science Module: Your Jool Transfer Vehicle includes a science lab (lab space does not count towards crew habitation space). (+4)
Re-entry Module: Re-entry speeds from Jool will induce heating beyond what Orion was designed for; you should include a dedicated re-entry module with space for all crew members. (+4)
Dual Orion: Use two Orion spacecraft to send crew from Kerbin up to the Jool Transfer vehicle. You should return them to Kerbin empty once the crew are in the JTV. (+4)
Celestial Assistance: Gravity assists from other planets will push the mission duration far beyond what is practical. If you use gravity assists outside of the Jool system, you lose points. (-50)

Assorted Tasks

These tasks are not part of any particular phase of the mission, and are simply extra goals that you can attempt if you want to earn some extra points.

Gravity Captures: All spacecraft entering the Jool system make use of a gravity assist from at least one Joolian moon. (+8)
Kraken Lair: Find the space kraken. (+3)

Completing this challenge will earn you this mission patch:

Mission 8: Crewed Mios Mission

Mios is a planet from Xen's Planet Collection. It lies between the orbits of Duna and Dres. You should explore it using modified Duna mission infrastructure.

Planet details:

Spoiler

Mios is somewhat similar to Duna, but is also different in many ways. Its most unique feature is its equatorial ocean, which covers several degrees of latitude (I think about 20°) to both the north and south of the equator. It also has a thicker atmosphere than Duna, but it's not as dense as the atmosphere of Kerbin.

Mios has two moons: Glac and Serc. They are both quite small (even by KSP's standards) but are worth visiting.

Delta-v info:

Mission goals:

Spoiler

Objective: Land 6 kerbals (5 for stock entries) on Mios and return them safely to Kerbin. (+30)
Extra Crew: Use an upgraded version of your Orion spacecraft that contains two extra kerbals. Alternatively, use two Orion spacecraft for the crew. (+8)
Scheduled Transfers: Launch the uncrewed payloads to Mios in the first transfer window, and send the crew to Duna in the second transfer window. (+6)
Careful Planning: Send a satellite to orbit Mios and choose a landing location with a high ore concentration. (+5)
Constellation Constellation: Send at least three relay satellites to orbit Mios to ensure that the crew have a connection to Kerbin at all times. (+4)
Cargo Lander: Use a standardized lander for both the Mios habitat and the Mios ascent vehicle. The lander should be able to make a parachute-assisted propulsive landing on Mios. (+8)
Transfer Stages: Use separately-launched chemical or nuclear transfer stages for the uncrewed payloads (does not include support satellites). (+5)
Heat Shielding: Cargoes landed on Mios are protected by a fairing during re-entry. (+3)
Landing Precision: Land on the surface of Mios within reasonable driving distance of the ocean. (+3)
Landing Prestige: Land on an island in the ocean of Mios. (+10; does not stack with Landing Precision)
Surface Habitat: Send a habitation module to Mios which has space for all of the crew and an airlock (airlock does not count as part of living space). The habitation module should await the crew in Mios orbit and be used to land them on the surface. (+10)
Hab Lab: Habitation module includes a science lab (lab space does not count as part of living space). (+4)
Mios Ascent Vehicle: A single MAV is used with space for all of the crew. It must have sufficient power systems and must be able to rendezvous and dock with the Mios Transfer Vehicle. (+9)
ISRU: The fuel tanks for the MAV are filled using ore mined and refined on Duna. (+7)
Mios Surface Mobility: Include a rover with space for at least three kerbals. (+3)
Mios Surface Mobility 2: The rover fulfills the previous requirement and is pressurized. (+2)
Snowball: Land four kerbals on Glac using a lander derived in some way from the Altair design. (+7)
Captured Space Potato: Land four kerbals on Serc using the same lander that was used for Glac (+7; requires Snowball)
Mios Transfer Vehicle: Your crewed MTV is derived from the same interplanetary transport design used in previous missions (upgraded if necessary) and has sufficient habitation space (at least 2 seats per kerbal). (+5)
Spacecraft Shipment: Your Orion spacecraft is transported to Mios and back whilst docked to the MTV, and is used to re-enter and land back at Kerbin. If you are using two Orion spacecraft, you must do this for both of them. (+2)
Mission Time: Your crew spend at least 1 Kerbin year on the surface of Mios, and are back on Kerbin in no more than 6 Kerbin years since they were launched. (+6)

Completing this challenge will earn you this mission patch:

Mission 9: Crewed Richell Mission

Richell is a planet added by Xen's Planet Collection. It has retrograde rotation and orbits Kerbol between Dres and Jool. Work In Progress

Planet details:

Spoiler

Richell is quite an interesting planet. It has a strip of rough land around the equator with oceans at both poles. Its biggest challenge is its exceptionally-tall atmosphere, which makes ascending from the planet's surface quite difficult even though atmospheric pressure is relatively low.

Richell has one moon: Iber. Though the planet rotates in a retrograde direction, Iber has a prograde orbit above the rings. If you choose to visit Iber you will have to make your Richell ascent vehicle even more powerful, as it will have to go against the planet's rotation.

Delta-v info: WIP

Mission goals:

Spoiler

Completing this challenge will earn you this mission patch:

Mission 10: Komet Rendezvous Mission

Building on the previous asteroid rendezvous missions, you now have to send four kerbals to study a komet in solar orbit. Work In Progress

Spoiler

Leaderboards

Stock/stockalike

Spoiler

Mission 4: Mun Base

Spoiler

Kerbolitto: 188

Modded

Spoiler

Mission 1: Munar Sortie

Spoiler

michal.don: 106.2

Science Bonus

Spoiler

Old Leaderboards (pre-December 2018/January 2019 update)

Spoiler

Stock

Spoiler

Challenge 1: Munar Sortie

Spoiler

Death Engineering: 123 (with life support)
Xeldrak: 98
Kerbolitto: 98
Martian Emigrant: 95
HiThere!2: 89
Thor Wotansen: 85

Challenge 2: Asteroid Rendezvous

Spoiler

Death Engineering: 118 (with life support)
Kerbolitto: 99
Martian Emigrant: 81

Challenge 3: Crewed Duna Mission

Spoiler

Death Engineering: 194 (with life support)
Kerbolitto: 170

Challenge 4: Munar Base

Spoiler

Death Engineering: 214 (with life support)

Challenge 5: Crewed Dres Mission

Spoiler

Death Engineering: 195 (with life support)

Modded

Spoiler

Challenge 1: Munar Sortie

Spoiler

Challenge 2: Asteroid Rendezvous

Spoiler

Challenge 3: Crewed Duna Mission

Spoiler

eloquentJane: 170
foobar: 154

Challenge 4: Mun Base

Spoiler

eloquentJane: 190
foobar: 182

Challenge 5: Crewed Dres Mission

Spoiler

Challenge 6: Extended Duna Mission

Spoiler

foobar: 228

Surface Science Bonus

Spoiler

Mun

Spoiler

eloquentJane: 1656
NISSKEPCSIM: 250

Duna

Spoiler

eloquentJane: 1580

Edited February 4, 2019 by septemberWaves
Updated leaderboards.

TheGuyNamedAlan · February 16, 2017

it would be helpful to make the mission parameters clear for those people who dont know how constellation works.

septemberWaves · February 16, 2017

59 minutes ago, TheGuyNamedAlan said:

it would be helpful to make the mission parameters clear for those people who dont know how constellation works.

It's a work in progress, as indicated by the big red "Work In Progress" sign at the bottom of the post. I haven't finished writing up the parameters yet.

septemberWaves · February 17, 2017

The first challenge is ready for completion. It's possible I might make a few tweaks to the scoring, but for the most part it should be good to go.

septemberWaves · February 17, 2017

I've changed the requirement from four kerbals to three for the Orion capsule, on account of stock having few suitable four-kerbal parts. This decision moves a bit away from realism but is designed to allow better balancing for stock players.

Edited February 17, 2017 by eloquentJane

MarvinKitFox · February 17, 2017

The correct way to replicate the Constellation spacecraft:

* Draw up elaborate plans for a spacecraft.

* Modify, re-modify, and re-re-modify your plans

* Now spend 17.3 earthly Fortunes on the projects

* Launch one token simulator of the least of your designs, then call it quits.

* 10 years later, rename your system SLS, and get ready to spend another double-handful of Fortunes on it.

* Tell everyone it will be ready in '16. erm, '17. make that '19. maybe '21

Martian Emigrant · February 17, 2017

2 hours ago, eloquentJane said:

I've changed the requirement from four kerbals to three for the Orion capsule, on account of stock having few suitable four-kerbal parts. This decision moves a bit away from realism but is designed to allow better balancing for stock players.

Hello EJ.

I will be doing this soon. Must take the shuttle one a bit further first.

I had accepted the four Kerbal part of the challenge.

Right now you have it has 3 Kerbals = 20 points. Could you had another bonus for doing it with 4?

Thanks,

ME

Edited February 17, 2017 by Martian Emigrant

septemberWaves · February 17, 2017

48 minutes ago, Martian Emigrant said:

Right now you have it has 3 Kerbals = 20 points. Could you had another bonus for doing it with 4?

I changed the requirement to allow three to balance it against stock. I may actually make it so that stock players require three whilst modded players require four (due to the wider range of suitable parts). Does that sound like a good idea?

Good luck with your attempt, in any case. There are also going to be an asteroid rendezvous challenge and a Duna challenge coming soon (those are the "first three challenges" that the introduction alludes to), with some extra things later. It'll probably end up being something like the Shuttle Challenge in that there will be several sub-challenges to complete.

Also, I need to modify the score system somewhat. There will be the same points categories as there currently are, but keep in mind that it'll have some changes soon.

Edited February 17, 2017 by eloquentJane

Xeldrak · February 17, 2017

Ah, I might give it a try. The three kerbal for stock, four for modded sounds nice to me. While you can botch together a four kerbal command module, it allways looks a little absurd.....

septemberWaves · February 17, 2017

35 minutes ago, Xeldrak said:

While you can botch together a four kerbal command module, it allways looks a little absurd.....

Thats why I changed it in the first place. I like things to look nice, and unfortunately stock KSP is already extremely limited in that regard. Requiring a 4-kerbal command pod from stock players would just lead to unpleasant aesthetics.

Edited February 17, 2017 by eloquentJane

septemberWaves · February 17, 2017

I'm going to get things started here with my entry for the Munar Sortie challenge. This is done as a test of the technology rather than as an attempt to gain points; having done it, I know what I need to do to improve my entry in future.

Mission designation: MSM1 (Munar Sortie Mission 1).

The Altair lander is launched first, on the Ares V rocket.

Spoiler

Ignition.

Liftoff of MSM1-Altair.

Commencing gravity turn.

Breaking sound barrier.

Approaching booster cutoff.

Booster cutoff and separation.

Reaching maximum dynamic pressure.

At this point in flight the main engines are throttled back to reduce time to apoapsis and ensure that first stage cutoff occurs before the intended 120km apoapsis is reached.

Fairing separation.

Here you can see some of the details of the Altair lander. I'm very pleased with how the design turned out.

First stage cutoff and separation.

KDSE (Kerbin Departure Stage Engine) ignition.

Confirmation from Stage Recovery that the SRBs landed successfully.

KDSE cutoff as 120km apoapsis is reached.

Circularizing.

Circularization complete.

The Altair lander and Kerbin Departure Stage now await the crew in Kerbin orbit.

Back at the KSC, the crew prepare for launch on an Ares I rocket. The crew of this mission are Valentina Kerman (Orion Pilot), Wenliana Kerman (Scientist), Phoanne Kerman (Engineer), and Berella Kerman (Lander Pilot).

Spoiler

Ignition. The engine plume is off-center due to a visual bug; it is not a problem with the launch vehicle.

Liftoff of MSM1-Orion.

Commencing gravity turn.

Breaking sound barrier.

First stage cutoff.

First stage separation. The first stage was destroyed for some reason; it is suspected that the failure has to do with the separation motors on the first stage. The second stage does not appear to have sustained any damage.

Second stage ignition.

Reaching maximum dynamic pressure.

First stage cutoff as 80km apoapsis is reached.

LES jettison.

Circularizing.

Circularization complete.

Second stage separation. The separation motors de-orbit the stage to avoid leaving debris in Kerbin orbit.

The Orion spacecraft in orbit of Kerbin.

Several maneuvers are executed to rendezvous with MSM1-Altair.

Approaching Altair.

Zeroing relative velocity.

Approaching the lander to dock.

Docking successful.

The only accurate delta-v information here is Stage 4, which is the KDSE.

Now that the spacecraft are assembled in Kerbin orbit, it is time to transfer to the Mun.

Spoiler

The Mun transfer burn is plotted.

Executing Mun transfer burn.

Maneuver complete.

A mid-course correction is required to ensure that the spacecraft can reach a polar orbit of the Mun.

After the mid-course correction, the Kerbin Departure Stage is jettisoned.

Using its own built-in control systems, it places itself on a collision course with the Mun.

The only accurate delta-v information here is Stage 2. That is the Altair descent engines, which will be used to circularize in Munar orbit.

Approaching the Mun.

The circularization maneuver is plotted and executed.

The crew transfer to the Altair lander, and then undock to prepare for landing.

They will be landing in the Mun's polar crater, as it is theorized that there may be water and other useful materials there. The scientific data collected on this mission will help to find a good location for a surface base.

De-orbiting.

Final approach to land.

Landing successful. MSM1-Altair has touched down on the Mun.

Valentina exits the lander through the airlock.

...and is soon joined by the rest of the crew.

The crew remain on the Munar surface for the entire duration of the Mun's orbit before preparing to return to Kerbin.

AME ignition, and liftoff from the Munar surface.

It may appear as though the ascent module doesn't have enough delta-v for circularization, but this is not the case. [I don't know what happened to commnet, I just noticed as I'm uploading this that it appears to have vanished, although I didn't turn it off].

The engine also has a monopropellant mode, and can use the RCS fuel to complete the circularization maneuver. It does not have the required fuel to dock, however, so the Orion spacecraft will have to do that.

The Orion spacecraft approaches the Altair lander after several maneuvers to rendezvous.

Docking successful. The crew transfer to the Orion spacecraft.

Undocking from the ascent module.

The Altair ascent module de-orbits itself autonomously.

Planning the return maneuver. it's not the most efficient maneuver, but Orion has enough fuel to accomplish it.

Leaving the Mun.

Service module jettison.

Re-entry successful. Drogue chute deployment.

Main chute deployment.

Landing successful.

Mission outcome: success.

General Score

Launch Vehicles: Only use replicas of the Constellation-specific launch vehicles (Ares I, Ares IV, and Ares V) for all launches from Kerbin. (+10)
Ares I: Your Ares I analogue has one solid rocket motor on the first stage and one liquid rocket engine on the second stage. (+5)
Ares V: Your Ares V analogue has 5 liquid rocket engines and two solid rocket boosters on the first stage, and one liquid rocket engine on the second stage. (+5)
Stage Recovery 2: The SRBs on the Ares IV and V can land safely in the ocean with parachutes. (+4)
Orion: Orion is launched on the Ares I rocket and has space for at least four kerbals. (+6)
Crew Safety: Orion includes a solid-fueled launch escape tower. (+4)
Crew Mobility: All surface modules have functional ladders. (+1)

Mission Score

Objective: Using the Orion spacecraft and the Altair lander, send four kerbals to the surface of the Mun and return them safely to Kerbin. (+20)
Kerbin Orbit Rendezvous: The Orion spacecraft and the Altair lander are launched separately and dock in Kerbin orbit before transferring to the Mun. (+8)
Accurate Altair: The Altair Munar Lander includes a descent module and an ascent module, and has space for all four kerbals. (+7)
Fuel Cells: The Altair lander is powered by a fuel cell. (+2)
Kerbin Departure Stage: The Mun transfer burn is done using the upper stage of the rocket that launched the Altair lander. (+3)
Altair Orbital Insertion: The orbital insertion burn at the Mun is done using the engines and fuel system of the Altair lander. (+3)

Total: 78

Edited February 17, 2017 by eloquentJane

septemberWaves · February 17, 2017

The second challenge has been added to the original post.

septemberWaves · February 18, 2017

Since my earlier entry I've upgraded my Altair design to allow it to work better and fulfill more challenge requirements, but I'm saving the reworked design for a future mission. In the meantime I have done an entry for the second challenge, which is the purpose of this post.

Mission designation: ARM1 (Asteroid Rendezvous Mission 1).

This is the asteroid chosen for the rendezvous mission. It's a Class E asteroid on course to fly by Kerbin with a periapsis of only seven thousand kilometers, making it relatively easy to reach. It's going to be in Kerbin's SOI for ten days, and the mission will need to be completed within that time period.

The first part of the mission to be launched is the Sirius ARM (Asteroid Research Module). It is derived from the Altair lander, and is very similar in design. It is launched on an Ares V.

Spoiler

Ignition.

Liftoff of ARM1-Sirius.

The launch window was timed to match the inclination of the asteroid. The ARM launches into a standard 120km parking orbit with an inclination of 31°. Acceleration is limited on this launch in an attempt to improve efficiency.

Commencing gravity turn.

Breaking sound barrier.

Booster cutoff and separation.

Reaching maximum dynamic pressure.

First stage cutoff and separation, KDSE ignition.

Fairing separation.

Circularizing.

Confirmation that the SRBs landed successfully.

Circularization successful. I realize now that I forgot to add struts to the ARM to make it look properly connected to the KDS. I'll have to fix that in future iterations.

The Sirius ARM now awaits the crew in orbit.

Shortly after the ARM is launched, the crew prepare to launch on an Ares I rocket. The crew of this mission are Valentina Kerman (Orion Pilot), Wenliana Kerman (Scientist), Phoanne Kerman (Engineer), and Berella Kerman (Lander Pilot).

Spoiler

Ignition.

Liftoff of ARM1-Orion.

Commencing gravity turn.

First stage cutoff.

First stage separation. As you can see, I solved the issue with the first stage exploding (the fairing wasn't separating with enough force and crashed into the stage).

Second stage ignition.

Confirmation that the first stage landed successfully.

Reaching maximum dynamic pressure.

Second stage cutoff as 80km apoapsis is reached.

LES jettison.

Preparing the circularization burn.

Circularizing.

Circularization complete.

Second stage separation. A staging error meant that the separation motors did not fire.

Orion deploys solar arrays and antenna.

After quite an expensive rendezvous (mainly on account of the 4° plane change) the Orion spacecraft approaches the Sirius ARM.

Re-orienting the ARM to assist with docking.

Docking successful.

The crew must now prepare to transfer to the asteroid.

Spoiler

The spacecraft isn't perfectly inclined for the transfer, so a somewhat expensive plane change must be done.

Plane change complete.

A maneuver is plotted to intercept the asteroid in several days.

After waiting for 3 days in Kerbin orbit, the KDS burns to transfer to the asteroid.

Transfer burn complete.

KDS separation.

The KDS executes a brief radial burn to place itself on a collision course with Kerbin.

A brief mid-course correction is needed to move the closest approach a bit closer.

A maneuver is plotted to match velocity with the asteroid at closest approach.

Matching velocity.

The asteroid is a bit further away than anticipated, but is approached after a brief burn in its direction.

This is a pretty large asteroid.

Berella Kerman transfers to the ARM, which then undocks from Orion.

After the ARM deploys a special payload, Berella prepares to connect it to the asteroid using the specialized grabbing unit attached to the ARM.

Connection secured. It appears as though the ARM has sunk into the regolith a bit; it appears that this asteroid is coated with a thick layer of dust. It's a good job the engines on the ARM aren't needed any more.

Now for that special payload that was deployed from the ARM before the asteroid docking:

It's a science stick for poking the asteroid with; fully equipped with science equipment.

Unfortunately the stick ran out of fuel before it could reach the asteroid.

The Orion spacecraft prepares to dock again with the ARM now that it is securely connected to the asteroid.

Docking successful.

Science experiments are done, the main ones involving the drilling unit on the ARM. The materials extracted from the asteroid appear to be usable as fuel after some refining.

EVAs are also conducted during the mission.

The crew now prepare to leave the asteroid. They transfer back to the Orion spacecraft and undock from the ARM.

The return maneuver will consume almost all of the Orion's fuel.

Executing return maneuver.

Approaching the atmosphere.

Service module jettison.

Re-entering.

Re-entry successful. Drogue chute deployment.

Main chute deployment.

Landing successful.

Mission outcome: partial success. The asteroid rendezvous was successful with the crew spending about 6 days in space, but we failed in the task of poking the asteroid with a stick.

General Score

Launch Vehicles: Only use replicas of the Constellation-specific launch vehicles (Ares I, Ares IV, and Ares V) for all launches from Kerbin. (+10)
Ares I: Your Ares I analogue has one solid rocket motor on the first stage and one liquid rocket engine on the second stage. (+5)
Ares V: Your Ares V analogue has 5 liquid rocket engines and two solid rocket boosters on the first stage, and one liquid rocket engine on the second stage. (+5)
Stage Recovery 1: The solid first stage of the Ares I can land safely in the ocean with parachutes. (+3)
Stage Recovery 2: The SRBs on the Ares IV and V can land safely in the ocean with parachutes. (+4)
Orion: Orion is launched on the Ares I rocket and has space for at least three kerbals for stock entries, or four kerbals for modded entries. (+6)
Crew Safety: Orion includes a solid-fueled launch escape tower. (+4)
Commnet: Do everything with commnet enabled at the default (normal mode) settings or more difficult. (+10)

Mission Score

Objective: Send a fully crewed Orion spacecraft and an Asteroid Research Module to rendezvous with a Near Kerbin Asteroid (NKA), and then return the crew safely to Kerbin. (+20)
Kerbin Orbit Rendezvous: The Orion spacecraft and the ARM are launched separately and dock in Kerbin orbit before transferring to the asteroid. (+5)
Asteroid Research Module: The ARM is derived in some way from the Altair lander (it should be visually similar), and includes a grabbing unit to attach to the asteroid. It should be able to undock from the Orion spacecraft when near the asteroid, and land on the asteroid using its own propulsion systems. (+8)
Asteroid Science: The ARM includes a functional drill, ore tanks, and some sort of science equipment for surveying the asteroid. (+5)
Crew Comfort: The ARM includes habitation space for all of the kerbals on the mission. (+5)
Moderate Duration: The total time the crew spend in space is less than 20 Kerbin days. (+6)

Total: 96

Martian Emigrant · February 18, 2017

Hi Jane.

Here is your patches.

ME

septemberWaves · February 18, 2017

53 minutes ago, Martian Emigrant said:

Hi Jane.

Here is your patches.

ME

Oh wow, thanks for making these! I'll add them to the OP by the relevant challenges.

Majorjim! · February 18, 2017

It's very nice to see this as a proposed challenge!

Having made a full Duna return constellation pack a few years ago I know what a challenge it is!

My new pack, still frustratingly in progress is a quantum leap over my last pack, as such it's taking an age and testing my resolve..

I won't be entering this though, at least not for a while, my last pack was made before stock ISRU for one.

I wish everyone good luck on this as it will take you a very long time indeed to make these craft realistically with stock parts!

Martian Emigrant · February 18, 2017

Darn.

I have to make another one.

Here:

ME

Edit

I am working on building/Testing my hardware. I will be submitting for my first patch soon.

Edited February 18, 2017 by Martian Emigrant

Xeldrak · February 18, 2017

Building a functional Ares I copy is suprisingly difficult. The Kickback SRB is just lacking in power...

septemberWaves · February 18, 2017

1 hour ago, Xeldrak said:

Building a functional Ares I copy is suprisingly difficult. The Kickback SRB is just lacking in power...

I suppose stock solid rockets do somewhat increase the challenge of replicating the Ares I accurately. I may modify the rules to allow the use of multiple solid rocket motors together for the Ares I first stage in a stock install.

EDIT: I am going to modify the rules to allow this. Stock solid rocket motors (and even stock-balanced modded ones like the modular SRB I used) impose enough extra difficulty for a stock entry that this seems to be a sensible decision for balance.

Edited February 18, 2017 by eloquentJane

Martian Emigrant · February 19, 2017

Hello Friends, Kerbals and Judges.

I have started a mission. That I can safely say is doing well. All stock no automation.

The Mission report: Doing it Constellation Style

Imgur, mostly in order if you start from the bottom: http://imgur.com/a/3YW48

Spoiler

Enough for today.

Till later,

ME

Edited February 19, 2017 by Martian Emigrant

septemberWaves · February 19, 2017

@Martian Emigrant You have some pretty good designs, I look forward to seeing this continue. And you'll be glad to know that in accordance with the rule change I made earlier today, your Ares I does comply with the single-first-stage-engine rule.

Angelo Kerman · February 19, 2017

@eloquentJane Pretty cool challenge and designs. It also looks like I need to fix the exhaust plume on the SRB...

septemberWaves · February 19, 2017

1 minute ago, Angel-125 said:

@eloquentJane Pretty cool challenge and designs. It also looks like I need to fix the exhaust plume on the SRB...

Thanks.

And oh yeah, I forgot to make a bug report about that one. Although I don't know for certain that it's caused by M.O.L.E; I have a lot of mods installed which could be interfering with it.

Angelo Kerman · February 19, 2017

53 minutes ago, eloquentJane said:

Thanks.

And oh yeah, I forgot to make a bug report about that one. Although I don't know for certain that it's caused by M.O.L.E; I have a lot of mods installed which could be interfering with it.

No worries, it's MOLE; I already have a fix in the works.

Kertech · February 19, 2017

Why do the good challenges occur when I'm on placement!!

Doing It Constellation Style

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Join the conversation