Search the Community

The Acapello 15 mission is neither completed nor failed if you splashdown on Kerbin instead of land on ground. If you finish the mission in water, the "splashed down" node does not lead to a "mission complete" or mission fail node. Instead it leads (for some reason) to a 5 minute timer node. At this point the player has no idea what's going on. There's no message, and if you recover vessel, the KSC is all disabled and nothing works. Either splashing down should be a fail or a success but it shouldn't leave the mission stuck in limbo.

I haven't been following KSP2 development too closely so forgive me if this is something that's already largely planned for KSP2, but I would really love some content or a DLC devoted around marine exploration. Aquatic alien environments are important future targets of investigation in space exploration, and I believe it would be great if this was reflected in KSP2. The content I have in mind would largely be focused on submersibles and buoyant rovers, although if IG wants they could totally expand to typical aquatic crafts like boats and submarines as well What would this additional content entail? Parts: Command Modules: 2-3 Crew pods, 1-2 probe cores, 1-2 habitat modules New Aquatic Propulsion systems (maybe some pure hydrogen fuel that can be generated with new hydrolysis parts?) Ballast & Flotation systems Structural & hydrodynamic parts Aquatic landing gear & new cargo/bay parts New lamps/lighting parts, cameras + monitor feeds (think raster prop monitor) Improved nuclear energy tech, fission too? (for deep sea mission power requirements) 2-3 new science parts/experiments Buoyancy system for kerbals on EVA Celestial Bodies: New marine environments/biomes/anomalies on the following: Kerbin Laythe Eve Gurdamma Merbel Icy moons (Vall + others) with a subsurface ocean that's many kms below, only reachable via deep canyon like cracks. Any celestial body that holds life should have that added in visually to create a more enriching experience for the players Kerbin: Modern earth like marine ecosystems. (coral reefs, kelp forests, deep benthic zones etc.) Vall + Other ice shell moons: Could have microbial-mats/stromatolite-like formations of chemosynthetic bacteria near hydrothermal vents It would also be cool to see a planet or moon outside of the Kerbol system that contains more advanced forms for life, something akin to Ediacaran or Early Cambrian life forms

Level: Intermediate/Advanced Craft used to illustrate this tutorial: BAK-52NS Version history: 1.2 - Updated with a note on 1.7.3 built-in rotor and propeller blades 1.1 - Updated with better rotors, thanks to a tip from @Hotel26 1.0 - Original version About this tutorial This tutorial is a basic primer on stock helicopters made with parts from the Breaking Ground DLC. It does not discuss pre-Breaking Ground stock rotary motors, nor helicopters made with mod parts. I have limited experience with both and it would expand the scope of the tutorial rather too much. I also do not claim to being the inventor of any of the construction techniques or principles discussed here; a quite a bit I have discovered on my own, and a quite a bit I have picked up around the forums. If you feel you ought to be credited, please say so and I'll add you. What's a helicopter? A helicopter is an aircraft that flies by producing lift from one or more powered rotary wings, or rotors. If the rotor is not powered it is not a helicopter, it is an autogyro; they are also very cool but out of scope of this tutorial. And if the rotor is not used to produce lift but for some other purpose -- thrust, for example -- then it is not a helicopter either. Helicopters can have other forms of propulsion as well: real-life choppers with jet engines bolted on exist and work well. If it's necessary to make the distinction, they are known as compound helicopters. This is a helicopter. It's the BAK-52NS. This variant uses hydraulically sprung and damped landing skids instead of wheels, making precision landings easy...ish. How is it different from an airplane? Airplanes fly by producing lift from airflow around wings. They need to be moving forward to do this and stay in the air. With helicopters, the spinning rotor moves the lifting surface through the air, producing lift. This allows them to hover. However, the big rotating propeller on top of the craft produces a whole set of complications, many of which are shared by kerbal helicopters and human ones; others however are specific to one or the other because kerbal physics aren't quite like real-life physics, and stock kerbals lack certain highly useful bits and pieces used to make human choppers more manageable. On the other hand, kerbals have some amazingly powerful components to build with. Cyclic and Collective Another obvious difference between a plane and a helicopter is how they're controlled. Planes are controlled by moving control surfaces -- rudder, ailerons, elevators, and canards -- which modify the lift produced by each lifting surface, applying forces to the plane and causing it to turn. Pull the stick back, and the control surfaces move to produce more lift near the nose and less lift near the tail, pitching the nose up; push it right, and port control surfaces move to produce more lift while starboard ones produce less, causing the plane to roll to the right. Since helicopters need to be controllable even when they're hovering, they work differently. The primary controls on a chopper are cyclic and collective. Cyclic means adjusting the pitch of the rotor blades differently depending where they are in the cycle of rotation. Imagine that your chopper sits in the middle of a clock face, nose pointing at 12 o'clock. Now, if you want to pitch up, you will want the blades to increase their pitch as they near the 12 o'clock position, and decrease their pitch as they near six o'clock, thereby producing more lift towards the front and less towards the back. You'll also want to adjust cyclic as you start going faster: if your rotor spins counterclockwise, the blades at three o'clock will have a faster airflow over them than the blades at 9 o'clock, because the airflow from your forward motion will get added to the airflow produced by the rotor's rotation. This means you'll want increased pitch around 9 o'clock and decreased pitch around 3 o'clock, or else your craft will roll to the left. This makes helicopters rather hard to fly in real life as well as on Kerbin. What's more, kerbals have no direct control over cyclic: instead, when you adjust the pitch, yaw, or roll, the magic control surfaces try to figure out what you want them to do. This works acceptably with regular aircraft; with helicopters, not so much. So cyclic control on Kerbin is crude at best and you will need partial or total workarounds for this. ~ * ~ UPDATE: FooFighter has built a working swash plate with collective and cyclic control. If you want to make a realistic helicopter that is controlled without reaction wheels, now it's possible! https://kerbalx.com/FooFighter/Swashplate ~ * ~ Collective is a much simpler proposition: it just means the average blade pitch on the rotor. Increase collective and the rotor produces more lift, causing you to gain altitude. Increase it more and your motor will run out of torque to spin the rotor: the RPM will drop and eventually the rotor won't be able to produce any more lift. You'll leap up and then drop down again. Increase it too much, and your rotor will stall, causing you to plummet rather precipitately. And conversely, decrease collective to descend and reduce the torque needed to spin the rotor, allowing it to rotate faster. Collective gives really fine control over hover, and makes a helicopter extremely responsive in vertical motion, comparable in KSP only to a wildly overpowered rocket-powered VTOL. Thankfully, it is possible to make a really nice collective in kerbal helicopters. Perhaps surprisingly, hover on a helicopter isn't actually controlled by throttle. The motor's job is just to keep the rotor spinning; collective and cyclic do the rest. Torque effects In addition to the asymmetrical aerodynamic effects described above, rotorcraft have one more issue to contend with: torque. Spinning up a rotor and, when flying, pushing against the air to produce lift requires torque. Because Sir Isaac Newton is no fun with his laws of motion, this torque will have to get transferred somewhere in an equal but opposing manner. If you don't want your helicopter to spin in the opposite direction of the rotor, you will have to find some way to balance out the torque produced by spinning the rotor. Most real-life helicopters do this with a tail rotor: the helicopter has a pretty long tail which works like a lever arm, and at the tip of the tail is a propeller producing thrust in the opposite direction of the main rotor's torque. The pilot controls the pitch of the tail rotor using yaw controls, and will in fact be continuously adjusting it in different flight conditions (unless he has a computer to do it for him). Sadly, this does not work all that well in KSP. It is possible to make a smallish single-rotor/tail-rotor that is somewhat controllable, but it is hard, it won't be all that easy to fly, and it will very likely require a lot of reaction wheels to paper things over. That's why we're going to discuss a different type of helicopter here: one that flies with twin coaxial contra-rotating rotors. This solution neatly balances out the asymmetrical torque and aerodynamic effects, making for a stable, neutral basis for your craft. By all means attempt to make a conventional main rotor/tail rotor helicopter. Just expect it to be quite hard! This has real-life counterparts as well, notably the Soviet/Russian Kamov Ka-50 and its relatives, and the solution is used there for the same reason it works for kerbals. It makes the craft stabler and easier to fly. By Dmitriy Pichugin - http://www.airliners.net/photo/Russia---Air/Kamov-Ka-50/0920728/L/, GFDL 1.2, https://commons.wikimedia.org/w/index.php?curid=5896037 The coaxial contra-rotating twin rotor powertrain The simplest kerbal rotorcraft powertrain uses a similar solution as in the Ka-50. Kerbals have the advantage of having incredibly powerful, yet compact electric motors that can be placed anywhere, so that's what we're going to do. The powertrain only consists of two parts: at the top a motor (the standard or heavy electric rotor work well for most craft), and below it, a flat servo with its motor disengaged (with no motor at all). The rotor blades attach to the motor above, and the freewheeling servo (or the bottom half of the motor) below. When you spin up the motor, the torque will be evenly split between the two rotors, which will start spinning in opposite directions. Note: this isn't the only way to make a contra-rotating powertrain; you can also use two electric motors surface-mounted to a base, then gizmoed into being coaxial; in this case, each motor will be spinning its own rotor. It has twice the power. For most purposes, the single-motor/freewheel solution is sufficient, however, and has the advantage of being simpler and stabler. Collective Since KSP 1.7.3, Breaking Ground includes propeller and rotor blades as parts. Clip them onto a motor, deploy them, and bind their authority limit to an axis group to control collective (e.g. up/down). Note that they come in clockwise and counterclockwise variants: if building a contra-rotating powertrain, be sure to use mirrored variants for each rotor so that the marking decals point the same way on each, and set the deploy direction on each of them so that adjusting collective up increases pitch on both of them. When building your own rotors (see below), mount an elevon on a servo as pictured above, limit the servo's angle to some relatively sane values, and bind it to an axis group as above. Rotor design The built-in rotor and propeller blades differ greatly in performance from ones made from elevons. They are much more powerful in the lower atmosphere, producing a great deal more thrust/lift. However, their performance drops off much more abruptly and their service ceiling is much lower. A craft powered with a rotor made from elevons can reach 20 km on Kerbin and operate easily on Duna. Therefore, for such special off-world uses, hand-built rotors still have a niche. With rotors, light weight is everything, so use the lightest components available for the job. Your rotor blades should be control surfaces -- FAT-455 for bigger rotors, elevons of various sizes for smaller ones. Here's the best way I know to make a rotor: Place servos onto the motor or the freewheel in radial symmetry. Small ones work most of the time; for very big rotors you might want to use larger sizes. Attach a control surface to the servo and rotate it to the correct orientation. Hold down the shift key and offset it outwards to your desired radius. Set the angle restrictions on the servo. Values of about 12 to about 35 degrees depending on rotor size work for me. If making a bigger rotor, add a second control surface and repeat step 3 for it. Optional: add a strut connector from the servo to the nearest control surface. It won't do anything much but it will make it look better. Copy the entire blade assembly onto your other power element and turn it upside down. Assign servo angle on both sets of servos to up/down, reversing one of them. Important: Disable yaw control on all the control surfaces on your rotor, leaving pitch and roll enabled. Powering it Rotorcraft require electricity to run the powertrain (and also operate collective). Small craft like the BAK-52NS "Kranefly" above could actually run just on a pair of the larger solar panels, or you could bring enough batteries to give you the endurance you want, but the all-around easiest solution is to use fuel cells as above: the golden tank contains enough fuel to fly the Kranefly for probably longer than you have patience, and it only needs a few cells to run. For the heavy rotors you pretty much have to use fuel cells; a pair of large fuel cell arrays is sufficient to power a single heavy electric motor. Controlling it You can set up whatever control scheme you like of course, but I have found the following to work for most things: Action group 1 Toggle fuel cells and engage motor(s) Main throttle[1] Adjust engine torque (you'll want this at maximum most of the time) Up/Down axis Adjust collective (K increases pitch, I decreases pitch -- this places them at the same positions on your right hand as pitch on your left) [1] Since 1.7.2, F/B in 1.7.0-1.7.1 Additionally, brake will apply brake on the motor driving the rotor. Because you have a freewheel between the rotors and the craft's body, this means you can stop the rotor very quickly by disengaging the motor (action group 1) and hitting the brakes -- both rotors will stop with the torque canceled out between them. The magic of reaction wheels Kerbals may not have cyclic but by the Kraken's tentacles they have reaction wheels. You can paper over minor misbehaviours in the craft by adding some reaction wheels... sometimes quite a lot really. Don't feel bad, it's a kerbal solution. Tuning it The powertrain described above is fairly docile and you can stick it on top of the centre of mass of pretty much any craft light enough for it to lift, and it will fly and hover. Getting it to fly well is a different kettle of fish altogether. If there is a science to tuning kerbal rotorcraft I haven't discovered it -- all of my tuning has been through trial and error. I suspect the unpredictability is due to the way KSP translates control inputs into control surface positions on the rotor, which is a bit on the flaky side: Change the number of rotor blades. I've had good results with rotors from 2 to 6 blades. More blades require more power but run smoother. Adjust blade length. Larger rotors are more efficient but less stable unless you feed them with more power. Move rotor forward/aft. Moving it forward and back changes the craft's tendency to pitch forward or back as you increase/decrease collective; it also changes its sensitivity to roll and yaw controls although I have no idea exactly why and how. Even tiny adjustments can make massive differences; less than a "click" of snap-to motion can completely change the handling characteristics of a chopper. I suspect this is due to the way the rotor blades respond to your control inputs. Move rotor up/down. Up tends to make the chopper more stable but less responsive to control inputs, down does the opposite. It's quite possible to make a really numb chopper that only goes up and down and barely even responds to pitch, roll, or yaw controls! Tilt rotor forward. It does something so it's worth a try. Adjust control authority. Less authority means less judder but less control; more does the opposite (and might cause blade stalls which is no fun at all). Adjust the craft's centre of mass. Generally speaking you will want a high centre of mass, close to the rotor: this is why the fuel tank is right below the powertrain in the BAK-52 above. Add or remove reaction wheels. Tip: Tune with SAS off. You might find that your chopper flies rather pleasantly without it in fact! Flying it To fly a helicopter, spin up the rotors with collective at zero, engines at maximum torque. Then increase collective until it takes off. Pitch to accelerate, slow down, or fly backwards; roll to fly sideways, yaw to spin around. When you're moving forward at a decent pace airplane-like aerodynamics start to enter the picture which is fun and different. Developing it further The basic Ka-50 style craft plan is just one possibility among many. Once you've got the power train figured out, you can make bigger ones and smaller ones, choppers powered by more than one set of rotors in a variety of configurations, tilt rotors with heavy servos making for an Osprey-style VTOL craft, and so on. You can stick on a jet or two just below the rotor assembly to make it go faster -- making fast choppers is a completely different and much harder challenge than making fast planes, since the limiting factor is stability rather than thrust to weight ratio; you will need to design rather different rotors for choppers that go very fast. You can also attempt different solutions altogether, like with non-coaxial contra-rotating rotors, or even attempting a main rotor/tail rotor style craft. There's a lot of room for tuning in rotor design as well, and if you feel the stock electrics don't quite produce the oomph you want, research turboprops and start breaking records (ht: @Azimech). You might have to get creative to find a practical use for helicopters in career missions but they are a lot of fun to build and, eventually, to fly. There are at least two helipads on the KSC just begging to be used, so go out and use them!

Thanks to a bunch of hippies from Green Springs and their goons at the so-called Environmental Security Agency (or, as we like to call it, the Economical Screw-up Agency), we now have to limit our Kerbin circumnavigation challenges to have ZERO overall emissions. In other words, whenever we circumnavigate the planet, we have to do it in an electric vehicle. Fortunately, thanks to our folks at Kerbal Motion LLC, we now have the means to do so. It may be slow, but it is possible. In other words, the challenge is to go one full equator's length of Kerbin WITHOUT any gas-powered engines - which means ABSOLUTELY NO: Jet engines Rockets Gas-powered turboshaft engines (like the R121 or the R7000) Electric motors are okay. Here are some other rules for this challenge. Leaderboard placement will be awarded based on TOTAL MISSION TIME ELAPSED (As you may have already guessed) vehicle must be all-electric. Which means are solar panels and/or RTGs are highly recommended. Having liquid fuel and/or oxidizer is okay ONLY for weight and balancing purposes. This can come in real handy if you need to move your CoM forward or backward. Fuel cells are not permitted, since we're trying to conserve gas thanks to those pot-smoking bureaucrats at the ESA. Even if I did allow fuel cells, they won't be enough to push your vehicle through the whole length of the trip. Stock and/or DLC parts only. Autopilot/navigation/gauge mods okay. Generally, no mods outside of DLCs that come with additional parts EXCEPTION: mods that come with balloon or dirigible-related parts are permitted, but those craft go in a separate division. If you want to allow a specific mod that conforms to the other rules, let me know and I'll take a look at it before deciding if it shall be allowed. Your vehicle must come back IN ONE PIECE. Not that you should need an extra fuel tank for an all-electric vehicle. Surface vehicles are okay, but they'll get placed in a separate division. Mostly because you'll take longer to go around the planet. On the bright side, if you have to stop to recharge, you can pause and take a break IRL. Just keep in mind that any and all recharge breaks in which the MET clock is running count for your finishing time. Crew capacity is optional. Divisions are as follows: Trekker Division - vehicles that can't fly, but travels on land and/or water to complete the journey. Earhart Division - aircraft like planes, helicopters, and gyroplanes. You'll get an Earhart Division: First Class medal if you successfully fly Kerbin's equator WITHOUT STOPPING. Heisenberg Division - balloons, blimps, zeppelins, et cetera. I don't know much about the balloon/airship mods, but the reason they're a separate division is because they can stay airborne without needing to land or stop. This may provide an unfair advantage over the aircraft, since they'll have to come down and recharge for God-knows-how-long before taking off again. Sun Soaker Division - any craft that can successfully cruise at 175 m/s. More details later. Multiple entries per person allowed, but only the best-performing one for each division will be accepted. Pictures and/or video required for entry to be valid. Be sure to include: Your craft in action. Start/finish times. (Optional) the craft in the hangar. If you're having trouble getting your rotors to work, please consult this thread below. @Echo__3 and @18Watt really helped me out when I started to use the Breaking Ground DLC. Sure, I originally asked about a motor that's prohibited on this challenge. Nevertheless, the same principles still apply - and I got the electric-rotor plane to work successfully. As promised, here's an explanation as to why the Sun Soaker Division has a speed requirement: And last but not least, here's my entry. Can't wait to see what you all come up with. LEADERBOARD - (ONGOING) MARCH 7, 2023 TREKKER DIVISION (empty) EARHART DIVISION @18Watt - 3 hours, 14 minutes (FIRST CLASS) @Mars-Bound Hokie (ME) - 5 hours, 11 minutes, 30 seconds (FIRST CLASS) This was a last-minute entry. Better time than my last entry, but not fast enough to overtake the current leader @OJT - 17 hours, 13 minutes HEISENBERG DIVISION @Snigel - 5 hours, 3 minutes I know that he damaged the Thunderbolt's lower battery pod during the landing, but the "Come back in one piece" rule was mainly intended to prevent jettisoning and mid-air explosions. Had he kept the landing a little softer - or if landing gear wasn't too much of a problem for the craft's performance - he could have landed the craft intact. SUN SOAKER DIVISION (Could be me, but I don't really care since I was doing a speed test before sending the E-40 to Laythe) (Please let me know if I missed anything)

I think it would be a great expansion to the game. Have specialized terraforming colony buildings and parts that would in-time change the environment of a planet. Yes, Surviving Mars did it first and it was a good DLC.

Hello, this is my first part release so please bare with me. I dont know how to make a fancy page yet. JxFab Utility Systems JxFab Utility Systems is the start of a parts pack that will add on to the robotics category of the Breaking Ground DLC. Currently there is one part type, the straight rail. There are four lengths of 5, 10, 15, and 30 meters, The straight rail comes in three variants. I plan on adding additional robotics parts to this pack, such as curved rails and rotational station hubs. DOWNLOAD LINKS Current Download: https://github.com/JackATac98/JxFab_Utility_Systems/releases/tag/v0 Dependencies This mod requires the Breaking Ground DLC to work! (I am working on a version that uses Infernal Robotics) KSP version 1.12.2 License This work is shared under CC BY-NC-SA 3.0 license.

FOREWORD After Reactor 4 of the Chernobyl NPP exploded, large amounts of rubble, graphite moderator and other radioactive material from the destroyed reactor were ejected onto the roofs of power plant facilities. Radiation on some parts of the roof was so severe that unprotected circuitry used in remote-controlled robots failed near-immediately. To continue cleanup works rubble needed to be removed from the rooftops. Since the radiation levels would give human workers lethal doses in a matter of minutes, robotic solutions were in high demand. One of such solutions was a repurposed lunar rover (named STR-1), a remnant of the Lunokhod program outfitted with dosimetry equipment and a bulldozer blade. It's circuitry was already hardened against cosmic radiation, and such it could be quickly modified and deployed into the containment zone. Even with this protection, it only managed to clean up a couple dozen square meters of the roof before succumbing to the extreme radiation. In this challenge, you will take on this exact task. You will develop a rover with limited operation time which will help remove graphite rubble from the power plant site along with a delivery method. THE CHALLENGE The cleanup operation will consist of four major phases. 1. Rover delivery Taking off the KSC airfield, you will need to deliver the rover to the disaster site. Time will be counted with the in-game clock from the mission start to the moment, where you come within 150m of the reactor (when the distance marker disappears). In this case, the quicker the better. Point assignment rules will be elaborated on in the next section. 2. Landing your rover on the roof Since the radiation levels near the core are extremely high, you will need to minimize your time in the proximity of the reactor. From the moment of your arrival within 150m of the reactor you will have two minutes in-game time to deploy the rover onto the roof and leave the 150m perimeter. 3. Retrieving the carrier craft This section will not be timed, albeit additional points will be awarded if you can return your carrier craft to the KSC unscathed. 4. Cleaning up the roof After your carrier vehicle has landed (or crashed horribly) you can begin your operation. This section is not timed - the only limit being your battery life (to simulate radiation exposure). Points will be awarded based on how many of the 10 graphite blocks (Oscar-B fuel tanks) situated on the roof you can remove before your battery dies. The blocks are supposed to be pushed off the edge of the roof into the destroyed reactor building where they will not pose a threat. The challenge ends after your rover battery dies. RULES As with all challenges, here are some rules: 1. Your carrier craft can be a VTOL aircraft, a helicopter or even a land-based vehicle. The choice is yours in that regard and creativity in the delivery method department is greatly encouraged! 2. Your rover's only power source can be a single Z-400 battery. All other power sources such as your control modules are prohibited and need to be emptied in the hangar. 3. You may not use any power producing parts such as solar panels, fuel cells and RTGs. 4. The rover has to be delivered onto the roof via the carrier craft, e.g. it may not be deployed outside of the 150m perimeter and flown or driven onto the roof. 5. Albeit the graphite blocks may explode after being dropped into the reactor, they may not be exploded directly on the roof as a mean of their removal. 6. Using kraken drives to propel your rover is prohibited, as the whole point of this challenge is dealing with the problems within time and resource constraints. 7. Please let me know if your submission is stock + DLC or uses some other mods for ease of organization 8. For obvious reasons, the rover must be unmanned. No Kerbals can come close to the reactor, they are already green enough as they are. The points for each section will be awarded according to these rules: Section 1 - Delivery Number of points is the value of the following function: ceil(max(300 - your_time [sec], 0) / 2) Section 2 - Landing the rover Number of points is the value of the following function ceil(max(120 - your_time [sec], 0) * 4) Section 3 - Returning the carrier craft Number of points awarded is 40 - if the carrier aircraft is landed undamaged at the KSC 0 - otherwise Section 4 - Clearing the roof Number of points is the value of the following function 100 * blocks_removed HOW TO SUBMIT YOUR ENTRY First, you should download the savefile containing the powerplant set up in the correct spot. It can be found here: https://filebin.net/h67zuoh36flmrfpz Afterwards, after creating your entry you should either film your run, or document it via screenshots. If you choose to go with the screenshot route, please provide the following: 1. Screenshot of your crafts on the KSC runway at the beginning of the mission 2. Screenshot of your arrival within the 150m perimeter with the HUD enabled 3. Screenshot of your carrier craft departure with HUD enabled (if you choose to retrieve it) with the rover on the roof visible in the shot, or just a picture of the rover on the roof if your delivery method is expendable 4. Screenshot of your carrier craft landed (if you choose to retrieve it) with HUD enabled 5. Screenshot of your rover on the roof with amount of electric charge remaining at the beginning of cleanup visible 6. Screenshot of the roof after your electric charge runs out with all remaining graphite blocks visible If you have any questions regarding this challenge, feel free to ask them via messages or here in the thread itself. Have fun and good luck on your journey. If you feel that any of the rules or point awarding mechanisms need tweaking please let me know! Be wary that the power plant building contains almost 1100 parts so you may experience quite a bit of lag. This is kind of offset by the fact that the model is static and the game does not seem to lag quite as much as with most mobile spawned high-partcount crafts. With a GTX1050 and 8GB of RAM I was able to keep the FPS at about 20-25 at all times and I could execute the mission without too many lag-related issues. I will prepare a proper badge for all participants and will post it here in a few hours. Cheers. c: STOCK LEADERBOARD 1. Cela1 - 1594 pts (134 + 420 + 40 + 1000) 2. jinnantonix - 1532 pts (140 + 352 + 40 + 1000) 3. ----------------------------------------------- 4. ----------------------------------------------- 5. ----------------------------------------------- 6. ----------------------------------------------- 7. ----------------------------------------------- MODDED LEADERBOARD 1. ----------------------------------------------- 2. ----------------------------------------------- 3. ----------------------------------------------- 4. ----------------------------------------------- 5. ----------------------------------------------- 6. ----------------------------------------------- 7. -----------------------------------------------

A continuation of the polls regarding buying decisions.

Hi everyone, I've ran into an issue with the breaking ground DLC, none of the parts included display in the SPH/VAB, the category 'robotic parts' is present, as is all the stock craft that come with Breaking Ground, but the category is completely blank and none of the Breaking Ground stock craft can be loaded due to containing 'locked or invalid parts' and can't be loaded. Clean (and new) install of KSP 1.12.2.3167, Breaking Ground 1.7.1, Making History 1.12.1 (both appear in the bottom-right corner of the main menu), attempted to completely remove KSP and then redownload to no avail. Windows 10 Home 64 bit. EDIT: Just to note, I've never had this issue before on previous versions of KSP/Breaking Ground. A link to the imgur album showing screenshots of what I'm seeing can be found here. Any help would be appreciated.

These are common problems for newer Kerbal Space Program players who own and play the game through Steam. The most frequently asked questions for these problems are: I update my mods manually or with CKAN; why is KSP-AVC (Kerbal Space Program Automatic Version Checker) telling me I do not have the latest update for this mod installed?! I deleted this mod (or craft). Now it's back again?! My DLC (Missing History or Breaking Ground) isn't showing up in my game?! Background: A while back ago, Steam began to offer a feature to create a cloud archive of key parts of the game as determined by the game's publisher. This idea was in Beta for nearly two years before being released sometime in 2016. It was added to Steam for a couple of reasons: This feature allows the owner of a game to be able to play flawlessly on various devices providing the game's software supports playing on that type of device. To help make it easier for the player, Steam makes a copy of your local files to the cloud storage linked to your account (everyone has cloud storage linked to their account. There is no way to completely disable the feature from your account). When you log onto your Steam account and download the desired game to your device, the files in the cloud are also copied. This way you can play a seamless gaming experience on your tablet, PC, or laptop. Your saved game data is synced with the cloud each time you load a game or exit a game. This feature allows you to be able to permanently delete your Steam library and account from your computer without losing your game's progress, downloaded content, or downloaded mods. You can install Steam, log in to your account, and transfer all your games - with the saved games files - to your new computer and not have to spend hours transferring stuff to an external drive or a lot of flash drives. For the most part, it does well. But with Kerbal Space Program and a dozen other games I have come across, this feature does not always go as planned.

Now introducing, The TEK-113 Light Aircraft Cruiser A 3rd generation aircraft carrier boasting an angled flight deck, clear deck markings, and a Mk-4A Ion reactor powering twin propellers capable of moving the 1500 ton vessel up to a speed of roughly 22 knots (11m/s). Designed to carry 2 Medium V/STOL Aircraft plus 2 light helicopters, the TEK-113 is a perfect scout vessel capable of operation many thousands of kilometres from the KSC. Gallery The specific vessel you are downloading; KMS Atlas DL; https://kerbalx.com/chadgaskerman/TEK-113-KMS-Atlas P.S. If anyone has any experience with making the BG pistons work, or any other ideas on how to make an aircraft catapult work, PM me. I have further projects in the works P.P.S. Thanks to @Yukon0009 for the flag pack https://cdn.discordapp.com/attachments/778244348897656853/821291735275143178/Markings-20210305T055031Z-001.zip

KSP: version 1.11.0.3045 - All DLC - 64Bit Problem: KSP always crashes after loading. (As in, when the initial loading bar fills and then it begins to transition to the main menu with the circular loading indicator in the bottom-right, it freezes momentarily and then crashes.) Mods: Flight Manager for Reusable Stages (FMRS) Continued (FMRSContinued 1.2.9.1) Advanced Textures (AdvancedTextures 1.8.1) AlphaMensae's Modular Launch Pads (ModularLaunchPads 2.1.2) Animated Decouplers (AnimatedDecouplers v1.4.2.2) Astronomer's Visual Pack (AstronomersVisualPack 2:v4.05) Astronomer's Visual Pack-2k Textures (AVP-2kTextures v1.11) B9 Part Switch (B9PartSwitch v2.17.0) Basic DeltaV (BasicDeltaV 6.0) BreakingGround-DLC (BreakingGround-DLC (unmanaged)) ClickThrough Blocker (ClickThroughBlocker 1:0.1.10.15) Commonwealth Rockets - Stockalike British Rocketry (CRE v2.1) Community Category Kit (CommunityCategoryKit v5.2.0.0) Community Resource Pack (CommunityResourcePack 1.4.2) Community Tech Tree (CommunityTechTree 1:3.4.3) Cryo Tanks (CryoTanks 1.5.6) Cryo Tanks Core (CryoTanks-Core 1.5.6) Cryogenic Engines (CryoEngines 1:1.2.1) Custom Pre Lauch Checks (CustomPreLaunchChecks 1.8.1) Deployable Engines Plugin (DeployableEngines 1.2.3) Distant Object Enhancement Continued (DistantObject v2.0.2.0) Distant Object Enhancement Continued default config (DistantObject-default v2.0.2.0) Dodo Labs - Stockalike Electron (DodoLabsStockalikeElectron 1.3.1.1) Dynamic Battery Storage (DynamicBatteryStorage 2:2.2.1.0) Easy Vessel Switch (EVS) (EasyVesselSwitch 2.2) Engine Lighting (EngineLighting 1.5.1) Environmental Visual Enhancements (EnvironmentalVisualEnhancements 3:1.10.1-3) Kerbal Actuators (KerbalActuators v1.8.3) Kerbal Attachment System (KAS 1.7) Kerbal Engineer Redux (KerbalEngineerRedux 1.1.8.3) Kerbal Inventory System (KIS 1.28) Kerbal Reusability Expansion (SpaceXLegs 2.9.1) Kerbal-Konstructs (KerbalKonstructs 1.8.1.15) Kerbin Side Remastered (KerbinSideRemastered 1.0.1) Kramax Autopilot Continued (KramaxAutopilotContinued 0.4.0) KSC Extended (KSCExtended 2.2) Making History (MakingHistory-DLC 1.11.0) MechJeb 2 (MechJeb2 2.12.0.0) MechJeb and Engineer for all! (MechJebForAll 1.3.0.6) Module Manager (ModuleManager 4.1.4) Near Future IVA Props (NearFutureProps 1:0.6.4) Near Future Launch Vehicles (NearFutureLaunchVehicles 2.1.2) Near Future Solar (NearFutureSolar 1.3.1) Near Future Solar Core (NearFutureSolar-Core 1.3.1) Omega's Stockalike Structures: No Textures Required (StockalikeStructures 0.0.12) RecoveryController (RecoveryController 0.0.4) Retractable Lifting Surface Module (RetractableLiftingSurface 0.2.1.1) SCANsat (SCANsat v20.4) scatterer (Scatterer 3:v0.0723) Scatterer Default Config (Scatterer-config 3:v0.0723) Scatterer Sunflare (Scatterer-sunflare 3:v0.0723) SmokeScreen - Extended FX Plugin (SmokeScreen 2.8.14.0) SpaceX Launch Vehicles - Real Size (SpaceXLaunchVehicles 6.5) Stockalike Station Parts Expansion (StationPartsExpansion 0.5.3) TextureReplacer (TextureReplacer v4.3.1) Textures Unlimited (TexturesUnlimited 1.5.10.25) Toolbar Controller (ToolbarController 1:0.1.9.4) Trajectories (Trajectories v2.3.4) Tundra Exploration - Stockalike Dragon V2 and Falcon 9 (TundraExploration 3.3.0) Tundra Technologies (TundraTechnologies 3.3.0) Tundra's Space Center (TundraSpaceCenter 2.0.1) TweakScale - Rescale Everything! (TweakScale v2.4.4.5) Zero MiniAVC (ZeroMiniAVC 1:1.1.0.1)

The Challenge: Build a military aircraft that falls under one of the following categories and submit it in your post for the most points possible: Fighter (Baseline, 5 points) Bomber (Baseline, 5 points) Transport (Baseline, 5 points) How to submit: Different submissions have different point bonuses. Choose one of the following ways to submit: Cinematic (Showcase Video with soundtrack, +20 points) Showcase Video (Show off your design in a video, +15 points) Image Gallery with Stats (Have a series of images of your aircraft with its in-game stats, +10 Points) Image with Stats (Have your favorite image of your design with its in-game stats, +5 Points) Image/Image Gallery (+0 Points) Additional Awards: VTOL (+ 5 points) Replica (Rebuild a real aircraft, +10 Points) Custom Aircraft (Make it your own design, +10 Points) Customized (Use custom made flags as details, +20 Points) EJECT! (Include an ejector seat, +10 Points) Skill points for complexity, beauty, and low part count will be awarded. Badges: If you are skilled in making badges and would like to make some for this challenge, please let me know via private message (so we don't clutter the challenge thread). Leaderboard: (Insert Username), (Insert Aircraft Name), (Insert Number of Points) If you are interested in partaking in this challenge, post that you are interested in joining in the 'reply' box.

Hey guys.A few hours ago, I successfully purchase DLC: making history at the KSP homepage.But, some reason, I cannot download DLC.It doesn't appear at the accounts/your orders tab.Where can I find downloads DLC?

I purchased the Making history DLC and used the code to add it to my Steam account. After putting the game down for a while, I re=downloaded it and suddenly my entire DLC was completely gone from my steam account. Is there any way i can get this fixed, or get a new code for my DLC? I might be able to dig up the proof of purchase, and if i do, will either Steam, Squad or Blitworks be able to help?

These new Triangular panels made me pretty excited at first, until I tried using them in the SPH and found the mirror symmetry feels all wonky and wrong for them, making it hard to design certain things with them. Look at these screen shots - the mirrored symmetry isn't making actual mirrored parts. It's behaving just like radial symmetry: The first two images are with Mirrored symmetry. The last image is with radial symmetry to compare. I don't see any difference.

Wondering, as the summer sale is going on, I was gonna buy making history and breaking ground, but I play on 1.7.3, if I buy the dlc, will it work with 1.7.3 and if not, is there a workaround that means it will?

Breaking Ground, the second expansion of Kerbal Space Program is coming to PlayStation 4 and Xbox One on Dec 5th! Console players will be able to enjoy this content-filled downloadable expansion at its fullest, all from the comfort of your couch, so get ready to join the Kerbals in exciting new scientific endeavors! Collect data with brand new deployable science experiments, explore mysterious surface features across all of the moons and planets of the Kerbolar system, and test your creativity with a new suite of robotic parts. Kerbal Space Program Enhanced Edition: Breaking Ground will help you and the Kerbals reach new horizons, all in the name of Science! These are the most significant features coming to this DLC: Robotic Parts Brand new robotic parts will add a whole new level of creativity to your craft. These parts will include some fresh control mechanics and will allow you to create all sorts of inventive vehicles and crazy contraptions to aid the Kerbals in exploring their universe! Surface Features Scattered across the Kerbolar System, you’ll find interesting Surface Features, like mineral formations, meteors, craters, and even more curious planetary features. Study them and collect valuable scientific data with a brand-new Rover Arm! Deployed Science Bring equipment for experiments with you from Kerbin and deploy them on the surface of a celestial body to take measurements over time. Set up a science station and put your crew to work. From seismometers to weather stations, there are plenty of experiments for you to try out! New Space Suit Kerbals are also getting a fresh new space suit to wear for their scientific endeavors! This sleek futuristic suit will make your Kerbals look flashy while they explore the canyons of Duna, the shores of Laythe, or any other exotic destination. The suits also allows for customization where you can choose which color emanates from the suit’s light panels. Kerbal Space Program Enhanced Edition: Breaking Ground Expansion will be released on December 5th for PlayStation 4 and Xbox One for $14.99 USD. Free Update Coupled with the Expansion, Kerbal Space Program Enhanced Edition is getting a content-filled console-optimized update that will contain long-requested features like the Improved Burn Time Indicator, the Delta-v per Stage and Delta-v Tool App, an Altitude toggle function to the Altimeter, Axis Group binding, dozens of Part revamps, as well as performance improvements, bug fixes, and more! Do you want to learn more about the upcoming DLC and free update? Then make sure to stay tuned for our next KSP Loading… where we’ll take a deep dive into the content and features of this exciting addition to Kerbal Space Program Enhance Edition! Happy launchings!

KSP 1.9.1 64x, fresh install, no mods I have 2 different Rotation Servo f-12's that are mirrored with wings at the end, I'm trying to get them to fold out to give lift to my craft. In the VAB when I put them at their max angle they deploy fine, but when I launch the craft and try to deploy the wings only 1 side works. Removing 1 side from symmetry does nothing, even if I invert the angle value still nothing happens. Autostrut is not on(although this never affects anything) Inverting the direction of the servo causing the part that doesn't move to jerk to 1 direction, then it returns to the centerline. Link to video showing what happens: https://youtu.be/kxdKusQWITs Output_log.txt: https://drive.google.com/file/d/1gPgQ38dIR7sEKy79BDhLioxJut4qX9cF/view?usp=sharing

Hello, I just got the DLC on PS4Pro (latest KSP-version, all standard settings) and have some problems playing the historical missions. Right during the first mission: The Dawn of the Space Age: After successfully landing (Wernher told me so :)) the K-7 near (but not directly on the runway) the old airfield I return to the VAB either via the button at the top or via the mission diagram. I build the K7-B and want to launch. But here I am sent back to the landen K-7 on the island. Here Wernher briefs me on the 48km-flight. Somehow the spawning of new vehicles does not work, From now on, when I manually return to the space center, all building are locked except the Observation building from where I just can return to the landen K-7.

Hi there, I've had the Breaking Ground and Making History Expansions since they day they've come out. Never had an issue with them. 1.8 was released and changed that. 1.8 functions as expected; however, the DLC appears to not have updated with it. I get "Expansions Failed to Load" as the error with a notice telling me that the DLC versions are incompatible with the current version of KSP. Using Steam, I have verified the install, re-installed the game, re-installed the DLCs all to no avail. Any suggestions appreciated.

Backstory I started a mission report a few months back. I liked sharing my missions and people liked reading them. But then my computer died and for a while I couldn't recover the data. And during that period of time, I started playing @Galileo's Planet Pack. And I love it. So I've discontinued my initial save, even if I may recover the data someday (TM), and started another save. Boring! Do you have anything else to say? I am playing on Moderate mode, but I have increased the science! returns so that I can do whatever I want as soon as I want. Moderate mode means that I have to pay to unlock new parts. Still boring! How about a modlist? I have: This continues to be boring! A chapter list? I only have 1 chapter at the moment, but... Chapter 1 started with this post. Still quite boring! Some launch scripts? Here's my Google Drive. But there are no ships to launch them with! Fine! Here are the first pages of Starwind (in GPP): The Ceti Campaign Oh yes, I kept the Original Four Gaelans and added the Original Four Kermen. So I have Eight. Tune in next time for Val making orbit, and an Iota flyby!

So i just bought the DLC on xbox one last night and ive had nothing but trouble with it. My main problem is i can't progress beyond the first challenge (build a rocket and land at the old runway). When i complete the challenge and land on the runway it prompts me to go to the VAB to start the next mission. I go to the VAB, create the rocket for the next mission, when i press launch it doesn't put my new vessel on the launch pad, it takes me to my old rocket still landed at the runway. When i try to leave and go back to the VAB it says the building is locked. Here is a video showing the problem. What is wrong here? I've reset the mission like 10 times now, deleted the DLC and redownload it. Completely uninstalled and reinstalled the game. And cleared save data. Nothing fixes it.

First post here so sorry if I am posting this in the wrong place When ever I try and build single engine propeller aircraft it rolls to what ever direction the engine is spinning and I also notice that they tend to slowly pitch down on there own. My question is that is there a way to mitigate these issues?