MunGazer

Ok. And, sorry, but I also forgot to ask you the craft name? This is because of Section C., part 9. Also, I forgot at first but it can't qualify as a speed run unless there's a video for it (read main introduction). So until that point it'll just be a basic cert.

Lol, good job man. Before I list you, I just need to know if that was a speed run, or just a basic certification run?

Understood about the damage. Regarding engines clipping into structural components or fuel tanks, that's ok and is allowed by the rules. The only thing I don't want to see is engines clipping into each other. If they're on a stock bicoupler and just barely touching on the tippy tip tips that should be ok.

Very interesting creation/piece of art you have there. You definitely caught me off guard with the infinite fuel thing, I will have to go and specify that and also, I need to make a specific rule regarding heat. I'll just say whatever the default difficulty settings are in sand box mode are the only settings allowed. Unfortunately the F3 screen shows damage, even though it was at least 1 planck frame (lol) after you apparently landed on the admin pad, and for that reason I won't quite list it yet - but still, thanks for sharing and I look forward to any revisions. edit: oh, and it was also over 20 minutes, that exceeds the time limit, but with a tad of work and a little more finesse I'd think that you can make it. Does anyone know if the admin building has a weight limit and what it would be specifically? If known, I'll add that information in the challenge guidelines to prevent headaches. I acknowledge, however, that you possibly didn't mean it as a serious entry.

Awesome entry! Thanks. That is a really cool bird, extremely fast. I like the harrier style wing slope/droop, also very fitting name - it looks like a Kestrel. Reminds me of the wind guage logo. I will list it in just a moment. edit: also adjusted verbage ("or as an alternative to") to allow video submitters exemption from having to submit a slideshow.

Yes, as per Section A via Division 2 and Division 4. By "strange or rare mod" or "overpowered", what I mean by that for instance would be: a banana shaped engine with a banana texture that has a weight of 0 and 90,000,000 kg of thrust or something. Edit: Added the following to Section C. "10. To be more clear about certain mods that some of you might be interested in using, I'll do my best to explain this matter a little further. TweakScale is allowed and encouraged (as a Division 2 or 4 entrant craft) - for instance, if you can't fit two wheesleys into a bay without them clipping a noticeable amount, then you might reduce their scale by 10% or so using TweakScale. If you wanted to, you could have 8 tiny wheesleys crammed into a small bay thanks to TweakScale. Also, Infernal Robotics is allowed and encouraged. To reiterate, this would end up as a Division 2 or Division 4 entrant depending on your physics. Any popular mod that you find on, let's say, Kerbal Stuff for instance, should be ok to use. The thing is, there may be some fairly popular mods out there that might be horrendously overpowered for this challenge - perhaps ones that I was not aware of. My fear would be that a Kerbal or Kerbette would put together an absolutely amazing modded craft for Division 2 or Division 4, perform an absolutely mind blowing display of skill in a speed run, only to get 1 upped by some gate crashing fellow with a mod that's so overpowered that a significantly less amount of cumulative engineering and/or piloting skill is required. However, judging what is considered overpowered or not in these instances will inevitably be somewhat subjective. I just want to maximize the opportunities for creativity while still keeping things challenging and/or competitive. Hyper Edit is not allowed!"

Hahaha. You know, I just watched pandora's kitten's ambulance video and just about fell out of my chair when the 80's music kicked in - then you hit me with some Kenny Loggins' Danger Zone and another really cool VTOL bird. So much humor and cool engineering in one spot! I look forward to your entry.

Haaa cool man. I bet that is pretty awesome to watch in BD camera tools flyby mode. The way the main wing spans across the engine modules is really cool and original. And the way you angled those two heavy lift pods... the whole thing is just so unique, and yet so functional. Thanks for sharing, hope to see more. edit: subbed your channel bro

No probs.

Haha, alright man. That slide show was fun to look at; I need to go and change my rules to relax the number of screen shots allowed - it wasn't as bad as I thought looking at more than 7 and I was able to find the required ones easily. I must say that was a very interesting stock design - kind of reminds me of something from Star Wars with the catamaran fuselage style. As far as officially listing the entry, sheesh man I feel bad about not listing it but I have to maintain discipline with what I actually list to be fair to others. In fact, I think I'll relax the required maximum time a bit - not every VTOL will be able to do Mach 0.6 the entire way back and forth from the island. I'll meet you halfway on this one and set it to 20 minutes. EDIT: Done. The time limit was there to prevent extremely easy designs that are heavily weighted towards hovering and who are extremely slow at horizontal flight - but your craft, I think, set the bar a bit with a three to one vertical to horizontal engine ratio; I used it as somewhat of a guage to set the new limit so it won't be too restrictive on basic certification entrants. EDIT 2: bahaha, just realized you had two different crafts in your slideshow. Wow, I'm the observant one aren't I. I'm sure it wasn't intentional. Yeah one has the horizontally oriented engine under the vertical stabilizer and the other doesn't.

Alright, cool beans. Have fun and I look forward to enjoying your entry.

They will be acknowledged, just not as a 1st, 2nd, or 3rd place badge holder. But, I will make a compromise with you on this one - I'll adjust it to where you will be listed as a speed run entrant in first place with the tag [Tentative]. I just want those 1st, 2nd, or 3rd place badges to only be permanently held by people who actually placed as such against others, not just via no competition. I want those badges to be a bit more coveted, if you don't mind.

Lol, actually... those hangars on the island are pretty huge... and I think the admin helipad would still hold you. It's just the bigger your craft is, the less room for error there will be regarding clearance. I think you'll be ok

Oh, I must quickly warn you - the airfield hangar points of performance do not include landing in them - you must fly through them without touching the ground! See Section B., point 4. I'll add an addendum to it to help clarify. And thanks for attempting the challenge, by the way. This is my first challenge submission and I've actually been slowly working at preparing it for a few months. The rules are pretty thorough and verbose but bear with me on that, they're just there to preempt misunderstandings and hopefully, gatecrasher loopholes.

If you're referring to landing on the administration building helipad, yes, I'd say it's the hardest with my stock craft. I usually do a little better than in my demonstration video, where I was clearly struggling. I just didn't want to re capture the video and re sync the screen shots all over again. The stock craft I used in the video's main design problem is vertical speed change responsiveness. If you suddenly realize you're dropping too fast, sometimes it can be too late to recover with full throttle. Also, in the demonstration I made the piloting mistake of initiating the hover at too high an altitude, resulting in difficulty seeing the pad and a longer descent duration. Luckily, I was able to sort of wave off when I realized I was plummeting toward the edge, and managed to save the craft. Hopefully others can learn from my design and piloting mistakes . In other designs I've used "puffers" consisting of secondary smaller vertical thrusters which can be conveniently activated in small pulses to solve the problem of vertical speed responsiveness, and reaction wheels to help with better rotational control.

Welcome to the VTOL pilot skill challenge! This challenge is about demonstrating your proficiency and having fun with atmospheric VTOL craft in addition to your engineering abilities (in the event that you choose to design your own VTOL or use a prior design of your own for the challenge). You can either complete THE CERTIFICATION TEST using either your own VTOL or the one that I've provided below (craft name will be "Sample craft" for entrants using it) and submit the required screen shots to earn a basic certification badge, or you can submit a YouTube video that verifies your competitive speed run of the certification test if you would like to compete with other forum users based on fastest total mission time for the Gold (1st Place), Silver (2nd place), or Bronze (3rd place) VTOL speed run badges. https://www.dropbox.com/s/pcjae0mc5gby4tq/SampleVTOL.craft?dl=0 Note that this sample craft is made of stock parts and works with stock physics, and hasn't been tested in FAR. I have not yet used FAR. If you would like to submit a video with an entry that isn't a speed run, then you will be exempt from having to submit screenshots or a slide show. If you would like to weaponize your design, that's ok too, and you can show off the combat abilities of your craft if you'd like so long as the requirements are met for the certification or speed run. All visual mods, engineering tools, and pilot assist mods (including autopilot tools) that don't alter parts and physics are allowed. Mods that deal with different parts and/or physics are addressed in the rules that follow. Section A: Rules regarding mods: To make things fair for a reasonably diverse community of mod users, I will divide the entries up into separate divisions based on physics and parts. They are as follows: Division 1 - Physics: Stock only Parts: Stock only Division 2 - Physics: Stock only Parts: Mods allowed* Division 3 - Physics: FAR only Parts: Stock only Division 4 - Physics: FAR only Parts: Mods allowed* *Mods allowed within reason; no tampering with the config files of stock parts or mods made by others in such a way that the part would become different from another person using the same mod part or stock part without tampering with the config file. If a strange or rare mod appears and I decide it is overpowered, which will hopefully be a rare event, it could be rejected pending an investigation. Section B: THE CERTIFICATION TEST: Execute each of the following points of performance (in order) after spawning onto the KSC runway: 1. Take off vertically from the KSC runway. Provide a single screen shot for this showing that you are not touching the ground, altitude (ASL) is between 72 and 80 meters, heading (HDG) is between 60° and 120°, surface speed is not more than 5 m/s, and that the runway can be seen below. 2. Land on the Vehicle Assembly Building (VAB) helipad. Provide a single screen shot for this showing that your craft has exactly 0 m/s vertical speed, 0.0 m/s surface speed, and that you are in contact with the VAB helipad (at least one point of contact). 3. Take off vertically from the VAB helipad from the state you were in at the previous point of performance. Provide a single screen shot for this showing that you are not touching the helipad, altitude (ASL) is between 177 and 185 meters, surface speed is not more than 5 m/s, and that the helipad can be seen below. 4. Fly out to the island runway and fly inside of both of the two hangars, one after the other, in through one opening and out the other for each hangar, without touching anything other than air. You may not touch the island or anything on it at any point prior to, during, or after flying through the hangars. At this point there will be some reliance on the honor system for basic certification entrants who aren't required to submit a video. Provide a separate screen shot for both of the two hangars that you fly through, and in each of them, show that you are completely under the hangar's roof, and that you are not touching anything other than air. -addendum 1: You are not to land under the hangars! Sorry if that was confusing. You must essentially barn storm them, fly right through. -addendum 2: If you bump into something on the way through a hangar, yes, you may try to pass back through them again and your certification will still be valid as long as no damage was done to the craft and you make up for it with another pass through the hangar. 5. Proceed back from the island runway after completing the fourth point of performance and land on the administration building helipad (not the VAB!). Provide a single screen shot for this showing that your craft has exactly 0 m/s vertical speed, 0.0 m/s surface speed, and that you are in contact with the administration building helipad. 6. Provide an F3 results screen shot AFTER having taken the screen shot from the previous point of performance, since the results screen can block the view. Your results must show a total mission time of 20 minutes or less for basic certification. Section C. Additional rules/guidelines: 1. Yes, propeller and rotor craft are allowed, however, they cannot have a fixed main rotor or rotors. Thus, using real life rotor craft as an analogy, a Bell UH-1 or CH-47 helicopter would not be allowed, but a V-22 Osprey would. Gyrocopter style craft are not allowed, since the rotor that provides vertical lift is fixed (despite having a swash plate, control rods, flapping hinges, etc.). 2. Entries must be manned (at least one kerbal on board, even if only as a passenger), however, your craft can be kOS controlled and/or assisted if you'd like so long as a kerbal is onboard somewhere. kOS can be a powerful tool if you know how to code and I encourage you to use it if you want to. If not, then props to you for your manual piloting abilities or usage of other tools. 3. Regarding the required screen shots and videos, they can be from any angle or camera view as long as the required information is visible during execution of points of performance. Extra screen shots in addition to the seven required ones are allowed. Videos may optionally be edited to accelerate time and clip out portions of the flight outside of the points of performance - please try to only clip out the long trip over the water. Usage of the stock time warp function provided in the game is not allowed within video submissions. If any rule violations are made in an entry, I'll address it and allow for re-attempts if necessary. 4. If you don't have the ability to submit a video, but would like to make a speed run, please say so in your entry. If you would like to collaborate with someone to have them fly your design and/or make a video of it, that's fine, as long as the designer and pilot are both mentioned in the entry. 5. At least 3 speed run entrants must be made in a division before they will officially be awarded a medal badge. So, if you are the first speed run entrant in a division, you have to wait until two other speed run entrants arrive before you can claim your badge. However, if you are a speed run entrant before that point is reached, I will list you with the [Tentative] tag and then at least you'll be listed although you won't have your badge quite yet. Legit speed run entrants can claim their BASIC badge at any time if they would like. To simplify badge management for 1st, 2nd, or 3rd place speed run badge holders, if someone claims your title, it is entirely optional if you want to keep your badge. Earning it once is sufficient to keep it if you choose to. Entrants who lose their 3rd place title will be listed in the basic section instead. 6. If you are making a competition speed run, nothing on your craft can be damaged or break in your entry! This includes mere damage to components from heat and thrust from rockets or jets. However, if you are just going for basic certification, this rule is relaxed to allow for a wider variety of creative designs. Plus, it would be really painful to make a complete run only to find it didn't count at the end. 7. No part detachments, decouplings, separations, etc. are allowed; the part count of your craft must stay the same throughout the mission with the exception of weapon munitions being fired from the craft, which must not serve any overlap function as fuel used by the craft. 8. Part clipping: Wing blending for shape and appearance is fine. Absolutely zero clipping of engines with one another (not a single pixel) - however, you may blend them into fuel holding parts, wings, structural components, etc. but keep in mind the exhaust isn't permitted to damage anything. Please try not to obnoxiously overlap dedicated fuel tanks - but I understand that some overlap will be necessary for many designs. 9. Please state which division you are making your entry in, whether or not you're doing a speed run or basic certification, list any mods used (if Division 2 or 4), and (optionally) provide a name for your craft. 10. To be more clear about certain mods that some of you might be interested in using, I'll do my best to explain this matter a little further. TweakScale is allowed and encouraged (as a Division 2 or 4 entrant craft) - for instance, if you can't fit two wheesleys into a bay without them clipping a noticeable amount, then you might reduce their scale by 10% or so using TweakScale. If you wanted to, you could have 8 tiny wheesleys crammed into a small bay thanks to TweakScale. Also, Infernal Robotics is allowed and encouraged. To reiterate, this would end up as a Division 2 or Division 4 entrant depending on your physics. Any popular mod that you find on, let's say, Kerbal Stuff for instance, should be ok to use. The thing is, there may be some fairly popular mods out there that might be horrendously overpowered for this challenge - perhaps ones that I was not aware of. My fear would be that a Kerbal or Kerbette would put together an absolutely amazing modded craft for Division 2 or Division 4, perform an absolutely mind blowing display of skill in a speed run, only to get 1 upped by some gate crashing fellow with a mod that's so overpowered that a significantly less amount of cumulative engineering and/or piloting skill is required. However, judging what is considered overpowered or not in these instances will inevitably be somewhat subjective. I just want to maximize the opportunities for creativity while still keeping things challenging and/or competitive. Hyper Edit is not allowed! 11. Please use the settings at their default, especially regarding heat and fuel. No infinite fuel is allowed. Gatecrashing exhibitions are permitted for fun, but please mention that you're gatecrashing 12. Parachutes are not allowed for vertical landings, but you may use them to bleed off surface speed. Any parachutes used for that may only be used once per chute mounted. 13. Mods like Raster Prop Monitor and various cameras are allowed as a supplement to entries in any division to include stock. Section D: If you meet the basic requirements, you will be eligible for the VTOL signature badge shown here: If you made a successful speed run and achieved a 1st, 2nd, or 3rd place position, the corresponding badges are shown here: Division 1 Entrants: 1st place speed run: [Tentative] Submitter: Vegetal :Craft: Aero Lander :Time: 3 min 46 sec :Comment: Late for work? Try this. 2nd place speed run: [Tentative] Submitter: The_Rocketeer :Craft: Swift Mk.I :Time: 4 min 10 sec :Comment: The first contender to Vegetal's original entry. 3rd place speed run: Basic certs: [Former speed run] Submitter: Vegetal :Craft: Aero Lander :Time: 4 min 52 sec :Comment: This person means business! The Formula 1 of VTOLs. [Former speed run] Submitter: The_Rocketeer :Craft: Kestrel :Time: 5 min 9 sec :Comment: Kudos for being the first entry! Submitter: mattssheep4 :Craft: Hummingbird :Time: 15 min 43 sec :Comment: So far, the most cute & cuddly design. Submitter: rudi1291 :Craft: Dragonfly-V :Time: 18 min 20 sec :Comment: The Kerbin Highway Department has considered this design for a potential consumer flying car version. Submitter: tewpie :Craft: piefighter :Time: 12 min 47 sec :Comment: If a MiG-21 and a Tie Fighter had a baby... Submitter: FlipNascar :Craft: Butterfly Effect :Time: 12 min 42 sec :Comment: Silly butterflies. Why would you flap your wings when you could just use jet engines instead? Wake up evolution. Submitter: borbalf :Craft: ESE VTOL Talon II :Time: 13 min 10 sec :Comment: A Kerbal rescue ship? .. And they say that a hero can save us.. Submitter: Monsterlunch :Craft: Zepto-300 :Time: 33 min 12 sec (mishap) :Comment: How low can you go? Do the TWR Limbo! Submitter: Tellar :Craft: _____ :Time: 11 min 39 sec :Comment: Landing gear? Pfff. Bay doors. Helloooo? McFly? Submitter: goldenpeach :Craft: _____ :Time: 16 min 53 sec :Comment: Bob: "Val, I don't remember being able to see the parking lot from here..." Val: "Ohhh, uh. Yeah, I was just running a little test. Hold on." Submitter: burnoutforzai :Craft: _____ :Time: 6 min 26 sec :Comment: What happens when you strap a jet engine or two onto a dorito? Welp. It's fast. Division 2 Entrants: 1st place speed run: [Tentative] Submitter: Darren9 :Craft: SkyKar :Time: 8 min 30 sec :Comment: Our first VTOL music video, and it even synchronized with the heart stopping near collision (I'm betting intentional). 2nd place speed run: [Tentative] Submitter: SasquatchM :Craft: Ferret :Time: 10 min 55 sec :Comment: Textbook VTOL set up, very stable. The only VTOL I'd let my grandmother fly in! 3rd place speed run: Basic certs: Submitter: DirkLarien :Craft: Drake :Time: 9 min 0 sec :Comment: A well made transformer. Air brakes make wonderful feathers! Submitter: SuicidalInsanity :Craft: F-21 Faust :Time: 8 min 15 sec :Comment: Perhaps the best potential air superiority VTOL entrant so far? Division 3 Entrants: 1st place speed run: 2nd place speed run: 3rd place speed run: Basic certs: Division 4 Entrants: 1st place speed run: 2nd place speed run: 3rd place speed run: Basic certs: Submitter: Darren9 :Craft: Harrier :Time: 11 min 34 sec :Comment: The first IVA-only entry with a very impressive suite of instrumentation. Challenge submitter (me) demonstration video and screen shots: https://youtu.be/M3yUHEYEpbw http://imgur.com/a/DeMC5 Here is a good tutorial video by Scott Manley for VTOLs: VTOL flying tip in KSP: I highly recommend learning to fly your craft in the Camera LOCKED mode (cycle modes by pressing "V"), and learn to keep a close eye on your nav ball and prograde marker. For me, it's the only way I can fly and land with precision. Free and Chase camera view modes can be very disorienting.

I started watching that particular stream, first timer here and I must say in the 8:13 I already learned a lot about how to land more efficiently in vacuum, I really enjoyed the lesson up to that point and you are well spoken. I'll have to watch more of your stuff when my internet is working better - for some reason your vid kept stopping at 8:13 and I'm certain it's a problem on my end - you tube was doing the same thing to me a bit ago.

Hey guys, I've been googling this for a while and can't figure it out. I want to turn off the fuel flow for a specific part/tank on my ship. It keeps telling me :resources isn't the suffix to a part. I'm trying to set " mypart:resources:enable to false " or something along those lines. Could anyone just provide a quick line of example syntax/code that would accomplish this for a specific fuel tank on a ship? Not all of them, just the cruise missile it's carrying Edit: I've been informed that this particular fuel flow shut off for fuel tanks is not accessible via kOS. Sounds like an opportunity for a simple mod... if only I knew how to do it, I'd make it.

Good information, thanks. I totally respect that decision to keep people from getting in over their heads with kOS, and it probably does save the mod developers a ton of headaches. People will inevitably be snooping around doing all sorts of wacky things. kOS is just a really great concept however; it would be really cool if someday all the mods out there could be kOS friendly. I'd imagine there is definitely truth in what you're saying about not being able to cater to several hundred mods. Generally it would seem that they should come to kOS rather than vice versa. And I would hope not, but don't know, if maintaining kOS compatibility during the development of any mod would impose limitations to what those mods could do; my hope is that it would, instead, expand possibilities even if only through compatibility with other mods that are kOS friendly. I also understand that a re-write would possibly be in order for guys like baha to make it kOS compatible, and would sympathize if such an action would be deemed too much trouble to execute if the aforementioned issues weren't already enough to avoid it. I'm sure they have lives and I get to enjoy their work for free so I'll never complain. I just love so many of these mods and when I slap that little kOS CPU on to manipulate my stock parts, I can't help but wish I could program insane amounts of code for all the cool toys I have crammed onto my craft.

Thanks bahamuto, I appreciate it. I'll throw in this link and a bit of example code from there that may be relevant. In that example, I'm thinking the same could possibly be done with your parts. Seems to be a matter of accessing the module and then setting the appropriate field... which might be how I'd pass coordinate data to a sensor or gps, or instructions to weapons. Here's an excerpt from the kOS documentation page: [h=2]PartModules and the right-click menu:[/h]Each Part, in turn has a list of what are called PartModules on it. A PartModule is a collection of variables and executable program hooks that gives the part some of its behaviors and properties. Without a PartModule, a part is really nothing more than a passive bit of structure that has nothing more than a shape, a look, and a strength to it. Some of the parts in the “structure†tab of the parts bin, like pure I-beams and girders, are like this - they have no PartModules on them. But all of the interesting parts you might want to do something with will have a PartModule on them. Through PartModules, **kOS will now allow you to manipulate or query anything that any KSP programmer, stock or mod, has added to the rightclick menu**, or action group actions, for a part. This particular example is a little complex looking because they are doing something for all the chutes on the vessel, and some prior user defined variables had presumably been made. http://ksp-kos.github.io/KOS_DOC/general/parts_and_partmodules.html?highlight=partsdubbed // Change the altitude at which all the drouge chutes will deploy: FOR somechute IN somevessel:PARTSNAMED("parachuteDrogue") { somechute:GETMODULE("ModuleParachute"):SETFIELD("DEPLOYALTITUDE", 1500). }.

I'll explain more clearly, sorry. I am aware that you can slew the targeting pod to a certain position on the ground, and then send those coordinates to the GPS Coordinator and store coordinates that way which the targeting pod can be subsequently slewed to. The specific thing I'm curious about, however, is how I can use kOS to pass the same coordinate information to the GPS Coordinator and/or targeting pod from a script. This would be similar to how a pilot already has mission data loaded into his plane before taking off. However, if there's already a way to do this just let me know. I'm hoping that there's some link or somewhere that I can see all the bahamuto variables, commands, functions, etc. so that I can manipulate his parts in automation, but I'm not going to be pushy about it because ultimately he may not want to expose his intellectual property to that extent, which I'd totally understand.

Hey Bahamuto, first of all I just want to say thank you for this awesome mod. I have been having an enormous amount of fun with it. You must be a busy guy, and probably get bombarded with 8 million requests per second for features. I was an all stock guy but suddenly after playing with kOS I downloaded a BUNCH of mods - well, the ones that are high quality anyway. Let's just say some mods, I removed. I have a quick question - I'm wondering how I can integrate the usage of kOS with your parts. For instance, if I wanted to write a script in kOS that would automatically set the targeting pod to a particular geoposition. In my flight sim DCS, in the A-10C I can do something similar to that by slewing my TGP to a pre-loaded waypoint.

Thanks very much, I will try that. EDIT: I figured out what my problem was. I think I simply had accidentally installed an older BahaSP folder; so I downloaded what I thought was the newest one and replaced the one I had, and now it works . Great work Bahamuto. I don't know what kind of a crazy genius programmer you are, but your mod is the most fun I've had gaming or exercising my engineering interests in a long time.

Hey guys, I just got this mod (bahamuto adjustable landing gear) and I was hoping for a workaround if this has to do with version compatibility (I have 1.0.4). When I right click the landing gear, I only have a couple buttons including the angle indicator. Any suggestions as to how to access all the other adjustment functions would be appreciated.