Search the Community

Showing results for tags 'modded'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • General
    • Announcements
    • The Daily Kerbal
  • General KSP
    • KSP Discussion
    • Suggestions & Development Discussion
    • Challenges & Mission ideas
    • The Spacecraft Exchange
    • KSP Fan Works
  • Gameplay and Technical Support
    • Gameplay Questions and Tutorials
    • Technical Support (PC, unmodded installs)
    • Technical Support (PC, modded installs)
    • Technical Support (PlayStation 4, XBox One)
  • Add-ons
    • Add-on Discussions
    • Add-on Releases
    • Add-on Development
  • Community
    • Welcome Aboard
    • Science & Spaceflight
    • Kerbal Network
    • The Lounge
  • International
    • International
  • KerbalEDU Forums
    • KerbalEDU
    • KerbalEDU Website
  • KSP Pre-release
    • 1.2.9 Pre-release Branch
    • 1.2.9 Pre-release Modding Discussions
    • 1.2.9 Pre-release Bug Tracker


  • Developer Articles

Found 62 results

  1. I'm running a fairly modded version of KSP 1.1. All mods are the respective latest KSP 1.1 compatible versions. What works ok: - VAB/SPH (I can load, modify, create new ships, see all modded components that were added, all mod functionality is nominal...) - Tracking Station (I can see all ships ok, new planets from ESO are good, I can go to and fly all ships, new KSP functionality is nominal...) - I can access all buildings at the KSC without any issues - I can load any saved files ok This is the problem I am encountering. Once I load a ship to go to the launch pad, the initial loading screen is as its always been. But once the ship gets loaded onto the launch pad at KSC, the screen goes dark and I only have very limited functionality. The game then proceeds to hard crash to desktop if I try to do anything from returning to launch, to VAB or to KSC. Screenshot of the issue: Here is the complete list of mods I was running (minus TAC Life Support for 1.1, Axial Aerospace and FASA. Those were NOT there when the issue occurred): The game is launching from its 64 bit version, so I know that is not the issue. I'm using Windows 10 64bit OS. The really weird thing that I did notice when trying to debunk this is that the ship seems to get instawarped into a solar orbit into deep space or something weird like that. I was able to (somehow) recover one ship and I got science for having retrieved a ship from solar orbit, or something like that... Here's the screenshot for it (this happens when I reload the game and try to launch another ship, at which point I have to clear the launch pad, and it gives me this): Really unsure what is causing this but, as you can imagine, this is a pretty bad issue. I cant launch anything at the moment. I can only play with what has already been launched. Thanks for any help! I really need it! CM
  2. Installed Extraplanetary Launchpads yesterday, along with KIS and KAS. I landed my first base yesterday with the new parts designed to build a self-expanding base. I was somewhat unfortunate with the landing location, as the ground isn't flat. The entire area around the base is a gigantic hill near one of the largest craters on the Mun. I designed the initial parts of the base to only use survey stakes for flexible construction sites. However, whenever I create a new site and a new ship, it bounces up and flies away. Any distance from 1m to 20m. How can I stabilize the ship when it is constructed and avoid it flying away?
  3. i did a thing and it's a cool thing. Side note, how do i embed albums? If the demand is large enough i'll throw up a download, but it requires mods and i'm not %100 sure what all ones i used so i'd just be putting my gamedata folder out there for ya'll to use.
  4. Chapter 1: Up the Rabbit Hole The VAB’s Cargo Bay 3 is a secluded concrete box behind a massive sliding door, but on that day, it nevertheless resonated with the ruckus as Jeb flipped over one of the empty fuel valve crates bearing his name, and perched on it. Bill shook his head, and joined him; Bob kept mulling about, while Val simply plopped onto the cold concrete floor, protected by the aramid fabric of her orange suit, gutted and stripped of badges. Around them stood the crowning achievement of KASA; but KASA itself was no more. The Kerbal Space Center was being stripped of anything that could be carried away by a swarm of workers that had descended upon it a week ago. The VAB, the Mission Control, the comms array, the administration and R&D facilities… like a swarm of locusts, they consumed everything. “So, I guess this is it,” said Bob, just to break the silence. “He… won the bet,” sighed Valentina, “and now we’re getting downsized.” “And Kerminsky didn’t hold his word either”, muttered Jeb, drawing surprised looks from everyone involved, “Yeah, I ‘have sources’”. Outside the door, amidst the extensive scaffolding, towered a half-assembled Sarnus V. They probably weren’t going to drag the five Mainsails and their fuel tanks anywhere, and would just leave them standing. A month back, another one of those monsters carried a tiny can containing Jeb and, unfortunately, Bob, all the way to Munar orbit, and the small ship on top landed onto its desolate surface. They planted a flag, they took measurements, they took samples, and then they blasted off and returned relatively safely. President Fitz Kerman was absolutely delighted – for about a week. Then, all this happened… “Hey, guys!” barked out Gus Kerman, in his usual safety helmet – which was coming in handy, because they could hear bolts and tools getting dropped left and right. “I’ve got a spare Rabbit out back, care to ‘accidentally’ launch it?” “Well…” drawled Val, “it’s not like we have anything better to do." ---------- The primary launch pad had been fully reconditioned. The modular gantry had been dismantled and the blast trench was covered by heavy grates that easily supported their truck. Gus casually drove straight over the crawlerway connecting the pad and the VAB, a big no-no back in the day. The Rabbit was a slender sounding rocket, three times as tall as Jeb, but only as wide as a helmet. A small slanted launch stand, the truck’s crane and a briefcase with remote firing controls; all of it about ten minutes’ work. However, Bob had to be sedated with Val’s elbow to the stomach. “Fire in the hole!” Jeb barked, appropriately. There was a brief hiss, then a burp, and the rocket blasted off. The screams of horror coming from the VAB were quite satisfying. The Rabbit spared itself the trouble of having any stabilization. The thick trail of its solid-fuel motor began to form a distinct spiral as the angled fins sent it into a wild spin, which actually helped keep it from veering off-course too much. They didn’t need any particular accuracy: after the motor burnt out, the empty casing tumbled into the bay to the north of KSC, with a parachute trailing behind it to reduce the impact speed to a reasonable 6 m/s. “Who do you think is going to buy all this stuff?” Val idly wondered. “I did,” Jeb answered nonchalantly, “All of it. And I also own Rockomax, so all that money the Pres has 'wasted' is now lining my pockets. And I have big plans.” Modlist (current as of June 2): This is going to be a poorly-roleplayed Sandbox game suffering from delusions of grandeur and realism.
  5. Forgotten Space Program Latest Post: 2017-02-25 - Infinite Departures -- It's happened again. Those well meaning kerbals ran off and completely forgot about their space program. Maybe there was a global crisis. Maybe they ran out of funds. Maybe the Kraken ate the ship Jeb and the Bs were in. Or maybe it was just snack time and the cheese dip was really, really good. Unfortunately nobody remembers what went wrong because nobody remembers being there. Space? Whazzat? And so years pass. Eventually an eccentric millionaire stumbles on the ruins of the long-forgotten program. Trailers. Sheds. Run-down labs. A dirt runway. Factories scattered here and there in the nearby countryside. Exploding barrels of fleas. Sharp metal bits. Gumball machines. Nuclear waste. The usual rust of a long forgotten industry. A few quick phone calls and some thousand signatures later and The Boss became the owner of their very own space program. And that's when the fun started. -- -- In something of a departure from my usual routine, this will be a mod-"heavy" playthrough focusing largely on the wonderful Engineering Tech Tree. Expect frequent and smaller posts, usually the same day of the mission or a very short time later. I will attempt to keep this save going for the indefinite future, but can make no promises that I won't forget what I've done and start over again. Again. And, seeing as none of the kerbals know what's out there, we may see some relics and wrecks from my previously forgotten space programs. Difficulty is my usual fare, a Career Mode game with the normal difficulty settings, no crew respawn, etc: Mods in Use (as/of KSP v1.2.2) Note: Many parts from mods not listed (or listed under previous versions) are still present on spacecraft, in flight, but are "retired" and have been edited (by me) so they no longer appear in the VAB. Aviation Lights Distant Object Enhancement DMagic Orbital Science Docking Port Alignment Indicator Engineering Tech Tree Engine Lighting EVE (Waz's Build) Flag Decals Hullcam VDS KAC KAS KER KIS kOS Mark One Laboratory Extensions Module Manager Persistent Rotation Planet Shine Raster Prop Monitor Real Plume (Stock) Reentry Particle Effect SCANsat Scatterer SpaceY Heavy Lifters SpaceY Expanded Surface Lights Trajectories Texture Replacer (RangeMachine's Build) Older Mods in Use (for previous KSP v1.1.3) Older Mods in Use (for previous KSP v1.0.5) Let's get this show on the road now, ok? -- The Hydrogen Flights The "exploding barrels of fleas" were apparently not made of fleas, but were instead created to dispose of them. (Which might explain the fire and smoke.) As far as the geniuses in the engineering department could determine, the intent was to aim the open end of the barrel at the fleas and "watch them burn." The Boss thought of a different use after three interns and one such barrel flew violently through the wall of the lab and into the waters of Booster Bay. The little green geeks quickly dug around to find the parts they needed: gizmos to measure air pressure, a gumball machine painted a dark grey with a "computer" stuffed inside, a flea barrel to strap it all atop, and a large silk blanket to carry the gizmos safely back to the ground. The "computer" was little more than a couple of vacuum tubes and an alarm clock, all held together with loosely assembled wires. The clock was to ignite the flea barrel, trigger the gizmos and detach the gumball machine; the vacuum tubes were there to make it look awesome. Lacking a clever naming scheme, The Boss painted "Hydrogen 1" on the side and the three formerly flying interns rolled it to a nearby mound of dirt. Only they must've messed up the clock while moving the H-1, as the flea barrel ignited late, flew off in a weird direction, and the gumball machine detached early. Regardless, the gizmos took proper readings and proved The Boss right: These barrels weren't built for killing fleas, but for helping them fly. Science points galore! Somewhat unexpectedly, a representative from the Kerbal First Record Keeping Society showed up to give The Boss a few shiny plaques: First Launch, new Speed Records of 25m/s and 80m/s, and First Landing. The prize money was spent on some bags of corn chips and the interns were sent back to work. There was still time enough in the day for another launch. Same gumball machine with a big barrel of science (which had been previously tested on the mound), all atop yet another flea barrel. The Boss named it the "Hydrogen 2" and everybody lined up to watch it fly. The H-2 flew higher and slightly faster than anything yet recorded (that one catapult accident doesn't count), resulting in yet more plaques from the record keepers: Altitude records of 500m and 2km. The money was just enough to buy some queso dip to go with the corn chips, and The Boss kicked in a few extra kerbucks for soda. And so on the first day they partied, and The Boss was happy, for The Boss saw it was good. Navigation: Next Post
  6. I took a break from ksp for a while and just now getting back I tried to open the game but it crashes before startup so I don't know what is happenning. I have the logs but don't know what they mean. Please help. (updated with logs)
  7. I'm tried to load a save file, but nothing happened, so I deleted my file and tried to make a new one (mistake). I have an output log here:
  8. Whenever I completely destroy my current vessel the camera shakes wildly. It stops when I zoom out and view the area from above. I've been able to reproduce this with mods as well as a fresh 1.2.2 install. Can I have some help? TiA
  9. I just downloaded a bunch of mods and started a new Science World, and I launched a small laboratory into orbit. The launch was successful, and I detached my final upper stage. I did some experiments, and transmitted the science back to the KSC. I was going to then go back to the space center to unlock some more parts. However, I was stopped by a alert that said, If I was to go back to the KSC my game would not be saved past the point where I launched the laboratory. I could have done a quick-save, but loading would just take me back up to "in-flight" mode, with no way of going back to the space center without losing my science, orbit, and my save. I've done heavily-modded science worlds before, and I could always go back to the tracking station/ Space Center, when my Vessel was in orbit. Does anybody know if I can go back to the KSC without reverting to a "pre-launch save"? (Sorry, I still haven't been playing that much Modded KSP yet.)
  10. From the Offices of Owl Aircraft Race Team We present... ODR-05 (Mk.2) The ODR-05 rally vehicle is to participate in the first ever Dakar Rally; A long distance survival event meant to test strength, speed, courage, and design. The car, with incredible grip and speed, was created with two goals in mind: Go fast, and Be safe. The car has a top speed of 40 m/s, including the DRS system and maximum power. The safety of the car was tested time and time again, with not even the most dangerous rolls and crashes able to upset the drivers. With a new deal coming from DK Salvage company, the ODR class has been outfitted with structural tubing to assist in the strength of the vehicles. Below are the pictures taken of the car during testing. Here is the car post-safety test. The car will be driven by Valentina Kerman, and her co-diver and navigator is Bill. We wish the team the best of luck in the Dakar Rally, and the KSC2-Desert Temple Rally.
  11. I've been working on this huge mobile rover base with the Kethane, Karbonite, and Extraplanetary Launchpads mods and when I spawned it onto the runway, the entire left side was missing, save for a drill which was missing on the other side. I tried to fix it in the SPH to no avail, instead, it wouldn't even let me re-place the parts. I've tried re-installing the game and I'm having the same issues. This didn't happen with the H.U.L.K.K. I, only the H.U.L.K.K. II
  12. This is my new fighter jet! I'll let you guys decide the name! Happy building, burning, crashing, Kerballing, and overall madness!
  13. I got really attached to Effusus and it's characters. In fact, I've grown so attached to Enfurt, he might make an appearance! Unfortunately, the kraken, on the other hand, wasn't to keen on the idea. Hopefully, this story gets to be told without upset. This will be a "Career Lite" game with little care or consideration for realistic progression, and I hope y'all enjoy!
  14. KSP version on Windows 10 x64 Command line option (launching through CKAN): KSP_x64.exe -single-instance A detailed explanation Game crashes, most often when switching vehicles when a large number of vessels are loaded. Not consistent, sometimes it happens within 2 minutes and sometimes I can play for an hour straight. The crash has also happened when interacting with KAS or KIS (example: attaching a vessel with a winch, or placing an item with an engineer). The main connection between the crashes seems to be related to vessel interaction. A screenshot Sometimes it's a CTD without an error. Most often though, it's just a "The game has crashed!" error. Save files, ouput_log.txt or player.log Save file: Crash log files: 1. 2. Most notable log entry: RtlLookupFunctionEntry returned NULL function. Aborting stack walk.<Missing stacktrace information> Even more crash logs (I updated a few mods after these happened): System specifications EVGA GTX 1080 (8gb) Intel i5-2500k (3.8ghz) 16gb Corsair Vengeance memory 1tb Mushkin SSD (other harddrives: 2x256gb Crucial SSD, 2x128gb Crucial SSD) More specifications: Mods I have arranged a details document of all of my installed mods. I went through each one today and updated them. Unless there is a community patch that was not mentioned on the first or last few pages for one of these, they should be up to date. A few do not officially support KSP 1.2.1, and are probably the cause. NOTE: I know that with the number of mods I am using, and by using out-of-date mods, I am asking for crashes. Telling me not to use them would not be helpful. Thanks.
  15. GHi all! his is a tale to provide a little bit of context to the Kerbin that my kerbals (at least some of them ) inhabit. Without further ado:
  16. I'm currently experiencing alot of crashes when flying planes. The error log always says "Write to location xxxxxxxx caused an access violation." the location varys but always is the same as the adress of "RAX" under Context. Some of my "crash.dmp"s and "error.log"s:!FxtBGSRY!c4298LUcgGBHXS-aUia9RkJufxV7ijm3_cU2wVpSlqk Virus Scan for the .zip: My installed Mods(I know its alot):
  17. Dear squaddies ive got stock and modded installs of 1.2 etc but i think ive maybe found a stock bug, but can only prove it by adding mods, so advice needed is 'where do i go from here' ? weve put up a thread in modded support, which hasnt been looked at or i should say commented on by squad (will provide link when i edit) edit - link : it seems, certainly not proven (still testing etc) that when a parts category gets too full, a strange UI bug rears its head. it doesnt happen in just stock and it doesnt happen when ive tried running ksp with each mod i use 'on its own', obviously all my mods are for 1.2 etc and i only use reputable developers mods (cut down on the random factor) logs dont show anything major. i can have 57-60 parts in category, any more and UI bug appears and it seems the more you have the worse it gets. so, without installing mods, how can i show that stock MAY have a bug with amount of parts installed ? Can i get an answer from squad before a mod moves this please cheers OH and ill keep bumping this up the thread til its solved or w.i.p.
  18. There was legend of a planet in a distant galaxy far far away where little green men crawled out of the water and well decided land just wasn't enough. There was the sky. And beyond that? Well nobody really knew what came after the sky. These creatures were called Kerbals and other species on other planets would probably liken them to little green rednecks. This is Lukes Awesome Space Agency or LASA for comedic effect. Who is luke? He is the one they call the architect, the grand designer, the ultimate noob...... BIIILLLL GET AWAY FROM MY COMPUTER!!!!! There are a few rules to go by. 1) Unless there is a remote command all crewed missions will require a Pilot or at least a one star Kolonist. 2) Have fun with it. 3) Add more rules as you remember/think of them. It begins
  19. hey I am Orionthusiast (an Orion enthusiat). And I am going to do a lot of missions using the Orion capsule from EFT-1 Dawn to EM-2 Freedom. I want to see y'all's replicas. So lets do this I don't care if it a crew retrival rocket I want to see it!
  20. If I have a vanilla game - which I do - and have a bug problem - which I don't (So it's all hypothetical) then Squad will look into the problem. If I also have a modded game - which I do - and have a bug problem - which I don't (So it's still all hypothetical) then squad will say "Not with a barge-pole mate!" and will not look into the problem. What if I have a modded game - which I do (in case you forgot) - and have a bug problem - which I don't (So even now we are still being hypothetical) and what if I ripped out all the mods from this modded game and then presented the still present (hypothetical) bug to squad, would this be touched with a barge-pole? Would the save game itself, having been tainted by mods still make it untouchable regardless of barge-pole length? Just wondering.. you know.. hypothetically.. can I de-taint a save game enough that squad will hug it and welcome it home and forgive it for getting tainted in the first place? Thoughts of the masses?
  21. I don't know if anybody else has been experiencing this issue, but my green comm lines to show connections between the craft and the groundstations or any relays are not showing up on the map view. The comm network works fine and the little tab on the flight screen still shows if I have a kerbal on board, how good my connection is ETC. Thanks Hope this pic helps.
  22. My Space Program is now on its third year and has landed kerbs on all bodies on the Kerbin with project Oromë, built an Kerbin SOI infrastructure with surface bases and space stations on KSOI with Project Aulë and flung Palantiri probes with varying degrees of success towards Jool and it's moons, Duna and Ike, Eve and Gilly, Moho and Dres with Project Namo. And it has sent (but not returned yet) a kerballed expedition to Eve orbit and Gilly with the ambitious Project Tulkas. Some relevant mods that I'm using are: So now the board of directors have decided it is time for the next big step, put some kerbs on Duna and bring them back! This is the mission report of this bold endeavor. Ah, caveat emptor: English is not my native language, and even with spellcheck a few embarrassing errors may pass through. If I end up saying something weird or even culturally insensitive, please give me the benefit of the doubt and kindly warn me so that I may perform the necessary rectifications. KSC, Year 2, day 260 Board of Directors Meeting Mr. Kerman: All right gentlekerbs, we've assembled here to discuss Project Estë, which shall comprise of exploring all the biomes on Duna and Ike and estabilishing permanent colonies. If you recall, we've succesfully put a Palantir mapping satellite on a polar orbit of both Ike and Duna and landed three Calmainen probes on each body just a few days ago. We're confident in our abilites of controlling and successfully landing vessels in each of these bodies. Moreover, the orbital scans have provided us with some estimates of the resources available on the surface of both Duna and Ike, as Mortimer here has been reminding me since. The next transfer window for Duna is in little over a year. Linus, if you please: Linus: Yes, thank you. If you look at the projection, you will see the critical dates for Project Estë, kindly provided by our friends on Alexmoon's Astronavigation Inc.: Kerbin -> Duna Departure Year 3, day 302 at 3:50:24 Arrival Year 4, day 153 at 2:50:24 Time of flight 276 days 5:00:00 Stay @ Duna ~1 year 135 days Duna -> Kerbin Departure Year 5, day 298 at 5:26:24 Arrival Year 6, day 161 at 4:55:12 Time of flight 288 days 5:28:48 Total Mission time: ~3 years 140 days == ~1418 days By keeping in mind our last interplanetary mission, Tulkas I, where our kerbonauts are currently aboard their ship Eämbar awaiting for the return window after just over 20 days of surface activities this may seem plenty of time, but there we had only to land on Gilly, which has such a low gravity that we could perform multiple hops to fully explore the moon in one go, and as of yet landing and returning from the surface of Eve is out of the question. In this case, we plan to take advantage of our orbital readings to incorporate In Situ Resource Utilization in our planning, much like the later Oromë missions on the Mün, to refuel on the surface of both Duna and Ike, allowing for as many landings as we may wish for. This should greatly reduce the fuel we would otherwise have to haul along and allow for heavier - and safer - landers. On the other hand, ISRU takes time, and we'd like to take the time to perform some field geoscientific studies to improve our odds of successfully refueling our lander, since so much of the mission relies on that, as you'll see later. Mr. Kerman: Thank you Linus. Much like Tulkas I, Estë I shall be comprised of an expeditionary team of one pilot, two scientists and one engineer. I need not remind you that our primary purpose is exploration and advancement of our knowledge of the Kerbol System. All other considerations such as financial returns, Mort, and public reputation, Walt, are secondary. Gus, I know engineering has produced extensive reports on delta-V requirements, Thrust-to-Weight considerations, reusability, redundancy and recent improvements on Life Support systems and propulsion drives, but just give us the short version. What can you tell us about the hardware? Gus: Project Estë is essentially an application of all the technology developed during the exploration of Mün and Minmus during our very own Project Oromë. The proposed lander is the Melian-D model, based upon the highly successful Nahar lander series of Project Oromë. This lander can transport up to six kerbals and all the equipment for an inflatable surface base of operations and in-situ assembly of a Eärendil exploration rover with a full science complement for a grand total of 52,108 kg, fully loaded and a total delta-V of 2821m/s on a vacuum, which should be enough for one chute-assisted landing on Duna and reorbit without refueling or as many as three powered descents and reorbits on Ike, if for any reason our ISRU plans don't come through. Which it should, of course. Work I mean, not... well you got the idea. If you'll recall, all of this hardware has been tested successfully earlier this Münth on both Mün and Minmus during Project Irmö, which is in charge of stress testing all proposed new designs. Melian-D shall be transported to Duna Orbit and from there and back to Ike orbit by our reliable Dailir tug. Our intrepid crew, initially consisting of Mission Commander Jeb, Primary Investigator Leema, Second Investigator Gwenial and Extraplanetary Assembly Specialist Beazie will be transported from Low Kerbin Orbit to Low Duna Orbit aboard essentially the same vessel that Commander Bill and his team are using on their trip to Eve, the Eämbar Interplanetary Crewed Vessel. Of course recent breakthroughs on the SuperNova fusion engine will... well.. no matter. Suffice to say that it has greatly improved on efficiency and we can add greatly to the supplies for the crew in case of any emergencies. Improvements on greenhouse and recycling technologies have also greatly decreased the required mass of supplies in comparison with Tulkas I. Mr. Kerman: Thank you Gus, that was most enlightening. Gene, would you be so kind as to expose to us the proposed mission plan for Estë I? Gene: Sure. The general idea is to depart from Kerbin around Day 300 of the Year 3 with the Eämbar vessel and the Dailir tugging the Melian lander. They should arrive roughly at the same time and park into a Low Duna Orbit of 100km above Duna Datum. A crew composed of Commander Jeb, Assembly Specialist Beazie and probably Primary Investigator Leema will then depart on the Melian lander to perform the first landing on a suitable equatorial site of scientific interest, from which it shouldn't be too much trouble to return to Eämbar if the ISRU systems should fail. Second Investigator Gwenial will remain aboard Eämbar to make sure all the vital systems are functioning properly as well as analysing all the data collected on the trip to Duna and on its orbit on the Mobile Science Lab aboard. There on the surface Beazie will assemble the Doriath Surface Base of Operations and the Eärendil Rover, with the support of the other, of course. While Beazie remains on Doriath drilling ore and converting it to refuel Melian, Jeb and Leema will take the Eärendil rover to explore the surrounding biomes, collect samples, perform experiments, all in triplicate, of course, and plant flags. In the case of a successful refueling, Doriath base and Eärendil shall be dismantled and stowed safely on Melian, and the away team will launch back into orbit. If the refueling is not successful, Doriath and Eärendil shall be abandoned on Duna surface to lighten Melian and provide an extra safety delta-v margin for the crew. All going well, this pattern shall be repeated as many times necessary to fully explore all the biomes on Duna, rotating the scientist in charge of holding the fort aboard Eämbar. After that, Dailir will proceed to push Melian to an Low Ike Orbit and Eämbar shall follow. The same pattern will be conducted to explore all the biomes on Ike. Once all surface activities are complete, the crew will remain on LIO shifting through all the collected data on the Mobile Science Lab and awaiting for the return transfer window for Kerbin. They have enough spare supplies onboard so that in case of critical systems failure we can send them an emergency life support probe in a highly energetic transfer to tide them on until we can send another ship to bring them home. Mr. Kerman: Thank you Gene, for this most delightful exposition. As our final point, we have a report that should satisfy you, Mort. All this hardware, coupled with our reusable lifter division, developed as per your suggestion, will cost us no more than 2 million funds, well inside our budget. Now, fellow directors, any questions regarding the proposed planning for Project Estë in general or Estë I in particular? So that's it folks. I've already sent them on their merry way, so any suggestions and commentary, while much appreciated, probably won't change any of the hardware available to the gang. I'm planning on a bit of sightseeing, looking for the anomalies and such. If anyone knows of interesting places such as canyons or anysuch and would like to contribute please do so! I'll see you next time, when our valiant team will depart from Kerbin and arrive on Duna Orbit and begin exploring the system! P.S.: Bonus points for figuring out whence came the naming scheme! Hint: P.P.S.:Also, on the game I'll be running a parallel Jool-5 mission, with Mission Commander Val, accompanied by Chief Scientist Bob and the rest of her team. It is a much more complex mission, and will probably have it's own report in the near future. Stay tuned!
  23. When people try to connect to my modded DMP server with the right mods and no whitelist, they get this error: "No connection could be made because the target machine actively refused it." Please help me. Ask for files if you need them.
  24. Hey Everybody! I'm finally biting the bullet and sharing my horrible KSP Experiences. I have been playing a full campaign with NO revert options, not even quicksaves. I stream a few hours on sundays on twitch, and then break it into episodes to put onto youtube. twitch stream is here (i play other games there, but who's interested in that?) and youtube is here: I have made it to the mun, and plan to do so much more. I have not done much streaming or youtube stuff, so I'm very shaky on how to do this, so any constructive (emphasis on constructive) criticism is appreciated!
  25. This is my entry for the Extended Kerbol Grand Tour challenge. The Plan Here is Astarael in Kerbin orbit (without its cargo): Its far from my best work aesthetically, but it's the only thing I've ever been able to make so far that can complete a mission of this scale. The naming scheme for the mothership and its landers comes from Garth Nix's The Old Kingdom book series.