Search the Community

I came up with this idea when I wanted to edit my spacecraft under x2 fairing. Problem that I didn't see craft because fairing blocked my view. Fairing opening depends on camera and cursor positions, and this system doesn't work well. For example half of x2 fairing still blocks view, while other half jerks sharply and blocks view if you zoom very much. If fairings were transparent, these problems would be solved easily and craft editing would become much comfortable

I'm not quiet sure if I'm the first person to discover this, because I havent heard of anybody else using it, (I bet I'm not) Say you have a fairing, and you finish it, and it pops up with a message saying "warning: cannot accept current changes. Fairing is colliding with invalid assembly part." So you try and try and try! To get the fairing right, but one of the two keeps happening; 1. You can't do anything without the fairing saying the message or 2. You can get a fairing, but it is not to you're liking Well, I have a easy fix for you! So, I discovered this while playing around, but it turns out, all you have to do it get the pop up message, and after that you can do one of the two things; 1. Click on any place, then place it back or If you don't want to replace a part on the craft 2. Click on any part on the part picker and recycle it It's literally as simple as that, hopes this helps!

If for example you set a fairing to x4 clamshell, and save it, when you load it back up, it does not save that change and reverts to 2x clamshell. The fairing I'm using is the "AE-FF375 Mussel" but I don't think which one you use matters.

I can create a ship with a fairing, set it to 3x or 4x clamshell, launch, fail/spot an issue, and revert to VAB, but then I notice the fairing deployment has reverted to 2x clamshell. Also, I launched an Apollo-style mission, 3-crew control-pod + 2-crew lander-can, with 3 crew only in that main pod and none in the lander, but when reverting to VAB Val got added to the lander-can, so now there were 4 crew being launched with 3 Kerbin-return rated seats (and despite dragging her/the Munar lander back to a stable LKO, the undocking imparted strange forces to her craft, resulting in her having a wildly elliptical, suborbital trajectory despite having no Methalox and minimal RCS available to her… Adding: Updated to v0.1.1 on Thursday Windows 10 5900X and 48 GB DDR4 TUF 3080 10 GB GDDR6X Expected: a fairing/part mode-selection in VAB pre-launch persists upon reversion/“reloading” Reproduce: create a fairing, choose 3x or 4x Clamshell instead of 2x (never tried shroud, but likely similar), launch, maybe check mode here but likely okay, then revert: now 2x again in VAB and if launched again without changing

Zero-Point Inline Fairings Parts Pack NOTe: Does NOT shield contents in stock aerodynamics! Please use FAR or NEAR. --------------------------------------------------------------------------------------------------------------- Supports TweakScale and AVC. Appears to be friendly to FAR/NEAR so far. Part of the NecroBones suite of mods, that work nicely together: Modular Rocket Systems (stock-alike parts pack, NASA-like alternatives, and filling the gaps) SpaceY Heavy Lifters Parts Pack (stock-balanced large rocket parts, 5m parts, large SRBs) Color Coded Canisters (replacement models/textures for stock fuel tanks: prettier, cleaner, and diameter color-coding for the tank end-caps) Fuel Tanks Plus (collection of large stock-like tanks with Color Coded Canister style) Zero-Point Inline Fairings (stock-alike fairings parts pack, no plugin code) VERY IMPORTANT NOTE: 1.0 and later versions ARE NOT COMPATIBLE with 0.9.x and earlier! If you are upgrading from 0.9 or earlier, be sure to delete the mod's folder from GameData before installing the new version. Savegames with active ships using the fairings will not be compatible across this transition (you could do a lot of hand-editing if you wish, as the same sizes still exist). Upgrading should be safe if no ships are currently using the fairings. IMPORTANT NOTE: This is an EARLY BETA -- That means there's a good chance that the parts will change significantly, and may break your save-games. We're looking for feedback, and have released version 0.1 of this pack after working on it for less than 2 days. --------------------------------------------------------------------------------------------------------------- 5-Minute quick overview: Overview/Tutorial by KottabosGames: --------------------------------------------------------------------------------------------------------------- Advantages and Features: All fairings support INLINE use, meaning that you can continue the rocket stack above them (such as an exposed command section, or another fairing + payload). Contains only three texture files (base, panels, and cone) shared by all models, so memory usage is light. Contains no mod code, instead relying entirely on the stock engine-fairing modules. This means the mod is unlikely to break when new KSP versions are released, or introduce any new bugs. Ejected panels are non-persistent debris (meaning they are deleted when you move out of physics range or use timewarp). Low additional part-count for your ships. Fairings are created by placing a single part (the base), and possibly a second (nose cone). Stock-alike appearance. Cooperates with other mods, including TweakScale, FAR/NEAR, and AVC. Choice between "full" pack (22 parts), or "Lite" version (6 parts). Disadvantages: (to be fair) Adds a large number of parts to the Aerodynamics tab Not as "pretty" as KW Rocketry Not as "easy" as Procedural Fairings. Fairings are restricted to the included sizes (unless you use TweakScale) Known Issues: Placing an engine as the first part above the fairings (at the "floating node", not the base) will result in a "ghost shroud", when the fairing panels are decoupled. This is just how the stock decoupler/jettison modules work in KSP. Don't worry, those shrouds are non-colliding. If you're using an engine that leaves behind a shroud and this bothers you, the recommended work-around is to place a stack decoupler/separator at the top of the fairing, instead of the engine directly. --------------------------------------------------------------------------------------------------------------- Information: This parts pack is intended to supply an alternate means of using payload fairings in KSP. It's meant to be somewhat stock-alike, and also provide the capability of having inline payloads, with a second vehicle ahead of the fairing section. As a real world example, the Apollo Saturn V had the lander inside a fairing, with the command/service module exposed and ahead of it in the stack. These fairings use the stock game's fairing jettison module, functioning like the LV-N engine's ejectable fairings. All of the models and textures were made 100% from scratch, using Blender, Photoshop, and Unity. --------------------------------------------------------------------------------------------------------------- Image Gallery: (Note that the stats, appearances, and descriptions of the parts shown below are subject to change, or may be out of date) --------------------------------------------------------------------------------------------------------------- Installation: Simply copy the "0PinlineFairings" folder into your GameData folder. If upgrading from a previous version, be sure to delete the old one from GameData first (this is the cleanest option). NOTE: ALWAYS backup your save-games when changing mods! If any parts fail to load (including the stock parts, which can fail to load due to a typo in a mod config), entire ships can be deleted out of your game. --------------------------------------------------------------------------------------------------------------- Usage instructions: 1. Build your internal payload first. 2. Don't forget a decoupler on the bottom of the payload! 3. Attach one of the fairing bases beneath the decoupler. (Be careful to choose one that is both wide and tall enough) 4. Build your second vehicle above the fairing, or cap it off with a nose-cone. (Do so by placing your parts on the "floating" attachment node above) 5. If you are stacking an engine right above the fairing (at the "floating node", not the base), you might consider placing a stack-separator here first, to hold the engine-shroud upon decoupling. Otherwise you will get a "ghost shroud" that hovers in place (due to how the shroud jettison works in stock KSP). 6. Your fairing panels will appear automatically upon stacking a part on the floating node. 7. Build the rest of your lifter stages as normal. The fairings will act as a decoupler for the top of the rocket stack, and will separate at the "floating node" where you continued the stack above (or capped it with a nose cone). --------------------------------------------------------------------------------------------------------------- Download the FULL VERSION: (Contains all 7 fairing sizes (4 lengths each) plus 7 specialized nose cones) SpaceDock -or- Curse.com download page -or- ksp.necrobones.com (( 1.0 and later versions ARE NOT COMPATIBLE with 0.9 and earlier! If you are upgrading from 0.9 or earlier, be sure to delete the mod's folder from GameData before installing the new version. Savegames with active ships using the fairings will not be compatible across this transition (you could do a lot of hand-editing if you wish, as the same sizes still exist). Upgrading should be safe if no ships are currently using the fairings. )) Download the LITE VERSION: RETIRED --------------------------------------------------------------------------------------------------------------- Creative Commons 4.0 Attribution-NonCommercial-ShareAlike CC BY-NC-SA --------------------------------------------------------------------------------------------------------------- Change Log: 1.0.2 (2016-04-28) - Working toward stock aero support. - Moved "ModuelCargoBay" definitions out to 0P-AD.cfg (for "Animated Decouplers" dependency for stock aero). - Moved change log and readme into the mod folder. 1.0.1 (2015-06-09) - Fixes - Added transparency in VAB/SPH. Known issues: - Flag decals look mangled in VAB/SPH, but look fine in flight. - Must mouse-over the base, not the fairing. - Updated Deadly Reentry config with more current data. - Updated the DRE config to not lower the heat resistence of the nose cones when DRE is not being used. - Added "ModuleCargoBay" modules to fairing bases, with hope of working toward stock aero support. 1.0 (2015-05-28) - Re-release after KSP 1.0. - Redesigned quite heavily. - Requires FAR/NEAR or similar aerodynamics mod. WILL NOT SHIELD CONTENTS WITH STOCK AERO. - Fairing bases consolidated. 4 lengths per base. - Panels now separate in halves rather than quarters. - Updated tech tree assignments to correspond to new stock fairing diameters. - Added matching "flush" nose cones for sizes 1 & 2 (1.25m & 2.5m). - Added new bulkhead profile and thermal settings for KSP 1.0+. - Renamed nose cones to match more recent fairing naming scheme. - Various size and scaling adjustments. - Minor texture updates. - Updated textures to use DDS format. - Lite version of mod is discontinued. 0.9.1 (2014-12-22) - Minor tweaks - Added DRE support, by including a wildcard heat-shield config for the nose-cones (full version only) 0.9 (2014-12-16) - Minor tweaks - Added manufacturer tag to item names to make all fairings name-sort together. - Fixed manufacturer icon in VAB/SPH manufacturer-sort. 0.8.1 (2014-11-17) - Beta Release - "Full version"-only sorting fix. - (Reminder: incompatible with v0.6 and earlier) - (Note: Remember to delete the old 0PinlineFairings folder before installing, otherwise you'll get duplicate parts in the menu) - Re-ordered the sorting of the fairing bases in the SPH/VAB (Full version only). Not game-breaking. 0.8 (2014-11-15) - Beta Release - (Reminder: incompatible with v0.6 and earlier) - Added Size-1 (1.25m) flush fairings (Full version only). - Added Size-3 (3.75m) flush nose-cone (Full version only). - Fixed "model" assignments for the "Lite" pack's fairings, causing them not to load unless the "Full" pack was installed too. 0.7 (2014-11-14) - Beta Release -- WARNING: Incompatible & Save-Breaking update from Previous Versions - Consolidated fairing bases to reduce part clutter. - "Full" version reduced to 12 bases (from 18), with two lengths each (adding 6 new total sizes) - "Lite" version reduced to 3 bases (from 6), also with two lengths each (same sizes available). - Now, choose a base, then choose length by selecting a floating node to stack onto. - Note: Be careful not to attach other parts to the other floating nodes accidentally. - Added shorter versions of fairings (in "Full" version only) - Overhauled mass and cost of all fairings. - VAB/SPH icons now show just the fairing bases (not the fairing tube panels). 0.6 (2014-10-08) - Beta Release - Reduced purchase & research costs of all fairings by 90%. Somehow an extra zero was tacked on. - Fixed a typo in one of the configs, that had an entry cost set to "aero" (yeah, I don't know) 0.5 (2014-10-07) - Beta Release - Fixed scaling issues, to align with 0.25's rescaleFactor bug fix. 0.4 (2014-09-29) - Beta Release - Tweaked the scaling on the "flush" fairings to be a hair wider. - Fixed aspect ratio of flag-decal on the "flush" fairings. - Renamed: Wide -> ExtraWide, and: Regular -> Expanded - Forked "Inline Fairings Lite" as separate download with smaller parts list. - Tweaked the panel ejection slightly. 0.3 (2014-09-24) - Beta Release - Reduced mass of all parts - Changed TweakScale settings to allow "free" scaling of the 2.5m "Regular" and "Wide" fairings (to give them separate functionality from the otherwise identical 1.25m variants) 0.2 (2014-09-21) - Beta Release - Added AVC (Add-on Version Checker) support. - Fixed attachment point in the Size-2 Regular Nose Cone 0.1 (2014-09-20) - Initial Beta - First release. Only 2 days of work making the parts so far.

Hi guys this is my next youtube video, its a very clumsy starship sn 15, its mostly light and is a joke (more or less) https://youtu.be/Q-Dz6NUVORQ

Recently when Upsilon Eeloo window opens, I've start building on new crew habitation Mongolian tents using fairings. But the fairings starts behave strangely when taken out from sub assembly: the fairing hit box is gone. Kerbals can just poke their head out of the fairing, and required rebuilding the fairings to regain the hitbox. Is this a bug or am I doing the fairings a bit wrong?

Fairings are one of the most utilized parts in ksp, but they have some flaws, these are changes that could address them. 0.625 meter fairing: Fairings are often used in ksp to make custom shapes. However, when using a fairing to make certain parts like engines it must be both heavily clipped and smaller than the size of the rocket itself (usually about two size classes. Necessitating rockets that use this technique to be massive, smaller fairings fix that. Increased size limits on fairings: Although I understand why there in place, often it is advantageous to hide the fairing base in a rocket, necessitating a smaller fairing size. This makes the size limit on fairing a serious problem, particularly with aeroshells. A possible better improvement would be to remove the size limit, but make cost and weight increase exponentially to justify using a heavier more expensive fairing. Procedural aeroshells/baseless fairings: These would be like normal fairings, but without a base. They would be closeable at at the top and bottom and could be switched from building above the "base" to building below it. The base is an attachment node for attaching the fairing to the craft. This would make building aerosols a simple preocess, rather than clipping fairings in a complicated and heavy way that looks awful. Option to make interstage nodes truss disappear, provided that the part in the nose is touching the fairing: Exactly as described above, upon jettisoning the fairing the parts attached would be jettisoned automatically. Useful because the truss is ugly, would make mounting parachutes on aeroshells a lot easier. And most importantly, make each section of fairing resizable with a tweakable, rather than being forced to use the inaccurate mouse.

i have no idea how to use fairings in the VAB. Someone help! They just won't set in place even after I clicked. Now thinking how I visited all the planets with no fairings.

There are 3 hitbox that a fairing may have, 1. Hollow hitbox 2. No hitbox 3. Solid hitbox So what are they? Basically hitboxes a fairing could have in ksp and the most common is the Solid Hitbox. I've been doing Fairing domes so that's why I know these 3 fairings, so let's dive in what are these hitbox and why I'm here. The hollow fairing is the perfect one, a hollow inside that Kerbal can walk inside, and has a solid wall. The no hitbox is self explanatory, your Kerbal can just phase through without being blocked. The top two always happens at launch, cheated tests (aka using debug to move the dome to another area for test). So test are always perfect when it comes to EVA inside a fairing. But the third hitbox is the most annoying. The solid hitbox is where even the inner space is filled with a hitbox, a hatch that can work before would not work, and if they work the kraken will arrive. This commonly happens after reaching the destination after launch from KSC and it is annoying since everything you tested would not work now.You could see that the first picture the Kerbal is getting warped by the kraken, and on the second pic the Kerbal gets pushed out, indicating a solid hitbox. It's just pain seeing your work for the interior is just useless after this. So I want to ask a few questions 1. Why are there these 3 types of hitbox 2. Why do solid hitbox form 3. How can I remove the hitbox ( in the game file) 4. Is solid hitbox another bug. Any answer for either questions will be accepted, please help.

I'd like to see the clamshell mode be enabled by default instead of each time users having to enable it. I'm pretty sure most people use near clamshell deployment as it looks more realistic, presents less hazard for the ascending rocket, and less strain on the computer since it can be as little as 2 parts, whereas confetti is a disaster on multiple accounts. When Squad first added fairings, there was no clamshell option at all, which rightfully caused lots of complains. Then it was added, but having to click the damn button each time just pokes my brain. If someone knows how to make it be ON by default, do tell and I'll give them a cookie.

I used to have this mod that would add fairings as individual side panels that you could attach to a base, but I forgot the name of it. I would like to find it again, as it makes payloads look much more clean than just the weird shapes of stock or even KW faring. It was useful for getting clean fairings that would look the same for all payloads, and they usually had nice curves to them. Could anybody point me in the right direction? Thanks

I'm sure this has been said quite a few times, but I just wanted to share some features I think would greatly improve fairings and their use-cases in the game. I've listed all the changes I'd like for them to make. 1. The most obvious one. Reduce the size of the part and make it look better. Right now it just looks ugly and out of place on pretty much every rocket. A much better look would be something like a decoupler only taller and without the markings. Another feature would be to make it hollow, like the structural tubes. That way there's way more flexibility with them. 2. Change the colours of the variants. I find that the variants look quite ugly because of the very repetitive and textureless surface. 3. Make fairings be solid so other parts can be attached to them. This would add a toggle in the VAB/SPH that would make the fairing solid. You can then attach the parts you like. If you then make it see-through again the attached parts become part of the fairing itself and will remain with it even after being deployed. 4. This is the most complicated one. Make it so fairings can be split up into multiple parts than can be deployed seperatly or not at all. This would work while making the fairing. An extra option would make the rest of what's build independent from the bottom of the fairing. Each section can then be staged seperatly or be disabled from staging. To visualize this just think of the fairing seperation on an Atlas V, where the top part of the fairing deployes while the bottom half stays attached. This feature would vastly improve the usability of fairings to beyond just protection from the air and streamlining. Thoughts or suggestion?

I was thinking, fairings are super useful as single-use cargo bays. It would be really nice though if, with a balanced mass penalty and whatnot, we could have a fairing which would not shatter or break off but either swing open its nose, split like a normal cargo/bomb bay along one side, or banana peel at the base, then close and seal back up. This would allow, for example, super-sized cargo transports that had >3.5-meter-wide "cargo bays" using ALMOST existing parts. Alternatively, we could have dedicated parts for either modular or procedural cargo bays that would actually seal and be recognized as such ingame. Note that the modular option may involve more coding headaches to try to determine whether the cargo bay is in fact enclosed, whilst procedural cargo bays would have no such problem since they could use the same code as fairings and normal cargo bays for that. Another thing that would be nice is if both these and normal cargo bays had the option to negate water physics, and if possible water rendering, inside them.

Hello I was hoping the manual would explain and talk thoroughly about fairings, but it was barely able to say what a fairing was. So, to start with, there's the "sides" options. The problem with this for me is that I can drag the bar, not having only whole numbers to choose from (for example: I can choose to have 4.09 sides, what got me pretty confused). Then there's Ejection Force. I think it's pretty self-explanatory, but is there any usefulness in changing the force? Now for Clamshell Deploy, Truss Structure and Interstage Nodes, I have absolutely no idea of what they're for or their uses. I'd be very glad if someone could explain at least this for me with pratical examples. Thanks.

Is there a general rule of thumb as to the optimum altitude/velocity/pressure (Q, I think) to jettison fairings-- where the aerodynamic drag reduction is no longer worth the weight/gravity loss? I don't really need the exact equations-- just a general "feel" for the right timing/altitude. Thinking of firing off a series of sounding rockets to test, but I imagine someone else has done a lot more thinking about it already...

So I've been playing a lot with procedural parts recently, and while researching how to properly use the procedural Interstage Fairings, I found out that those parts are NOT supposed to be used for engine shrouds. This explains a lot about the odd lack of an internal top node, and the placement of the decoupler. The only way I've been able to do it is to surface attach the engine underneath the tank to leave the tank's bottom node free for the Interstage Fairing top node. I don't think this technically shields the engine at all though, since it's not attached to an internal node of the fairing part. Also, I've been having weird issues with the fairing base jumps to odd positions when I try to use the whole launch vehicle as a subsystem. Usually, it jumps downward, leaving a big gap in the rocket, although this appears to be cosmetic only, the thing will still fly the same. Is there a more appropriate mod/part that I should be using for interstage engine shrouds? I'm using pretty large tank sizes, so even the 3.75 stock fairing is too small, and rescaling that part doesn't seem to rescale the fairing. Suggestions? Thanks

In the last days I have been running around the forums searching for a way to add textures to the module TextureSwitch2 (Firespitter) to the fairings from Procedural Fairings parts.I found a very old mod from 1.1.x called Procedural Fairings for Everything, which main objective was to collect and merge different texture mods for fairings into one.I gave a look inside of the folder and it was quite a mess.I am trying to make a more polished version of it for myself but I can't get around a thing that is quite anoying: Some fairings have the "Payload Fairings - [...] [Procedural]" and some don't.Anyone has any idea where I can find the file that adds this thing?(So I can remove it and rebuild it to be more specific). On another side I would like this to become a thread on where to discuss the problem of textures for Procedural Fairings and to make a standard guide on how to make and plug them into KSP.

To premise this topic, I'm not sure if this is a bug, or a limitation of the stock fairing behavior when used as an "interstage". I'm trying to use an open fairing as a lower fuselage of a cargo lander. After launching the craft to orbit and jettisoning the bottom cargo bay "plug", I am unable to insert cargo or other craft into the open bay. IMPORTANT NOTE: Anything jettisoned from the lander can be maneuvered inside the cargo bay just fine, but anything launched separately cannot. To anyone wanting to reproduce this behavior, you will need to perform two launches. Anyone that has any thoughts or suggestions, feel free to comment. @Rune, you might find this of interest since this is the DC-X-style cargo lander I teased you with.

Version 1.1.2.1260, Windows 10 Home, x64, Nvidea 980 gtx, i7 4790k, 16 gbs ram 9 times out of 10 when I try to use fairings they will cause the ship to fall apart and then explode on launch pad. Example: http://s32.postimg.org/ps1z2y40j/fairingproblem.png I wanted to post the ship file, but it said I couldn't attach because of my account :(. But basically any time I use a fairing the ship just falls apart on the launch pad, its extremely reproduce-able for me. Is anyone else seeing this behavior? I cannot comment on when this started to break for me since I did not start using fairings until recently.

Fairings that automatically reshape for any attached payload: Download from GitHub Frequently Asked Questions How to use (Imgur album, somewhat obsolete) Licensed under CC BY terms (attribution) Source code Notes: In career mode, minimum and maximum size is limited by tech. You won't be able to resize bases far from 1.25m at first, but as you unlock new aerodynamics and construction tech larger (and smaller) sizes become available. Unlike KW Rocketry fairing bases, Procedural Fairings' fairing bases intentionally lack a decoupler, allowing docking nodes, structural parts, multiple payloads, etc. The fairing bases can be so modded as to include a decoupler. Compatible with FAR and KSP 1.0 aerodynamics. Bug reports, suggestions and any other feedback is welcome! Future plans: Simple procedural decoupler with shroud for engines that lack built-in fairings and engine clusters. Procedural nose cone. Stock-alike fairing bases with non-part side panels. Side fairing part with switchable textures and shapes. More side fairing styles, matching KW Rocketry, AIES, NovaPunch, etc. More complicated texture mapping schemes for less texture stretching etc. Documentation and tutorial for creating side fairings. Particle effects on jettison. If you want to support me, here's my Patreon. Change log: Funding provided by FlexGunship.

Good day to all. I've gotten a bit back into KSP once more; been launching satellites for an RT comm network/constellation in the Kerbin system as well as my first real space station. (The only other "station" I ever attempted was just an orange tank with basic craft utilities bolted on as a fuel depot...) For once I wasn't using SSTO spaceplanes that much. (Just for the initial three KEO sats for a basic network so unmanned launchers could be used without issue.) Lots of rockets this time. (Seems I've gotten pretty decent at doing gravity turns using KER readouts and mimicking what I saw the GravityTurn mod does...) Lots of rockets = lots of fairings. Suffice to say, I got sick of adjusting the fairing settings to my personal default every time I grabbed one from the parts list. Module manager to the rescue! I made catch-all MM CFG where you can change a few settings to whatever you like so you can save yourself some time in the long run: Number of Sides Ejection Force Clamshell Usage Max Length of Sections Visibility of the Interstage Nodes and Truss Here is the MM CFG itself: // This MM Config sets some defaults for your fairings so you don't have to all the time. // The FINAL is there because I make all my personalized MM configs run last after all the mod configs. // I figure it makes sure I catch all changes and mod parts that use/apply/edit the same settings I'm modifying. // Probably safe to remove if you wish. @PART[*]:HAS[@MODULE[ModuleProceduralFairing]]:FINAL { @MODULE[ModuleProceduralFairing] { %nArcs = 2 // Number of fairing sides. In-game Editor Tweakable Limits: 2-6 %ejectionForce = 1000 // Self-explanatory. In-game Editor Tweakable Limits: 0-1000 %useClamshell = True // Self-explanatory: True/False // The next setting controls the max length of each section. // I'm applying a multiplier here to the part's stat. // If you want a hard number, delete the *. // Not a normal tweakable, so I don't know the limits. @xSectionHeightMax *= 3 } @MODULE[ModuleStructuralNode],* // Needs indexing wildcard here since each node is using an instance of this module. { %visibilityState = False // Visibility of the Truss(?): True/False (Related to "showMesh" below; change in tandem.) } @MODULE[ModuleStructuralNodeToggle] { %showMesh = False // Visibility of the Truss: True/False (Related to "visibilityState" above; change in tandem.) %showNodes = False // Visibility of Nodes: True/False } } As you can see, I made sure to annotate it with notes so you (and I) know (remember...) what does what. Just copy it into a plain text file (.txt), then rename it to a .cfg file. I really wish the stock part configs had more notes in them... Where do people get info about modules and such to make proper configs? The official Wiki is kinda half-assed and mildly out-of-date. License is PUBLIC DOMAIN. (It's just a practical config file with some commentary from me...) I'd stick up a file download, but I don't really have anywhere to place it; it's just a text file anyway. (Seems like overkill for me to upload this to something like SpaceDock.) BTW, the config looked A LOT nicer in NotePad++ (Tab spacing here is bigger.) I have a couple of other genericized MM CFGs I made for myself. Dunno if anyone would be interested in them, though: RemoteTech Probe Core Support - Adds SPU and passive antenna to any unmanned command module from any mod. RealPlume "Engage" Audio - Changes the activation sound for RealPlume'd engines (because I shouldn't hear an explosion when at zero throttle and turning an engine bank back on. Too loud for my tastes.) SurfaceLight Replacement - Just replaces the stock ModuleLight with the module from the mod SurfaceLights and sets a default color. I technically have a generic MechJeb config (adds it to all command modules), but I got that off the forum here (MechJeb Embedded).

I don't know about anyone else, but I've been having real issues with the stock fairings lately. For one thing, they don't stage with action groups. If I have a pod (or something I want to save in case of emergency) under a fairing, and my action groups look like this Abort> LES activate, Decoupler decouples, fairing jettisons. What will happen in case of emergency is this: I hit backspace Everything but the fairing jettison occurs My crew pod gets smashed against the inside of the fairing and they die. Which brings up my next point (kinda). After that, everything inside my fairing has been obliterated; my rocket is falling back down onto the space center; it lands on the grass; and... Everything but the fairing breaks and explodes. Fairings are needlessly strong. Don't you think that my launch escape system (homemade, it packs 300 Kn of thrust) should be able to crack that fairing open and carry my crew to safety? We like explosions don't we? Don't we want to see the fairing explode and crack into little pieces? This last thing is much less urgent than the first two. It'd be really cool if we had multiple textures for fairings. Stock, solid white, grey, some kind of ability to upload your own (maybe?) be able to add a flag and such. While still maintaining the ability to customize the shapes of your fairings, I'd also like to see Procedural Fairings become stock.

Okay, so one minor thing that bothers me about the new stock clamshell fairings is how perfectly evenly they separate and float away. No tumbling or nothing. It's freaky! As a matter of fact, the mod that fixed the absence of clamshell fairings when fairings were first introduced by Squid, that mod had them tumbling through space as you would realistically expect. So what I'd like to ask is a simple thing, which is to do a "jazzing up" pass over the stock fairings and re-introduce this tumbling behaviour, maybe even with a little bit of a camera shake effect. Thanks for reading. From an older version of the game, but this is the sort of thing I'm talking about. Fairing separation at many points throughout, but particularly at 10:43.

I've been trying and trying to build the smallest possible recoverable Kerballed orbiter by mounting an EAS control seat on top of a fairing base and (supposedly) using the fairing to protect the pilot from heat: Even though the pilot is fully enclosed by the fairing, it appears as though he is being heated as if fully exposed to the airstream, and he inevitably explodes even though no other part on the craft even has a heat indicator lit up. Is this just a quirk of the control seat or am I using the fairings wrong? I tried building it out a bit further, and other than making it heavier and draggier, it seemed to make no difference.