Search the Community

My Kopernicus Planet is not wanting to load: I found some trouble points in log: [LOG 18:48:04.280] Load(Texture): Galaxy/Planets/Sarna/Color [ERR 18:48:04.283] DDS: File is not a DDS format file! [WRN 18:48:04.283] Texture load error in 'C:\Kerbal Space Program\GameData\Galaxy\Planets\Sarna\Color.dds' NOTE: My color map is in .dds format [LOG 18:48:32.773] [Kopernicus] Bad DDS header. [LOG 18:48:32.774] [Kopernicus] failed to load C:/Kerbal Space Program/KSP_x64_Data/../GameData//Galaxy/Planets/Sarna/Color.dds These are all the errors kopernicus wentrough in startup log. Here is planetary Config @Kopernicus:AFTER[Kopernicus] { Body { name = Sarna Orbit { referenceBody = Sun inclination = 5.6 eccentricity = 3 semiMajorAxis = 113549713200 longitudeOfAscendingNode = 0 argumentOfPeriapsis = 0 meanAnomalyAtEpoch = 0 epoch = 0 color = 0.5,0.1,1,1 } Properties { description = Sarna is the second gas giant of the kerbol system. It has host of about 10 moons and is ''alot better than Jool'', according to Jeb. radius = 7560000 geeASL = 1.4 rotationPeriod = 36000 rotates = true tidallyLocked = false initialRotation = 0 isHomeWorld = false timewarpAltitudeLimits = 0 30000 30000 60000 100000 300000 600000 800000 ScienceValues { landedDataValue = 8 splashedDataValue = 1 flyingLowDataValue = 5 flyingHighDataValue = 5 inSpaceLowDataValue = 7 inSpaceHighDataValue = 5 recoveryValue = 5 flyingAltitudeThreshold = 12000 spaceAltitudeThreshold = 140000 } } ScaledVersion { type = Atmospheric fadeStart = 0 fadeEnd = 0 Material { // Common scaled space settings texture = /Galaxy/Planets/Sarna/Color.dds shininess = 0.1 specColor = 0.0,0.0,0.0,1.0 // Atmosphere settings rimPower = 2.06 rimBlend = 0.3 // Atmosphere color ramp texture Gradient { 0.0 = 0.094,0.220,0.643,1 0.6 = 0.0549,0.0784,0.141,1 1.0 = 0.0196,0.0196,0.0596,1 } } } Atmosphere { // effectively the ambient lighting color for all objects on the ground of this body (provides a slight tint) ambientColor = 0.006,0.187,0.8,1 // // shader.invWaveLength = Color( 1 / r^4, 1 / g^4, 1 / b^4, 0.5); // lightColor = 0.709,0.788,0.543,0 // General atmosphere settings enabled = true oxygen = false altitude = 25000.0 // Atmosphere Pressure // pressure (in atm) = multipler * e ^ -(altitude / (scaleHeight * 1000)) pressureCurve { key = 0 1722.525 -3.68761403636364E-02 -3.68761403636364E-02 key = 13750 1215.4779 -2.89618181818182E-02 -2.89618181818182E-02 key = 27500 926.0747733 -1.70812909090909E-02 -1.70812909090909E-02 key = 41250 745.7422867 -1.22066367272727E-02 -1.22066367272727E-02 key = 55000 590.39232 -1.03885874909091E-02 -1.03885874909091E-02 key = 68750 460.0561533 -8.63595672727273E-03 -8.63595672727273E-03 key = 82500 352.9034533 -7.05044647272727E-03 -7.05044647272727E-03 key = 96250 266.1688867 -5.6660456E-03 -5.6660456E-03 key = 110000 197.0872333 -4.48274916363636E-03 -4.48274916363636E-03 key = 123750 142.8932733 -3.50056581818182E-03 -3.50056581818182E-03 key = 137500 100.8216733 -2.71949803636364E-03 -2.71949803636364E-03 key = 151250 68.1071 -2.13953963636364E-03 -2.13953963636364E-03 key = 165000 41.98433333 -1.65774109090909E-03 -1.65774109090909E-03 key = 178750 22.51922 -1.00126501090909E-03 -1.00126501090909E-03 key = 192500 14.44954667 -4.06759432727273E-04 -4.06759432727273E-04 key = 206250 11.33333333 -2.27824727272727E-04 -2.27824727272727E-04 key = 220000 8.184366667 -2.25669374545455E-04 -2.25669374545455E-04 key = 233750 5.127426667 -2.06283192727273E-04 -2.06283192727273E-04 key = 247500 2.51158 -1.61502101818182E-04 -1.61502101818182E-04 key = 261250 0.68612 -9.13301818181818E-05 -9.13301818181818E-05 key = 275000 0 -4.98996363636364E-05 -4.98996363636364E-05 } // temperature Curve temperatureCurve { key = 0 141.67 -0.002333333455 -0.002333333455 key = 33000 104.4583677 -0.0003304941091 -0.0003294753455 key = 57750 104.4583677 0.0003294753455 0.0003294753455 key = 85250 131.0381051 0.0001800779636 0.0001800779636 key = 154000 131.0381051 -0.0002483375636 -0.0002483375636 key = 220000 90.44359713 -0.0003304941091 -0.0003304941091 key = 247500 90.44359713 0.0001722816364 0.0001722816364 key = 275000 111.2241191 0.0002525833091 0.0002525833091 key = 343750 0 -0.0001634942182 -0.0001634942182 } } } } Does anyone know how to fix this.....

When I try to launch my game, it crashes as soon as it finishes loading. I suspect that it is because of lack of memory, but I would like some more input. Mods: KSP: 1.2.2 (Win64) - Unity: 5.4.0p4 - OS: Windows 10 (10.0.0) 64bit Filter Extensions - 2.8.1.2 Toolbar - 1.7.13 B9 Part Switch - 1.7.1 Basic Orbit - 1.0.5 Community Resource Pack - 0.6.6 CommunityTechTree - 3.0.3 CryoEngines - 0.4.6 DistantObjectEnhancement - 1.8.1 Extraplanetary Launchpads - 5.7.1 Interstellar Fuel Switch - 2.4.6 Kerbal Attachment System - 0.6.2 KerbalAtomics - 0.3.5 Kerbal Joint Reinforcement - 3.3.1 Kerbol StarSystem - 0.4.1 Kerbal Inventory System - 1.4.3 KSP-AVC Plugin - 1.1.6.2 ModularFlightIntegrator - 1.2.4 NearFutureConstruction - 0.7.6 NearFutureElectrical - 0.8.7 NearFuturePropulsion - 0.8.7 NearFutureSolar - 0.7.2 NearFutureSpacecraft - 0.6.3 TweakScale - 2.3.4 Universal Storage - 1.2.2 KSP Interstellar Extended - 1.12.19 Error Log: https://db.tt/ueqmyfBeAp Output Log: https://db.tt/080KMTMJff

Past the Haze main lobby Please Note: Due to the loss of the original image uploader website, and my failure to keep a backup image folder, many of the pictures on pages 2-3 are permanently lost. Introduction: Hi. Before the story starts, I'd like to speak for a little. I have... commitment issues, and have started several stories here, but never progressed far on any. I want this topic to be different from my other ventures, but if it goes dead, that'd be why. My intention is for this to be a series of probably-not-that-short stories using my current science mode game. The premise? I'm kinda making this up as I go along, but so far it involves a space program attempting to survive in a Kerbin previously hit by an unnamed series of disasters (AKA the installation of visual mods), and get to the bottom of the convoluted story of why the planets look so different. All the while, Kerbin itself might not be safe. Quality and enjoyment are nowhere near guaranteed, and there will be early installment weirdness, but I'll do my best to make something decent. Story will start on the next post, listed here is the table of contents, a current modlist, a (WORK IN PROGRESS) character list, and a (WORK IN PROGRESS) organisations list. Table of contents: Story 1: Night Rescue, Chapter 1: Exposition Much? Story 1, Chapter 2: Undeniably Majestic Story 1, Chapter 3: Buck Story 1, Chapter 4: Alone at Sea Story 1, Chapter 5: Kerbal in the Water Story 1, Chapter 6: Fishing Story 1, Chapter 7: Contact Story 1, Chapter 8: Return Story 2: Phoenix II Story 3: Network Story 4: Oculus Station, Chapter 1: Core Story 4, Chapter 2: Minor Hiccups Story 4, Chapter 3: Onboard Story 4, Chapter 4: Telescope Start! Story 4, Chapter 5: Science Run Story 4, Chapter 6: New Mission Story 5: Eve probes, Chapter 1: The Plan Story 5, Chapter 2: Summit 3 Story 5, Chapter 3: Inquirer Story 5, Chapter 4: Survey Story 6: Shroud Lifted, Chapter 1: Hollywood Science? Story 6, Chapter 2: hey cool we found a dot Story 6, Chapter 3: New Guy in Town Story 7: Test the Waters, Chapter 1: Notions of an Idea Story 7, Chapter 2: The rest of the Idea Story 7, Chapter 3: Assembly Story 7, Chapter 4: Set sail Story 7, Chapter 5: Enroute Story 7, Chapter 6: Some assembly required Story 7, Chapter 7: Fission mailed Story 7, Chapter 8: On the road Story 7, Chapter 9: The pumpkin pie planet Story 7, Chapter 10: Can I go home now Story 8: Explore from a safe distance, Chapter 1: Recover vessel* Story 8: Explore from a safe distance, Chapter 2: Going coastal Modlist: Characters (spoilers): Organisations (spoilers): Situation report: Unfortunately, due to numerous obstacles and problems, including losing a great deal of pictures and the game deleting many of my story-important craft, Past the Haze is over. However, as soon as I get my gaming computer up I'll reboot it under a new title.

i did a thing and it's a cool thing. http://imgur.com/a/j6JEg 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.

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?

Kerbalkind would go interstellar soon, the preparations were made - crew trained, target acquired, calculations made, spacecraft built. The only things left to were get the warp drive in orbit and then bring the crew up... The warp drive sat on the launchpad. 5... 4... 3... 2... 1... IGNITION! The engine clusters lit up with a roar and the colossal spacecraft rose slowly from the launchpad on a pillar of dazzling blue fire, building speed as it gained altitude. BLAM! Something caused a booster to snap off and hit the lower stage, setting off a chain reaction that destabilized the warp drive. All the brave (and not so brave) kerbals on Kerbin perished, so did the Munans. Kod had mercy on the Minmians, however, sparing us and our tiny, self-sustaining base. Due to our self-sustaining nature and Minmus's low gravity, we were the main supply line of water and metals to the Munar kolony, mining it from the rich, icy surface, but then our families, friends, history, and potential all vanished in an instant. That was several centuries ago. We survived and slowly grew on the little blue snowball, but scans of Kerbin from an old satellite that survived the blast indicate that the radiation levels have dropped to the point where some areas of the planet could be considered safe, if not habitable again. We must rediscover old technologies and rebuild our once-great civilization. It won't be easy, but then again, nothing is easy here. Your mission - Part 1 - Build a fully-functional Extraplanetary Launchpads base on Minmus and populate it with kerbals. The more the better. I'd have at least 60, but it's up to you. After part 2, you cannot get more, so make sure you have enough to last. You cannot have kerbals just standing around, they have to be in a crew container. Remember, even though you can make breathable air, solar radiation is still a threat Part 2 - Destroy the space center, save for the VAB and SPH. You can still design craft, just not launch them. They must be built on Minmus Part 3 - Re-kolonize Kerbin and build a fully-functional Extraplanetary Launchpads base on Kerbin where the large impact krater is (It's to the west of the desert near the equator. You can't miss it. There are complicated reasons for the base being here, but I'll boil it down to resources and environmental hazard reasons. The warp drive was nuclear. That was the logical-sounding reason. The real reason is that it's pretty but nobody ever goes there for some reason) and populate it with some kerbals from the Minmus base using only craft built on Minmus. Part 4 - Build a fully-functional Extraplanetary Launchpads base at the North or South Pole and populate it with kerbals. The crew and parts for this base can be built at the Krater Base or the Minmus Base. Part 5 - Rebuild the Astronaut Complex and Runway/Launchpad at the KSC. The population on Kerbin is increasing somewhat-rapidly now. Only crew-carrying craft can be built, and they must be destroyed once the crew are where they need to be (the crew are being born, not transported, so the craft don't "exist", but there's no population growth mechanic in KSP, so they have to get there somehow). I won't put restrictions on the number of kerbals that can be made, but keep it at a sane level. I don't want to see a kolony of 15 kerbals suddenly become 1,500 in a day or two. The crew must be inside a crew container, not just standing around. Remember, even though Kerbin is "safe", maybe even "habitable", it is still dangerous Part 6 - Return the population on Minmus to the original amount. The base cannot support more crew than there were when you left. Part 7 - Build a third base on Kerbin anywhere but near the KSC or a pre-existing base. I won't place any restrictions on this, but keep in mind that you're trying to spread out and the land near the KSC is still uninhabitable and will be for a while. The parts for this base must come from a pre-existing base but the crew can come from anywhere Part 8 - Send a drone over to the KSC and mine some ore from there. Bring that ore back to a base for study Part 9 - Build a fully-functional Extraplanetary Launchpads base near the KSC. The craft for this base must come from a pre-existing base but the crew can come from anywhere Part 10 - Fully rebuild the KSC Part 11 - Bring the Minmians home. Part 12 - Set up a communications network around Kerbin Part 13 - Put a satellite in a polar orbit around the Mun to search for survivors. You find nothing (or do you?) Part 14 - Outlaw all uses of radioactive material in or related to space travel Part 15 - Immediately ignore Part 14 and place a fully-functional Extraplanetary Launchpads base on Laythe with at least one RTG and/or nuclear generator Rules - All mods are allowed except cheaty mods like HyperEdit. No cheats menu. Please leave links to screenshots of all steps in the comments A fully-functional Extraplanetary Launchpads base is a base that is capable of building and fueling spacecraft with the Extraplanetary Launchpads mod. This includes mining ore and refining it into various fuels and then storing them, mining metal ore and refining it into rocket parts and storing them, building spacecraft with the Extraplanetary Launchpads mod. Off-planet craft building mods can be used alongside or instead of Extraplanetary Launchpads. This includes KIS/KAS and Ground Construction. Vessel Mover can be used to spawn and/or deliver crew at bases and move modules around if they touch down in the wrong place or you just want to re-arrange the base. It cannot be used to transport base modules, even if they have crew in them. Extraplanetary Launchpads mod -

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)

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: https://www.dropbox.com/s/re34rj9nzm89g8e/output_log.txt?dl=0

OK, so here is the breakdown: A new (heavily) modded Career Save with the goal of accomplishing a few of the Challenges that I am interested in. The primary Challenges at the moment are the Doing It Apollo Style - Redux, The Ultimate Jool 5 Challenge, and the Interstellar Rendez-vous idea. I am sure there will be some more that I come across as I play through this save, but those are the ones for now. This Career will use the SETI Unmanned Before Manned Contracts and Tech Tree. Other major mods include all of Near Future Technologies, KSPI-E, Kerbin Shuttle Orbiter System, TAC Life Support - because why not make an already difficult challenge even harder?, SCANsat, DMagic Orbital Science, Kerbal Construction Time (Dev Version), and a whole host of others - the number may change based upon how many times I break my computer For the Jool 5 challenge: -No barred mods will be used for the challenge ship's construction, orbital assembly/refuelling, or the vessel itself. I'll post as many screenshots/videos (if I can figure that out - tech neophyte here) as I can. That Challenge may even involve 2 missions, one for the Jebediah's Level (stock science experiments) and one for non-stock experiments - we'll see how ambitious I get. For the Insterstellar Rendez-vous Idea: -The following changes have been made to the Extrasolar solar system mod pack (Valentine red dwarf star): (changes courtesy of @AndrewDrawsPrettyPictures) This will move Valentine 4 lightyears or so away from Kerbol. For a general "thing": -Kerbin Environmental Institute will not be used until after I have done at least 1 or 2 launches.... (I find it kind of cheaty right at the start) Without further ado here are the important bits: KSP 1.2.2 build (not sure - will add later) Gamedata folder: Mod list: We'll have to see how this goes, I haven't run this many mods before! Updates and reports to come!

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.)

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

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.

So, I am currently writing a war series on the forums and I am going to need your help with a new chapter. I am (planning to) have a naval battle, and submarines are going to be crucial in this. One issue though; I have no idea how to make said submarines. PLEASE HELP ME!!! (Note: I have no mods except BDArmoury and I'm thinking about getting Kerbinside (Which adds more airbases), so anything with stock parts except weapons) Would be super handy.) (Note II: I'm using 1.1.3)

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

KSP version 1.2.1.1604 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 https://s3-us-west-2.amazonaws.com/elasticbeanstalk-us-west-2-868470985522/ShareX/2016/11/KSP_x64_2016-11-19_15-46-45.jpg 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: https://s3-us-west-2.amazonaws.com/elasticbeanstalk-us-west-2-868470985522/ShareX/2016/11/radley.zip Crash log files: 1. https://s3-us-west-2.amazonaws.com/elasticbeanstalk-us-west-2-868470985522/ShareX/2016/11/2016-11-19_151312.zip 2. https://s3-us-west-2.amazonaws.com/elasticbeanstalk-us-west-2-868470985522/ShareX/2016/11/2016-11-19_154002.zip 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): https://s3-us-west-2.amazonaws.com/elasticbeanstalk-us-west-2-868470985522/ShareX/2016/11/other-crashes.zip 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: https://s3-us-west-2.amazonaws.com/elasticbeanstalk-us-west-2-868470985522/ShareX/2016/11/DxDiag.txt 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. https://docs.google.com/spreadsheets/d/1K3qWPOEiYz_zqoNZ_l-QiBsdAL4gVlYVPKPEkYT6cAQ/edit#gid=0 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.

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: https://mega.nz/#!FxtBGSRY!c4298LUcgGBHXS-aUia9RkJufxV7ijm3_cU2wVpSlqk Virus Scan for the .zip: https://www.virustotal.com/de/file/442af8355a716ae47370f1d3c6dd5d050e1abef20426c37ecd9229f0d951735c/analysis/1479230776/ My installed Mods(I know its alot): http://pastebin.com/YZttRTXL

This is my new fighter jet! I'll let you guys decide the name! Happy building, burning, crashing, Kerballing, and overall madness!

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

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!

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?

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.

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.

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!

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:

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.