Search the Community

Showing results for tags 'helicopter'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • General
    • Announcements
    • The Daily Kerbal
  • Kerbal Space Program 2
    • KSP 2 Discussion
  • 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
  • Making History Expansion
    • Making History Missions
    • Making History Discussion
    • Making History Support
  • Breaking Ground Expansion
    • Breaking Ground Discussion
    • Breaking Ground Support
  • International
    • International
  • KerbalEDU Forums
    • KerbalEDU
    • KerbalEDU Website

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



Website URL





Found 50 results

  1. Airplane Plus Powerful stockalike parts for aircraft enthusiasts. Feedbacks would be helpful. And if you have time, please take the Poll: Click here to vote on what part do you want to be added Download at: Spacedock · Curseforge Github Want to support me? You can on either of these: PATREON User Patches: Tweakscale Compatibility RPM Compatibility AJE Compatibility F-16 Cockpit RPM Remotetech Config Community Tech Tree Sound Issue Workaround is under "Issues" Below If you want assist in hovering, I recommend this mod I'm using Craft Files (Click Image): Release 22-24: Release 20: Old Files: Extra Images: Old Part Selection Images: -- Collection of Aircraft Photos: Old Album: -- APU in Action: Huey in Action: Machbuster Video: Extra: Demonstration of the Tilt-Rotor function, assisted VTOL landing and New Diagonal Gear Other videos: Latest Changelog: Installation: Remove old folder if there's an old installation. Copy the GameData folder into your root folder. -Included in the pack are AirplanePlus and Firespitter folders. It also packs ModuleManager* *I do not own these mods, I merely packed them in for Airplane Plus to be functional and avoid linking downloads for dependencies. Big thanks to their Authors. FAQ: License: *I only take credit on my parts. Firespitter and Modulemanager which are included in the pack are made by different authors with their own licenses. Most performance configs powered by @Tanner Rawlings Shout out and big thanks to @acc for doing a test run back then. @kiwinanday helped a lot on producing important info in reconfiguring performance, thanks a lot!
  2. Most people like to think big: Go big or go home. But how about going small? I 've designed a small VTOL. Hoverbike, Skycycle, whatever you call it, it's small (barely one ton), fast (It can cruise at up to 62 m/s, although ~55 m/s is advised), and with excellent endurance. And it seats two kerbals! Running on batteries is how I got it so small. twin rotors and SAS wheels keep it stable. Truth is, it's got more power than you'll actually need. *edit* how do I attach images? *edit2* fixed with KerbalX mod Here's the lowrider on KerbalX:
  3. So, I got this DLC wanting to make helicopters. I found out pretty fast that metaphorically bought the tool, but not the skill. Yet. The DLC has a few stock "helicopters" which are just ducted-fan VTOLs and flying platforms. However, I'm trying to make a "conventional helicopter" so to say. A helicopter with a main rotor and a smaller tail rotor. So far, my results have been far from desirable. My first rotor-tail rotor helicopter design (image links below) was awful. All it did was break itself. What's the right way to make a rotor-tail rotor helicopter?
  4. I tried to replicate the DeLorean from the epic movie "Back to the future". I think it looks okay, but I did miss something to make it feel more authentic... That's why I reenacted a part of the last scene from the movie (poorly), just to add a bit more flair.
  5. Hi folks, I recently decided to do a circumnavigation of Duna by plane or helicopter. After many hours of testing, I finally came up with a compact helicopter that flew pretty darn well! Here are its specs: - Weight: 1.24 tonne - Top speed: ~75 m/s (65 m/s on average) - Kerbal capacity: 2 meat bags - Power consumption: ~2.5 Electrical untis/s - Max air time: infinite - KSP Version: 1.9.1 with breaking ground My goal was to circumnavigate Duna and get as much biome-science as possible. I didn't want to visit every biome, but only land on the ones that were along the path of the circumnavigation. Since Duna's circumference is ~2.000 km and my average speed was around 65 m/s, this mission would take me at least 8,5 hours. I believe I flew over 3.000 km in the end, but I wasn't able to record it properly, so I could be wrong. I made a time-lapse video of the mission. You can check it out in the link below (~7:00). Hope you liked it. Some highlights from the mission:
  6. I created a feedback report explaining the situation in detail.
  7. Boeing AH-64D Apache Longbow To control the heli, start by controlling the rotor collective with Translate U/D keys I and K. Then, set the throttle to slightly below 1/3. Parts: 351 Weight: 23t Length: 13.6m Top Speed: ~35m/s AH-64D on KerbalX
  8. So, I spent the afternoon building this: It's using two of the largest rotors in a contra-rotating arrangement, with four fuel cells as power. My problem is, it stubbornly refuses to leave the ground, at least without tipping over and ripping the rotor blades off. I suspect this is something to do with the contra-rotating rotors cancelling each others' motion out, but I'm not sure. Since I've seen a lot of successful helicopters being build since BG released, I'm asking the experts how to get my chopper into the air safely.
  9. I present my newest invention: Samson Mk 1.5! Inspired by the Samson Sa-2 from James Camerson's Avatar, this little helicopter is a vehicle of choice for the scouting parties both on Kerbin and other planets. Initially designed as a search-and-rescue craft by KAEC, which also made a combat prototype also known as "Samson 0", the KSCRD team upgraded it for exoplanet missions. It can carry up to 4 passengers (seats can be swapped for cargo holds), its engines can be easily tweaked for a thinner atmosphere, has an infinite range with the help of its 2 RTG generators, and thanks to its ability to fold the rotor blades, it can fit in the MK3 cargo bay, making it easy to transport. This craft has two modes: transit and lander (ACTION GROUP 5) Recommended engine speed for "lander" is 80%, for "transit" is 100% HOWEVER: before you fly the helicopter, make sure you have pressed ACTION GROUP 3 in order to make it work. It is highly recomended that you fly with SAS on, and that you take caution when performing maneuvers. Download from KerbalX (You need both expansions for this craft.) I am open for suggestions on how to improve the craft. If you feel there is something I really need to fix, please comment below and I will update the craft ASAP Known bugs: *Sometimes, when the craft is landed on a building, the lander legs clip through them when loaded FIXED *When opening the engines, there is a chance that one of them will go rogue. Revert to start/quickload to fix this.
  10. Hello everyone! I enjoy your interest in my previous craft Mi-26, so this community inspired me to create the second! Pretty small, stock and fun to play with! KSP 1.8 + BG 1.3 Specifications: No SAS, no reaction wheels and no RCS, only tiltable blades and several servos! Parts: 98 Crew: 1 or 2 kerbals. Possible to put up to 2 more seats, but it will nose dive almost everytime Mass: 1221 kg Main rotor diameter: 7.9 m (200 rpm) Lenght: 8 m Speed forward: 22-24 m/s Speed sideways: 17 m/s Climb rate: 5 m/s Flight time: up to 90 minutes Control groups: 1 - start/shutdown all systems. Throttle - main rotor pitch How to fly? I advise to use gamepad or some sort of controller to feel real cyctic control, but it possible to use keyboard. Set camera to locked behind tail, press 1, set throttle to 40 and wait 20 second. Then you can increase throttle, nice and easy, watching its positon, speed and forgeting about Z/X. As speed rises it will tends to climb and maybe roll left a bit. Once you reach medium speed it will feels like some sort of an airplane. Just watch a video below and you'll see. Have fun flying around! Craft file:
  11. Dear Kerbonauts, I am a long time KSP player but i had been gone for a while. I started playing again and became as fanatical as the first time i played. I intend to be more interactive, post stuff on the workshop, visit the KSP forums more often and i even started redditing and youtubing for the occasion. Recently i discovered the robotics. Awesome! I finaly made a functional helicopter. I Present to you: Mayakovski Helicopter: -10 person, main rotor-tail rotor configuration, lifting capable Helicopter. Flies great! Space: Toggle engine. R: Rotor brake. (Double tap to release first time. Only works when engine is engaged) Throttle: Lift. 1: toggle grapler and landing lights. I use Q/E for yaw and A/D for Roll, i dont know wether that causes issues for others. Part count: 57 Length: 15.5m Width: 13.3m Heigth: 3.7 Top speed: 50m/s Needs Making History and Breaking Ground DLC Side view: Front view: Youtube footage: Workshop page: Reddit post: ttps:// KerbalX Entry: Kind regards, Robdjee
  12. KSP 1.7.2(Now 1.7.3) and TweakScale used. I've played this game more than 3 years and that helicopter and it's swashplate are my best work. Almost 6 month ago I created a helicopter with Infernal Robotics and huge internal swashplate, but it was difficult to fly because of incremental control and some freezes of the game. Breaking Grounds inspired new life in this old vehicle... EY-30 It's kind of a semi-copy of Mi-26 Parts: 180-186 Main rotor diameter - 25.8 m (8 blades) 110-140 rpm Tail rotor diameter - 6.3 m (6 blades) 160-220 rpm Total Length - 33 m Dry weight - 29.1 ton Max takeoff weight - 40 ton Max speed - 50 m/s Max altitude - 5000 m Fuel - 134, oxidizer - 164(3 tons) Power exchange: Fuel+oxidizer --> generating electric energy --> battery --> rotations Consumption - about 0.03/s Controls: 1 - start engines Throttle - angle of blades and motor speed of main and tail rotor Q-E roll W-S pitch A-D turn Recomended to use joystick! Changes: 15.07.2019 - main rotor limit 150 rpm - tail rotor 180-210 rpm - max payload 9 tons, possible to lift above 500 m - increased strength of axles due to changes in 1.7.3, so maybe bigger helicopter comes next. 05.09.2019 - 5-bladed tail rotor - Improved swachplate - 2 KAL group controlles for main and tail rotor separatly(inside cargo bay) - 3 tiny J-20 on main rotor axis for sound and air flow imitation. (Squad, why robotic parts and air surfaces are completely silent?) 1.7.3 Craft file
  13. Here's my Mil Mi-24 Hind I made with the new breaking ground/1.7.3 parts, I hope you enjoy! Parts: 161 Weight: 21.613t Length: 18.8m Top Speed (asl): 50 m/s KerbalX Link Flight instructions notes First, start the Fuel cell with AG1 and turn on SAS. Next, the heli's rotors are the control point, so control the heli's vertical power with the rotor deploy angle (this control system is sensitive to changes). Set the throttle to roughly 30%, let the rotors spool up, and you're up! AG2 controls the juno engines in rotor assembly, and are used for higher straight line speed, and are not necessary to standard hover flight. My other russian aircraft replicas
  14. 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! ~ * ~ 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 -, GFDL 1.2, 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!
  15. I'm trying to build VTOL crafts using new helicopter blades from Breaking ground DLC. But always when I'm building it, these crafts start crazy rotation or even don't take off. I know that real helis requires propellers on a tail to kill rotation, but how the physics works in KSP?
  16. Hi all. It has been a while since I posted a craft, but Breaking Ground has brought me back from another hiatus. Today I present the Vertitrace three bladed helicopter. Essentially, I wanted to see if I could implement an R/C three channel helicopter design with the new Breaking Ground parts. As in real life, it was never meant to represent the most efficient or advanced use of helicopter technology. Rather, I was mainly just curious to see how it would work in Kerbal. As such, it is not fast and has a few quirks, but overall the craft can be said to be flyable. If you choose to download and try it out, keep in mind the following: -Rear rotor is bound to pitch axis. -Custom 1 cuts power to and brakes the rear rotor. You must do this if you intend to enter into a hover and/or land the craft. -Custom 2 enables motors with 100% torque. Throttle controls RPM only on main rotors. It is more stable when two small reaction wheels are added to the lower railings (line of fuel tanks that connect to the landing skids), but I wanted to build something that did not need wheels in order to fly. Here is a link to the .craft file for any interested parties: Vertitrace Thanks for reading! Please let me know if you have any questions. *Update: Custom 1 no longer has effect. Rear rotor rpm is tied to pitch. Old version had rpm and torque tied to pitch.
  17. 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: 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. -----------------------------------------------
  18. This post is to share some tips at improving the efficiency of turboshaft engines, driving propeller blades (airplanes) or rotor blades (helicopters). The concepts should apply equally to electric rotors driving propellers or heli-blades. I'm using 1.7.3, the electric rotors, turboshaft engines, and propeller/heli blades are new to stock KSP, so in later versions some of this info might become outdated. It's easy to focus on either the Turboshaft Engine, or the Prop/Heli blades when troubleshooting 'why doesn't my vessel work'. The reality is you need to look at both elements to make a functioning prop-airplane or helicopter. The engine produces torque, which spins a shaft. This is important, torque produces zero thrust. Add all the torque you want, it will not produce any thrust- until it is coupled to a lifting device, such as a propeller blade or heli blade. On the other hand, the prop/heli blade also produces no thrust unless it is moving. You can angle the blades any way you want, they will produce no thrust unless they are moving. The movement is provided by the Turboshaft Engine (or electric rotor). As of 1.7.3, the stock engines can rotate at a maximum rate of 460 rpm, which is evidently a Unity limitation. Adding torque will increase rotational speed (rpm) up to that limit of 460 rpm. What happens if you are already at 460 rpm, and increase torque? That's an important question. What happens (in 1.7.3) is you increase the Fuel Flow (or EC draw), but do not get any increase in rpm. Beyond 460 rpm, adding torque is simply wasting fuel. In the following examples, we're going to experiment with turboshaft engines. There are two variables we are going to adjust, and unfortunately they are on two different parts. One is the Torque of the Turboshaft Engine, the other is the Authority Limiter of the prop/heli blades. To make things easy, I like to assign these values to action groups. I assign Engine Torque to the Main Throttle, and the Blade Authority Limiter I assign to Translate Forward/Back (usually 'H' and 'N'). Okay, lets get started. Here's a turboshaft engine we're going to play with. It's in the 'propeller' configuration, but the idea is the same for helicopters. Ok, we have an engine built on a stand, let's play with it to see how Torque, Blade Authority, RPM, Fuel Flow, and Thrust are related. In the next spoiler window, I'll play with Torque and Blade Authority Limit, to see what happens to rpm and Fuel Flow. Keep in mind that Thrust is only dependent on rpm and blade angle. If my rpm and blade angle stay constant, but my Fuel Flow increases, I have not increased my thrust. I'm just wasting fuel at that point. So, one goal is to find the minimum Fuel Flow which will maintain a specific rpm at a specific blade angle. Here goes. In the next spoiler window, I'll demonstrate an actual aircraft, making adjustments to torque (and Prop Authority) to reduce fuel burn. Ideally I'd use a single-engine airplane to keep things simple. However, counter-acting the torque effects of a single-engine are difficult to design for, and fly efficiently. It's easier to just make a plane with two counter-rotating engines and propellers. Then, it flies quite easily just like a jet, with no nasty torque effects. The takeaway here is that to get the most out of the turboshaft engines and propeller or helicopter blades, you need to look at more than just the engine or just the blades. Both elements need to be adjusted for optimum performance. Ideally, you need to be able to adjust both Torque and Blade Authority Limit in flight, to adjust for varying conditions. Regarding efficiency, the big takeaway is that adding Torque beyond what is required to maintain rpm is just wasting fuel, and lots of it. As of 1.7.3, I believe the concept is the same for electric rotors driving propellers or heli blades- adding torque beyond what is required is only wasting EC.
  19. I'm creating a V-22 Osprey replica with the new robotic parts (incredibly original idea, I know). I am using the largest helicopter blades and the R7000 turboshaft engine. The vehicle lifts off fine, albeit with some help from vernor engines, but the second I enter it into "plane" mode the engines are massively too weak to propel it, capping at about 35m/s. The vehicle weighs 66,5 tonnes. Is there any way of improving the thrust/weight ratio without adding more rotor/jet engines? Why is it that they have enough power to lift the whole thing off the ground, but not to propel it? Since I'm new here and couldn't figure out how to insert images into my post, here's an imgur link:
  20. Hi folks, I'm new to the forum but playing for a while now but now I ran into something very weird. After I got Breaking Ground I started a new game and at some point I decided to make a helicopter/drone using the new motors I watched some tutorials and then tried to do my own but I ran into something I find very weird. As I increased the torque the propellers did spin faster but no lift, only a lot of vibration. I then opened the debug tools and enabled display of aero forces. The weird thing I noticed was that as the propellers were spinning the lifting force kept alternating up and down instead of only being up. At some point I got one that worked ok but no clue how to do it again or what's wrong. I tried with Elevon 5, FAT-455 Aeroplane Control Surface and even a few wings with the same thing happening Also how can I add screenshots on this forum? I only found a button to Insert image from URL Any help is greatly appreciated!
  21. Need More Rotors? Apart from Firespitter and KAX, I felt there wasn't enough rotarywing parts. This mod is my attempt to answer that. Introducing K.R.X. (Kerbal Rotor Expansion). DOWNLOAD From SpaceDock! Videos: Included in this release: Heron: coaxial rotor Sparrow: 3 blade rotor (left and right rotating versions) Osprey: 3 blade tilt-rotor style (left and right rotating versions) Seagull: 6 blade super heavy rotor Tail Rotors: 3 Blade, 6 Blade, and Fenestron Issues: Some tuning and balancing is still needed. Co-axial rotor (Heron) has a problem with one of the rotor switch/prop-blur, a limitation of firespitter. I'm working on a fix. Recommended Mods: Throttle Controlled Avionics: For single rotor use 'unbalanced thrust' on the main rotor and 'manual' on the tail rotor. For intermeshing, tandom, or quad, etc. configurations, use 'thrust'. Change Log: Version 0.31.1 Minor Update -Fixed Crash Tolerance on Fenestron tail rotor -Fixed Spelling Error on Osprey rotors -Increased torque compansation in Osprey rotors Version 0.31: -Added Fenestron tail rotor -Corrected the direction of the Osprey rotors -Increased the thrust of the Osprey rotors Version 0.30: Added 2 new tail rotors: -TR7 tail rotor to compliment the Sparrow main rotor. -TR24 tail rotor to compliment the Sea Gull main rotor. Added specially rigged gimbals to main rotors to emulate cyclic. Remodeled the Osprey rotors. Version 0.25: Initial release. Additional Credit: Snjo and RoverDude: for FireSpitter (*.dll Packaged with K.R.X.) Keptin: The sounds were made by Keptin (tweaked by me) and for much of the inspiration of this mod. This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.