This mod is not known to work with the latest version of Kerbal Space Program. Proceed with caution.
Supports TweakScale and AVC. Appears to be friendly to FAR/NEAR so far.
0.7 and later versions ARE NOT COMPATIBLE with 0.6 and earlier! If you are upgrading from 0.6 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.
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.
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).
Cooperates with other mods, including TweakScale, FAR/NEAR, and AVC.
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)
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.
Build your internal payload first.
Don't forget a decoupler on the bottom of the payload!
Attach one of the fairing bases beneath the decoupler. (Be careful to choose one that is both wide and tall enough.)
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)
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).
Your fairing panels will appear automatically upon stacking a part on the floating node.
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).
Released on 2016-04-29
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.
Released on 2016-02-17
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.
Raw stats are from the beginning of time until now. Each follower and download entry represents one hour of data. Uneventful hours are omitted.