OpenWorldAddict

This is more of a question then a challenge, but would it be possible to drag a large asteroid into a stable orbit around Kerbin and then land on it, do science on it, and even build a mining base on it. It would become Kerbin's third moon. There is enough space between Kerbin and the Mun, and the Mun and Minnus to have another object orbit Kerbin. If you think it is possible, then show me how it would be done?

I don't know. Try giving it a shot. If people really want to all do additional scoring category that is by itself, but for the main challenge, no. I am looking forward to seeing some actual entries. I am also trying to do it myself, but that will take some time. I am first going to try going to the mun with the one burn with a small probe. In that try my only requirement is that I get to the Mun, which means as far as I am concerned, the probe can crash into the mun and as long as got there on one main burn. Next attempt will be to try to land a probe on the mun with only two main burns. (I haven't landed anything on the Mun since 1.0 came out, so this will take quite some time for me to figure out) If I accomplish that, then I do my first test run of the unmanned command pod landing on the Mun with only two main burns as required for the challenge. Once I am able to do it, I will do a couple more test runs before recording the mission for upload to YouTube.

To clarify: the first burn means everything from the initial 'lift-off' to the 'main engine cutoff'. This includes boosters, secondary engines, whatever is used to get the rocket into space. The only requirement is that when you do the 'main engine cutoff', your orbital trajectory has Mun encounter. Also to note, the only other burns allowed other than the 'lift-off to MEC' burn and the 'suicide burn to land on the moon' are course corrections. However, remember to try limit the total of amount of fuel burned because it reduces your final score.

After completing the 'Get Rid of Jeb' challenge, I decided to post this one. Story: Ever since the start of the kerbal space program, kerbal's have been yearning to go to the Mun. No matter how many people came to Gene Kerman to ask to be sent to the mun, he kept saying no each time. "In these early days of the program, it is just too expensive." Everyone knows that to get to the mun would require 5 burns. One to take off and get into space, a second to get into orbit around Kerbin, a third to do the transfer between kerbin and the mun, a fourth to orbit around the mun, and a fifth to actually land on the moon. The fuel required to do all those burns just costs the program too much money. However, one kerbal named Jebudiah was very persistant, and was constantly arguing with Gene. One day, Jeb came in and said that he thinks that the mun can be reached with only two burns. Gene first initial gut reaction was "Impossible!". After arguing about it for several hours, Gene gave in and (after arranging for Jebudiah to take an extended vacation in kerbol orbit) sent out a challenge to all the engineers in the program. Rules: Build the smallest, cheapest, and lightest rocket that can get to the Mun in only two burns; one burn to take off from Kerbin, and one burn to land on the Mun. The rocket must include a probe computer and an empty Mk 1 Command Capsule. It must also land safely on the Mun (no crash landings). Then fly it to the mun unmanned to prove it to Gene that it can be done. Smallest: Cheapest: Lightest: Least amount of fuel burned: Final Score: (your combined score for the smallest, cheapest, lightest - the amount of fuel burned.)

Thanks. This challenge was kind of easy for me because I kind of experiment with these kinds of rockets all the time. When I saw the challenge, I knew it was right up my alley. Several of the assumptions I made is that since I was sending it on an escape velocity, then it didn't need parachutes, heat shields, and the like; and the capsule didn't need to be seprated from the final stage of the rocket. Those assumptions really helped me cut back on the number of parts I used.

So here is my entry. It is called 'The Ejector'.

So the question I have, is can I use Ship Manifest without this being update to 1.0. I never really used Connected Living Spaces, but now that Ship Manifest requires it, well... Ship Manifest is a must have mod for me.

This request is simple, There are many games were death is permanent, where you can name the individuals that are in the game. You can name them after friends, family, even viewers of your livestream. This gives them uniqueness and personality, and makes it hurt even more when they die. Kerbals can die often in KSP, especially now with the new aerodynamic and thermodynamic systems in place. So I would like a mod that allows you 'add' custom kerbals that you get to name and then hire from the astronaut complex to be a part of your space program.

In Nasa, you don't have one person handling everything. Instead you have team of people each with a specific job and specific area of expertise working together to complete their objectives. You have pilots, scientists, engineers; you have flight directors, mission controllers, radio operators, and programmers. When I play kerbal space program, I do not see myself as a pilot or the programmer that worked on a probe's guidance system. I see myself as a flight director/mission controller, the one that plans the missions, overseeing the launches, landings, and orbital maneuvers (such as transfers, corrections, and rendesvous), trying to come up with solutions when problems arise. I see mechjeb as the work of the pilots or the programmers, which is not my area of expertise. I use mechjeb for the fidgety stuff, like getting my ship into a perfectly circular orbit, or doing a rendezvous with another ship (including the docking, which i have had no problems with), or landing my ship with pinpoint accuracy, or plotting a orbital plane transfer for when going to places like Minnus. Some of those things I have to much of a heavy hand to do due to my disability (like the docking), and so mechjeb is my accommodation, other things I can't just figure out (like getting int a perfect curricular orbit, doing the rendezvous and the orbital plane transfers). I also use mechjeb to help me plan my maneuvers cause sometimes mechjeb is just better than my brain. Of course, when mechjeb screws things up royally, I do take manual control to try to rectify the situation. Mechjeb is not perfect, after all. By the way, I do not use mechjeb for information. Kerbal Engineer gives me all the flight information that I need. So, using mechjeb is not cheating. Flight Directors are not expected to fly the rocketships they send up, that's the job of the pilots and programmers; so why should I be expected to do it too. Running a space mission takes a team effort, and in my mind Mechjeb is just part of my team.

I think I may have to re-work this challenge from square one now that KSP 1.0 is out. If anybody has any ideas, let me know.

I hope the mod authors are working hard on this. I can't play KSP without my atmospheric trajectories, especially now that you have to consider the heating of re-entry and using a low profile re-entry trajectory.

So I tried this out a bit, and I found it a bit confusing. I currently use KSP Mod Admin. What makes this manager better?

It saddened me to see a topic that was totally unrelated to KSP be taken up here. However, with that said... it's over. Valve has taken the paid mods option off the skyrim workshop. So, there.. let's drop it and move on. We have a wonderful KSP 1.0 on our hands.

I don't know where else to put this, but I just want to give a big thank you to the KSP modding community. I have been very concerned when it comes to new updates of KSP, because all of my installed mods suddenly become out of date and incompatible with the latest version, and because I have KSP on steam, I have no way of reverting to previous versions of the game. What I have experienced with previous updates is that it would be a quite awhile before all the mods that I consider essential (Mechjeb, Kerbal Engineer, Enhanced Navball, atmospheric trajectories, ship manifest, and more recently added to my essential list Kerbal attachment system.) The wait would be even longer (some times two or more months) for my favorite mods to be updated. (like rastor prop moniter, vessel viewer, launch countdown, probe control room, remote tech, procedural fairings, procedural parts, and tac life support). Many times it would be frustrating as I wait week after week for some of the mods to be update, and some times weeks would turn into months. So I was pleasantly surprised after steam updated KSP to 1.0, that many mod authors of my essential mods and even some of my favorite mods were hard at work in updating their mods to 1.0. I am very excited to get started, and hopeful that with in a week or two I will have most of my essential mods so that I can start getting used to the new game mechanics, and I am even more hopeful that from the end of may to even mid June I will have many of my favorite mods available. Again, Kudos to all those mod makers that are working hard to get their mods compatible with 1.0 and improving our enjoyment of KSP.

I don't know if this is the right place for this, but here goes: I purchased Kerbal Space Program for my father on Steam during the last Steam winter sale. He installed it on his IMac, but had trouble with the game because the mac mouse only has one button and there are no ways to access the context sensitive menus accessed by right clicking on objects. It also makes it hard building rockets in the VAB. My father told me he can't play it until someone fixes the program to work without the right mouse button fuctionality. Do any of you have any ideas?

I know that over 100 people have read this so far, but not a single person has told me what he/she has thought of my story. Please! Feedback would be useful.

Chapter 3: The Flight and Disaster of Beta 1. With the scientific data recovered from the Alpha 3, the researchers and engineer felt they had enough technology to build a rocket that was capable of getting into orbit, so when the Flight director gave the go ahead for the Beta Program, the VAB engineers begun quickly began designing the first rocket of that program. By 1pm, the Beta 1 had been unveiled... Note this is the final version of the Beta 1. At first the Beta 1 only had 2 boosters and 1 launch stabilizer attached to the side of the main rocket just below the command pod. The ship looked flight worthy, so the Flight Director gave the go ahead to have it sent out to the Launchpad. it was decided that Bob Kerman would be it's pilot because of all the hype that he had garnered earlier in the day. Visitors crowded the lawn in front of the VAB, and when the crawler came out with the Beta 1 with the van holding Bob just behind, the crowds were cheering with bob waving his hand out of the van's window. Few minutes later Bob was strapped in an did his started his preflight checks. Alot was riding on this mission. New monitors had been installed in the MK1 Command Pod, and that gave the pilot a an unprecedented amount of information about the rocket and about the flight. In fact pilots were able to choose what they looked at any given moment. For the center moniter, bob loaded up the new navigation tracker with a visually generated heads up display. This one screen provided vasts amount of info that was needed on a moment to moment bases about the flight of the rocket. On his left hand side he activated the orbital data window that not only showed him everything that he needed to know to get the ship into orbit, but it would also show his orbital trajectory once he got airborne. On the right hand screen he tried activating the new cameras that were installed but two of them were not in a good position, and third failed to send imagery. So he opted to get vessel readings instead. With everything set up and his pref-light checks done, bob activated the auto stabilizers and contact mission control that he was ready for launch. After a second, mission control confirmed everything was in the green and the Flight Director issued the command "Go Flight!" With that, a famous announcer who had been brought in to announce the countdown and launch which would be broadcast over the radio waves, started his 30 second countdown, wowing the crowd with his grand statements every five seconds. As the countdown came to t-minus ten, the crowd got ecstatic. Even Bob was excited, checking everything one last time to make sure that everything was okay. In fact he was so thrilled about the new moniters that he did even realize the countdown was over, when he heard a load roar as the engines ignited, and then after that faded away, there was nothing, no engine roar, no movement, no sound. He looked up and still saw the sky. Outside the crowd was hysterical, laughing like crazy, and the Flight Director was furious. What had happened is the booster ignited, launching into the sky. however it left behind the main rocket with the command pod still attached to the launch stabilizer. The Flight Director order the annoucner to take the visitors on a tour of facility while they straightened this mess, and then ordered the recovery of the Beta 1. It was brought back into the VAB in one peace and the Flight Directer watched carefully as the engineers took the launch stabilizer off, attached to new boosters, and then put two launch stabilizers on attaching them to the boosters instead of the main rocket. An hour later, Beta 1 was back on the launchpad, and Bob was back in the Command Pod, happy that they did not change the setup of his moniters, but unhappy that nothing was done about the cameras. Wanting to make sure that everything was going to work, the Flight Director order the launch before the announcer and the visitors could return from the tour. The ship launch perfectly, but with in 30 seconds it seemed that things were going awfully wrong. The rocket was veering far off to the right, and Bob was struggling to correct it. Because the boosters were not helping, Bob decided to ditch the boosters and ignite the main engines, however that did also not help and the rocket started going down. The Flight Director immediately ordered bob to shut down the engine and separate from it, then to immediately put up the parachutes. Bob did as ordered and soon enough the command pod safely landed on the ground somewhere in the fields east of the center. The visitors saw the results of the failed launch as they returned from their tour, and all was worried about the fate of Bob, but they were screaming and yellling when the recovery team brought Bob back to the space... with scientific data in tow! Good Ol' Bob, always the scientist even during failure. While that was going on, the team in mission control was abuzz. Everyone thought that due to what had happened, that the KSC should close down for the day giving everyone a needed rest. However the higher ups that was funding this operation demanded a tight timetable, and that meant that a launch into orbit if possible must be met by day's end, which was going to be upon them soon enough. So despite everyone's concerns, a redesigned Beta 1 was brought to the launchpad, this time with 3 boosters for more stability during the initial phases of the mission. After only an hours rest, Bob was back in the command pod. Since everyone on the team agreed that they were sure things would work now, the announcer went live again announcing the countdown for world to see, as well as providing some comic relief for the exhausted staff and the tired visitors... and then everything went horribly wrong. As the countdown reached zero and the engines ignited, the struts connect the three boosters to the main engine broke and the boosters slammed into the main engine before falling back and exploding. Bob, not knowing what was going on, panicked and started hitting the staging button over and over. Before he realized he was on a rocket that ablaze and out of control. Mission control ordered Bob to engage the parachute and turn the capsule so that it would slide off the rocket and fall back to a safe landing, but the forward momentum of the rocket was so great that it was impossible for Bob to nudge the pod off it's end. Moments later, Bob Kerman died when Beta 1 flew nose down into the ocean. The flight director broke the news before ordering the wailing visitors off the premises, promising that a memorial for Bob would be held at sunset. Then he began a strict investigation into the accident. As log reports were recovered from the sea, it was clear what happened. As the Beta 1 waited for the countdown to finish before takeoff, the directional nose indicator was all over the place. Cameras of the launchpad showed that as time went on, due to aerodynamic forces; the boosters became more unstable, slowly splitting away from the main rocket. Although the second launch of the Beta 1 was a failure, it's takeoff was perfect, and so it was deemed that a prolonged launch sequence meant certain doom for the the rocket and anyone who was aboard it. The Flight director declared at a press conference an hour after the accident that any launch that the KSC makes must be done as quickly as possible once the pilot is strapped in, until more technologies are unlocked that could potentially have prevented this disaster. With that, she also publicly and unceremoniously fire the announcer, saying that his speeches were deadly for any Kerbal flying a rocket. That evening a memorial was held by the harbor at the south end of Kape Kerbal. Important people were making speeches about the life of Bob and the importance of his work. However, no one noticed that key members of the KSC were missing. As a boat with Bob's coffin floated off into the sunset, the former launch announcer was playing a loud serenade, so no one heard the muffled roar of rocket engines taking off north of the Harbor, nor did anyone hear the watery splashes as the discarded empty boosters hit the ocean off shore. People were just to fixated to see that red dot in the sky arc east as Jebudiah began his gravity turn at 10,000 meters. After the music played, Bill Kerman stepped up, explaining that Bob gave his life to see the mission of the space center march forward into the future, and that he will never be forgotten. How fitting it was that at the time the staff at Mission control were yelling in joy as Jebudiah discarded the main stage of the rocket and began his orbital insertion burn. For the next two hours as people wondered over to the docks where flowers were piling up, and payed their final respects to Bob before leaving in their vehicles to go home, while high overhead Jebudiah was enjoying multiple sunrises, the joy of zero gravity, and collecting valuable scientific data on space walks. That evening, rumors stirred of a shooting star flying over the desert on the continent far to the west of KSC. The following morning reporters caught up to the gleeful Jebudiah Kerman wondering the desert. There in a special report, he made the statement that he accepted the evening orbital mission even though he was going to miss the memorial in honor of Bob's name. He insisted to the Flight Director after what happened to Bob, that the mission should be launched without fanfare, so not to take everyone's attention off of what was important, the memory of bob; and that yes, Jeb did miss him. Jebudiah Kerman then set the record straigh, he was the first Kerbal to reach space, the first kerbal to reach orbit, and the first kerbal to return to Kerbin from orbit safely. Goodbye, ol' Bob! In the next chapter, the crew and staff work into the night after the memorial as the try to get a kerbal in the Beta 2 into a polar orbit to land at the north pole, while the engineering crew try in vain to figure out why their Solitare 1 Communcations Satellite won't launch. Chapter 2 Epiloge: I am posting the footage of the events of this chapter to Youtube, and I will embed it here for everyone who wants to see.

Chapter 2: The Alpha Program steams ahead. (this chapter relates the events that can viewed on my Twitch stream highlight starting at 20:56.) The success of Alpha 1 had everyone at the Space Center excited, for it was the first mission of the agency. However the flight director wasn't satisfied and so he sent the engineers back to the drawing table with the goal of coming up with a rocket design for the Alpha program that could be used for very short flights. 30 minutes later, the Flight director was called to the VAB as the engineers revealed their new rocket, Alpha 2. The director; while in shock of how fast they were; was definetly pleased. So within the hour Alpha 2 was placed on the launchpad with Bob Kerman on board with the mission to do a short burn, then ditch the rocket and land back at KSC. As it turned out, it worked perfectly, and Bob was so good that he landed the capsule on driveway between the VAB and the Launchpad. Of course Bob collected all kinds of scientific data about the KSC biome, in air and on the ground. With all the data being brought back, research was proceeding at a breakneck pace. As bob's command pod was being recovered, Alpha 2 was being renamed Alpha 3, and immediately went to the launchpad with Bill Kerman on board. Bill's mission was to land on the shores of Kape Kerbal and collect scientific data from the shores biome. The mission was a slight success, Bill burned his fuel for just a slight too long, and ended up landing just offshore but far enough away that the beach was out of reach, so Bill could not plant a flag for this mission. Nonetheless, with the data he brought back, the researchers and engineers convinced the Flight Director that enough research had been done to make a rocket that was capable of reaching orbit. Although the potential scientific data from the highlands and mountains near KSC still remained untapped, the Flight Director gave a go ahead for the Beta Program. However, as the flight directer came out of his top secret meeting with the engineers and researchers, a news flash had come on to the TVs of kerbals living rooms everywhere. It seems that after his flight of Alpha 2, Bob Kerman conducted an un-authorized interview with the media, stating the claim that he would be the first kerbal launched into space later that afternoon. This had the media all whipped up in a flurry, and as the day passed to noon, visitors excited about the first launch into space started piling into the KSC parking lots. This would lead to the agency's first mockery, followed by it's first tragedy.

So this a report of my Kerbal Space Program during my attempt to do the 54 hour KSP real time challenge which ultimately failed. The reason why I am doing this is because even though it failed some good story came out of it. Now I don't have pictures from the entire thing, but I have highlight of it http://www.twitch.tv/openworldaddict/c/6369132 However I did take a picture of all the rockets and landing sites post fact, so that is what you get here. Chapter 1: Flight of Alpha 1 After completing an initial science test by taking the initial command pod out onto the launch pad, I (as Flight Director) had begun to plan the first rocket program. Because I am not that good at coming up with unique names for rocket programs, my manned rocket program would be Alpha Program, Beta program, Gamma Program, Delta Program, etc. The plan for the Alpha program was to use the Alpha rockets to make short trips into the atmosphere to land in certain biomes near KSC to collect scientific data to use in the research of new parts. So the engineers got to work on the first rocket design. The first rocket was Alpha 1, made out of just a parachute, a command module, and a solid rocket booster. This was just to be a short mission. Take off, turn right a bit, drop the empty booster, then land on KSC grounds. However, the engineers forgot to report to the flight director just how powerful that solid rocket booster was. So Jebudiah Kerman climbed in, the rocket took off, it climbed, and climbed, and climbed. When it had burned out it had gone a lot further than the flight director was expecting it to go. It had finally landed in the grasslands west of the Kape Kerbal. It wasn't what was expected of this first mission, but Jebudiah did get some grasslands biome science data to bring back to KSC, so overall it was still a successful first mission. As a plus, when Jebudiah returned he did get awarded with ribbons for being the first kerbal to launch in a rocket from KSC, another for being the first kerbal to land on kerbin, and a even a third ribbon for being the first kerbal to plant a flag. (thanks to the Final Frontier mod). However, the objective that the flight directer set out for (collecting data from the KSC biome) was never met, so the engineers was sent back to the drawing table.

I think I have been having a problem with this mod. I love how it downs the countdown thing and everything, but every time I tried to do a launch with this, after waiting about 45 to 60 seconds for the whole countdown thing, as soon as I hit the spacebar my rocket would destabilize and fall apart with the boosters taking off and ramming into my main stage. The thing is that if I launch as soon as I get out onto the launch pad, everything works as it should. I've tried it with different boosters and different radial decouplers. I've tried it with small rockets and large rockets, and the same thing happens all the time. Launch right away without countdown, everything works. Activate countdown and then launch when it is over, everything blows up. It is getting kind of frustrating.

I used procedural parts yesterday during my failed attempt at the challenge i made for myself this weekend due to my problems with Remote Tech 2. I like how thin the stack decouplers were, but I did not see any controls to adjust the sizes of the parts. It was for that reason that i decided not to use the boosters that the mod adds, as I did not see any controls to adjust anything.

I love the idea behind those mods, but the biggest problem I have is with all those new parts required. When i first started playing KSP, it took me a long time to figure out how to get all the rockets that I wanted to build into space, and then even longer to figure out to have enough fuel in them to go to the Mun or escape the Kerbin SOI. Even now some rockets I can't get off the ground, and then others get into space but can't go anywhere. Having all these extra required parts just forces me back to the drawing board. I would love it if there was a system that was built in to the stock or modded parts with out needing 'extra parts' for life support.

You could also just do other things while you are waiting (fly to another planet, build a space station, go mining for kethane/karbonite, etc.) There is so much you can get done in that time span.

I've never had an issue with KSP mod admin, and you with in that program you can select which folders are installed.

I don't edit cfg's period. In fact, i don't install mods manually either. All the mods I have were installed using KSP Mod Admin. I've been using mod managers like that for ages in all my modded games, and I won't go back because during the times when i install things manually, when I come to uninstall them I end up deleting things the game needs to run. Mod managers makes installation and uninstallation much safer. - - - Updated - - - Oh, so that is what was going... I thought that they just were not attached. I'll try it again. Talking about fairings, I could not get them on. As you can see in the image i posted before, i placed a fairing base below the Stayputnik probe pod, but then when i tried to put the fairings I had available, I get not get them to work.