Search the Community

This mod is being continued with permission from @DoctorDavinci Original thread here. I may be attempting to continue other parts of his work in the future. Enemy Mine Please Note that Enemy Mine requires BD Armory Continued v1.2.2.2a or better ... please install the appropriate version for your BDAc version See download links for dependencies posted below Adds Land Mines, Naval Mines, Depth Charges and Hedgehogs to KSP PLEASE NOTE: Land Mines are virtually invisible when deployed (95%opacity) as well as ALL MINES WILL GO OFF REGARDLESS OF TEAM - THEY ARE EQUAL OPPORTUNITY KILLERS Naval and Land Mines can be disarmed ... Land Mine Disarming requires the use of the Mine Detector KIS attachable item ... Do not move faster than 1.5 m/s or the mine will go off Land Mines are virtually invisible ... only way to find and disarm them after deployment is by using a Mine Detector Naval Mines have depth control ... Set the depth you wish them to sit at and they will automatically deploy themselves to that depth after being dropped Naval Mines can be disarmed in the same fashion as the Land Mines as well as being able to be set off via the use of DWI mine Removal Equipment DWI Mine Removal Equipment is used by attaching the "Ring of Death" to an aircraft and flying low across the water All models courtesy of @SpannerMonkey(smce) and are licensed All Rights Reserved Code Build Status License: GPL v3 License Dependencies - BDAc 1.2.2.2a and it's dependency Physics Range Extender NOTE: Only for BDAc 1.2.2.2 or higher! Enemy Mine v0.1.2.2 - Github Enemy Mine v0.1.2.2 - Dropbox

I have created a fresh new Topic to maintain BDAc continuity. For any past forum posts please refer to the Old BDAcTopic here: The old BDAc Forum Topic has been locked by the topic owner. Please note that Physics Range Extender and Module Manager are required dependencies for BD Armory Continued Also be advised that using the World Stabilizer mod will cause problems with PRE as it has it's own world stabilization code we refer to as Black Spell ... Only solution to this is to not use the World Stabilizer mod ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ BD Armory wiki: http://bdarmory.wikia.com/wiki/BDArmory_Wikia BDAc Release Links: Releases link: https://github.com/PapaJoesSoup/BDArmory/releases Issues link: https://github.com/PapaJoesSoup/BDArmory/issues Physics Range Extender (REQUIRED): https://github.com/jrodrigv/PhysicsRangeExtender/releases Papa Joe's Soup Github link: https://github.com/PapaJoesSoup?tab=repositories ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ PUBLIC SERVICE ANNOUNCEMENTS: Importing craft that are armed into the new BDAc is going to mess with the weapons as the craft file that has been saved will have values in it that are no longer in BDAc as well as not having the new variables that are in BDAc The current release of BDAc is a maintenance release, and only KSP compatibility updates will be performed going forward. The Mod is NOT dead, though, as others have taken the reigns of keeping BDA alive and well. with that said: Please Check out the New BDA+ NOTE. BDA for Runway Project (now BDA+) is a separate fork by Brett Ryland and others. New forum Post for BDA+ is here: ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ TL;DR - DO NOT IMPORT OLDER CRAFT WITH WEAPONS ON THEM FROM VERSIONS OF BDAc PRIOR TO THE ONE YOU ARE INSTALLING ..... REMOVE ALL BDAc AND BDAc ADDON PARTS AND THEN IMPORT YOUR CRAFT See spoilers below for release notes, videos, Github issues and download links The BDAc family of mods were all created by @BahamutoD, and in his absence, we have taken it upon ourselves to keep the explosions flowing For anything related to BDAc or mods in the BDAc family, I refer you to the Github link for Papa Joe's Soup (Slightly Over Used Parts) where there is listed download links for the mods in question ... If you have questions or concerns, feel free to post here and the team will do our best to assist you I also refer you to our in game KSPedia where you will find a wealth of information on the operation of BDAc Be aware that forcing opengl will result in many shaders showing as pink ... the only solution is DO NOT force opengl If you think you have come across a gremlin or a bug with BDAc or any of the mods we maintain, feel free to post here, however we ask that you also take a look at the issues list on Github to see if your problem has been addressed. We use the built in Github issues tracker to keep record of bugs, enhancements and feature requests as it is difficult to keep track of bug reports and all the great ideas that the community have come up with on the forum (things can get buried and lost under newer posts) Please note that only the most recent version of BDAc is supported at this time and that BDA needs PhysicsRangeExtender to work properly: https://github.com/jrodrigv/PhysicsRangeExtender/releases Also, to correctly install BDAc, first download the latest release from the BDAc releases link posted below (not the source download) and then extract the BDArmory folder contained within the zip file and place it into your KSP/Gamedata folder ... Do not, I repeat, do not place the Gamedata folder contained within the BDAc zip into your Gamedata folder as this will cause umpteen million conflicts to arise as the BahaTurret pickle looks for textures, configs and whatnot in specific places In regards to CKAN ... It is our policy not to provide support for CKAN as we have no control over the process beyond listing when deploying to SpaceDock. If you are having issues with CKAN we request that you take it up with CKAN, otherwise follow the clear instructions posted above and if your issue continues then feel free to ask the team for assistance In regards to support, KSP.log please (Found in the same directory as the KSP executable ... this file is overwritten each time you start KSP ... upload this file to a filesharing site such as dropbox and post the link so the team can take a look) ... I also refer you to the following thread where it describes in detail everything else that is required for us to help you: Best Regards, The BDAc Team @Papa_Joe @jrodriguez @SpannerMonkey(smce) @gomker @TheDog @DoctorDavinci @Eidahlil @TheKurgan BDAc Release Notes (latest only): BDAc Development Timelapse: Just a little video that @jrodriguez put together to show the development of BDA from its modest beginnings to around April of 2018. We thought you might like to see it: BDAc Family Mod links: BDMk22 Plugin Releases link: https://github.com/PapaJoesSoup/BDMk22Plugin/releases Issues link: https://github.com/PapaJoesSoup/BDMk22Plugin/issues Burn Together Releases link: https://github.com/PapaJoesSoup/BurnTogether/releases Issues link: https://github.com/PapaJoesSoup/BurnTogether/issues Camera Tools Releases link: https://github.com/jrodrigv/CameraTools/releases Issues link: https://github.com/jrodrigv/CameraTools/issues Destruction Effects Forum link: http://forum.kerbalspaceprogram.com/index.php?/topic/154379-12x-destruction-effects-v130-010217/&page=1 Releases link: https://github.com/jrodrigv/DestructionEffects/releases Issues link: https://github.com/jrodrigv/DestructionEffects/issues Improved Chase Camera Forum link : https://forum.kerbalspaceprogram.com/index.php?/topic/173436-14x-improved-chase-camera-v162-apr-02-2018/ Releases link: https://github.com/PapaJoesSoup/ImprovedChaseCamera/releases Issues link: https://github.com/PapaJoesSoup/ImprovedChaseCamera/issues Vessel Mover Continued Forum link: http://forum.kerbalspaceprogram.com/index.php?/topic/144421-12-vesselmover-continued-v1513/& Releases link: https://github.com/PapaJoesSoup/VesselMover/releases Issues link: https://github.com/PapaJoesSoup/VesselMover/issues Vessel Switcher has been incorporated into BD Armory Continued In regards to Adjustable Landing Gear, please consult the Kerbal Foundries Continued thread where @Shadowmage has taken it upon himself to maintain an ALG-like addition to KF Continued ... his thread can be found at the following link: http://forum.kerbalspaceprogram.com/index.php?/topic/155056-122-kerbal-foundries-continued-tracks-wheels-and-gear-02-05-17/&page=1 Videos: Physic Range Extender: Guard Mode and Wing Commander: Modular Missiles: Sonar and Torpedoes: Missiles - Cruise and Terminal Guidance BD Armory was originally developed by Paolo Encarnacion (BahamutoD) and distributed under the license CC-BY-SA 2.0. BahamutoD has moved on to creating VTOL VR, found on Steam. Go check it out! This mod is now called BD Armory Continued, and is being maintained in BahamutoD's absence by the BDAc team. It continues to be distributed under the license CC-BY-SA 2.0. Please read about the license at https://creativecommons.org/licenses/by-sa/2.0/before attempting to modify and redistribute it BD Armory Continued contains code based off of Aircraft Carrier Accessories and is used with permission (https://forum.kerbalspaceprogram.com/index.php?/topic/152916-14xaircraft-carrier-accessories/) ... Courtesy of @flywlyx BD Armory Continued also contains code based off of Firespitter. To comply with the requirements of Firespitters' license, the following permission notice, applicable to those parts of the code only, is included below: License: You may reuse code and textures from this mod, as long as you give credit in the download file and on the download post/page. Reuse of models with permission. No reselling. No redistribution of the whole pack without permission. UV map texture guides are included so you can re-skin to your liking. For reuse of the plugin, please either direct people to download the dll from my official release, OR recompile the wanted partmodule/class with a new class name to avoid conflicts. https://github.com/snjo/Firespitter

I think it would be pretty cool if there was a plugin to integrate BDArmory modules such as the targeting cam and radars to be displayed in RPM or ASET MFDs, like using the targeting cam through an MFD and displaying radar information and locking targets on it. Weapons display would also be cool. Instead of a plugin that alters the functionality of the current MFDs added by the aforementioned mod, a separate MFD prop that could do all described above would work, too. This is what I'm looking for. I do not know how to do this myself as I only make models. This could be very useful for me as I'm currently working on a realistic A-10 Thunderbolt model with detailed internals.

So... I got bored again. This time, I made an anti ship missile. With terminal Proportional Navigation capabilities, it is able to engage moving surface targets (since it flies really fast, it can also double as an anti air missile). Here's a boring video of me destroying a ship made with a bunch of fuel tanks. Here's a video of the same missile shooting down a plane.

By trial, error, and advice from others, I have learned alot about building competitive BDArmory Fighter aircraft. Because of the growing number of people interested in making competitive aircraft, but do not have the knowledge how, I am making this guide on how to make competitive BDArmory Fighter aircraft. Feel free to suggest additions, and to share your advice. This guide will be divided into two parts: physical design tips, and AI tuning/weapons selection tips. According to @Box of Stardust, an experienced designer on the forums, making a good fighter plane is "25% airframe, 30% weapons and utilization, and 45% AI tuning." Also, keep in mind these characteristics, suggested by @Box of Stardust. These characteristics are the main traits that define an airplanes strengths, weaknesses, and performance. Maneuverability: Maneuverability of an aircraft. Aside from general control authority, it also includes the ability to perform extreme dogfighting maneuvers, which may be influenced by factors such as thrust. Propulsion: Acceleration and speed of an aircraft. High thrust-to-weight is good, but can also be influenced by aerodynamics; know the ins-and-outs of the KSP aerodynamics system to help create less draggy aircraft. Endurance: Time an aircraft can remain in combat before running out of fuel. 15 minutes dry thrust according to KER readout is the lower bound I recommend. Size: Size and form factor of an aircraft. Influences ability to avoid damage, due to being a harder-to-hit target, as well as smaller radar cross section. Damage Mitigation: Ability to take damage and remain combat effective. To clarify: not simply surviving damage, but remaining able to fly effectively despite the damage and not be locked into basic defensive actions only, and if possible, continue fighting. Structural durability comes into play greatly. Offensive Capabilities: Aircraft armament and the effectiveness of the utilization of the weapons (weapon ranges and such). Flight Control: Ability of the AI tuning to both push an aircraft to its maneuvering limits and maintain stability and directional control. The AI must be able to perform extreme dogfighting maneuvers, evade incoming fire, pursue enemy aircraft, and be accurate when firing on a target. Additionally, the ability for the AI to accomplish this despite the aircraft having taken damage. (Note: this has become increasingly harder to judge with BDA 1.2.) Now, we will start with the structural/aerodynamic construction: 1. Never use manned aircraft, unless required by competition rules. And if possible, use lawn ch- err, command seats. Command modules weigh almost a ton, and increase the size(and thus, radar cross section (RCS), and more area for the enemy guns to aim for). Additionally, avoid Mk1 (1.25m) parts. They again add unnecessary size. 2. Aim for about 300 units of liquid fuel. Again, you should get your fuel from sources other than 1.25m parts. The Big-S wing strake can hold 100 units each and, combined with 2 Mk0 liquid fuel tanks, provides you with enough liquid fuel to provide sufficient endurance. 3. Do not use the stock panther engine. Use the AirplanePlus tiger 0.625m engine. It offers greater thrust for the weight, and generates much more electric charge than the Panthers for its thrust. Additionally, the tiger runs at a "cool" temperature for the thrust, allowing the shortest AIM-9 lock range of any afterburner(AB)capable engine, approximately 2.8 km in non AB mode, with a low throttle setting, compared to just over 3km for the panther. Although 0.2 km might not sound that much of a difference, it is, when you take into account the near-mach 2 closing speeds. Just that little distance may allow you to fire your AIM-9s and cause the enemy to dodge before firing theirs. 4. Design your airplane for maximum battle durability. Avoid attaching multiple wings to each other, instead, attach all wings to a hidden structural part, like a structural I beam inside Big-S wing strakes. Ideally, any one part exploding shouldn't have any affect on the others. However, this normally isn't possible. And since BDA 1.1/2, hidden parts wont receive damage until the part covering it explodes, (unless you got an armor penetrating shell). So, you attach all wings to this hidden part, to ensure maximum battle durability. Additionally, place wings close to the fuselage(e.g, small wingspan), and if competition rules allow, clip wings close to the center. This insures that most lift is coming from the center of the airplane. Thus, the plane wont spiral out of control when a wing is lost. (FYI, lift from the body/fuselage IRL is called "body lift". This is what allowed that Israeli F-15 to land on 1 wing. The F-15s body generates a good amount of lift) Now we will discuss aerodynamics, and making the best plane aerodynamically. 1. More wings almost never hurts. Turn rate is 85% determined by wing loading (which is the amount of lift each square unit of wing has to produce in order for lift to equal the weight of the aircraft). More wing area means less lift each square needs to produce to equal the aircrafts weight. Thus, the lower the wing loading, the more excess lift is available. More excess lift means that you can turn with less Angle of Attack (AoA), meaning less drag. Less drag means less thrust is needed, which also means less fuel can be carried. That means less weight. And weight is probably any aircraft designers worst enemy. Alternatively, the reduction in drag can also be utilized to improve energy retention, the greatest advantage in a dogfight. Overall, high lift is key to a high maneuverability aircraft, and gives you a significant edge over opponents without this knowledge. The question is, how much wing is ideal for an aircraft? After all, wings do weigh, and too many wings induces unnecessary drag. From my designs, I have found that around 1.2 to 1.4 units of wing area per ton is ideal. Anything under 0.9 is insufficient lift, and over 1.7 produces excessive drag. And, like stated in the structural section, moving wings inwards, and clipping wings near the middle are ideal, because if the lift is coming very close from the lateral center, the loss of a wing will not severely affect flight performance. TL; DR: you should aim for about 1.2-1.4 units of wing area per ton of aircraft to maximize excess lift, and to minimize excessive drag. 2. If maneuverability is 85% wing loading, whats the remaining 15%? Thrust to Weight radio (TWR). Why does TWR have anything to do with maneuverability? Because even the most perfectly designed wing produces drag while turning. And slowing down reduces your turn rate. Thus, to keep up energy, you need thrust. Practically, your craft will weigh about 6.5-8.5t loaded, depending on the amount of guns, ammo, fuel, missiles, etc. Anything above 8.5t is generally a bit to heavy for ideal performance. And its very hard to make a well-designed aircraft under 6.5t. If the craft weights over 7.5t, use 7-8 Tiger engines. If under 7.5t, use about 5-6 tiger engines. Optimal numbers may vary depending on other factors (mainly drag and wing loading). 3. Place elevators as far back as possible. This maximizes pitch authority, which (as we will see later) allows you to decrease control deflection, which is key to providing ideal response time. Also, 4-6 reaction wheels are ideal. 4. Place the center of lift(CoL)just behing the center of gravity(CoG). Ideally, the center of the CoL sphere should be halfway between the center and outer edge of the CoG sphere, or maybe maybe a tad bit closer to the CoG, depending on your plane design. 5. This tip (first suggested by @goduranus) is a poorly known (and counter-intuitive) one, but can greatly increase responsiveness. This is the theory behind this tip: all control surfaces on an aircraft should be able to respond to an full input in 0.3 seconds. In other words, the control surface should have no more than 0.3 second "lag time" from center to max allowable deflection. Unfortunately, most control surfaces default deflection values provide lag time in excess of 0.5 seconds, some approaching 1 second. To counter this, you reduce the max deflection untill an 0.3 second lag time is achieved. To calculate the exact number for the max deflection, you multiply the control surfaces actuator speed in degrees per second (found by right-clicking the part) by 0.3. Then, divide this by the maximum deflection in degrees (found next to the actuator speed). Multiply the result by 100, and that number shoud be your max deflection. Very few surfaces (namely, the advanced canard) can be left at 100 and still meet the 0.3 sec limit, and none can be increased to 150. This is why you want your elevators as far back as possible(to maximize control authority) and a CoL just behind the CoG(to minimize resistance to pitch up). 6. Choose the right control surfaces! In order to get maximum deflection, but still remain in the 0.3 sec timeframe, you want the maximum actuator speed. Note that this tip isn't very critical, especially if your plane is well designed. Also, having a bigger control surface with slightly slower actuator speed is better than a smaller surface with a faster speed. This is why the best control surface IMHO is the Big-S type 1. It combines ideal size with sufficient speed. And the best canard IMHO is (not surprisingly) the advanced canard. When more size is needed, use the standard canard. This concludes the aircraft design section. The next part of this guide covers proper selection and tuning of BDArmory weapons, countermeasures, and sensors. It also covers tuning the weapons manager settings. 1. Don't use radar. Its simply dead weight right now. The most competitive drones have such a low Radar Cross Section (RCS), that trying to lock on them is virtually impossible, especially when they have jammers. Besides, they can dodge AMRAAM's easily anyway. So just don't use radar. Unless you're in a competition that requires one. 2. Spam sidewinders! Since the BDA 1.1 update, planes have gotten much more damage-resistant. Meaning a single sidewinder wont do much to a well-designed aircraft. Actually, many planes can take multiple missile hits and fight as if nothing happened. So you need a lot of sidewinders. Ideally between 8 and 12. And you want the weapons manager to fire 2 at a time, but we will discuss that later. 2. Don't gun spam. Prior to BDA 1.1, when heat was used to determine damage, planes were not very damage-tolerant. That's when the idea of gun spamming in the merge was invented with @Eidahlil's Cookie. A "flying ceiling fan" with 8 GAU-8 cannons. It basically hovered while rotating to aim at you. Unfortunately, this didn't work well, due to the fact that it can't dogfight. Soon afterwards, I was trying to make an ultimate dogfighter, but ended up with one of the most hated planes in the ASC competition. The Du-3. Basically, it was a guns-only airplane with 5 vulcans, a low top speed(to reduce IR signature), and very manuverable. Unknowingly, the decision to make it guns only is what gave it its formidable reputation. Here is why: because it came in slowly(~210 m/s), the engine was on very low throttle. Thus an IR lock would be achieved at just under 3km. Now, when the AI has a missile lock, it doesn't fire immediately, which is simply how the AI works. Then, people left their guns range at 2.5km (a big no-no today). Before the AI could fire its sidewinder, it reached gun range. And there is about a 0.5-1 second lag when switching weapons. The Du-3 never had to switch between weapons, meaning it sent a hailstorm of 20mm bullets downrange immediately at 2.5 km. The other airplanes, because of the lag, didn't start firing until ~2km or less. Thats over a half kilometer. Often, before they could evem return fire, the Du-3s would already have destroyed one of the enemies. Thus, when fighting a Du-3, you were basically guaranteed to loose a plane or two (sometimes all 3) in the head on pass. Numerous other aircraft (@dundun93's TFD 2.1 with 16 Vulcans, @Box of Stardust's Basillisk with 6 Vulcans and Flying Gunbrick with 10) followed this tactic, with great success, until the BDA 1.1 update. And thats when gun spam because impractical. Because of planes increased damage tolerance, it is rare to get enemies in the merge. And guns/ammo are heavy. Thus, carrying around all those guns and reduced maneuverability. Now, this has always been true, but previously, you could turn a 3v3 into a 3v1 just with the merge. Now, you need to dogfight to get enemies. And gun spammers are normally less-than-ideal dogfighters. Additionally, some new methods eliminate the merge all together, namely the Pre-Routing device(PRD), and certain weapons manager tweaks. We will discuss both soon. TL;DR. Gun spamming used to be a viable tactic, but isn't anymore. You want no less than 3, but no more than 6 Vulcans. And 4 ammo boxes is perfect. Also, pressing F2 in the SPH will show you how your guns are aimed, e.g, converging, diverging, how far away they converge. 3. Set your Vulcans max engagament range to under 1.3km. Also, set the gun range on the weapons manager (by right-clicking it) to just over the number you choose for your Vulcans. This is why: in the ASC challenge, it was noticed that planes were not using their sidewinders. This is because of the 2.5km gun range. And after the merge, airplanes are pretty close together. Normally closer than 2.5km. Thus, when enemy planes were extending to ~2 km and turning around, a perfect AIM-9 shot, the planes were wasting ammo on hopeless long-range vulcan shots, instead of properly used the AIM-9s. Thus, @box of stardust started the trend of reducing gun range to force planes to utilize their AIM-9s. Although reducing Vulcan range seems counter-intuitive, you have to think like this: at 2 km, which is more effective: Vulcan fire, or AIM-9s? At 1.5km? 1.25km? Generally, over 1.3km, AIM-9s are more effective than cannon, especially if fired two at a time. Under 1km, Vulcan fire is the most effective. The exact number between these two varies. For example, if your plane has a limited number of AIM-9s, or your plane can exceptionally aim long range gunfire, you might want a value on the high end, maybe 1.25km. Alternatively, if your plane runs out of ammo quickly, you would want a lower value. Maybe 1km. I personally choose about 1.0-1.1 km. Note: I know I didn't quite to the best job explaining this, so maybe someone could come up with a simpler explanation? 4. Fire two at a time! In the weapons manager, by right-clicking on the part, set the missiles per target to 2. That way, it fires two AIM-9s at a time. 1 AIM-9 at a time is not enough to do any significant damage in the latest BDA(also, it means you only have to dodge half as many missiles), and 3 depletes your missiles too quickly. 5. Set your intervals properly. In the weapons manager settings, put the "firing interval" at 1, and the "burst length" at 0. You want the plane to fire guns in short intervals, with short breaks inbetween, not continually. This ensures that less ammo is wasted, while keeping effectiveness. In my testing, non-continuous fire is just as effective as continuous fire. 6. In order to avoid your missiles colliding with you at seperation, shorten the, missile rails as much as possible. Additionally, you want forward jettisoning missiles. By default, its on lateral, or downwards ejection. Right-click on the AIM-9, and set the drop time to zero, decouple speed to 10, and forward firing, not lateral. Also, set the max engagement range to about 4-4.5 km. This is to avoid the missile exploding immediately after launch due to the loss of a long-range lock. 7. Use a PRD! A PRD, Pre-Routing device, works by firing a missile without a lock. This missile will trigger the enemies RWR, and cause them to dodge, but the missile doesn't have a lock. Meaning you can avoid merges by firing a PRD just prior to the merge. The only stock missile that will work is the RBS-15 cruise missile. Set its max engagement range to about 4-7km (experiment to see what works best). Also, set it to engage air targets only. It will fire the missile at the set range, and the enemies will respond as if it was a guided missile. There are more complicated PRD's, that fire unguided sidewinders/AMRAAMs, using some modular missile guide programming. But the RBS-15 PRD should be just fine. Additionally, the more complicated PRD's require decouplers(which are banned in some challenges), unlike the RBS-15 one, which doesn't need any decouplers. Just the missile rail. I reccomended you place the PRD on the belly of the airplane. Not on the top. 8. Always have at least 4 flare boxes, and at least 2 chaff boxes. Use ECM only if necessary. Normally, a PRD will stop AMRAAM shots by causing the enemies to dodge before they can fire their AMRAAMS at you. This is because most competitive drones have very small frontal RCS, meaning AMRAAMs lock at about 3-4 km. A little after your PRD should fire. If you use jammers, set them to activate with the gear action group. Don't use toggle, use activate. And, angle 2 of your your flare boxes at 45° angle backwards. And all of the flare boxes should have an eject speed of 30. Lastly, we will cover tuning the AI, probably the most important part of designing any BDArmory aircraft. 1. Leave the Pitck Ki on 5, and Max G/Max AoA on the maximum allowable values. Default and minimum altitudes: the default altitude can be kept as it, though setting it a bit higher can be advantageous in a dogfight. The minimum altitude should be put at 300 for a plane designed by these tips. Then, if you notice the plane crashing into the ground abnormally, raise it to 400. Steer Factor: steer factor is a multiplier that determines how much control input is used to turn the airplane. Higher values mean larger inputs for a given turn. (Here is a simplified example(not using the actual values): with steer factor at, say, 5, it will turn with 50% input for a target 30° above it. Put it at 10, and it uses full input). In order to properly set it, I highly reccomended you fly the finished plane by hand. That way, you have a general sense of what the capabilities of the airplane are. If you notice that the plane isn't turning fast enough, increase the steer factor. Alternatively, if the plane is turning too sharply, and bleeding airspeed unnecessarily, reduce the steer factor. Steer damping: the easiest way to adjust steer damping is this: place a stationary target with a weapons manager on the grass by the runway. Next, launch your craft. Temporarily set its guns to engage ground targets. Now, put the airplane and stationary target on different teams, and battle! While the plane is firing at the target, look to see how steady it is flying. If it is oscillating/wobbling in pitch/roll/yaw, increase the damping. If it appears to be steady, decrease the steer damping as much as possible while still being steady. You want the lowest steer damping value that provides stability, as excessive damping negatively affects turn performance. Min Combat speed should be set to around 40. So should the takeoff speed. Idle speed can be left as is, although increasing it to 200 never hurts. Max speed can be left as is, or maybe lowered to about 300. But never increase it. You dont want your plane merging with full afterburner, do you? BTW, here is a design that utilizes the tactics suggested in this guide, except the PRD, which didn't seem to help this design. the updated version has a MLRS. https://kerbalx.com/dundun92/Du-11 Updated version: https://kerbalx.com/dundun92/Du-11B-Blk-10  

So I got bored one day, and I decided to build a ballistic missile in KSP. Then I decided to build an anti ballistic missile in KSP. Mods used in this video include Vessel Mover, BDarmory, Trajectories, Physics Range Extender, Sounding Rocket parts pack, Kerbal Engineer ... and some more. Here's an unedited video of the missiles in action.

I'm running the latest version of KSP on linux along with BDArmory and the required module manager and physics range extender. When I play with the mod in game (such as dropping bombs or launching missiles), they just bounce harmlessly off the ground without exploding. This also happens when anything else hits the ground, whether it is debris or an entire plane; they bounce of the ground with no damage or explosions. I'm pretty sure I installed the mods correctly, putting the BD Armory, physics range extender, and the module manager files/folders all inside the gamedata folder. Nothing else seems wrong with the game except for that. Any suggestions for a fix?

Post here any picture of any jet fighter of yours!

Can someone help me spawn military vehicles controlled by AI in random locations so as to create a military campaign? The idea is to place military units like mission markers n u need to engage them there.

I have installed BDarmory with PhysicsRangeExtender and when i open up the GUI it says in red text module manager is misssing. BDA will not work properly. and it doesn't. all the parts are there the tracking works fine but the weapons wont damage other vehicles. so i installled module manager 3.0.6 and it did nothing.

I just downloaded bd armory (and yes i have the newest one) and i aldready have a problem. My weapons manager says i have no weapons even tho i obviously have. I have googled it for like 30 min and i can't seem to find an answer.

Hello all! Recently I installed BDAc and when I install two or more different types of machine gun class weapons (i.e. .50 cal and Vulcan) I can fire the first, switch to the second fire it as well but when I switch back to the first it will only fire one round and not work after that. Does anyone have any ideas what might cause this or is there a better thread for this type of issue?

Hello all! Recently I installed BDAc and when I install two or more different types of machine gun class weapons (i.e. .50 cal and Vulcan) I can fire the first, switch to the second fire it as well but when I switch back to the first it will only fire one round and not work after that. Does anyone have any ideas what might cause this or is there a better thread for this type of issue?

In order to train the new KAF pilots, you have been contracted to make an aggressor fighter jet. The competition for the contract is fierce. Can yours stay at the top? This is a BDArmory fighter competition. RULES: 1. The battles are run King Of The Hill style. You fight the 5th place aircraft, and work your way up the leaderboard. 1.1. There are 5 maintained spots on the leaderboard. 1.2. Fights are 3v3 matches, best out of 3. 2. No space-grade parts permitted (oxidizer, monoprop, rockets, non-cockpit reaction wheels, ISRU, etc). 2. Ore is allowed for ballast purposes only. 3. No drones (or lawn chairs). 4. Armor thickness must be left at the default value. 5. No unreasonable part clipping 6. 75 part count limit(may be raised later to 85 if necessary) 7. No decouplers/multi-staging (this is a plane, not a rocket!) 8. Up to 2 Vulcan hidden 20mm cannons, 1 GAU-8, 6 Browning AN/M2 .50 cal, or 2 M230s (locked in forward position) 8.1. No turrets (unless locked in forward position). 8.2. No mixing different types of guns. 9. Up to 6 AIM-9 "Sidewinder" missiles. 9.1. AIM-9s are the only missiles allowed. 10. Up to 4 flare boxes 11. Your plane must fall under 1 of two categories: light and heavy fighters. 11.1. Your plane (light or heavy) has a two engine limit. 11.2. Thrust is calculated with the engine on AB (if applicable). 12. Light fighters must weigh at least 6t at combat weight. 12.1. Light fighters can have up to 250kn of static thrust, and at least 400 units of liquid fuel. 13. Heavy fighters weigh at least 12t at combat weight. 13.1. Heavy fighters can have up to 500kn of static thrust, and at least 800 units of liquid fuel. 14. Editing of the craft outside of the game (e.g, text editing in notepad) is ABSOLUTELY prohibited. (Looking at you @Eidahlil) 15. BDA 1.1, and KSP 1.3.1 is used. 15.1. We will use 1.4.x as soon as BDArmory is ready . 15.2. AirplanePlus and BDArmory (duh!) are the only allowed mods. 16. Have fun! 17. If you have any questions, ask me (@dundun92). PLANES IN TESTING: [none yet] LEADERBOARD: 1. 2. 3. 4. 5.

I am having problems getting NKD and BDARMORY explosions to show up. I'll show you an image of my gamedata. P L E A S E H E L P M E. GAME DATA: https://imgur.com/CospfaQ

For about a year now I've been looking a mod to give space ship/fighters "combat AI" to move ships around, turn guns to face and to dodge incoming fire. Are there any fighter/ship AIs out yet for use with BDA these days?

All the bdarmory parts show up and do work, but when i click the bdarmory icon in flight, the weapon manager GUI doesn't show up. can anyone help me with fixing this?

For those that struggle with finding that perfect part or put together that perfect fighter fuselage, this is the mod for you. Brought to you by SM Associates @XOC2008 and @TheKurgan (with some excellent modelling by @SpannerMonkey(smce)!), we bring you Versus! Versus was created with two things in mind, lower part count aircraft to utilize BDArmory and related mods more efficiently, and to put together head-to-head match-ups between aircraft of similar style and function. These fuselages are all-in-one, including cockpit, radar, engine, ammo, and fuel. (On some occasions, the fuselage will also have a weapon integrated such as with the F-15 in this initial release.) Versus contains the following parts: F-15 Fuselage with inegrated 20mm MiG-31 Fuselage Su-25 Fuselage 3 F-15 droptanks in varied sizes 2 Pilot Pitot parts for WM and AI function FAB-100, 250, 500, and 5000 bombs (assets from NKD, rescaled and edited for current BDAc compatibility.) You will of course also need to outfit the vessel with wings, landing gear, control surfaces, weapons, and whatever various odds and ends you'd like. To note: This mod is intended for "full size" aircraft. Tweakscale is not supported, as it can and will most likely alter the weight and flight characteristics with disastrous results. Thrust, velocity, and atmospheric curves have been toiled over to get the most realistic performance we can squeeze out of these aircraft. This mod was designed for and with Stock aero, as such FAR is not supported, but if this works in FAR then all the better for those users. Versus is CC BY-ND 4.0 I know, no pics no clicks! Download on Spacedock or Dropbox. Recommended (but not required) Mods: BDArmory Continued - Required for pilot pitot part to function SM Armory SMI Missiles and Launchers - Full of missiles, especially some perfect Russian ones to outfit your vodka fueled planes. KWS - Cold War BDArmory Extension Kerbal Foundries Procedural Wings

I think it would be pretty cool if there was a plugin to integrate BDArmory modules such as the targeting cam and radars to be displayed in RPM powered MFDs, like using the targeting cam through an MFD and displaying radar information and locking targets on it. Weapons display would also be cool. EDIT: Instead of a plugin that alters the functionality of the current MFDs added by the aforementioned mods, a separate MFD prop that could do all described above would work, too. This is what I'm looking for. I do not know how to do this myself as I only make models.

BDARMORY FX NOT WORKING PLS HELP my ksp is 1.3.0 and i have downlloaded all de bdarmory mods with kchan but the mods dont function as ive expected the effects of most bombs do not work

My ships! coming soon Cleared all of the craft out. due to KSp updates, Will start adding some back soon

The is the Open Beta for the next release of BDArmory Continued. This next release (version 1.1) will be a complete refactor of the damage model, ballistics and explosive force calculations. Our goal was to model realistic values for ballistics, bullet penetration explosive damage and force. All formulas used to calculate these values are based on real world values and physics formulas with balancing to account for game play. Beta Release #1 : https://github.com/PapaJoesSoup/BDArmory/releases/tag/v1.1.0 Fixes Too many to list - see this tag in get for issues being corrected and comprehensive lists : https://github.com/PapaJoesSoup/BDArmory/labels/Fix Pending Release New Features Main issue tracking changes : https://github.com/PapaJoesSoup/BDArmory/issues/307 Damage is no longer tied to heat or temperature of the part, a completely new "Hitpoint" health system has been created. By default all parts will have their Maximum Hitpoints calculated based on part area and density Documentation : https://github.com/PapaJoesSoup/BDArmory/wiki/1.2.1-Hitpoints-&-Armor For Modders: you can override these values by using the following in your part config or MM patches MODULE { name = HitpointTracker ArmorThickness = 120 maxHitPoints = 100000 ExplodeMode = Never } Example baseline values for balancing : 10,0000 hitpoints for Tank Hulls, 100,000 hitpoints for larger boat hulls. Armor The Armor and penetration system has been completely redone, no longer needing custom layers or parts. All parts will have a default value of 10 "Armor" units to approximate default thickness of metal composed of the part. Armor can be changed in the VAB or by the same method above with a MM patch. Any part can have Armor if you choose, allowing for more flexibility. There will still be dedicated Armor panel parts for those who choose a different build path. Armor will stop bullets and limit damage depending on the amount present and bullet mass and velocity Bullets Documentation https://github.com/PapaJoesSoup/BDArmory/wiki/1.2.2-Bullet-Configuration Bullet configurations now have real world values for caliber and mass. Ballistic coefficients are calculated in code based on these values for a more accurate drag model Most damage values for weapons have all been moved to the bullet configurations. This will now make weapons more consistent with same ammunition. BULLET { name = 30x173HEBullet caliber = 30 bulletVelocity = 1180 bulletMass = 0.3880 //HE Bullet Values explosive = True tntMass = 0.3104 blastPower = 2 //deprecated, use tntMass, left in for legacy support blastHeat = 3.7 //deprecated, use tntMass, left in for legacy support blastRadius = 2.5 //deprecated, use tntMass, left in for legacy support apBulletMod = 3 //not yet implemented bulletDragTypeName = AnalyticEstimate } Weapon Configurations All damage values are now calculated from the bullet configuration. All other value are deprecated. ammoName and bulletType are required MODULE { name = ModuleWeapon .... ammoName = 30x173Ammo bulletType = 30x173Bullet .... Decal Bullet Hits Bullet strikes currently have two sizes for (90mm below / above) This is a very early feature and has much work left to be done (i.e. mapping bullet decals to curved surfaces properly) Explosive Damage @jrodriguez to provide more details on the changes of the explosive detonation code New value of tntMass is replacing all other values for explosive in bullet configuration. For Missiles the following will need to be added, where tntMass should be the approximate real world value of explosive mass the missile contains. MODULE { name = BDExplosivePart tntMass = 27.15 } Compatible Mods SpannerMonkey has graciously allowed me distribute his pre-release updates that are compatible with the Open Beta. Please do not comment on any other thread but here about issues with these parts. Feedback should be provided here in relation to BDA testing only. Do not merge any of these , complete re-installs SMIndustries : https://github.com/SpannerMonkey/SM-Marine/releases/tag/v0.9.9.0 https://github.com/SpannerMonkey/SM_Armory/releases/tag/v0.99.90.10 https://github.com/SpannerMonkey/SM_AFVs/releases/tag/v0.9.1.99 https://github.com/SpannerMonkey/SMI_MissilesLaunchers/releases/tag/v0.1.1.0-beta https://github.com/SpannerMonkey/SM_OSTandT/releases/tag/V0.1.1.0-beta https://github.com/SpannerMonkey/SM_Stryker-Aerospace-and-Armory/releases/tag/v1.1.20-beta https://github.com/SpannerMonkey/Large-Boat-Parts-/releases/tag/V3.9.3-beta Malfunc Weapons : https://www.dropbox.com/s/yf41npj2kuual9j/MalFunc Industries BBDA dev ready SM version 1.zip?dl=0 HullBreach Compatible with SM Mods : https://www.dropbox.com/s/54s7i9s2vtk2hy9/HullBreach.0.1.6.2_12022017.zip?dl=0 Thanks Test / QA Crew borrowed from @SpannerMonkey(smce) @Azimech @TheKurgan @Wrench Head @XOC2008 Other QA and Mod Makers : @Acea @lancefoxcia @harpwner The Standard Warnings and Notes Use at your own risk, this is a beta build an will have issues. We recommend you test in an isolated copy of KSP. It is possible you could corrupt craft or saves, no guarantees. Always completely delete / replace the entire BDArmory directory Delete your partDatabase.cfg & ModuleManager.ConfigCache before loading if updating the new build Module manager is required New / Daily builds will be posted at https://github.com/PapaJoesSoup/BDArmory/releases We hope you'll enjoy these new features, and looking forward to an interesting open beta phase with lots of insights & discussions! Your BDAc team @Papa_Joe @SpannerMonkey(smce) @DoctorDavinci @gomker @jrodriguez @TheDog Boring demo Beta Release #1 : https://github.com/PapaJoesSoup/BDArmory/releases/tag/v1.1.0

Hello to all again. I'm new to the KSP forums and after searching google I'm turning here for support. I want to build a customized artillery shell but the small warhead isn't working. Sometimes it'll explode like its supposed to, but mostly it just impacts and disintegrates. Can anyone help?

The goal of this is just to make parts that I have wanted that just may be useful to someone else. Currently: 4 Variants of a 50 caliber long recoil machine gun. Why: I like how long recoil guns look when they fire with the very visible mechanisms moving I like low part count parts that combine multiple things together for quick assembly. The four variants are wing mounted, wing mounted with a magazine, surface mounted (shrouded) with and without a magazine. This is not based on any real machine gun but the barrel and mechanisms are, I think, within reason as I tried to follow typical specs/barrel sizing while modeling. The magazines also hold what I measured to be a to scale amount of ammunition. For sound these use the base BDArmory sounds. This needs BDArmory to work 2 Variants of aesthetically different gun pods. Why: I like low part count parts that combine multiple things together for quick assembly. These may eventually become turrets These very roughly follow realistic sizes. They come with ammunition. (If you can guess, I made these before the previous ones.). This needs BDArmory to work 3 Variants of BDArmory Combination Command Boxes. Why: To combine 3/4 frequently needed parts into one To have to closest thing to a laser I can make These have AI flight modules, Weapon Management modules, Flight Command modules, Solar panels, Batteries Lights (lasers?!), Very Small Reaction Wheels Radios and Small RTGs. Still trying to figure out how to orient the bdarmory modules correctly in relationship to the command module. This needs BDArmory to work Edit: 0.01 Update: Added slimmer AI Command box that looks far more stealthy/sleek. 1 Small Single Shaft 1 mode thrust direction changing turbojet fin (Based loosely on the TJ100(Tweakscalable)) Why: I like low part count parts that combine multiple things together for quick assembly. Ive wanted a small drone sized jet engine that does not need anything but itself to produce thrust/steering. (Intake, directional thrust, fin, small fuel tank, engine included). This has about 5 minutes of fuel at sea level, 15 degrees of articulation and has no thrust vectoring but instead acts as a fin. the engine itself occupies a 27cm by 27cm by 64 cm box (like the real life PBSTJ100) (very slightly off angle at the moment, to be fixed ). This needs no other mods to work. Has turbine rotation animation, along with heat animation. Placed in career mode to the same place as the smallest available jet. Edit: 0.00201 Update to the UR100c TurboJet fin. It will function more like a typical fin, and have a far more reasonable aerodynamic effect for its size. The animations were also updated with more orangey red lighting from the engine heating up, and an animation that visibly goes the correct way. Turns out it was never off angle and stock fins also have a similar effect. Nevertheless its improved. It has also been edited to work with Tweakscale (Recommended as outside of the early stages of career mode, these engines are quite weak without scaling (given the real life analogs are made with small planes or rc planes in mind)). Edit: 0.01 Update to UR100c TurboJet fin. It now has a drage cube that better reflects its shape. Ive noticed its more powerful than the real life engine as in ksp itd be pretty near to useless if my calculations are right. Its not too far off though, so tweakscale is still something you'll want to use with this most likely. Im considering making a bigger one. 1 Electric Ducted fan ((Tweakscalable)). Why: I like electric ducted fans, and wanted one I could tweak to feel more realistic and like the look of. This is not based on any particular real world fan and does not have any special tweaks to work in ksp. Its finished mostly. I just need to add sound. Edit: 0.01 Update: This has been added. It relies on community resource pack with intakeatm to work. Balance could use work. Both this and the mono prop engine use KAX sound assets. 1 Atmosphere breathing mono propellant powered 0.625/half size piston engine (Tweakscalable). Why: For low flying flying rovers on planets with atmospheres but no oxygen like eve based on concept from nasa in the 70s This is pretty much done. Modelling is complete, variable pitch propellers work along with reversing thrust. All I need to do like the electric engine is finish sound. Edit: 0.01 Update: This has been added. It works without intake atm for the time being. It still provides no thrust without atmosphere however so that is good. Im considering using firespitter for both this and the ducted fan. Single Piece Landing gear. (scalable) Why: I like low part count parts that combine multiple things together for quick assembly. This is really nowhere close to being made. It will be using KSP wheel (so that it can support having more than 1 wheel collider) and while the model is done, setup will probably take a while even with a helpful example from the maker of kspwheel (Shadowmage) . Edit: 0.01 Update: Its been made! Its designed differently than the first design, but it works completely. Im actually pretty happy with how its turned out. It uses tank steering and looks a whole lot more rugged than the first iteration. I plan to make another one with a more typical arrangement as well. Thanks to Shadowmage for answering probably too many questions about this. It uses KSPWheel as well as Kerbal Foundry sound assets. One Part y axis balanced dual wheel landing gear. Why: To have a small steerable landing gear piece that has functional wheel colliders for each wheel, meaning a vehicle can be balanced on just 2 of them. Planned: Single Piece Landing gear (No tank steer). Why: To match a more typical landing gear look. Variety Turbo fan jet engines (With animations than go to 90 degrees for vertical takeoffs). Why: Making vertical takeoffs easier Electric lift fan (With animations than go to 90 degrees for vertical takeoffs). Why: Making vertical takeoffs easier Add Fire Spitter to props/fans. Why: Better matching rotations Making the variable pitch propellers on the monoprop piston engine function better. Rotation affected by air speed Landing gear enhancements (Making the small single axle menu have full customizability (difficult now due to having 3 real wheel colliders)). Why: Allowing the same customizability as would be on normal ksp wheels with a single part that balances on 2 wheel collider Add to CKAN Fix shading on parts of the 50 cal machine guns, particularly the outer housing. 0.011 Its fixed. Not perfectly, as I think that would require changing the model, and that would require re doing a whole lot of the setup in unity after fixing it in blender. Ive just made things generally less shiny/rough. Put this on the actual addon release page since thats basically what this is really. I have posted this there now. I'l probably just keep updating this main post and linking to it from that one with small updates, issues etc. Just stuff that I think would clutter up the release page. Link to SpaceDock Download Dependencies, recommended and included mods: Included Included Not Included. Latest Downloads available from the official Github Releases page. Recommended License: Feedback is appreciated. Ive never done this before and am clueless. If anything is off, and you know how to make it better, Im open to advice. Also thanks to Shadowmage and Spannermonkey for their assistance with KSPwheel and BDArmory Continued respectively. They've both been extremely helpful with questions, examples and advice. Also thanks to all others who have been helpful here and there.

Kerbal Space Program Ultimate Fighter Competition (KSP-UFC) With the Guidance of Emperor Allister of house Kerman. The Bosognian Empire would now host a gladiator pit-fight between the world's greatest aircraft designer's fighters. The First set of the competition would be Theme-less and would follow an 8 competitor bracket. The battle would be fought with 2 planes per player with the opposing planes facing each other back-back. No tampering on the planes would be done. If you sent your fighter with an maneuverability even an AI cannot control then that's how it shall battle. The Competitor would be chosen through Random Selection The Competitors Submission must be sent by E-mail to [email protected] The Competition Shall Impose restrictions on the fighters however the restriction would be light. Mods (Required) BDArmory (The (Optional) Quiztech Airplane Plus Aviation Cockpits Firespitter SMArmory Master Tech weapons Procedural Wings Adjustable Landing gear Restrictions No Gimbaling Turrets No Gimbaling missile launchers No Meteor Missile from Master Tech Weapons Crafts should be 80 parts or less FAR would not be used No PAC-3 missiles Clipping is allowed but Resource Clipping is not allowed The Clips from the battle would be posted at: https://www.youtube.com/channel/UCfLcV69Rtie9wDHmAoW-8kA