Search the Community

Showing results for tags 'plugin'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General
    • Announcements
    • The Daily Kerbal
  • General KSP
    • KSP Discussion
    • Suggestions & Development Discussion
    • Challenges & Mission ideas
    • The Spacecraft Exchange
    • KSP Fan Works
  • Gameplay and Technical Support
    • Gameplay Questions and Tutorials
    • Technical Support (PC, unmodded installs)
    • Technical Support (PC, modded installs)
    • Technical Support (PlayStation 4, XBox One)
  • Add-ons
    • Add-on Discussions
    • Add-on Releases
    • Add-on Development
  • Community
    • Welcome Aboard
    • Science & Spaceflight
    • Kerbal Network
    • The Lounge
  • Making History Expansion
    • Making History Missions
    • Making History Discussion
    • Making History Support
  • International
    • International
  • KerbalEDU Forums
    • KerbalEDU
    • KerbalEDU Website

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Skype


Twitter


Location


Interests

Found 139 results

  1. Textures Unlimited The Textures Unlimited addon brings the Unity 5 Standard shader functions to KSP along with a suite of utilities for loading shader and model asset bundles, and a host of shader and texture-related functions to support them. It does not add any new part or textures by itself, but is intended to be used and distributed by other mods who do not wish to develop their own plugin code or shaders. Features: Asset-Bundle Shader pack loading system Reflection Probe Manager - updates the reflection probes in a fashion that works in KSP, with quality and performance configuration available Reflective textures are fully supported through the PBR shaders Texture Replacement system - replace the textures on any .mu model, in a mesh-by-mesh fashion; complex material arrangements fully supported TextureSwitch module - includes a simple texture-switch module that can be added to parts through MM patches to facilitate in-game user-driven texture switching User-driven 'recoloring' system for parts. Define the pattern on the part through a mask texture, and let the user specify the color scheme. Legacy and PBR versions available. Requires special texture and shader setup. Asset-Bundle Model loading system -- supports loading of BlendShape/ShapKey models compiled as AssetBundles (and/or any other model). Supports loading of models using non-KSP shaders. List of included shaders; all are compatible with KSPs part-highlighting and thermal glow functions: SSTU/PBR/Metallic -- Unity 5 Standard-Metallic workflow, diff/met/nrm/ao/glow SSTU/PBR/MetallicTransparent - Same as above, but with transparency/opacity support. SSTU/PBR/StockMetallicSpecular -- uses stock Diff-spec(a) texture, with user-provided MET maps. Aimed at converting stock parts to PBR rendering. SSTU/PBR/Masked -- PBR-Metallic based 'recolorable' texture system SSTU/PBR/Solar - Subsurface-Scattering based back-lit solar panel shader. Uses a GLOW/thickness map to determine backlight effect, along with several tunable shader parameters. SSTU/Masked -- Legacy Diff/Spec based 'recolorable' texture system SSTU/SolarShader -- Legacy Diff/Spec solar-panel shader. Includes a GLOW map for a view-direction dependent back-lit effect. Scatterer / EVE / SVE fully supported. Any/all of these functions are optional. Use only the features that you want or need. Potential uses Mods wanting to use PBR textures and rendering for their parts Mods needing custom shaders for their parts Mods needing BlendShape/ShapeKey animated models PBR stock-conversion mods Downloads: The latest releases will always be available from: https://github.com/shadowmage45/TexturesUnlimited/releases Dependencies: Requires Module Manager (not yet included) Requirements: TexturesUnlimited currently requires the use of the either the DirectX11 or OpenGL-Core graphics API. This may be activated by using the '-force-glcore' command line option to launch KSP. Other graphics APIs will 'work' (DX9, legacy GL), but will have rendering errors. User-created Configs and Texture Packs: (PM me to be added to the list, not required for use): Used in the following mods: (PM me to be added to the list, not required for use): Legal/Licensing Licensed under GPL 3.0 or later (https://github.com/shadowmage45/TexturesUnlimited/blob/master/LICENSE). Source for the plugin and shaders are provided online at: (https://github.com/shadowmage45/TexturesUnlimited) You are free to use and distribute this mod as long as the terms of the license are followed. Generally speaking this should place no restrictions if an unmodified copy is bundled in full and included in third party mod's releases. Modified copies are subject to further restrictions as are detailed in the license. Examples Examples of some of the capabilities of the shaders (all examples using parts from SSTU) PBR - Reflective and semi-reflective (reflections can range from mirror-sharp to dull based on texture setup) Masked/Recoloring (PBR and legacy versions, require special texture setups) Back-lit Solar Panel Shader + PBR shaders (+EVE + Scatterer) (solar panels still using legacy backlit shader) Reflection of surroundings; colored ambient light handling Technical Support All requests for support must be done through the GitHub issues page: https://github.com/shadowmage45/TexturesUnlimited/issues All issue tickets must be accompanied by a KSP.log file Known Issues DX9 Has cube-map blurring problems with PBR shaders, results in sharp lines in reflections even on non-reflective surfaces -- use OpenGL This is a Unity Engine problem, and not one that can be solved or worked around easily. DX9/DX11 Has incorrect faces in cube-maps, resulting in very poor reflections. Kerbals and other vessels are not visible in reflections. Momentary lack of reflections upon scene load. Any other issues listed on the issues tracker: https://github.com/shadowmage45/TexturesUnlimited/issues Future Plans Documentation on shaders properties and texture setup Documentation on configs for shader and texture replacement and texture switch module Unity 5 Standard - Specular workflow support (more shader variants) More specific shader variants - only include NRM/GLOW/AO slots if needed - or - somehow support the SHADER_KEYWORD feature to switch variants at runtime depending on features used Support vessel reflections More comprehensive texture-replacement methods; skyboxes, kerbal suits, ksc buildings? Support EVA visor reflections/etc Possible inclusion of post-processing support, at least bloom Investigation of HDR rendering support in KSP Credits / Contributors @Lilleman for his original work on using PBR shaders in KSP. While I didn't use any of his code directly, I did learn a few things from it. @HaArLiNsH for his updated/maintained TextureReplaceReplaced, which provided valuable insight into the rendering setup used by KSP @shaw for his work on TextureReplacer (legacy), and @rbray89 for his original work on the reflection code. @blackrack for including workarounds in Scatterer that allow for integration with TexturesUnlimited (by using the TR reflection camera naming scheme). @Electrocutor for his work on the Stock conversion patches, and for helping track down issues with the code/configs/shaders.
  2. AtmosphereAutopilot plugin stagnation thread I'm a flight man. After getting bored from mundane KSP launch routine I found myself enjoying my old hobby - atmospheric flight. And then the struggle was born - lack of control. SSTO's were annoying, keeping them on ascent was hard. Flying anything but overdamped dart was exhausting even with joystick. I felt like i'm in 1940-s, and it was not the feeling i wanted to get from a game I love so much. One year ago, in November of 2014, I started working on this plugin to solve those problems for me. I needed three things in my life: generic fly-by-wire, cruise control and automatic lander. It makes me sad, but after one year, I only managed to implement the first autopilot (cruise control is also implemented). Considering my free time shortage as a student, I decided to still release this mod here, for one may find it's functionality useful for him, or for another to see the potential in this mod and help it with his advice or coding\engineering skills. Autopilots list: Standard Fly-By-Wire. Control signal abstraction autopilot, SAS replacement. Here is a short flight footage of statically unstable plane I took: VIDEO. You can see roll-yaw induced isolation, AoA and G moderation, as well as general behaviour of the autopilot. Mouse Director. Plane tries to fly towards camera direction. Use middle mouse button hold + mouse turn to look above the craft and have a convenient camera angle. Precise control (CAPS LOCK) prevents from roll-over while accelerating down, as well as restrains acceleration in general. VIDEO. Cruise Flight. Maintain course, altitude, speed, fly towards a waypoint, picked on Kerbin in map view by click. More details in documentation. Videos: Quick overview by KerbalItalia dude (in Italian of course, but that doesn't really matter): https://youtu.be/k3rLK4uuJg8 Download links: Curse or SpaceDock or Github As usual, put .zip contents in gamedata. License: GNU GPL v3. Dependencies and compatibility: FAR is supported. No wind mods are supported, as well as any mods, wich are changing control surface, rcs and engine gimbaling behaviour. I recommend using Kerbal Joint Reinforcement by ferram4. If you're using "Stock Bug Fix Modules", turn off ModuleControlSurfacePlus and ModuleGimbalPlus modules in it's manager. FAQ: >FAR? - yes >Wobbling on my plane. - yes. In 99% of cases I'll know what's the problem, it's just that to fix it would be impossible under my time budget. Warm it up by pitching\rolling, tweak some stuff, it may help. Ask me, if desperate. Documentation: I tried my best at providing documentation of the code itself and writing a readme you can find in the archive, or in Git repo - https://github.com/Boris-Barboris/AtmosphereAutopilot/blob/master/README.md. Please, make sure you've examined it before asking any questions. I'm not very good at support, but i will try. FPS impact: Computational complexity of plugin (when active) - O(n), where n - number of parts. You will feel it on 100+ part crafts, and you will feel a heavy GUI, wich is full of numbers (Unity is slow with rendering strings, or maybe I'm just a bad coder), needed for debugging. Fortunately, most of the time, you don't need any GUI at all. Hotkeys: Default ones: "P" - "Master switch" you can use to toggle AA. "Shift"+"P" - toggle Autopilot Module manager GUI. "O" - default hotkey for moderation switch, when Fly-By-Wire is active. Can be changed in Global_settings.cfg in Fly-By-Wire section. Acknowledgments: Sarbian - for support of ModuleManager and consultation on numerical precision issues, and other cheesy KSP stuff. Kobymaru - he kindly helped with initial criticizm and debugging of plugin in August-September. Ferram4 - for providing a license application example to copy from, I'm new to this stuff. Morse - neo-GUI design and implementation.
  3. Nano Gauges tiny ana1og gauges for kerbalnauts current version: 1.8.2-3354 There are already some plugins that add gauges out there. SteamGauges by Trueborn for example or an older version from Bucky: Bucky-s-Instruments. Well, Bucky's Instruments are no longer updated and the Steam Gauges are nice, but way to large for my personal taste. So I decided to add an alternative: NanoGauges. They look similar but a bit smaller than those by Bucky and his gauges have inspired me to create my own ones. Readable but less space consuming gauges was the design goal for this mod. If you think the gauges are to small, try SteamGauges instead. Download: Spacedock Spacedock direct link for KSP 1.1.3 Mirror: Curse Installation: Extract the archive into the KSP home folder. Do not change the path! There has to be a folder Nereid/NanoGauges in your GameData folder! Of course you can disable any gauge and change the positions, too. New in 0.5.15: Trim Indicators (not working currently) Kottabos Space Program has done a review of Nano Gauges. His video is far better than mine and explains the usage of NanoGauges: Gauges: There are 56+ different gauges (plus 6 gauges if TAC life support is installed; another 2 if Kethane is installed, 2 gauges for Deadly Reentry) available at the moment: R ALT: Radar Altimeter V SPD: Vertical Speed Indicator H SPD: Horizontal Speed Indicator MASS: Mass of the current ship in tons G: Accelerometer (Gee-Force) ORBIT: Excentricity of an established orbit FUEL: Remaining liquid-fuel in percent FLOW: Liquid-fuel flow CHARGE: Remaining electric charge in percent AMP: Current drain on the electric charge MONO:Remaining monopropellant in percent Ox:Remaining oxidizer in percent ApA: Apoapsis PeA: Periapsis Xe: Remaining Xenon AIR IN: Air intake R AIR IN: Air intake in percent ATM: Atmospheric density SPD: Speed THRUST: Thrust TWR: Thrust-Weight-Ratio AOA: Angle of Attack (fixed in 0.4.8) INCL: Orbit inclination D TGT: Distance to target dISP/s: Change in ISP per second (only running engines) (new in 0.4.5) ISP/E: average ISP per running engine TEMP: Temperatur (needs a thermometer sensor of course; averages over all thermometer sensors onboard) O2: Oxygen (TAC life support or Kerbalism required) CO2: CO2 (TAC life support or Kerbalism required) H2O: Water (TAC life support required) W H2O: Wastewater (TAC life support required) FOOD: Food (TAC life support or Kerbalism required) WASTE: Waste (TAC life support required) EVA MP: Remaining EVA monopropellant (new in 0.3.1) O SPD: orbital speed (new in 0.4.2) MAX G: Maximal sustained gee force (with reset button, new in 0.4.2) SRB: Remaining solid fuel (new in 0.4.2) KETHAN: Remaining Kethane (Kethane Pack required, new in 0.4.2) K AIR IN: Kethane air intage (Kethane Pack required, new in 0.4.2) GRAV: Gravimeter (needs a gravimetric sensor of course; averages over all gravimetric sensors onboard) VAI: Vertical Attitude Indicator VVI: Vertical Velocity Indicator Vt: Terminal velocity deviation (not very useful in KSP 1.1.x/1.2, because of the way drag is handled) V TGT: Velocity to target Camera: current camera mode (new in 0.5.2) MACH: current mach number Q: dynamic pressure SHIELD: remaining ablative shield HEAT - heatshield temperature IMPACT: time until impact (or land) ALT: Altimeter ACCEL: Acceleration in m/s^2 H ACCEL: Horizontal acceleration in m/s^2 V ACCEL: Vertical acceleration in m/s^2 extTemp: External temperature in °C atmTemp: Atmospheric temperature in °C ORE: Used ore storeage capacity DRILL: Drill temperature ABLATOR. Remaining ablator resource on all (!) heat shields BIOME: Biome under vessel (text gauge) Coordinates (latitude): Latitude coordinates of the vessel (text gauge) Coordinates (longitude): Longitude coordinates of the vessel (text gauge) PR.REQ: Propellant Requirement gauge (in percent) Indicator gauge for Brakes, Airbrakes, Flaps, Afterbruner,... KARBNT: Karbonite in percent of the total capacity PRESSURE: Barometer (needs a barometric sensor of course; averages over all barometric sensors onboard) SEISMIC: Seismometer gauge (needs a seismic sensor of course; averages over all seismic sensors onboard) CRAP: Crap (Kerbalism required) IAS: Indicated Airspeed Vessel name Camera view direction VOR/ILS (heading of vessel, bearing of airfield/waypoint, ILS) ILS/DME (vertical attitude of vessel, distance to runway (DME), ILS) Throttle (throttle setting and relative thrust of all engines) MINI-DSKY (5 display modes) Digital Apoapsis Digital Periapsis All gauges positions are locked by default. This can be disabled in the config window and then all gauges are fully dragable and you can place them where you want. Hint: save the gauge positions in the config window or quit KSPO in the main menu, or the positions are not saved! By using the Automatic Layout in the config window, NanoGauges tries to rearrange the visible gauges in a grid. Just drag the gauge near a position were you want it to reside, and all gauges are added to the right. If you want more than one line of gauges, just move some below each other. The leftmost gauge will start a line. Hotkeys (changed in 1.2.5): RIGHT-CTRL: disable gauges / drag as group RIGHT-CTRL-KP/: hide/unhide gauges (Keypad) RIGHT-CTRL-KP*: Autolayout (Keypad) RIGHT-CTRL-BCKSPC: reset all gauge positions and their enabled/disabled states to their defaults KPENTER: hide/unhide gauges (Keypad) RIGHT-CTRL-KP1: select STANDARD gauge set (Keypad) RIGHT-CTRL-KP2: select LAUNCH gauge set (Keypad) RIGHT-CTRL-KP3: select LAND gauge set (Keypad) RIGHT-CTRL-KP4: select DOCKING gauge set (Keypad) RIGHT-CTRL-KP5: select ORBIT gauge set (Keypad) RIGHT-CTRL-KP6: select FLIGHT gauge set (Keypad) RIGHT-CTRL-KP7: select S1 gauge set (Keypad) RIGHT-CTRL-KP8: select S2 gauge set (Keypad) RIGHT-CTRL-KP9: select S3 gauge set (Keypad) RIGHT-CTRL-KP0: enable all gauges (Keypad) PGUP: select previous gauge set PGDOWN: select next gauge set WIN-MENU: select navigation point / ILS RIGHT-CTRL-TAB: opens a special gauge for alignment of gauges over several gauge set; this gauge has the same position in all gauge sets. If you want the same positions of gauges in all sets use this one as a reference All hotkeys can be changed in the config window. Profiles: In 1.2.x there is a new feature calles Profiles to automatically switch to a gauge set depending on the vessel situation or a special hotkey. To open the Profile configuration window click on the button "Profiles" in the configuration window. Enable the profiles (topmost checkbox) and change the gaugesets as you like. There are 12 Profiles Launch: Change the gaugeset whenever the vessel situation changes to launch Flight: Change the gaugeset whenever the vessel situation changes to flight Orbit: Change the gaugeset whenever the vessel situation changes to orbit Escape: Change the gaugeset whenever the vessel situation changes to escaping Flight to Suborbital: Change the gaugeset whenever the vessel situation changes from flight to suborbital Orbit to Suborbital: Change the gaugeset whenever the vessel situation changes from orbit to suborbital Other to Suborbital: Change the gaugeset whenever the vessel situation changes from any other situation than flight or orbit to suborbital Landed: Change the gaugeset whenever the vessel situation changes to landed Docked: Change the gaugeset whenever the vessel situation changes to docked Docking (UI): Change the gaugeset whenever the vessel is in orbit and the docking UI mode is selected (DEL key) EVA: Change the gaugeset whenever a kerbal starts an EVA Hotkey: Change the gaugeset whenever a key is pressed The profiles are disabled by default. You will have to enable them to use this feature. MINI-DSKY: The Mini-DSKY can display flight data in five different modes: Orbital Mode Velocity Mode ILS/Runway-Mode ILS/Glide-Mode TRIM-Mode The mode can be changed by clicking on one of the five buttons in the lower part of the DSKY gauge. Notes: NanoGauges stores its configuration in the file <KSP-home-folder>/GameData/NanoGauges.dat. There are no other writes on the filesystem. License: http://creativecommons.org/licenses/by-sa/3.0/ Changelog: Bugs: The terminal velocity gauge isn't working right. But there is not much I can do about this at the moment. Credits: NanoGauges are inspired by Bucky's Instruments. No part of the source code from Bucky's Instruments were used for NanoGauges but some of the included art. Bucky's Instruments were released under the license http://creativecommons.org/licenses/by-sa/3.0/. Thanks to Bucky for using this license. NanoGauges uses the toolbar created by blizzy78, see http://forum.kerbalspaceprogram.com/threads/60863-0-23-0-Toolbar-1-4-3-Common-API-for-draggable-resizable-buttons-toolbar. The stock toolbar can be used as an alternative. The trim indicators are based on an idea by dazoe but were completely redone.
  4. VesselMover Continued v1.7.3 Pick up, move, rotate, place, or drop landed vessels quickly and easily. NOTE: Since BahamutoD is now busy with real life and has graciously made it known that we can continue support in his stead, I'm reviving the mod in this thread and will continue its support. The original VesselMover thread is here: BahamutoD's Original VesselMover Thread Download Locations: Download from GitHub | Download from SpaceDock Installation: Extract the folder called "VesselMover" to KSP's GameData folder. For installation convenience, VesselMover is now CKAN listed, and supports KSP-AVC. KSP-AVC. This mod checks your installed mod versions against the mod's latest version. Let's you know when you need to update. CKAN. The Comprehensive Kerbal Archive Network (CKAN) Package Manager (CKAN) is a multi-platform app that manages nearly all your mods from one clean executable. Performs installs, updates, and uninstalls of your mods automatically. NOTE TO CKAN USERS: don't expect support for installs via CKAN. if the CKAN install fails, contact the CKAN folks, NOT me. Usage: Use the toolbar menu buttons to pick up, place, or drop a vessel. It must be landed or splashed down in order to pick it up. Use Tab key to change Movement Mode. This changes the base altitude and movement speeds For long distances, it works well to use "Ludicrous speed" in map mode! New!* Use the Throttle Up and Down (Shift and Control by default) to raise and lower the Altitude New!* Use Throttle Cuttoff (X by default) to Reset the Movement Mode Altitude if changes have been made. Use pitch/yaw (WASD by default) to move around. Use roll (Q/E by default) to roll, and translation buttons (IJKL by default) to rotate pitch and yaw. Use translate fwd/back (H or N by default) to auto rotate planes and rockets respectively to level/upright. Click spawn vessel to open the craft browser. Select a craft, then select a place to spawn it. It will spawn in vessel-move mode so you can reposition it or rotate it before placing it down or dropping it (free fall baby!). Support: If you expect me to provide support for issues with this mod, I will expect that you have read and will follow these instructions. Video Demonstration: Change Log: License: MIT Source: https://github.com/PapaJoesSoup/VesselMover
  5. Deadly Reentry 7.7.0, for KSP 1.4.5 - The Ariel Edition What Deadly Reentry does! (especially with KSP's new handling of thermodynamics) Deadly Reentry balances part thermal properties (max temp values of skin and internal as well as various conduction properties: skin-skin, skin-internal, emission, etc) If parts get too hot then they may catch fire. (or begin to melt; depends on if they are logically flammable or not). This begins to happen at 85% of its max temp. Some parts have had their max temp increased to compensate. Basically, think of the 85% mark as being a soft failure point leading to hard failure. As of DRE 7.6.0, this is implemented on a per area skin damage system (X+-, Y+-, Z+-). As the exterior is damaged, the interior becomes more exposed to direct reentry or supersonic heating. (the interior usally has less resistance against heating) Parts and Kerbals that experience excessive G forces for excessive periods of time may fail/die. Download latest version! (official release) If you find this mod helpful and want to throw some money away, feel free to click the donate button below! ialdabaoth (who is awesome) created Deadly Reentry 2, based on r4m0n's Deadly Reentry; this is a continuation. This continues NathanKell's work on Deadly Reentry continued, and he might contribute more at times. License remains CC-BY-SA as modified by ialdabaoth. Also included: Module Manager (by sarbian, swamp_ig, and ialdabaoth). See Module Manager thread for details and license and source: http://forum.kerbalspaceprogram.com/threads/55219 Module Manager is required for DREC to work. INSTALL INSTRUCTIONS: If you currently have Deadly Reentry installed, go to KSP/GameData/DeadlyReentry and delete everything (files and folders). Also delete any old versions of ModuleManager (modulemanager.dll for example) in your KSP/GameData folder. Extract this archive to your KSP/GameData folder * ModularFlightIntegrator is not currently required or used by Deadly Reentry as of about DRE 7.2.2. USAGE INSTRUCTIONS: Be careful how you reenter. Make sure your craft has a heatshield (the Mk1 pod has a built-in heatshield, as do stock spaceplanes; the Mk1-2 needs a heat shield from the Structural tab). For a low Kerbin orbit reentry, try for a periapsis of about 10-20km over Kerbin. do not deploy your parachute until speed has dropped below ~350m/s. (typically you should be at a safe velocity by the time you reach an altitude of 7km) Note: Deadly Reentry no longer interferes with chutes. Both stock chutes and Real Chutes have adopted their own implementations of punishing deployments at unsafe speeds. The above warning still applies except you don't get to blame Deadly Reentry about it. Compatible shield/reentry packs! Deadly Reentry Frequently Asked Questions. Changelog: Old Legacy Changelogs! Download (latest official) Source on Github
  6. Shadow Space Technologies Unlimited - Labs Division This is the public discussion thread for ongoing development of SSTU parts and plugin code. Downloads: The latest test versions may be found at: http://www.curse.com/ksp-mods/kerbal/241283-sstu-shadow-space-technologies-unlimited And are also available on Github: https://github.com/shadowmage45/SSTULabs/releases (Github will always be more up-to-date than curse, as they are auto-published there; I have to manually update Curse; so please check the GitHub link if you are looking for the latest versions) Please keep in mind that these are all testing releases. Things may break between releases. There will be bugs. Many things are unfinished and/or unoptimized. The test versions are for ironing out bugs in new features and for testing out prototype parts before they are finished; as such they will always have bugs, often severe, and there will often be unfinished parts (no textures, missing features, etc). Please only use these versions if you wish to contribute to testing and are comfortable with the state of the releases. Additional Parts / configs (by @JoseEduardo) Wiki (WIP): https://github.com/shadowmage45/SSTULabs/wiki Contribution: IVA Modeling: SSTU could greatly use someone with interest and experience in modeling IVAs. If you think you are that person, please contact Shadowmage through PM to work out the details. Testing: If you would like to contribute to pre-release testing (and get to try things out in their pre-release state), please follow the link above; the most recent test version will be at the top. Please submit issue reports for any problems you encounter via the GitHub issues tracker: https://github.com/shadowmage45/SSTULabs/issues (If you do not report the issue there, it will not be resolved; issues posted in the thread or through PMs will be forgotten about and likely never fixed; so please, do the organized thing and use the bug-tracker). Configs/Patches: I welcome pull requests and contributions for adding patches for mod compatibility, adding new part configs, or fixing issues in existing part configs. Documentation: One very major part of the mod that could greatly benefit from public contributions is the Wiki: https://github.com/shadowmage45/SSTULabs/wiki While this is the 'dev version' wiki, I will be using it to form the basis of the public release wiki; so any/all information and details that can be filled in now will be transferred over to the public release repository and wiki when it is created. Feedback, suggestions, comments, etc: Please feel free to post feedback, suggestions, questions, etc regarding development releases and/or any posted previews. Even if you are not on the testing team, I still value your feedback and suggestions. Please use the issue tracker for any 'official' feature requests; it may be found at: https://github.com/shadowmage45/SSTULabs/issues Bug Reports: Please submit issue reports for any problems you encounter via the GitHub issues tracker: https://github.com/shadowmage45/SSTULabs/issues. No other method for submitting bugs will be supported; posts on the forum or through PM will be forgotten about before I can ever get to them. Opening up a ticket ensures that your report does not get lost in the forum or forgotten about. No ticket = no fix. Enough with the disclaimers, and onto the parts! The Parts: The goal of SSTU is to provide low-part count, CPU-efficient parts for common uses. To this end many of the parts are designed with additional integrated functionality beyond the base functions, for instance integrating RCS ports and engine(s) into a fully fledged service module. I have tried to maintain a stock-compatible appearance, though as I am not an artist or modeler (at least not by training/profession), how well this has worked out is subject to opinion. Master list of parts; current, planned, the whole lot: https://github.com/shadowmage45/SSTULabs/wiki/Parts---Master-List Ship Core: Engines A set of engines in many varieties, including pre-built engine clusters. Many more engines, mounting options, and cluster designs will be added over time. Ship Core: Series A A set of parts modeled after the Soyuz CSM stack. Includes Orbital Module, Descent Module, Service Module, and LAS. Ship Core: Series B A set of parts modeled after the Apollo CSM stack. Includes two command modules (one with integrated heatshield and parachutes), launch abort system, and Apollo-inspired service module. Ship Core: Series C A series of parts heavily inspired by and based on current NASA - SLS project. Includes representations of SLS upper stack initial configuration, and lifter parts designed in the vein of the lower/core portions. The upper stack is designed to allow for a low-part-count manned orbiter setup, while the lower-stack parts are intended for super-heavy-lift capabilities. Command module and upper-stack are 3.75m, while the lower-stack lifter parts are 5m. Ship Core: General A line of generic / utility parts. Fairings, RCS, Science experiments, and procedural decouplers of various types. Includes a full line of configurable/dynamic fuel tank parts in standard cylinder, sphere, R-7 booster (integrated decoupler), and upper-stage (integrated rcs) form factors. Includes a full set of truss based cargo bay modules. Also includes a full line of interstage fairings and petal adapters, and standard payload fairings. (Many parts not shown in album) Lander Core A series of parts specially crafted to enable low-part-count non-atmospheric lander designs for use in the stock Kerbol system. Station Core A line parts for low-part-count station use. Includes inflatable Bigelow-inspired inflatable modules, inflatable centrifuge modules, ISS inspired habitat and lab modules, and a line of TKS/DOS inspired single-part station cores (integrated solar, engines, rcs, docking ports, sas). Also includes a full line of stand-alone solar panels and a 'welding' docking port. (Album not yet available) Craft Files None currently available, will possibly start becoming available when the mod has reached a stable state (not for the foreseeable future). Additional Addon Compatibility and Integration RealPlume -- Optional but highly recommended. SSTU includes a set of patches for RealPlume for all engines as well as most other engine-enabled parts. More will be added over time. Stock effects are also included, but options and configuration for those are much more limited. If you want pretty-looking exhaust effects, get RealPlume. MechJeb -- If MechJeb2 is installed, Command Pods (and some service modules) include a built-in MJ module. The tech-unlocks for these are based on the default MJ tech-settings. Kerbal Joint Reinforcement -- As of KSP 1.2+, KRJ is no longer necessary, as the stock Auto-Struts can eliminate most of the wobbles. Might still have utility on extremely large craft designs, but should no longer be nearly-mandatory. USI-LS -- Patches for most parts are included, and will be enabled when the requisite mods are installed. These patches add a few days worth of life-support to each of the pods and some of the service modules. TAC-LS -- Some patches are included. Not up to date, and not all parts are patched. ConnectedLivingSpace - A simple CLS patch is included to add CLS passability to all SSTU crewed parts. FAR - Unsupported. You are on your own if you choose to use FAR. Any problems involving FAR needs to be brought up in the FAR thread. RO/RSS - Unsupported. Take any support requests regarding RO to the RO threads. KR&D - Known to be incompatible. Some config edits can be made to allow them to work in the same install, but KR&D cannot adjust stats on most SSTU parts. Introductory video by MrMeeb Known Issues IVAs - Many are incomplete. WIP. They'll be finished 'eventually'. Textures - Many unfinished textures. Please see the Github issues tracker for a complete list of known issues: https://github.com/shadowmage45/SSTULabs/issues Future Timeline / Future Plans Please see the Github Milestones and Issues Tracker to see future/current development plans. Milestones (long-term plans): https://github.com/shadowmage45/SSTULabs/milestones Issues Tracker (current in-dev stuff): https://github.com/shadowmage45/SSTULabs/issues Legal: Source: All source code and compiled plugin binaries for this addon are distributed under the GNU General Public License (GPL) 3.0, except where noted below, where that code is distributed under its own license. The text of this license may be found at: https://github.com/shadowmage45/SSTULabs/blob/master/LICENSE-SOURCE.txt EXCEPTIONS: None at this time Source code for plugins is included in all releases packs (source may also be found for the most current version at: https://github.com/shadowmage45/SSTULabs/tree/master/Source). Models/Art/Configs All Assets and Artwork in this addon are licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License, except those areas noted below, which are distributed under their own licenses. The text of this license may be found at https://github.com/shadowmage45/SSTULabs/blob/master/LICENSE-ASSETS.txt EXCEPTIONS: None at this time ModuleManager Module Manager is distributed under its own license (CC-SA). Source code and licensing details may be found at: https://github.com/sarbian/ModuleManager Community Resource Pack Community Resource Pack is distributed under its own license (CC-BY-NC-SA). Source code and licensing details may be found at: https://github.com/BobPalmer/CommunityResourcePack Mini-AVC This mod includes version checking using MiniAVC. If you opt-in, it will use the internet to check whether there is a new version available. Data is only read from the internet and no personal information is sent. For a more comprehensive version checking experience, please download the KSP-AVC Plugin KSPWheel KSPWheel is a dependency for the SC-E (shuttle) landing gear, and is distributed under its own license (GPL 3.0+ https://github.com/shadowmage45/KSPWheel/blob/master/License-GPL3.txt). It may be found at: https://github.com/shadowmage45/KSPWheel The Team: Development: Shadowmage - Modeling, animation, texturing, plugin code, concept development, and most configs (balance). And a special thanks go out to all others who are making this add-on possible: JoseEduardo - Co-Conspirator, Testing and feedback, RO and RF Integration, Craft files, additional texture sets blowfish - Testing, feedback, and concept development MrMeeb - Intro video, testing and feedback. StratoChief - RO and RF Integration VenomousRequiem - Concept development and feedback. MeCripp - Testing and feedback _Augustus_ - Testing and feedback drtedastro - Testing and feedback riocrokite - Testing and feedback, concept development for part reduction falken - Testing and feedback martinezfg11 - LC-POD IVAs Jimbodiah - Craft repository and testing -if I missed you on this list, sorry! (feel free to send me a PM if you think you deserve a mention in the credits) Donations: I work on this mod during my spare time, and use vast amounts of caffeine in the process. If you would like to help contribute to my coffee fund, please see the link below. This is purely optional, but can help keep me motivated and energized ( = more work getting done!).
  7. THANK YOU GER_SPACE FOR SAVING WINDOWSHINE! Thank you @Teflon_Mike for the logo! Gif with GemFX and KSPRC v2 courtesy of @cobbman11 Video (-v2) Pictures: Album on imgur, Gif in VAB Downloads: WindowShine is dependent on TextureReplacerReplaced managed by @HaArLiNsH (TextureReplacer maintained by @RangeMachine for 1.2x) and ModuleManager maintained by @sarbian. Make sure to install them both first. KSP 1.3+ WindowShineTR-v16 TextureReplacerReplaced latest ModuleManager latest KSP 1.2- WindowShineTR-v12.4 TextureReplacer v2.5.4 ModuleManager 2.7.6 Mod Support packs (for KSP 1.3+) Thank you @miromed! Dropbox folder Mod support pack installation: Check the Dropbox folder and make sure your mod is supported Install your mod Install WindowShine Install the mod support pack How to add reflections to your own mods License: Link Shameless plug: If you've enjoyed this mod you might also like the other stuff in my signature! - I hope you enjoy.
  8. Project Manager DOWNLOAD On GitHub Overview. Project Manager is a small and unintrusive plugin to help organise craft files into "projects" whilst ingame. One of the main benefits of this is that you can give your crafts more helpful and descriptive names (I.E. "Two stage Mun Lander"), but launch them with more "poetic" and organised names - allowing better role-playing and a more structured career game. Projects are stored per-save file. Examples. Imagine you have three craft files: [STS] Discovery [STS] Atlantis [STS] Endeavour As these craft files have a tag in the name (in this case STS) they will be launched with the project name instead of the original craft name, and sequential numbering will be applied. On launch, these crafts would become: STS 1, STS 2, STS 3... and etcetera. Crafts without the square bracket tags will be completely unnafected! Just in case you have any 'special' launches planned Future Plans. Tracks more stats about a project, how much you have spent on it and maybe the launch to recovery ratio? GUI to control projects, rather than the tag system. Please, feel free to give constructive criticism, I will listen. Any suggestions, ideas, or bugs found are greatly appreciated. Licence. Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License
  9. Contract Configurator - A config-file based solution for creating new contracts! How it Works Contract Configurator exposes various hooks into KSP's contract system through a standard config file syntax. This means that modders using Contract Configurator can create new contracts without writing any code. The config file format has 5 basic sections: Contract Summary - This contains all the summary text, expiry/deadline dates, and reward information. Parameters - These are mappings to the stock ContractParameter classes which specify what the player has to do to complete the contract. Requirements - This is what is required before the contract will show up. Most of the ProgressTracking information is supported, along with a few other things. Behaviours - These are behaviours that are applied at the contract level. A behaviour can create additional objects related to the contract (such as spawning Kerbals), be used to store persistent data or any number of other things. Data nodes - These define new data for use within the contract using Contract Configurator's powerful expression language. And if the provided parameters and requirements aren't enough, Contract Configurator is extensible. New parameters and requirements can be added in as little as a dozen lines of code. Download Contract Configurator can be downloaded from GitHub. Source The full source and test configuration is available on GitHub. Documentation The user guide is hosted on the GitHub wiki. Change Log Version Checking This mod includes version checking using MiniAVC. If you opt-in, it will use the internet to check whether there is a new version available. Data is only read from the internet and no personal information is sent. For a more comprehensive version checking experience, please download the KSP-AVC Plugin. Recommended Mods The following is a list of mods that enhance some of the things Contract Configurator does: Waypoint Manager - this will help with any contract using the stock waypoint system by drawing the waypoints in the flight view. Makes hitting targets more accurately much easier! License Contract Configurator is licensed under the MIT License. RemoteTech integration (CC_RemoteTech.dll) is licensed under GNU GPL v2.0. Like what you see? Consider donating to the coffee fund! It will not go directly to supporting this or other mods under my care, but it may keep my motivation up!
  10. Updated for KSP 1.3.1 Once upon a time there was LAZOR mod from famous Romfarer, which included a useful docking camera, that displays the videostream a small window in the main flight scene. However, it has not been updated for a long time, and refused to work in recent versions of the game (or I could not start it). Nevertheless, I like it output style of information and I was bored without this service. That in turn has led me to attempt to revive the aforementioned docking camera. And YES, i know about Docking Port Alignment Indicator, HullCamVDS, cameras for RasterPropMonitor etc. But i do not know about any working cameras in window. New shaders example: So, what we have here. Docking-camera itself, which can be integrated to any part (MM patch enclosed for the docking port modules). It looks ahead by the vertical axis of the vessel's and displays a minimum of necessary info for the docking maneuver - namely, range, speed, angle, alignment and when the correct trajectory occured - time prior to docking with the mark that such trajectory will lead our vessel to dock without additional actions (small lamp will become green and will show time to docking). camera window has three size presets. It also has three viewing modes: color, Black and white and infrared. Powered zoom function. Also, there is a button to remove flight data from the screen. Furthermore, effect of television interference can be added. The range of the camera,parameters of night vision (RSMA) and presence of noise - can be configured through CFG. Camera requires a target to operate. In addition the ugly external camera enclosed. It can show videostream only and also has three modes of vision and is able to rotate on two axes. For cameras, installed under the belly of the aircraft (which gets inverted upside down) there is the mode of rotation of the image. In the CFG of the partcamera some meshes could be configured for use with other camera model. All cameras have a title with its number, and also can work a few pieces at a time. Docking camera reporting its target on its window title. There is an experiment on part camera - a try to reproduce a surveilance (spy) activity. You need to be at a distance less than 1000 m near any targetable thingie, catch it on camera's screen and targeted. press "⦿" button. A ray will be shoot. If all requirements have met and there are no obstacle on ray's path - you'll should get experiment results, if something wrong - you just spend one bullet. Experiments is limited by bullets (4 yellow balls around cam, dissapearing one by one each time). I thought it will be interesting if contracts. Camera has 3 presets of shaders (noisy TV 1960th style, TV 1980th style and standart (color, b/w and nightvision). available via button, appearing when blizzy toolbar is installed. Also, by toolbar button you could find info about nearby cameras installed on other vessels in transmission range. If camera has been activated on some vessel, but you drive other one - a new window from distant camera will appear when distance from first one will become less than 2500 (or 10k (customizable)). If you want you can use "look at me" mode by activating it on distant camera. "Targetcam" and "follow me" modes on your active vessel (set camera position using scrollers). The cameras can transmit the videostream to nearby vessels, but only at a distance of up to 2 500 meters. You can change this unload range via toolbar button. Configuring examples History Download from Spacedock DONATE Source installation: remove previous version and just extract an archive into Gamedata. requirements: ModuleManager recommends: Blizzy Toolbar
  11. So I have been considering over the past month or two the creation of a life support system tailored to fit in with the USI mods, and also bring together some the bits I like about other mods already on the market, and add a few of my own tweaks, etc. This is pretty much my interpretation of how, if I were to go buy Kerbal in a store, I would expect a stock-ish life support system to work. I've been playing with it and minus a few refinements am very happy with the result. With that, I am pleased to introduce USI Life Support. Basic overview stuff. Mechanics wise, it's pretty simple. Kerbals require supplies. Kerbals also require EC. these are both on the same timer, so I just check supplies for the status window. When Kerbals are done consuming supplies, leftovers, scraps, and 'anything else' is either tossed overboard, or (if storage is available) tossed into a 'mulcher'. The resulting organic slurry is called 'mulch' and can be used to feed greenhouses, etc. at the player's discretion (or in the case of MKS, converted into Organics at varying levels of efficiency). 15 days out, the visuals go yellow (sorry, no auto-warp-slowdown-thingie, use KAC). When supplies run out, things go into the red. If you leave them unsupplied for 15 days... well, they just say 'screw it', get grouchy, and quit. They are still in the pod. they still take up a seat. But they can't fly, can't EVA, and essentially do the Kerbal equivelant of spinning around in their office chairs, refusing to work, until resupplied. This is a design consideration in that all of us, at least once, has just flat out done goofed, and lost a whole colony of Kerbals via glich or other sadness. Yes, death/despawn will be an option. Not the default one tho. Mechanics wise, they are transformed into tourists, as they are essentially on a self-imposed vacation Once resupplied, they are happy as clams and will return to work. While on EVA, they will not quit. But if they are brought back aboard a ship and have been starved (and can't find a hot meal waiting) they will promptly go in strike, and begin their self imposed vacation immediately. Orange suited Kerbals (Jeb, Bill, Bob, and Val) are immune to the ill effects of life support. They will still consume supplies if given, but do not leave the job, because they are just that awesome. This always gives a player (especially a new one) an 'out' to test out a manned mission before actually committing your other kerbals, etc. to a horrible fate of snack deprivation. Yes, it's a bit more 'Kerbal' than TAC-LS, but also a lot more predictable and with harder consequences than 'Snacks'. It does, however, feel 'right' (at least to me) from a design standpoint. Parts wise: Three inline storage compartments. No extra recyclers needed. No resourced added to pods (the 15 day window covers all of the Kerbin SOI so no point). No random contracts. MKS/OKS Changes MKS wise, closed loop just got a lot harder/more interesting (depending on your point of view). The old C3 (now renamed to the Pioneer Module) will have a basic mulcher and greenhouse and can do recycling at 50% efficiency for up to four Kerbals. Kerbitats operate at 75% efficiency. Mk-IV modules (once released) will operate at 90% efficiency off-world, 100% efficiency on the surface (pulling in of local material is inferred, no extra drills required). Supplies come from organics. Organics come either from mulched supply waste, or from a combo of water/substrate. So surface bases are easier to get to self sufficiency - if they are on water/substrate deposits. Orbital will always be a pain - so you will need to fly up fresh organics or keep large stores. And since organics creation is not tied to the life support loop, building large surface farms is also pretty easy now. Dealing with hungry Kerbals So you can do some very interesting things. Run a command pod to dock reviving supplies/snacks to a starved out colony ship. Use one of your orange-suits to lead a mission and conserve supplies. Note that Kerbals are pretty damn aggressive about getting their snacks - the only way to lock them out of the biscuit tin is to click that little feed button by the resource on a part (same way we reserve some battery power for a probe). Note that a Kerbal about to starve (i.e. no supplies for 15 days) will in fact happily break open said biscuit tin. witty screen message included Design side note: So 'Mulch'. Waste was used, and too generic. And I wanted something that showed that the stuff was kinda useful, not edible, and felt more 'kerbal' (and less like poo!) if that makes sense. The idea of Kerbals tossing all of the spare bits and scraps into a contraption and getting out a semi-useful generic organic slurry had a certain appeal, hence the abstracted mulchers and mulch resource. The resource itself is just 'supplies' and has the visual representation of a translucent, semi-rounded green cube. What are they? Well... leave that to the imagination. But the labeling will read 'N.O.M.S. - (Nutritional Organic Meal Substitute)' on the tins LICENSE: Configuration files and code are licensed under the GPL v3 license. Assets, including Models (*.mu) and Textures *.png/*.dds) are All Rights Reserved. If you wish to use any of these assets in your project, just ask nicely DOWNLOAD: Get it at the GitHub Repo! https://github.com/BobPalmer/USI-LS/releases
  12. Because UbioZur has kindly allowed to update his work, Alewx and girka2k have taken care to update and maintain this great mod. From the UbioZur's original thread: ----IMPORTANT---- These are the basic requirements that are necessary for any support of the issues that are happening. -What KSP Version is used -What Welding Version is used -Which Mods are installed -Preweldment craftfile -KSP.Log If you do not provide this information, do not expect great help. ----IMPORTANT---- Please read carefully "Known limitations" and "Known Issues" sections before using this mod. The program is still under heavy development, so you may encounter problems when using it, and the result of it's work may not satisfy you. In this case, do not hesitate to report it here. This mod includes version checking using MiniAVC. If you opt-in, it will use the internet to check whether there is a new version available. Data is only read from the internet and no personal information is sent. For a more comprehensive version checking experience, please download the KSP-AVC Plugin. Download version 2.5.3 for KSP 1.4.2 Download version 2.5.2 for KSP 1.3.1 Download version 2.5.0 for KSP 1.2.2 Download version 2.3.3 for KSP 1.1.2 Download Config and Icons for very useful Filter Extensions mod. Examples for welding (even including single animated parts): Latest changes: 2018-04-06 - Version 2.5.3 - Continued Recompiled for KSP 1.4.2 2017-07-09 - Version 2.5.2 - Continued Recompiled for KSP 1.3.1 2017-07-09 - Version 2.5.1 - Continued Recompiled for KSP 1.3.0 Fixed empty WeldedMeshSwitch slots 2016-11-15 - Version 2.5.0 - Continued New Feature: Internal merging Welding parts with internals will now create new internals for this weldment Improved mass calculation precision 2016-11-15 - Version 2.4.4 - Continued Fixed NPE with certain parts Full history of changes: Installation As usual, extract the GameData folder from archive into the main folder where your game is installed - for example: C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program WARNING! Don't delete GameData\UbioWeldingLtd\Parts folder or you will lose all your weldments! Usage Create the set of part you would like to weld inside the VAB or SPH Press button in stock Launcher Follow the instructions. Weldments will be saved in the GameData\UbioWeldingLtd\Parts folder Reload game and then you will have your weldment available on the part list. (You can try to save time by enabling the "Database autoreload" option in settings, but it should be borne in mind that this mode is incompatible with many mods and can cause problems.) Known limitations / supported and unsupported mods If you weld together multiple RCS, you will not be able to use the weldment for rotation - the game doesn't allow it. Don't include in your weldment more than one Leg/Light/Solar panel/Science experiment - it is game limitation. The main restriction is not to weld together two identical parts from this list. So for instance, you should not weld two legs together. One leg and one illuminator on the same weldment does not present a problem. Also it is better not to combine together several Docking ports in one weldment. If you weld Engine with integrated Alternator, your weldment always will have Electricity amount equal to 0 even if you have welded a battery to it (Bug/Feature of the game). Multiple Engine with Fairing are not supported by the game. Generally, I suggest not include the engine(s) in your weldment. Crew Hatch: Game allow them only near the CoM of the weldment or hatch will be unusable. Game won't allow several hatches. Winglet/wings/control surfaces/parachutes: they can/must work incorrectly after welding. Wheels are cuasing problems with craft spawns. Other limitations will be described Soon(â„¢) Incompatible mods: You can have all these mods installed, and will have no problems. But welding the parts from them will lead to unusable weldment. Procedural parts Infernal Robotics Compatible mods: Tweakscale Hullcam VDS (only one camera per weldment) Remote tech (don't add more than one antenna to your weldment) Feel free to share in this thread what mods works and don't work for everyone to know. Known Issues welded engines are causing a major trouble, already when they are welded and also as a new part. Other stuff Sources The latest version for 0.25 The latest version for 0.24.2 Legal stuff Code and artworks are licensed under the Attribution-NonCommercial-ShareAlike 3.0 (CC BY-NC-SA 3.0) creative commons license. See http://creativecommons.org/licenses/by-nc-sa/3.0/legalcode for full details. This work based on malkuth's update for UbioZur's original code. All rights to original source code belong to UbioZur. The rights to malkuth's code update belongs to malkuth The rights to subsequent code changes and artworks belongs to Alewx and girka2k Thank you UbioZur for kind permission to continue your work! <--- If you suddenly decided to press star to raise reputation, do not forget that support of this mod is our joint work with Alewx and Girka2k so please raise his reputation too!
  13. S.A.V.E automatic backup system current version: 1.5.2-3063 Have you experienced some kind of major bug in a plugin? Did your save game got corrupt or have you lost all your ribbons in FinalFrontier, because of a single stupid mistake the developer (who is me unfortunately) has made? No? Well, you are lucky then. If you have experienced this, S.A.V.E may come to rescue. This plugin will handle automatic backups of your save games for you to prevent loss of data. As most other software, this software comes with no warranty of any kind. If you use it, you do it at your own risk. All releases until 0.9.11-319 will not backup your ship templates! And a word of warning: I have tested this on Windows only. I do not know, if S.A.V.E works correctly on a MAC or on Linux. Important! Please read! This plugin will store the backups at the location on the file system that is set by the user! It may write on any location on the file system if the user changes the default location. Please keep this in mind, if you are setting S.A.V.E to a different backup location. The default location for backups is: <KSP-HOME>/backup. There is a subfolder for each save game. Each backup is stored in a folder YYYYMMDD-HHMISS. Download: Spacedock license: LGPLv3 Features: Completely automatic; it will create a backup after a save Backups can be stored anywhere in the file system ("a king who must say 'I'm the king' is no real king" -a backup on the same hard disk is no real backup) Configurable backup interval Configurable minimal number of successful backups Configurable maximal number of backups Configurable time in days to keep backups Backup of all games at once Restore functionality Automatic backup before a restore is done. Compressed backups Cloning a game from a backup Screenshot: Hints: Setting "days to keep backups" to 0 will keep backups forever (as long other constraints are not violated). Setting "max number backups" to 0 will keep an unlimited amount of backups (as long other constraints are not violated). Setting both "days to keep backups" and "max number backups" to 0 will never delete any backup (not even failed ones). The value of "min number of backups" determines the number of successful backups that have to be kept in any case.
  14. DiRT - Drop-in Replacement Textures Latest Release: v1.4.3.0 (for KSP v1.4.3) Source code available on Github: https://github.com/cydonian-monk/KSP-DiRT The Whats What Is This? DiRT is a fork of Shaw's TextureReplacer, updated for newer versions of Kerbal Space Program. The intent of this fork is to remove features and simplify the plugin. It allows zero-configuration texture replacement by dropping your correctly-named replacement textures into the "GameData/DiRT/Textures/" folder. What Does It Do? Replaces in-game textures and normal maps with like-named textures in GameData folders as configured. Optionally exports a list of the game's replaceable textures and normal maps to a text file in the plugin's GameData folder. What Does It Not Do? Absolutely anything else. Specifically, this plugin does not perform Active Texture Management, does not compress textures, does not convert PNG files to RGB, does not generate MipMaps, and does not allow suits and heads to be mapped to specific kerbals. It also will not pop popcorn for you. If you need any of those features (except popcorn), please consider using "Texture Replacer Replaced", "Texture Replacer", or one of TR's other forks. Additionally, this plugin does not replace NavBall textures (or if it does so they may or may not be replaced correctly). For NavBall textures, please consider using "Navball Texture Changer". I strongly suggest the use of DDS/DXT1 or DDS/DXT5 texture files with pre-generated MipMaps (where appropriate). The Whys Why Did I Do This? Because I needed it. Because others might find a use for it. Why Should You Use This? You only want to replace a couple textures, such as the skybox or the normal map used by the --redacted--. You're running KSP in a memory or resource constrained environment and want to replace textures without extra overhead. You want a list of textures and normal maps in use by KSP. This plugin is provided in the hope that it will be useful. I've been using it on my increasingly-antique MacBookPro to replace the SkyBox and Jool's cloud textures. With per-part texture switching now present in the base game and the suit switching mechanic coming in the expansion, I suspect others might also find a use for such a feature-limited plugin. Why Should You Not Use This? You want to replace NavBall textures. You want to map faces or suits to specific kerbals. You like menus and nice UIs. You don't need it. You don't like it. The Wheres Where Can You Download This From? The most recent release, as well as all previous releases not deleted for causing corruption to the basic fabric of reality will always be available on GitHub. If for some reason GitHub disappears into the void, it was (likely) not my fault and I will provide an alternate download location. https://github.com/cydonian-monk/KSP-DiRT/releases Where Do You Put It? There is a GameData folder in the zip file. Inside of that GameData folder there is a DiRT folder. Once you have downloaded the zip file, copy that DiRT folder into the GameData folder of your KSP installation. Do not copy the GameData folder into the GameData folder, as that will achieve nothing. Do not copy your KSP installation's GameData folder into the zip file's DiRT folder, because why would you even want to do that? Where Can You Get The Source Code? Same place as the plugin: GitHub. The source is also available in a raw form (minus the Visual Studio bits) in the plugin's download zip. https://github.com/cydonian-monk/KSP-DiRT Where Do You Find the Names of Replaceable Textures? Change the value of the "exportTextureNames" field in the "GameData/DiRT/config.cfg" file to "True". The next time you start the game DiRT will write a file named "ExportedTextureList.txt" into the very same "GameData/DiRT/" folder. Determining which texture and normal map does what will require a bit of creative reasoning, but many of them are obviously named. (Warning: There are things which some might consider to be spoilers in the texture and normal map names. Read at your own risk.) Where Can You Get Textures? Anywhere. There are many textures available on this forum and across the endless intertubes that are appropriate for KSP. If you find one you like, rename it to use the name of the texture you want to replace and drop it in the "GameData/DiRT/Textures/" folder. (If you give me a few days to finish them, I'll have my suit textures available for download. I need to finish cleaning some things up first.) Where Can You Put Texture Packs? Anywhere in GameData, provided you have the correct config files. This plugin will load textures from any config file which includes a "DiRT_Config" root node and a "TextureFolder" entry inside that node. If for some bizarre reason you want to distribute a texture pack for this plugin, just drop one such config file into your pack's folder, set the "TextureFolder" to the GameData-relative path where your texture files live, and DiRT will handle the rest. See the "config.cfg" file provided with the plugin for an example. If you've created a texture pack using a DiRT config file, leave a note and I'll add a link to it here. The Other Stuff Planned Features There are none. (Sorta. Maybe.) While this plugin is intended to serve as a building block for a future project (hence the "phase 1" subtext), the basic premise of dirt-simple drop-in texture replacement is not expected to change. Phase 2 will be discussed at a future date. Technical Support If it's broke I'll try to fix it. If it's not broke I'll still try to fix it. If you find something weird or wrong or kraken-inspired please mention it. Raise issues here, in a private message, or on GitHub. Use your best judgment. I may or may not need logs depending on the issue. This plugin is provided as-is and with absolutely no warranty, even in cases where I might want otherwise, but especially in jurisdictions where I may be required to provide some strange or inhumane warranty. It is not responsible for feeding your cat, correcting the ills caused by Daylight Savings Time, or cleaning up after the questionable garbage collection in Unity. Known Issues I'm a C/C++ programmer and C# is D♭. I've probably missed something obvious. A Request For Tests I have tested this plugin on the following Squad/KSP-store-bought English-language versions of KSP: Windows 64-bit (in Windows 10): 1.4.0-1.4.3/MH MacOS 64-bit (in MacOS Sierra 10.12.6): 1.4.0-1.4.2/MH This plugin is untested on all other platforms and versions (specifically Linux, as none of my Linux boxes are capable of running KSP), and has not been tested against any Steam installs (which should be fundamentally identical; I'm not worried about Steam). If you happen to use this plugin on one of these other platforms, please send me a note regarding issues or lack thereof. Thanks! License and Credit This plugin preserves TextureReplacer's original MIT license, provided below. The majority of the work I did for this plugin involved liberal usage of the Delete key, excluding my rework of the code used to log texture and normal map names. The bulk of the remaining code was originally written by @shaw. I do not think any of @rbray89's code remains in this plugin, but he deserves a mention anyway.
  15. ** New ** Vessel to vessel crew transfers! Ship Manifest is a tool to manage your ship's "things". I originally started with Crew Manifest as a basis for this work. My great thanks go out to vXSovereignXv for creating Crew Manifest, and Sarbian for contributions to and continuing maintenance of Crew Manifest. I've now re-imagined it into Ship Manifest, Crew transfers are now only a small part of what SM can do. Ship Manifest moves crew, Science and Resources around from part to part within your ship or station. It also manages docked vessel refueling, hatches, deployable Solar Panels, antennas and lights. Kinda like your Ship's bridge... Ship Manifest has a LOT of flexibility and a lot of Options. So much is available that is NOT seen in a default installation (Realism mode set ON by default) that you may be missing a lot of what SM has to offer. Please go to the Settings Window to see what options are available, and play with them. You will be surprised at the number of features that exist in this tool. I believe in choice, so you can configure SM to be pretty much exactly what you want. You want a "realistic" experience? Check. You want to be a god and chafe at realism mode restrictions? Check. I also invite suggestions for things you would like to see. Current Version: 5.2.1.0, 17 Mar, 2018 -- Download: SpaceDock | CurseForge | GitHub (all releases). Also supports CKAN and KSP-AVC for your convenience in updating. NOTE: This version of SM is NOT backwards compatible. It will not work on KSP version 1.3.1. License: CC BY-NC-SA 4.0. Original license on Crew Manifest was do as you want. I felt the original and contributing authors deserve due attribution, since this is a derivative work. Source code (and all releases): http://github.com/PapaJoesSoup/ShipManifest Ship Manifest WIKI: http://github.com/PapaJoesSoup/ShipManifest/wiki No Mod Dependencies!: Ship Manifest is mod independent. You don't need any other mods to use Ship Manifest. However, if you install the mods below, Ship Manifest provides specific support for their features. Toolbar, by blizzy78. This mod is the "original" and a great alternative to the stock toolbar. Connected Living Spaces (CLS) by codepoet. This mod provides the player with graphical information on livable spaces in a ship. It shows you where you could go internally on your ship. Module Manager. This mod allows you to extend the configurations on your parts. Used by CLS. RemoteTech. This mod overhauls the unmanned space program and makes antennas much more important. Very powerful mod. DeepFreeze. This mod provides part(s) for cryogenic freezing of kerbals for long duration flights. JPLRepo has taken over maintenance of this mod. USI Kolonization System (MKS/OKS) Inflatable Modules. Very cool mod for compacting your trips and station builds. KSP-AVC. This mod checks your installed mod versions against the mod's latest version. Let's you know when you need to update. CKAN. The Comprehensive Kerbal Archive Network (CKAN) Package Manager (CKAN) is a multi-platform app that manages nearly all your mods from one clean executable. Performs installs, updates, and uninstalls of your mods automatically. NOTE TO CKAN USERS: don't expect support for installs via CKAN. if the CKAN install fails, contact the CKAN folks, NOT me. What's New: Version 5.2.1.0 - Release 17 Mar 2018 - KSP 1.4.1 Edition - New: Recompiled for KSP 1.4.x compatibility. - Fixed: Bug in Selected Target Mouseover. CLS Target Crew Part was incorrect color. Git Issue #53 - Fixed: Updated icon graphics to restore quality after Unity update in KSP. Increased image sizes to 128 x 128 px (Git Issue #52) - Fixed: Sometimes the Manifest window will not appear. Git Issue #49 - Fixed: gain/loss of resource(s) in transfers. (thanks to Arivald Ha'gel for the PR #48!) - Fixed: RT antennas not appearing in the control window. PR #48 - Fixed: Kopernicus Solar panel detection problem (Git Issue #47) PR #48 - Fixed: Correct version file data to agree with release version. Git Issue #46 Installation: 1. Remove the ShipManifest folder from your GameData folder before installing any new version.. 2. Overwrite your GameData folder with the contents of the archive. Ship Manifest is KSP-AVC aware and is CKAN indexed Support: If you expect me to provide support for issues with this mod, I will expect that you have read and will follow these instructions. Change History: This work was originally based in large part on Crew manifest 0.5.6.0 by xxSovereignxx as modified by Sarbian to work with 0.22. It has since been completely reworked and massively expanded. Videos: - Kottabos did a fine review here: (Feb 28th, 2014). It was very educational for me . I've long since fixed the bugs and added much more... Screenshots: Donations: I wrote and support SM (and other mods) as it is an opportunity to give back to the community I love in some small way. But, some folks have asked me how they could donate. It completely blew my mind. So, I've added a donation button. It is Completely voluntary, absolutely amazing, and I very much appreciate the gesture!
  16. Are you tired of your Kerbals complaining about having nothing to do during long flights? Do you want to give them more buttons to push, and maybe some displays so they can keep track of what's going on? Then look no farther. RasterPropMonitor is a plugin and toolkit originally by Mihara that provides functional props within your IVA. It was originally designed for the displays of the ALCOR capsule, but it evolved to add more features and widgets, dragging the Kerbal Space Program into the 21st Century. RPM includes some overrides for stock capsules (and a few mod capsules) to show off what can be done, but there's far more in the plugin than these examples can show. DOWNLOAD: From GitHub. IVAs require Module Manager, which is not bundled with this mod. CKAN USERS: I do not support installing by CKAN. If you have questions regarding this mod being on CKAN, or missing from CKAN, you can talk to the people on the CKAN thread. If you installed this mod using CKAN, and you are having problems with it, you must uninstall this mod through CKAN and install it manually to make sure it is not a CKAN installer issue. If you have not taken that minimal step, I will not provide additional support. I am not involved with CKAN - installation issues need to be taken up with them. HOW TO GET HELP: Did you use CKAN? Look at the previous entry. Otherwise, read the first few entries in the FAQ on GitHub. DOCUMENTATION: Want to tweak an IVA to your liking? Documentation is on GitHub. RELEASE NOTES: On GitHub. FREQUENTLY ASKED QUESTIONS: Also on GitHub. SOURCE CODE: Also on GitHub (notice a theme? ). LICENSE: GNU GPLv3. Props courtesy of alexustas and other contributors, and available under the terms of CC 3.0 BY-NC-SA. Portions of this package are derived from stock textures by Squad and are distributed according to Squad policy of permitting to distribute stock assets with mods if required. TinyPirate's 2-minute-mod review: Add-ons for RasterPropMonitor: Plugins that integrate with RasterPropMonitor, enhancing the IVA experience. Astrogator, for planning transfers between worlds. Docking Port Alignment Indicator, to make IVA docking much, much easier. NavUtilities, providing ILS and HSI in the cockpit. SCANsat, for map views on the MFDs. VesselView, for graphical representations of your craft. Plugins RasterPropMonitor can interact with, enhancing the IVA experience even more. Ferram Aerospace Research: for FAR-computed variables, as well as controlling flaps and spoilers from IVA. MechJeb: for all sorts of auto-pilot features and flight information. RealChute: RPM can arm, disarm, deploy, and cut RealChute parachutes (as well as deploying and cutting stock 'chutes). RasterPropMonitor contains example props based on stock internal props. If you want to create a really good looking IVA, you should consider grabbing Alexustas' ASET Props. It implements more of RPM's features than any other mod I've seen. Even better, ASET Avionics provides props for space planes (or any other IVA wanting some aviation-styled props). Projects using RasterPropMonitor: Aerokerbin Industries Modified IVAs by MasseFlieger. The ALCOR capsule and ERS rover by alexustas. CST-100 7-seat crew vehicle by xxhansonmaxx Falcon Drone cockpit Home Grown Rockets KSA IVA Upgrade Mk3 Pod IVA Replacement by Apex Don't see a current IVA project on this list? Let me know. I may have missed it, or I may not have imported it from the original RPM thread. Speaking of which... Mihara had more to say about RPM on the original thread (and I'll edit this post some time down the road to include more of the links and info he had).
  17. Final Frontier kerbal individual merits current version: 1.4.2-3375 Sometimes it's hard to choose a kerbal for a mission because they are all the same... well, they differ in courage and stupidity but they have no history, no personal merits they have achieved. Do you remember who was the first kerbal in space? No? Ok, who was the first kerbal on Mun? Still no idea? The Final Frontier plugin will handle this for you. Each kerbal will get ribbons for extraordinary merits. And the number of missions flown (i.e. vessel recovered), total mission time and total EVA time is recorded, too. Download: Spacedock Spacedock direct link for KSP 1.1.3 Mirror: Curse For modders: Version 0.8.12 and later includes an api to reward ribbons from an external plugin. You will find an adapter class and an example here: FinalFrontierAdapter Planet Packs (for use in 0.6.0 or later): PFCE: Download Kerbol Expanded: Download (WIP, last update 02.01.2015) Ribbon Packs (for use in 0.9.1 or later): RANKS and MILITARY RANKS FOR KERBALS (Base ID 1000) by Araym Expedition/Rank Ribbon Packs (Base ID 8000) bySmarterThanMe Armed Forces Ranks (Base ID 3000) by Shadriss If you want to create your own ribbon pack feel free to do so. But you should use IDs other than in the ribbon packs above. Just set the BASE in the config file to some other number and keep in mind that every ribbon must get an unique ID. (Screenshot of my development copy and not from a real game) To open the Final Frontier Hall of Fame window just click on the button labeled "FF" in the toolbar or press LEFTALT-F (hardcoded at the moment, so it's not assignable to another key). If you are using the stock toolbar you will find some kind of award icon. To browse all available ribbons just press the "Ribbons" button on the right of the hall of fame. Currently the following ribbons are awarded to kerbals: Orbit around a celestial body (including Kerbin) Landing on a celestial body (including Kerbin – kerbals do reward even simple tasks, because most of the time they fail...) EVA in around a celestial body without a stable orbit (including Kerbin) EVA in an orbit around a celestial body (including Kerbin) EVA on a celestial body (including Kerbin – let's hope they will survive...) Docking around a celestial body (including Kerbin) Collision in a vessel Dangerous EVA while not on ground and not in a stable orbit Get into a Kerbin orbit in less than 200, 150 or 120 seconds Accumulated mission time of at least 5, 20, 50, 100, 500, 2000 or 5000 days (20, 80, 200, 400, 2000 or 20000 kerbin days) A return from single mission that lasted for at least 20, 50, 125, 500 oe 2000 days (80, 200, 500, 2000, or 8000 kerbin days) At least 5, 20 or 50 missions flown (i.e. vessel recovered) Done a splashdown landing First kerbal in space A ribbon for entering the sphere of influence of a celestial body (new in 0.2.2) Planting flags on celestial bodies Launching with solid fuel boosters of 10%, 20%, or 30% ship mass Achieved gee-force of 3, 4, 5, 6,..., 17 or 18 g Entering the deep athmosphere of Jool Orbiting the Sun at half or less the distance of Moho Moving a vehicle (hopefully a rover) on the surface of a celestial body Crew member of a heavy vehicle of at least 250, 500, 750, 1000, 1500, 2000 or 4000 tons Launching a heavy vehicle of at least 250, 500, 750, 1000, 1500, 2000 or 4000 (!) tons Landing a heavy vehicle of at least 250, 500, 750, 1000, 1500, 2000 or 4000 (puh!) tons Ribbons for 1h, 2h, 6h, 12h, 24h, 48h, 96h and 192h in EVA Ribbons for flying a vessel at Mach 3, 4, 5, 6, 8, 10, 15 below 20,000m in Kerbin atmosphere (0.4.1 and later) Ribbons for EVA Endurance, i.e. a single EVA of at least 20, 30, 40, 50, 60, 90, 120, 180, 240 or 300 minutes. Ribbons for entering atmosphere of Eve, Duna, Jool,... A Ribbon for entering the sphere of influence of all celestial bodies (Grant Tour ribbon) A Ribbon for entering the sphere of influence of all moons of Jool (Jool Tour ribbon) Ribbons for completing contracts Ribbons achieving research (while in a mission) Ribbons for first completed mission as an engineer, pilot or scientist Ribbons for altitude, distance, speed and depth records A Ribbon for entering deep space beyond Eeloo (or whatever outermost planet may exist) Ribbons for landing in polar regions Ribbons for landing at high elevations on kerbin Ribbons for landing with less than 5% or 1% liquid fuel More than 500 ribbons in total! If a kerbal is the first one rewarded with a celestial ribbon, he will get the "First kerbal" ribbon of that kind (for example "First kerbal in orbit around Kerbin "). Some ribbons replace some others when earned. For example: The ribbon for EVA in an orbit around a celestial body replaces the ribbon for EVA around the same body without a stable orbit. The ribbon for 20 missions flown replaces the ribbon for 5 missions, etc. A tooltip gives a short description for each awarded ribbon. The ribbon graphics are inspired by the ribbons created by Unistrut (view this thread). But unfortunately I still do not have his permission to include his ribbon graphics into Final Frontier so I have created my own set of ribbons. They are using the same color and sometimes similar graphics (so they will look similar). If Unistrut will give his permission to use his ribbons, I will include them in a modified form with better graphics than mine. Some of the custom ribbons are created by SmarterThanMe and nothke and are used with their permission. Update: I finally got the permission to use the ribbons from Unistrut. But why is it called "Final Frontier"? Well, I'm quite surprised that nobody is asking, but I will try to explain it anyway. I was thinking about this plugin since the personal achievement mod by blizzy78. I liked the idea in general but in a sandbox game achievements for the player doesn't mean to much to me (but this is a personal opinion of course). Unfortunately I'm a Java/C++ programmer and C# is quite new for me, so time and missing skills/experience delayed the implementation until the first days of 2014. Then I decided to give it a try and created a small C# project for testing/learning the basics. The first decision to made was the name of the project. I do not exactly remember how I get the idea for the name, but I searched a bit in Youtube, Google and well, perhaps there was a replay of Star Trek in TV. I really don't know how I got the name, but I created a project "Final Frontier" and so it begun. And I don't like to change the name of a project afterwards without a specific reason. Installation: Important! Please read if you have trouble with Final Frontier. Just unzip the archive into the KSP folder. Don't move the FinalFrontier folder, it should be nested in the folder GameData/Nereid. If you are already using the toolbar you don't have to extract the toolbar folder. Do not change the installation path! Final Frontier must reside under GameData/Nereid Compatibility: Final Frontier should be compatible with most mods. There is one important exclusion from this rule: Mods that are changing names of celestial bodies or add new celestial bodies will cause trouble. All releases from 0.6.0 and later can handle the altering of celestial bodies. There is still one exclusion: All celestial bodies must have unique names. To get ribbons for new celestial bodies, you must install a planet pack (see above). Changelog: 0.7.15-1047: Fix for missing button in blizzys toolbar 0.8.1-1282: Fix for lost ribbons bug 0.8.2-1285: minor bugs fixed 0.8.6-1370: fix for Contract Configurator compatibiliy 0.8.8-1410: Update for KSP 1.0.5 0.8.9-1414: new custom ribbons from SmarterThanMe 0.8.13-1728: 7 new ribbons (includung deep space ribbon) support for external plugins that may award ribbons minor fixes 0.9.1-1749 support for user defined custom ribbons 0.9.3-1792 fix for not properly removed kerbals in hall of fame that were spawned by CC+ new ribbons: Lost And Found (untestet), Significant Contract, Exceptional Contract, Passenger Transport removed some uneccessary log spamming added optional logging of ribbons/achievements (to analyze incorrectly awarded ribbons; see last checkbox in config window) 0.9.4-1798 fix for Lost And Found ribbon and Passenger Transport ribbons (NREs in log) 0.9.5-1819 Minor fixes (if you do not enable the logging of ribbon awards you should be fine) Lost And Found ribbon disabled Reasearch ribbons tuned down a bit 0.9.6-1826 Fix for mission summary window 0.9.8-1882First North Polar Lander ribbon North Polar Lander ribbon First South Polar Lander ribbon South Polar Lander ribbon 5% Fuel Landing ribbon (only liquid fuel ist taken into account!) 1% Fuel Landing ribbon (only liquid fuel ist taken into account!) 1500m Mountain Lander ribbon 2000m Mountain Lander ribbon 2500m Mountain Lander ribbon 3000m Mountain Lander ribbon 3500m Mountain Lander ribbon 4000m Mountain Lander ribbon 1.0.2-2131 Update for KSP 1.1.0 1.0.3-2181 Update for KSP 1.1.2 Minor fixes (e.g. windows stay open in main menu) 1.0.4-2216 New First-Kerbal-In-Space and First-EVA-In-Space ribbons graphics by SmarfterThanMe Configurable hotkey 1.0.5-2223 correct URL for KSP-AVC no other changes 1.0.6-2301 Fix for Closer Solar Orbit ribbon and OPM 1.0.7-2319 Hotkey fixed (hopefully) 1.0.8-2443 no more 0%/5% Fuel Landing ribbons if a vessel is landing with deployed (or cut) parachutes logging of some keypresses to analyze the still not solved hotkey issue 1.0.9-2459 timestamps in log now in kerbin time, if enabled in KSP settings fix for FinalFrontierAdapter (kerbal type applicant now eligible for ribbon awards) hall of fame is now refreshed, if an applicant joins the crew roster 1.0.10-2467 Fix for hotkey issue (maybe) minor fix to prevent NRE 1.0.12-2505 Build for KSP 1.1.3 RSS compatibility 1.0.13-2539 Mountain Lander Ribbon for 4000m now superseedes 3500m fixed a typo in the description of the polar landing ribbons 1.2.1-2650 Build for KSP 1.2 1.2.3-2675 fix for the incorrect data in the mission summary window "show summary window" checkbox in config 1.2.4-2772 mission summary window only shown if crew recovered 1.2.5-2906 Fix for conflict with Contract Configurator 1.2.7-3080 KSP 1.2.2 (no significant changes) 1.3.1-3103 KSP 1.3.0 (no significant changes) 1.3.2-3155 no more science records for no science points earned low gravity landing ribbons 1.3.3-3172 KSP 1.3.1 logbook pages 1.3.5-3175 Rover ribbon no longer supersedes EVA ground ribbon 1.3.6-3189 Option to permanently disable ribbons in the Ribbon-Browser without tampering with the ribbon png files 1.4.0-3325 KSP 1.4.0 1.4.1-3335 KSP 1.4.1 1.4.2-3375 KSP 1.4.2 Fix for blurred ribbons in low quality settings The plugin is currently in some kind of alpha beta gamma stage. It works or at least I think it will work. But bugs may occur and don't try this plugin in a current game without a backup. And it its my first project in C#, so don't expect to much from the code . Kerbals are identified by their names. So don't add kerbals with the same name or Final Frontier will get confused. The plugin takes use of System.IO to store its data in the corresponding persistent.sfs of a game and its settings in GameData/FinalFrontier.dat. Release 0.8.x will do a scan for old save games in the saves folder and converts them upon permission by the user. There are no other write operations anywhere on the system. License: http://opensource.org/licenses/BSD-2-Clause Source is included in the zip archive. Final Frontier uses the toolbar created by blizzy78, see http://forum.kerbalspaceprogram.com/threads/60863-0-23-0-Toolbar-1-4-3-Common-API-for-draggable-resizable-buttons-toolbar. If you don't like the toolbar or just want to use the stock toolbar for Final Frontier disable the use of blizzys toolbar in the configuration dialog of Final Frontier. Bugs: Ike and dres ribbons are the same. (fixed in 0.4.20) Decoupling in orbit, leaving orbit and immediatly returning into orbit give Fast Orbit Ribbon (fixed in 0.5.4) A splashdown landing in water give Mach 10 Ribbon (fixed in 0.5.4) Typo" Grant Tour" instead of "Grand Tour" (fixed in 0.5.4) SOI ribbons (and maybe others too) are not awarded when in time acceleration (fixed in 0.5.6) Gee force ribbons don't work as intended if crew is changed in flight (still suspicious) Closer solar orbit ribbons don't work (fixed in 0.6.0) quickload may cause loss of ribbons (fixed in 0.6.3) Ribbons may get lost, after installing new mods (fixed in 0.8.1-1282) Kerbals may get cloned (fixed in 0.8.3-1361) mission summary incorrect in some cases (fixed in 0.9.6-1826)
  18. What it does It makes better automatic default choices for crew assignments (e.g. "labs need scientists" or "drills need engineers"). It remembers your assignments, so that the next time you launch that ship, it will try to do the same thing. (No more discovering, *after* you're in orbit, that your gosh-darn rescue ship filled up all the slots and you've got nowhere to put the stranded kerbal!) You can customize the default behavior with ModuleManager config. NOTE: This mod is not compatible with Kerbal Construction Time. Download from SpaceDock License: CC-BY-NC-ND 4.0 Source code How to install Unzip into your GameData folder, same as any mod. How to use Just play KSP! The mod is deliberately minimalistic. It adds no UI, it doesn't require any special actions to use. It just silently makes the crew-assignment experience better. The only thing that affects you at all is: if you go into the "crew" tab of the editor and change crew assignments, then your choices won't be persisted unless you hit the "save" button before launching the ship. That's it, that's all there is to know. Cool things it does by default Makes sure there's a pilot on board, if you don't have any SAS-capable probe cores. Staffs science labs with scientists. If you have any non-rerunnable science experiments on board, makes sure there's at least one scientist. If you have any parts that need an engineer (ISRU, drills), makes sure there's at least one engineer. Repairable parts (parachutes, landing legs, wheels) also have an engineer requirement (if there's an available engineer of sufficient level). Tries to pick the highest-level crewmembers available. (Except for pilots; if you have an SAS-capable probe core and your pilots are all lower-level than the core, it picks the *lowest* pilot available.) Tries to fill all command pods; doesn't try to fill passenger cabins. If you do manual assignments in the crew tab and then save the ship, it remembers your choices the next time you load the ship. Empty slots will be left empty. It will try to assign specific kerbals by name (e.g. "Jeb goes in slot 0 of this command pod"), and if that crewmember is unavailable, will try to assign another kerbal of the same profession (e.g. "I want Jeb, but he's on a mission already, so I'll use this pilot here.") How it decides The mod works with two types of assignments: default choices, and player choices. Default choices Default choices are controlled by ModuleManager config in a file that comes with the mod (see "How to customize", below). There are two flavors of default choices, *assignments* and *requirements*. Assignments are default choices for crew slots in specific crewable modules. The default config that comes with the mod assigns scientists to science labs, and all crewmembers to command pods. The default config deliberately leaves passenger cabins empty, though you can tweak this by adding your own config if you like. Requirements are added to parts that are not themselves crewable, but which need a particular type of kerbal to operate them. If your vessel has any parts that specify requirements, then the mod will try to ensure that at least one of the specified kerbal type is present in the crew. The default config that comes with the mod adds a "scientist" requirement to all non-rerunnable science experiments (Mystery Goo, Science Jr.), and an "engineer" requirement to ISRU units and ore drills. Player choices When you load a new ship, or add a new part, then everything is controlled by the default behavior and assignments will be updated dynamically as you switch stuff around on your ship. It can do this because you haven't *observed* the assignments and it's therefore free to shuffle assignments around without invalidating any of your choices. However, the moment you switch to the "crew" tab in the editor and see what the assignments are, it then nails all the assignments in place. (It's a Heisenbergian sort of thing.) Basically, what it's doing is assuming that the moment you *see* the assignments, they become your conscious choices rather than something the program assigned. Once you see the assignments (and make any changes of your own), those get persisted to the ship, and will be saved when you hit the "save" button. Such specific choices are assumed to be for a specific kerbal, or for a kerbal of that profession if the kerbal isn't available. How to customize Since all crew assignments/requirements are controlled by ModuleManager config, you can add your own .cfg file to change the behavior to whatever you like. If you'd like to customize the behavior, the following references may be helpful: BetterCrewAssignment.cfg: This is the ModuleManager config that is installed with the mod. It includes detailed comments explaining how it works, so that you can write your own config. ModuleManager documentation: You can find helpful information here and here. A word of thanks Many thanks to @sarbian for a small but vital bit of advice that unblocked the completion of this mod. Thanks to @HebaruSan for the feature suggestion of adding engineer requirements to repairable parts.
  19. Strategia - A Brand New Strategy System! Description Strategia is a revamp to Kerbal Space Program's strategy system. All the stock strategies are removed, and replaced with new and unique strategies. The first set of strategies are special mission strategies. These strategies will give you advance cash and bonuses to certain milestones for completing a high level objective as part of your space program. They are dynamic, so they will work with mods that change the stock solar system by adding or changing celestial bodies. Be warned though - if you cancel one of these strategies without completing the objective, you will face a heavy penalty! Crewed Missions Once we've proven we can get a Kerbal to orbit and back, we need to continue to break new barriers. We have a choice of nearby bodies that we can get to. We choose to go to <insert celestial body here>, not because it is easy, but because it is hard. Uncrewed Missions The costs of sending a Kerbal to another planet are astronomical compared to those of sending a probe that we can leave behind. Why don't we send some probes to our neighbouring planets to gather science autonomously for us? The remaining strategies are the standard strategies - these give a bonus while active, and can be active for as long as you like. Astronaut Training Program Our standard training procedure is to treat newly hired astronauts as a disposable commodity to greatly reduce the cost of unscheduled disassemblies. Still, some argue that training our astronauts before putting them on top of a top of a ton of explosives will result in a lower mission failure rate. The cost of setting up the program will be high, nevermind the cost of actually training the astronauts. What do you say, do we want the right stuff, or the almost-good-enough stuff? Massive Scale Launches We've found some investors who are willing to sponsor us if we're able to launch colossal structures into space in a single launch. We'll have to employ some truly Whackjobian construction techniques to get these things into orbit. Contract Slot Machine These agencies seem to think they're doing us a favour offering by us these ridiculous contracts. Why should we be penalized for being choosy? By closing our books to the public, agencies will have no idea what we're willing to accept. There might be a little chaos in the contracts we see under this model, but if we're only choosing the best ones, then who cares?!? To Boldly Go If we want to get the most research possible done out there, we need to explore as many new biomes as we can. Government grants from exploration programs will ultimately help us fund further exploration and research. Probe Frenzy If we want to do some research, then probes are the way to go. What we save on sending Kerbals out there can be spent on a vast fleet of autonomous probes. Local Science There are so many research opportunities right in our back yard. We should focus on local research to bootstrap our space program. That way when we do make it further out there, we'll be sending the best technology we can. Stagnated Research There are several conservative groups on Kerbin that think we've gone too far, too fast. We're not about to shut down the space program, but maybe slowing down our development of new technology to appease these groups will get us some goodwill and ensure that they don't burn down KSC? Free Ice Cream We've come up with a crazy idea - giving out free ice cream at the space center. The public will absolutely love us. If we push the program far enough, we'll get better rewards for rescuing Kerbals (they'll get ice cream when they land!) and maybe even be able to get a discount on hiring new astronauts. FREE. ICE. CREAM. Media Circus To make a reputable space program, we need to ramp up the media involvement. Cameras everywhere, coverage 6 hours a day, 426 days a years. Of course, this could easily backfire if we have any... accidents. Pilot Focus Clearly the most important role among our astronauts is that of the pilot. Without a skilled pilot, nobody is going to space today (or any other day). Shall we build our space program around our brave pilots? Engineer Focus Where would we be without our engineers? They make sure everything is in order to get the other astronauts up and down safely. Shall we build our space program around the skilled engineer? Scientist Focus The scientist is the key role that we need to focus on. A skilled scientist knows exactly which sample to send back to maximize our science gain (we can only fit so many Mun rocks in those capsules). Shall we build our space program around our brilliant scientists? Download CKAN: In CKAN, select and download the mod "Strategia". GitHub: For the direct download option, please ensure you have all the dependencies before raising a support request: Contract Configurator is a required dependency and can be downloaded from its release thread. Custom Barn Kit is a required dependency and can be downloaded from its release thread. ModuleManager is a required dependency and can be downloaded from its release thread. Strategia can be downloaded from GitHub. Source The full source is available on GitHub. Change Log Special Thanks sarbian - For mods like ModuleManager and Custom Barn Kit that make my life a lot easier. smjjames - For the ridiculous amount of bugs he found during the beta phase. License Strategia is licensed under the MIT license. Like what you see? Consider donating to the coffee fund! It will not go directly to supporting this or other mods under my care, but it may keep my motivation up!
  20. Contracts Window + v9.2 Download from SpaceDock Download from CurseForge Alternate Download: GitHub Localization is supported and the following translations are included in the download package: Russian | Chinese | Polish | Spanish by @vladimir_v| by @QAQdong| by @Moskit| by @fitiales -------------------- Consider donating if you like what you see here. * Money will not go directly to development or upkeep of this addon -------------------- Source is available at GitHub A new contract monitoring window designed to give more information and be more flexible than the stock window. This window gives players a number of options for displaying contracts. Grouping and ordering of contracts can be modified and contracts can be placed into custom mission lists. All contract and parameter reward and penalty values are displayed, along with the amount due to any strategy modifiers. The contract reward modification section of this addon has been removed. Its functionality has been moved to a new, separate add-on that can be found here. The top bar has several buttons that are used to adjust contract ordering and display options. The top-left icon opens a new window with options for changing sort order based on several criteria. The next icon toggles between ascending and descending order for the selected sorting type. The eyeball icon on the right toggles between the active and hidden contract list. Each mission list has its own active and hidden contract lists. The top-right icon opens a new window displaying all of the existing contract missions. Selecting a mission will switch the primary display to those contracts. The primary mission is always at the top of the list and contains all contracts. The bottom bar has several buttons that control various window options. The version number is displayed on the left. Tooltips for most buttons can be toggled on and off with the next icon. The spinning arrows icon is used to reset the window and primary contract list. A confirmation box will open upon pushing this button. This should generally not be needed, but if there are errors in the contract window (no contracts displayed, no "MasterMission" contract list, the window is too small, etc...) this can be used. All window size, font size, and position options will be reset; the internal list of contracts will be updated with all active contracts and the "MasterMission" will be reset with this internal list. All other mission lists should be unaffected, these can be manually deleted if there are any other problems. The aA icon controls font size for most of the window's labels. Each font is increased by one unit. The next icon toggles the overall window and texture element size. It also increases the font size by two units. Between the font and window size options there are four available font sizes and two window element size options. The arrow icon in the lower-right is a re-size handle; it can be dragged to increase or decrease the window size in either dimension. Each contract has a title bar above it with information and options for the contract. The contract difficulty, or prestige, is displayed on the left with one to three stars. The time remaining for the contract is shown next. It updates every five seconds (at high time-warp several days can go by during this period) and switches to days and hours, and turns yellow, when the counter gets low. The year/day time is dependent on your selection of Earth/Kerbin days in the KSP settings menu. The A icon can be used to display the flag and name of the contract's agency. The eyeball icon can be used to move the contract into the hidden or active contract list. The pin icon can be used to pin the icon to the top of the list, regardless of sort type or order; a contract's pinned state is persistent. The checkbox icon can be used to move the contract into a different contract mission list or create a new one. The blue icon at the end can be used to display contract notes if they exist; these are different from individual parameter notes. The primary contract and parameter display shows the same information as the stock window. In orange is the contract title. It is a button that can be pushed to collapse or expand the contract's parameters. When completed the contract text will turn green; when failed it will turn red. The contract parameters are shown in white. When completed these will turn green. Contract parameter notes can be displayed using the blue icon. Sub-parameters are offset slightly and are shown in a darker color. When all sub-parameters are completed they will be collapsed into their parent parameter and no longer displayed. The rewards for each contract and their parameters are displayed on the right side of the window. Funds, Rep, and Science rewards are displayed depending on how wide the window is. Rewards are in green, penalties are in red. The amount of any reward/penalty due to strategies, if any, is displayed in parenthesis. When the green checkbox icon is selected the mission list will appear. The current contract mission lists are displayed in this window. A green checkmark indicator on the left indicates that the currently selected contract is already in that mission. The green number to the right is the amount of contracts in that list. The red x box on the right can be used to remove a contract from any mission that it is present in. Selecting any existing mission will add the contract to it. Selecting the "Create New Mission" option will open the mission creator window. New missions can be created after giving them a name. Missions must have a name, can't use the same name, and must be under 20 characters. All progress nodes, their rewards, and in some cases, information about when they were completed is shown in this window. There are four types of Progress Nodes. Interval Nodes: These are nodes with multiple levels of progression, such as the altitude or speed records. Standard Nodes: These are nodes not specific to any one Celestial Body. Point of Interest Nodes: These are nodes completed by visiting anomalies. Celestial Body-Specific Nodes: These are nodes which are given separately for each Celestial Body Interval progress nodes. Standard progress nodes. The mission title bar is shown at the top of the window. The Title Bar is a button that can be used to switch to Progress Node mode. The edit mission window is opened with the pencil icon in the mission title bar for all but the Master Mission. Change the name of any mission. Delete any mission; this won't affect the contracts, and all contracts are still available in the Master Mission list. ChangeLog: This add-on uses TriggerAu's KSP Plugin Framework code Released under the MIT License.
  21. Connected Living Space (CLS) NOTICE to CLS USERS: Codepoet's real life is preventing him from supporting CLS. He has asked and I have volunteered to support CLS going forward. Codepoet is NOT gone, but has no time. Therefore, I'm cloning his OP and creating a new thread to continue the support and maintenance of CLS. Source code and download locations will remain the same, only the Forum thread will change (vBulliten limitation). The link to the original CLS thread is here. The link to the original development thread is here. The Forum mods have locked the original thread, so post your needs in this thread going forward. Current Version, 1.2.6.2, For KSP 1.4.3. Can be downloaded from SpaceDock || GitHub NOTE: Version 1.2.6.2 is backwards compatible to KSP version 1.3.1. (Thanks to @cakepie for the PR) You will also need ModuleManager to load the config files for CLS to work. CLS now supports KSP-AVC, an addon version checker. If you have KSP-AVC inistalled, it will detect when CLS needs to be updated. CLS also is listed in CKAN for your automatic installation convenience. You can access the source code here. If you spot a bug please let me know. Ideally bugs should be raised in Github. More helpful than raising a bug report is to raise a bug report with lots of information about how to reproduce the problem, and with logs files, save files, craft files etc. Even more helpful is to write a fix by forking the code in Github, and then generating a pull request Introduction This mod identifies areas within a vessel that can be crewed by Kerbals and through which kerbals can pass internally to reach other parts that can be crewed. It is provided to make the concept of connected living spaces easily available to other mod developers and so to provide a single consistent understanding of which pars connect to each other, bringing together both multiple features via plugins and multiple part pack via configurations. CLS itself has a simple GUI to show the player which parts are connected to which. It also has an optional feature that conforms the stock crew transfer system to CLS's view of internal connectivity. License: ConnectedLivingSpace is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License CLS API WIKI - of interest to modders using CLS in their own mods. There is also some early documentation in the development thread. While CLS is primarily an API, it will operate in standalone mode, and does offer a few features. Check out Acessing CLS and CLS Features in the Wiki for details.Updates Acknowledgements: @codepoet, for the original ConnectedLivingSpace. Thanks for a great idea and your support. @JPLRepo, for many nights of helping me better understand KSP and reflection. @Kerbas_ad_astra, for contributions to config files @cakepie, for contributions to enable Airlock Plus compatibility and bug fixes @Booots, for contributions to enable Recoupler compatibility. @linuxgurugamer, for helping keep the mod going in my absence! and many others. I will continue to add as I go back and review my change logs. This section was long overdue. Change Log: ---------- release v1.2.6.2 release date: 13 Jun 2018 - recompiled for 1.4.3 - incorporate PR #102 Add Italian translation. Thanks to CRL42! - incorporate PRs #101 from cake-pie make CLS 1.3.1 compatible. Thanks cakepie! - Updated KSP-AVC version file to reflect backwards compatibility to KSP 1.3.1 - fixed Git issue #99 inflatable airlock deploy/retract does not update clsvessel state. Incorporate PR #100 from cake-pie. - incorporate PR #98 from cake-pie correct updating cls state on crew movements Thanks cake-pie! - fixed Git issue #96 localization of certain languages due to string order. - Added surface attached is passable to structural tubes (Making History). - Recoupler issue hatch status not changing when opening/closing hatches after recouple release v1.2.6.1 release date: 09 Apr 2018 - Made solution structural changes to ensure improved multi developer support and distribution. Reorganized / cleaned up solution folders - Added missing configs configs to CLSStockFreedomAddon.txt per PR97 by wookieegoldberg, Thanks wookie! this updates some renamed parts, and adds some Making history parts. release v1.2.6.0 release date: 09 Apr 2018 - Added configs for new Mk1-3 pod to base CLSStock.cfg - Added configs for Making History Expansion - Added configs to CLSStockFreedomAddon.txt per PR97 by wookieegoldberg, Thanks wookie! this updates some renamed parts, and adds some Making history parts. release v1.2.5.8 release date: 17 Mar 2018 - New: Recompiled for KSP 1.4.1 - Fixed: CLS ApplicationLauncher Button is blurry in KSP 1.4 update. Updated textures to 128x128 px. Git issue #95. - Added back in Recoupler support. Previous PR#83 accidently removed it. Merged PR#94. Git issue #83. release v1.2.5.7 release date: 30 Jan 2018 - Changed: Color for "No" response in information displays changed from Maroon to OrangeRed to improve readability (contrast) - Fixed: Blizzy's Toolbar wrapper needs updating. Git Issue #77 - Fixed: Vessel data is not updated when creating/modifying/deleting a vessel in the Vessel Editor. Git Issue #85 - Fixed: Passable strings reversed. Git Issue #92. (thanks to @yalov!) - Fixed: Hatch status reporting error in tweakable. Git Issue #93. release v1.2.5.6 release date: 29 Jan 2018 - Correct errors in config files for Mod version, and KSP version supported. release v1.2.5.5 release date: 03 Jan 2018 * New: PR from linuxgurugamer for an Updated CLSB9.cfg: Thanks to @Mine_Turtle: linuxgurugamer has added CDP docking port(supposed to be used with s2 parts) to the list and made s2 crew parts passable, when surface attached. Reason: there is no inline s2 docking adapter, nor it is possible to attach stock docking ports to s2 modules and have crew transfers with CLS. release v1.2.5.4 release date: 28 Oct 2017 (beta by linuxgurugamer) * New: Merged PR from @tyehle: Make kibble storage passable. Fixes #87 * New: Merged PR from @yalov: Localizations * New: Merged PR from @cake-pie: Refactor * New: Merged PR from @kerbas-ad-astra: Some new part configs release v 1.2.5.3 release date: 1 Jun 2017 * New: Added Spanish translation. (Thanks to Deltathiago98!) release v 1.2.5.2 release date: 31 May 2017 * New: Added compatibility with Airlock Plus. (thanks to cakepie!) release v 1.2.5.1 release date: 29 May 2017 * New: Added support for Recoupler. Modders can now request to merge spaces on reconnect of parts. -------Note to Modders: This changes the CLSInterface.dll, so if you use this and want the new features please include the latest CLSInterface.dll with your mod. * Misc: Cleaned up text rendering to consistently use C# string interpolation. release v 1.2.5.0 * New: Refactored to support KSP 1.3 * New: Implemented Localization system. Now it is possible to translate CLS into other languages. English included to start. * New: Revised Crew and part display window for spaces. now takes less real estate, and is more intuitive. * New: Revised Space selection buttons to make it easier to tell which space is selected. Now buttons toggle to allow deselection of a space. release v 1.2.4.2 * New: Added a custom event to notify mods that the CLS vessel data has been refreshed. * New: Added a some configs per GitHub issue and PR 79 Thanks Kerbas-ad-Astra! release v 1.2.4.1 * Fixed: Some parts were not merging spaces event when hatches were opened. Github Issue #75. Forum Post: http://forum.kerbalspaceprogram.com/index.php?/topic/109972-122-connected-living-space-v1240-30-dec-2016-customize-your-cls-parts/&do=findComment&comment=2906269 * Fixed: CLSDefaultPart.cfg was included in distribution. There should only be a CLSDefaultPart.cfg.txt file. Removed. Github Issue #78. release v 1.2.4.0 * New: Refactored to support KSP 1.2.2. * New: Completely refactored method used to Add hatches to vessels. Now utilizes a module manager config, eliminating prefab manipulation in game. * New: Code refactored to improve performance and garbage collection. * Fixed: Some parts containing ModuleDockingNode without a referenceNodeName would be rendered impassable in some nodes. * Fixed: NRE generated during Vessel load. The addition of a female kerbal broke the CLS Module attachment code when a vessel is loaded at Flight. (This was a old undetected bug, that may explain some parts not showing as passble) * Fixed: Spammed Index out of range error during space changes while CLS Window is opened. release v 1.2.3.0 * New: Added support for intercepting Parts selection list during stock Transfer target part selection. A part not in the same space will be unselectable and is highlighted orange like full parts. * New: Added support for overriding the "Allow unrestricted Crew Transfers"in CLSInterfaces.dll setting via other Mods to prevent "competition" between mods when handling stock crew transfers. * New: Updated config for Docking Port Jr. Squad now says that a kerbal can squeeze thru. * New: Refactored code to improve performance, recuce garbage collection, & use Explicit typing. * Fixed: CLS windows now properly close when changing scenes. * Fixed: In the Editor, part highlighting does not work correctly when adding new crewable parts. release v 1.2.2.1 * Fixed: Stock Crew Transfer fails for "not in same space" even when the 2 parts are in the same space. release v 1.2.2.0 * New: Refactored Stock Crew Transfer Handler to use new KSP 1.1.3 events to pre-empt the transfer if disallowd by CLS. release v 1.2.1.5 * Fixed: Finally squashed NullRef exceptions when RemoteTech is installed. * New: Added Distribution folder to project for ease in locating binaries from Git. * New: Added folder check for PluginData to ensure proper config file creation when Mod is installed. release v 1.2.1.4 * Fixed: NullRef exceptions when RemoteTech is installed. * New: Moved configuration file from GameData root folder to GameData\ConnectedLivingSpace\Plugins\PluginData folder to comply with KSP folder standards for mods. release v 1.2.1.3 * New: Changed behavior of CLSClient.cs (API wrapper class) to prevent additional assembly scans when called. Ref Git Issue #72. * New: Added new configs for Taurus HCV. Git Issue #71 * New: Added config changes for KOSMOS SSPP Git Issue #69 * New: Refactoring for KSP 1.1.2 (WIP) release v 1.2.1.2 * Fixed: When a Stock Crew transfer is overridden, the override message is not properly displayed. * Fixed: When a Stock Crew transfer is overridden, the original move message is not properly removed. :release v 1.2.1.1 * Fixed: Null reference errors. * Fixed: Window would not open release v 1.2.1.0 * New: Updated mod for KSP 1.1.2 compatability. prerelease v 1.2.0.9 New: Updated mod for KSP 1.1 compatability. New: Corrected Stock Screen Messages so that they are properly removed when CLS overrides a Stock Crew Transfer. Fixed: CLS would not display a window when the stock Icon was clicked. Fixed: CLS should now only display 1 icon in Editor or flight. Removed redundant icon call in Start, now that stock buttons now behave as intended.Version 1.2.0.2 - 21 mar 2016 New: Added Changes to configurations based on conversations in forums and a Pull Requests by Technologicat, khr15714n & Kerbas-ad-astra. Fixed: Correct build deploy automation to project (missing icons for blizzy). Fixed: CLS tweakables incorrectly visible when custom passability is disabled. Version 1.2.0.1 Corrects an implementation bug. in 1.2.0.0 release, the wrong dll was distributed.. Build and deploy process is now automated. Version 1.2.0.0 makes CLS KSP 1.0.5 ready, and adds a new feature to the VAB/SPH Customizable Part configs for CLS. This feature is off by default. Refer to the CLS Wiki for more details on this handy new feature. Version 1.1.3.1 Fixes a KSP 1.0.2 toolbar issue when Blizzy Toolbar is not insatlled, a display issue with options when no vessel is loaded, and a change to the Freedom Alt Stock MM config. Version 1.1.3.0 Fixes a KSP 1.0.2 toolbar issue, a vessel loading bug, and adds support for Blizzy's toolbar. CLS now supports KSP-AVC if you have it installed. Version 1.1.2.0 Fixes a bug. Version 1.1.1.0 makes changes to the way hatches and highlighting work to make is easy to co-operate in these areas with other mods. Version 1.1.0.0 makes CLS work with KSP 0.90 Version 1.0.11.0 fixes a bug with the stock crew transfer integration Version 1.0.10.0 fixes a bug and integrates with the stock crew transfer system Version 1.0.9.0 is to support KSP0.25 and adds more config for various mods. Version 1.0.8.0 is to support KSP0.24.2 and uses the new stock toolbar. A bug in the VAB/SPS descriptions is fixed too. Version 1.0.7.0 fixes a bug in the editor when the root part is deleted, and adds config for FASA Version 1.0.6.0 fixes some problems with the hatches closing themselves across saves, and also allows hatches to be opened for attached rather than docked docking ports. Version 1.0.5.0 provides a scheme for mods using CLS to "loose bind" to it, which means that they can more easily work without CLS. However if you upgrade to 1.0.5.0 you should update other mods such as Ship manifest that use (or do not use!) it. Version 1.0.4.1 fixes bugs, allows for shielded docking ports and is the result of a major rework of the code. Hatches in docking ports have been re-written. There is also config for many more mods, and more options for the configs. Version 1.0.3.0 fixes a few bugs and adds more configs Version 1.0.1.0 is now available. this version adds closable hatches in docking ports, as well as improvements to the GUI, and configuration for more part packs. Here is a deep space transport vessel docked at an LKO transfer station with 3 crew shuttles also attached. Mods using the CLS API Here is a list of mods that have been released that make use of ConnectedLivingSpace. If you would like to add your mod to this list, send me a PM. KerbalHotSeat Ship Manifest Kerbal Crew Transfer Wetworks crew tanks KeepFit Recoupler (thanks to @Booots!) AirLock Plus (thanks to @cakepie!) Mods that provide CLS configuration themselves. This list is by no means complete. If you would like to add your mod to this list, send me a PM. Sum Dum Heavy Industries USI Modular Kolonization System GingerCorp Station Hubs Lack Luster Labs. (separate link from the forum thread) Fustek Kip Engineering: Low profile structural hub set MRS Space Station Parts Expansion Near Future Spacecraft Civilian Population Mods that CLS provides config files for: Here is a list of mods that CLS provides configuration files for. If you would like to add your mod to this list, send me a PM. FASA Novapunch B9 Home Grown Rockets KSOS LSSC ASET Stack-able inlight lights Kosmos KW Rocketry Porkjet's Habitat Pack 2 different stock configurations. and loads more (I loose count!) Mods that the community has provided config files for: Taurus HCV. Contributed by: ModZero Roadmap Provide configuration for every part pack anyone has ever heard of. improvements to the GUI (added in v12.5.0) hooks that can be used by mods such as Porkjet or wetworkshops to change the passability / habitability of parts in flight.
  22. I've always been a fan of @Overengineer1's GravityTurn (see original thread). Unfortunately it wasn't updated for a while, so I thought to take care of that myself . Also thanks @sarbian for all the useful MechJeb code of which parts were/are incorparated into this plugin. So this is what it does: Launch a craft into a low orbit with a few customizable settings. Performing a Gravity Turn is arguably the most efficient launch procedure. The plugin will take care of the entire ascent for you by maintaining a strict hold to prograde (as much as possible) and varying the throttle to keep the desired ascent curvature. The circularization burn will be up to you, but it's normally less than 50 m/s. The "First Guess" button tries to find the best settings for a particular rocket. After the trajectory reaches the destination height and the vehicle leaves the atmosphere, you can revert back to launch and use the "Improve Guess" button to get a better set of parameters. Do this multiple times and you will get a very efficient launch. Download the mod here Source on GitHub License: GPL V3 V1.7.7: recompiled for KSP 1.4. ATTENTION: not compatible with 1.3.1 or earlier any more! Feature requests are welcome, but of course subject to spare time restrictions and personal taste... Next on the plan: Reworking UI Adding KSPedia support (maybe) Storing an loading a set of default launch parameters.
  23. Ever had a Kerbal stranded in orbit in a deflated USI inflatable module, or other crewed part without a hatch? This is your solution. This is a simple micro-addon that does one thing; restricts the pods that may be selected to spawn kerbals in for orbital rescue contracts. Any new contracts that are generated will have the part that they use validated against a list of approved parts and replaced with a random approved part if it is not on the list. This will not effect any contracts that you have already accepted, or any contracts that are already 'available'; as such you will need to complete or decline any existing rescue contracts after you first install the mod. The pods that are 'valid' are configurable via a simple config file, the default configuration file only includes stock command pods. Other 'valid' pods can be added by end-users through module manager (recommended) or manual edits (not recommended). See the included .cfg file for details / node names / etc. Downloads: https://github.com/shadowmage45/KSPRescuePodFix/releases Simply drop the KSPRescuePodFix folder from the .zip into your KSPs GameData folder and you should be good to go. Requirements: ModuleManager for KSP 1.2 (latest version you can find) Issues/Problems/Bug Reports: Please report all issues/bugs/feature-requests on the github issue tracker, located at: ( https://github.com/shadowmage45/KSPRescuePodFix/issues ) Legal: Source is licensed under GPL v3 ( http://www.gnu.org/licenses/gpl-3.0.en.html ), and is available on github: ( https://github.com/shadowmage45/KSPRescuePodFix ). Much of the source is based on the concept presented by @xEvilReeperx, which can be found at ( link ).
  24. Hi fellow kerbonauts After years of downloading and enjoying mod from the great KSP community it's time I do something myself, so here it is : Crew Light The goal of this mod is to automatize, as much as possible, the lights of your vessels (and of kerbal's helmet). Every part that currently hold crew gets its lights turning on Lights react to the sunshine And to depth GIF incoming... When approaching a distant vessel its lights will blink, sending you a welcoming message in Morse code Kerbal on EVA can toggle lights Lights can have a motion detector set up Youtube review by @Kottabos : How does it works ? Vessel's lights are divided into 3 groups : Lights of crew-able part : They will remain off until a kerbal gets on-board Lights NOT in the light action group : (and kerbal's helmet light) They'll go on when the sun's fall, off when it rises Other Lights : They will work as usual, toggling by the light action group This mod rely on the light action group to determine which light belongs to which group, in stock KSP you can change action group only in the editor, so no lights on all crafts already launched will react to the sun rising/falling. To change action group in flight you will need the mod Action Groups Extended, by @Diazo. And an enhanced support of the mod Aviation Lights by @BigNose, maintained by @MOARdV : By default its navigation and strobe light will get turned on at night using the custom blinking light provided by AviationLights, flash, double flash, interval. This is configurable, per light, in the setting file. The beacon light will stay off until you push the throttle, acting as a real warning light And it now support Kerbal Electric (a set of tweak-able and very cool lights) : How to modify how it works ? There is a file Settings.cfg in Kerbal Space Program/GameData/CrewLight/PluginData/ with some variables to tweak, names and comment should be explicit enough. Most useful one are : morse_code : change the morse message sent by distant vessel, here you can find a Morse alphabet distance : set the distance at which the Morse message begins only_light_not_in_AG : if False every light will toggle according to sunlight always_on_in_space : if True kerbal who disembark will always turn their lights on while on orbit use_staggered_light lights which respond to the sun light will be turn on in a staggered way What is needed ? ModuleManager is the only dependency, all credits go to @ialdabaoth and @sarbian Know issues : Lights on kerbal's helmet don't turn on/off as the sun rises/falls. Lights will be turned on if the kerbal disembark in the dark but status of the sunlight won't be checked after that. The range sphere of the Motion Detector is offset from the light position only for the stock light, for others the sphere center is at the light position. What to do if it doesn't work ? Report it to Github or on this thread. This is my first mod for KSP and one of my first working C# code, I've tested it on every situation I could think of but it may have bugs left. And a big thank you to @Diazo, @Nereid, @Crzyrndm, @RealGecko, @Skalou for helping me, and to every modders out there who wrote good code for learning Download on SpaceDock Download on Github Last 1.4.2 version Last 1.4.1 version Last 1.4.0 version Last 1.3.1 version Last 1.3 version Last 1.2.2 version Source on Github License is MIT Dev thread, now closed
  25. RealChute is a complete rework of the stock parachute module to fix a few of its inconveniences and get more realistic results out of parachutes! Issues that do not follow the bug reporting format will be ignored. NO LOGS, NO SUPPORT. Download - GitHub Special thanks to @Starwaster for the KSP 1.4 compatibility update! ModuleManager patch files included in the download. Issues that do not follow the bug reporting format will be ignored. NO LOGS, NO SUPPORT. Features: Gradual deployment: Chutes gradually deploy, increasing realism and decreasing deployment shock. New Deployment Conditions: Chutes deploy in conditions ranging from Eve's crushing clouds to Duna's silken veil. Parachutes deploy either according to atmospheric density or altitude and will not deploy when not intended to; e.g. in space or on the pad. Autocuts can be set for a certain altitude per chute to cut some chutes while other deploy! Parachutes on Ground: Parachutes will not autocut upon nearly stopping mid-air or touching the ground, enabling drag chutes for planes! Parachutes Return to Staging: Parachutes can be restaged again and again without restrictions! Drag Chute: Drag chutes deploy at low altitude to slow landing airplanes. Full Customization: Parachutes' values can be edited, and modders can add the plugin to their packs. Combo Chute: Deploys a drogue and next a main chute. Custom parts: sumghai gave this pack its own parts! Vessel Hangs from Chute: Even nose chutes! Editor window: Edit parachutes from the editor for any shape, size, or characteristics! Presets: Quickly edit parachutes by saving configurations into presets and loading them quickly later! Thanks to Duxwing for rewriting this part Video by 7499275 showcasing the mod Changelog: November 30th 2017 v1.4.5 -Compatibility for KSP 1.3.1 -Fixed issue with editor window -Implemented increments for in flight window sliders -Solution-wise code cleanup/optimizations June 1st 2017 v1.4.4 -RealChute 1.3 compatibility update -Recompiled and fixed missing parameters -Updated to CompatibilityChecker 6 -Fixed custom filters not showing in the editor -Fixed settings button appearing in flight March 25th, 2017 v1.4.3 -FAR compatibility update. Addresses changes to FARAeroUtil.GetCurrentDensity() -Bring RC chutes in line with stock contract changes. (hopefully prevent impossible chute contracts from being generated by the contract system) October 14th, 2016 v 1.4.2. -Use part.addForceAtPosition instead of calling rigidbody functions (1.2 specific compatibility changes) -Updated versioning in RealChute.version and assembly property files -Fixed mispelled field name in compatibility checker (_version) -Fixed toolbar button showing up in Flight. (broke in 1.2) April 30th 2016 v1.4.1.1 -Recompiled for KSP 1.1.2 to prevent nasty PopupDialog exceptions April 29th 2016 v1.4.1 -Fixed bug related to reloading the database through ModuleManager -Added an OnActive override, potentially fixing a few contract oddities -Removed deprecated MM configs April 19th 2016 v1.4 -Removed IPartSizeModifier support (no longer needed) -Added search tags to parts -Compiled for the latest version of KSP 1.1 April 16th 2016 v1.4x4 *Prerelease* -New NyanMode™ -Fixed plugin loading problems from IPartMassModifier and IPartCostModifier -Added IPartSizeModifier support -Refactored and cleaned the codebase through ReSharper April 2nd 2016 v1.4x3 *Prerelease* -No longer purveys the Nyan. Leaving that to Sarbian. -Issue in the editor with part mass modifying is fixed in the game and the subsequent hack has been removed -Fixed PopupDialog anchor issues April 1st 2016 v1.4x2 *Prerelease* -Fixed some slight GUI issues -Fixed redundancy in editor part mass update (correction, awaits new KSP build) -Added a new custom parachute deployment sound -Slightly modified parachute canopies textures -Created an 1.0.5 port of all the newer changes (backward ports FTW) March 29th 2016 v1.4x1 *Prerelease* -Updated to Unity 5 -Updated KSP references -Fixed issues with part mass editing -Temporarily removed Win64 lock (testing stability) -Built on Win x64 February 4th 2016 v1.3.2.7 -Fixed an issue with parachutes not having a staging icon when on the same part as one disabling the icon December 2nd 2015 (second take) v1.3.2.6 -Reuploaded with the correct binaries, not the RealChute 2 ones, won't crash anymore. Sorry. December 2nd 2015 v1.3.2.5 -Fixed a bug with early reentry giving chutes an exagerated amount of heat (thanks to Starwaster!) November 10th 2015 v1.3.2.4 -Updated chute heat/aero failures to new changes -Added indicator for chute deployment safety through the staging icon's background -Now using MM 2.6.13 -Compiled to KSP v1.0.5 May 2nd 2014 v1.3.2.3 -Updated flags to DDS files, thanks to sumghai again -Slight bugfix to parachute heating, they now heat, much, much, MUCH faster, as they should. -Fixed a bug with minimum deployment pressure being in kPa, allowing deployment way too early May 1st 2015 v1.3.2.2 -Parachutes can now burn up during reentry shock heating, each material has it's own characteristics -Added a MM node for the new stock radial drogue -Updated all parachute max temperature values -sumghai converted all the part textures to DDS for faster loading April 28th 2015 v1.3.2.1 *Hotfix* -Fixed the breeding problem with the AppLauncher button -Fixed the ConfigNode persistence issues with ModuleManager -Fixed the DragCubes weight problem of the stock Module -Bundled ModuleManager v2.6.1 April 27th 2015 v1.3.2 *KSP 1.0 compatibility update* -Updated aerodynamics reference to correctly get new atmospheric values. -Fixed a few GUI issues all around April 2nd 2015 v1.3.1 -Removed all this tasty bacon. Wasn't the best parachute. -Improved enum parsing/tostring, will serve in the future April 1st 2015 v1.3.3.7 -Optimized toastiness -The amount of snacks has increased by 401%! -Now with brand new flavour! -MOAR March 12th 2015 v1.3 -Massive optimization of every line of code in RealChute. Literally. Everything. -Massive optimizations of all the GUIs and of the editor window. -Presets no longer save the target body, so you can easily apply any preset to any body -FAR compatibility fixed, previous versions would not correctly use the fetched values -You can now select if only engineers can repack parachutes in career mode -You can also select the minimum level required for engineers to repair parachutes in career mode (0 to 5) -Complying with the last two changes, fixed the bug with engineer levels and repacking in career mode -Stock parachutes have been removed from the Utility tab and now only appear in the Parachutes tab -Did I say massive optimization? December 27th 2014 v1.2.6.3 *Hotfix* -Reverted the editor GUI changes which caused CoM bugs in flight -Fixed a bug where stock chutes would not apply parachute model changes correctly -Only lvl 1+ engineers can repack chutes anymore December 26th 2014 v1.2.6.2 -Fixed compatibility issue with FAR -Added a right click menu to modify the size of the parachute case if the action groups are not available yet -Added a setting which automatically adjusts the size of the canopy while changing case size through right click menu -New editor RealChute icon by sumghai! -RealChute logo updated to be clearer in the filter by manufacturer tab -Moved parachute specific GUI to it's own object -Fixed a bug where the combo chute would have two main sized chutes -Updated to ModuleManager 2.5.6 -RealChute parts are now only visible in the "Parachutes" category -Fixed a bug where RealChute contracts would not display the RealChute/Wenkel logos correctly December 17th 2014 v1.2.6.1 -KSP 0.90 compatibility update -Added a parachutes filtering tab in the "filter by function" category -Changed the default RealChute icon in the "filter by module" section to the RealChute icon -Added a parachute count field in the general part stats section -Changed the RealChute default module name in the module info section -Made so that RealChute parts will be invisible if the mod is incompatible with the current KSP version November 16th 2014 v1.2.6 -Fixed the bugs related to stock chutes -Fixed the bug related to parachutes not deploying on first staging action -Fixed the bug where you could no longer repack if a loading sequence took place ater deployment -Fixed the numerous bugs with quicksaving/quickloading when parachutes are deployed -Made part GUI display logic more fluid -Small optimizations to the editor GUI October 9th 2014 v1.2.5.3 -Probably fixed the bug when loading crafts October 8th 2014 (take two) v1.2.5.2 -Win64bit detecting changed to prevent it to be disabled -Fixed typo in the SovietPack MM config -Fixed potential bug with the AppLauncher button -Corrected the Agents.cfg file to have the correct URLs to the logos and prevent dumb stock bug October 8th 2014 v1.2.5.1 -Updated to new license October 7th 2014 v1.2.5 -Fixed the bug where parachutes would disappear during quicksave/quickload process -Fixed repack bug after reloading a craft with expanded chutes -The SpaceCenter icon is now added to the stock Applauncher -RealChute is now part of Wenkel Corporation -Wenkel Corporation and RealChute flags -Wenkel Corporation and RealChute are new agencies -Entry cost reviewed for all chutes -Added an option to target a specific landing altitude -Now using a new timer device which follows game time -Said timer sets parachute deployment correctly through time. -Upgraded to CompatibilityChecker v4, RealChute is disabled on Windows 64bit installs -ModuleTestSubject added to parachutes -Now uses ModuleManager 2.5.0 -Moved the editor GUI to a separate object. August 6th 2014 v1.2.4 -Updated correctly all ModuleManager files -Added ModuleManager support to Tantares and the KP0110 pod -Now uses ModuleManager 2.2.1 -Optimized FAR code to not fetch the method each frame -Optimized the rescaling code once more, radially attached parts should behave better -All .png files crushed in size without quality loss thanks to dak180 -SpaceCenter icon will no longer be shown over the Astronaut Complex, RnD Building, or Mission Control views -CompatibilityChecker now checks for KSP 0.24.1 or higher for procedural part cost -All ModuleManager files are now package with the rest of the mod, only the needed nodes are loaded July 27th 2014 v1.2.3 -Implemented procedural cost for all RealChute parts based on canopy diameter and case size -Refactored a lot of GUI labels to render more efficiently -Fixed the nasty bug where parts with only a RealChuteModule would not animate -Fixed bug where minPressure would not persist through scenes -Tweaked case masses to make more sense, they were quite heavy in the past July 22nd 2014 (take two) v1.2.2.2 *Hotfix* -Hopefully last fix to the symmetry bug July 22nd 2014 v1.2.2.1 *Hotfix* -Fixed a bug with symmetry parts (once more) -Fixed a bug where you could not repack chutes which did not all deploy. July 21th 2014 v1.2.2 -Fixed a bug where stock chutes with RealChute configuration would break upon reload -Added a way to remove the Action Groups GUI from the ProceduralChute if needed July 20th 2014 v1.2.1 -Fixed bug where the stack chute would never work at all -Fixed bug where crafts with symmetry parts would have a CoM offset bug and not function properly upon reload if the stats had not been applied to counterparts -Fixed stock parts MM configs to work properly with this update -SpaceCenter RealChute icon can now be hid by pressing 'h' July 18th 2014 v1.2 WARNING: ALL VESSELS AND CRAFT FILES WILL BREAK WITH THIS UPDATE. YOU HAVE BEEN WARNED. -v0.24 compatibility, built to work on Windows x64 -Completely changed the way multiple chutes on a part are handled¸ -Very large part of the code refactored, once again -Options from the RealChute_Settings.cfg file are now available to be tweaked from the SpaceCenter, icon gracefully offered by sumghai -Parachutes are now contained into PARACHUTE{} nodes inside PART configs -The plugin can now handle an indefinite amount of parachutes on a single part -Various small bugfixes -Now uses ModuleManager v2.2.0 April 27th 2014 (take two) v1.1.0.1 *Hotfix* -Fixed a problem with parts having no size node April 27th 2014 v1.1 -Extensive code refactoring in both PartModules to clean up a little (no, a lot really) -Augmented FAR support: when FAR is installed, RealChute will now fetch it's density values -New size nodes allow changing the attach nodes size when cycling through the different selections -Presets are now a thing: You can create them, apply them, delete them, but not eat them -A wide selection of presets are included by default to mimick all the past chutes and allow for quick parachute modification -Stock chutes will now use the RealChute canopies, and will have procedural size according to their diameter -Better support for the settings file -Cleaned the editor GUI a little -Now uses ModuleManager v2.0.3 April 18th 2014 v1.0.5 -Fixed the bug with secondary chutes not deploying -Maximum deployment height/pressure now depend on target planet -Added automatic deployment on ground contact with intend of usage for drag chutes -Added possibility to compute parachute diameter from empty ship mass -Applying stats to symmetry parts will now copy over all the fields. -Added descriptions to materials -Size cycling swapped to be more intuitive -April fools prank can be reenabled through the RealChute_Settings.cfg April 1st 2014 (third try) v1.0.4.1 *Hotfix* -Refixed target speed range for drogue chutes April 1st 2014 (serious edition) v1.0.4 -Removed the Arpil Fool's prank -Bumped drogue target speed to 5000m/s -Fixed potential division by zero bug -New part descriptions, graciously offered by Duxwing April 1st 2014 v1.0.3.37 -Fixed the tiny chutes appearing in the editor -Fixed the last bugs with parachute texture/canopy model not updating correctly -Fixed symmetry counterparts not having the right deployed/predeployed diameter -Added procedural diameter to canopies other than RealChute parts -Fixed pressure/altitude deployment not switching on secondary chutes -Fixed secondary canopy texture selector not displaying the one said in the module config on first initiation -Parachute type can now be declared into the module node (main, drogue, drag) -Removed all legacy parts from the tech tree to avoid confusion -Moved the cone simple chute to the start TechNode -KSP v0.23.5 (ARM) compatibility March 7th 2014 v1.0.3 -Fixed the very small bug where the popup announcing the application worked would not resize after a warning -Added a display of the current RealChute version on both the editor window and the info window -Did some very minor code wise improvements around March 5th 2014 v1.0.2 -Fixed material of the second parachute not updating with his window but with the winodw of the main material -Similarly to the above, fixed the window of the seconda material showing stats about the main material -Fixed texture of the second parachute not updating whatsoever -Fixed symmetry counterparts not ever keeping their size -Fixed a bug where the "mustGoDown" clause would actually never update for the parachute -Various tweaks to GUI display (mainly the decimals shown by materials drag coefficient) March 3rd 2014 v1.0.1.1 *Hotfix* -Fixed size not remaining in flight properly -Fixed symmetry counterparts not having the right predpeloyed diameter -Sorted some problems with the correct updating of part GUI March 2nd 2014 (take 2) v1.0.1 *Hotfix* -Fixed a bug where some fields in the editor window would not update -Fixed a bug where everything using MM would flat out not work -Fixed staging activating even from other vessels March 2nd 2014 v1.0 Editor: -New editor window which allows tweakaing of parachutes far more easily than stock tweakables -Said window is accessible in the VAB/SPH through the action group editor panel, by selecting a RealChute part -Texture, canopy models, and part size can be edited with this window, and only four parts are now necessary -Old parts are still included to preserve compatibility but are not visible in the editor -Added a field to prevent parachutes to be tweakable if necessary -When a texture library is defined, the parachutes will automatically resize to the right diameter Flight: -New info window in flight allows seeing the stats of the current parachute -Predeployment altitude/pressures and deployment altitudes can now be generally tweaked from this window in flight -When parachutes fail to deploy, their icon will blink red and a message whill show indicating a short reason why -Parachutes do no need to be moved in a new stage to allow redeployment through staging -For those who do not like the deployment logic, behaviour can be changed to arm on staging automatically by changing the value in RealChute_Settings.cfg -Fixed a bug where when coming quickloading or coming back to a flight prevented from repacking correctly Drag calculator (.exe) -Repassed the code and added the ability to select the drag coefficient by material Misc: -Heavy code repass to fix and optimize multiple things -The plugin now uses CompatibilityChecker by Majiir to verify if the KSP version is compatible with the plugin January 9th 2014 v0.3.3.2 *Hotfix* -Fixed the stack main chutes animation problem January 8th 2014 v0.3.3.1 *Hotfix* -Fixed a bug where single parachutes would still not arm propoerly -Fixed stack main chute configs to have the right canopies so they actually work -Fixed a problem with staging reset bugging the staging list -Changed the default drag values of parts to 0.32 to actually match the real stock values -Changed altitude detection to a faster, safer system -Hopefully, the change above to altitude detection fixes parachutes deploying too early January 7th 2014 v0.3.3 -Fixed a bug where dual chutes would not arm -Changed default predeployment altitudes to 30km for drogues and 25km for mains -Changed predeployment on drags to 100m and full deployment to 50m -Switched triple canopies to single canopies on the stack 1.25m main chutes -Fixed forced orientation so that it actually follows vessel orientation -Fixed forced orientation remaining even if only one parachute is deployed. -Small tweaks to attachement notes on stack chutes (thanks to eggrobin) -Fixed caps being inverted on stack chutes (thanks to eggrobin again for making me notice) -Changed behaviour or repacked chutes, if not in the last stage, they might not need to be moved to e reactivated. -Moved the random deployment timer to OnStart() for future MechJeb implementation -Various tweaks to the tweakables UI controllers -Fixed a bug where dual chutes with the same material would show "empty" as a second material -Fixed a bug where full deployment shortly after deployment would result in the animations skipping -Fixed an annoying and unreliable bug where parachutes would make your craft spin out of control by making the force applied to the part once more December 18th 2013 (take two) v0.3.2.1 *Hotfix* -Fixed the bug where dual parachutes would take mass forever -Fixed a bug with combo chutes having ridiculous starting weight -Finally fixed the bug with the FASA and Bargain Rocket parachutes, they will now animate properly (big thanks to sirkut) -All the ModuleManager files are now included with the main download, remove those you don't want. December 18th 2013 v0.3.2 KSP 0.23 compatibility update! -Added combo chutes which contain both a drogue and a main for soft landings in one part -Added the ability to define a second material for the second parachute -Added the ability to force the parachutes partially in one direction, thus eliminating clipping chutes on dual parts! -The force is now applied on the whole vessel, so no more weird hangings if the part origin is weird -Tweakables! Nearly every value that can be changed in the editor can now be. This is only until I set the editor window up on my side. -Fixed a bug with parachutes facing downwards on reentry -Added a random deployment delay for parachutes! They will now take between 0 and 1 second to deploy. This is chose randomly for every parachute -Every parachute now has random "movement noise" different from every other parachutes currently active -Said random noise will now appear to be much smoother than before -Usage of the new EFFECTS node has permited to get rid of FXGroups and to remove all those nasty .wav files all around! Decemer 7th 2013 v0.3.1 *Hotfix* -Fixed a bug with the mustGoDown/timer clauses -Fixed a bug with dual chutes not cutting properly -Fixed yet another bug with predeployment of main chutes always having the same drag -Added an "reverseOrientation" clause in case a modeller builds the parachute transform the wrong way -Parachutes no create drag from the very area where they originate from. This means a chute on the side will hang realistically without a CoM offset -Rescaled all the parachutes to have the real size in game. If you find this too big, tell me on the forum and I'll revise them (note, this is not procedural yet, if you change the part yourself, you need to change the scale) -Fixed a bug with the calculator when calculating the diameter of multiple chutes -Added a sound on repack, thanks to ymir9 once again December 4th 2013 v0.3 -Completely removed stock drag dependancy. The parachutes now calculate drag according to real drag equations -Given the above, the drag parachutes generate is irrelevant of the mass of the part and now depends of the diameter of the parachute -Parachutes are now made of different materials, defined in cfg files -Parachute canopies now weight something which depends on which material they are made of and what is it's area density -Optimization of the code by about 300 lines as the module is pretty much complete -New parts with the pack, thanks to sumghai! You can now select between many different parachutes for the job you want to accomplish -It is now possible to arm a parachute to deploy as soon as it can through action group or part GUI -Minimal deployment can now be defined by altitude or pressure -Added FXGroups to parachute cut and repack, and providing a cut sound with the parachutes, offered by ymir9! -A small program made to help calculating parachute diameters is also included with the download! November 24th 2013 v0.2.1 *Hotfix* -Fixed a bug where single parachutes don't show the right icon colours -Fixed the weird glitchiness of the parachute's orientation in some occasions -Fixed parachutes not working if not on the current active vessel November 23rd 2013 v0.2 -Added a compatibility mode for a second parachute on the same part! Can only be used if the parachute has a a second set of parachute transform/animation -Reworked deployment code from the ground up to allow the above feature November 16th 2013 v0.1b -Fixed the issue where deploying the parachute below the full deployment height would play the second animations faster -Added sounds on both predeployment and deployment -Added a deployment timer that will show a countdown on the flight screen -Added a clause that the ship must go downards to deploy and that will show status on the flight screen -Fixed a few remaining deployment bugs -Changed the behaviour of the part GUI to only show when the action is available November 13th 2013 v0.1.1a -Hotfix of a few deployment bugs that could cause weird unresponsive parachutes -Added a "cutAlt" feature to automatically cut a parachute below a certain altitude. November 12th 2013 v0.1a -Initial release Components: --RealChuteModule-- //General caseMass: mass of the case of the parachute (what you would normally put at "mass = xx" (put it there too though)) timer: time before deployment after the part has been activated in seconds mustGoDown: whether or not the craft has to be going downwards to deploy (true/false) cutSpeed: speed at which the parachute will automatically cut when on the ground in m/s spareChutes: amount of times a parachute can be repacked (set to -1 if you want to repack it as much as you want) reverseOrientation: check this to true if the transform was built backwards, else don't put this in at all //Main parachute PARACHUTE { material: what material the parachute is made out (must be initiated in a MATERIAL{} node) preDeployedDiameter: diameter of the parachute when predeployed deployedDiameter: diameter of the parachute when deployed minIsPressure: whether the value in "minDeployment" is pressure or altitude (true/false) minDeployment: minimum altitude or at which the parachute predeploy (if minIsPressure = false) minPressure: minimum pressure at which the parachute will predeploy (if minIsPressure = true) deploymentAlt: altitude at which the parachute will fully deploy cutAlt: altitude at which the parachute will automatically cut (set this to -1 if you don't want an autocut at a certain altitude) preDeploymentSpeed: time required to predeploy the parachute in seconds (affects how fast it decelerates) deploymentSpeed: time required to deploy the parachute in seconds (affects how fast it decelerates) preDeploymentAnimation: name of the predeployment animation (from the model) deploymentAnimation: name of the deployment animation (from the model) parachuteName: name of the canopy of the parachute (from the model) capName: name of the protective cap of the parachute (from the model) forcedOrientation: angle to angle the cute at from the center of the part (greater than 0, lower than 90) } //Add as many PARACHUTE{} nodes as you want parachutes on the part --ProceduralChute-- textureLibrary: name of the texture library to get textures and models from type: type of parachute this is refered as in the texture library currentCase: current parachute case texture (from the texture library) currentCanopies: current canopy texture for the main chute (from the texture library) currentTypes: current type of the main chute (Main, Drogue, Drag), defaulted to Main isTweakable: if the Action Groups GUI appears //Size nodes SIZE { size: rescaling vector for the part (x, y, z) caseMass: case mass for this size sizeID: generic ID for this size. Can be whatever you want, but know that presets will use this to find the right size. topNode: position of the top node at this size topNodeSize: size of the top AttachNode at this size bottomNode: position of the bottom node at this size bottomNodeSize sixe of the bottom AttachNode at this size } //Add as many as you want sizes for your part --Texture library-- TEXTURE_LIBRARY { name: name of the library CASE_TEXTURE { name: name of this case texture types: types of parachute this texture can apply to (separate each by a comma) textureURL: string url of the texture from the GameData folder } CANOPY_TEXTURE { name: name of this canopy texture textureURL: string url of the texture from the GameData folder } CANOPY_MODEL { name: name of this canopy model diameter: diameter of a single canopy at (1, 1, 1) count: number of visible canopies on this model maxDiam: max deployed diameter possible for this model CHUTE { modelURL: string url of the model from the GameData folder transformName: name of the parachute transform preDepAnim: name of the predeployment animation depAnim: name of the deployment animation } //Add as many of those as you want this type of chute to have, models must have different transform names } } --Material node-- MATERIAL { name: name of the material (string name you put in the PartModule) description: short description of the material areaDensity: density of the material in t/m² dragCoefficient: drag coefficient of this material (recommended to not go below 0.5 and above 2) maxTemp: maximum temperature of the material (will autocut past this temperature) specificHeat: the specific heat of this temperature, in J/kg*K emissivity: the emissivity constant of this material (usually between 0.5 and 1.5) } --Effects node-- EFFECTS { rcpredeploy //name of the predeployment effect { AUDIO { channel = Ship clip = sound_parachute_deploy volume = 1 } } rcdeploy //name of the deployment effect { AUDIO { channel = Ship clip = sound_parachute_single volume = 1 } } rccut //name of the cut effect { AUDIO { channel = Ship clip = RealChute/Sounds/sound_parachute_cut volume = 1 } } rcrepack //name of the repack effect { AUDIO { channel = Ship clip = RealChute/Sounds/sound_parachute_repack volume = 1 } } } And now finally, if you want to donate a little something to support for all the coffee and the nights I spent on this, you are very welcome, and it would make my day my year. FAQ (if you ask a question that is here, I'm not answering you.): Q: How/Where do I edit and customize parachutes? A: In the action groups panel. Click on the said panel like you wanted to edit action groups, then click on the parachute you want to edit. A window with all the editing options will appear. for this specific parachute. Don't forget to press apply before leaving. Q: This panel is too complicated, isn't there a simpler way to do this? A: If you don't want to use the editor panel, you really don't have to. There is a preset system that allows you to select the parachute's type (main, droge, drag, or combo), it's size (0.625m - 2.5m for cones/stacks, small - large for radials), and apply it to your current chute. You don't even have to complicate your life. Q: When I'm pressing apply, it's telling me that the craft is too heavy for the parachute. What do I do? A: Make sure the the only parts attached to the craft when you press apply are the parts that you want to land. Detach your launcher or any other fluff before pressing apply. The parachute is calculated with the weight of all the parts currently attached to the craft. You can also toggle dry/wet mass in the editor to help, but it defaults at dry. Q: What is this "parachutes used" field in the editor window? A: This is the amount of parachutes deployed at the same time to land your parachute. This option will spread the load of your craft throughout all the parachutes used, effectively lowering the size of each. Be careful: a triple canopy is only a visual effect, it's only one chute. Stach chutes, on the other side, are two chutes (one comes out on each side). This is why this field does not say parts; a part can have multiple chutes on it (like the stacks and the combos). This is why a cone chute with a triple canopy would put one in parachutes used, and a stack chute would put two. Four radial chutes in symmetry would use four. Basically, you just put in the amount of individual active chutes at the same time, regardless of what the canopies look like. Q: Why can't I access the parachute editor when starting career? When does it come available? A: The parachute editor comes with the action groups panel. As long as the most basic action groups are unavailable, the panel is unavailable. In a normal stock game, the basic action groups become available with the first VAB and SPH upgrades. Q: I used to be able to resize parachutes with the right click menu, but those options aren't there anymore. What happened to them? A: The right click resizing menu is a helping too with the previous questions. While the action groups menu is unavailable, you can resize parachutes with the right click menu. When they are, resizing now happens in the action groups menu. This only happens in career mode, so in science and sandbox, you would always go to the action groups window. Q: Why does the Engineer's Report say there are no chutes on the craft when I clearly put some? A: The Engineer's Report looks for stock chutes. I haven't implemented a check for RealChute yet. Be patient. Q: Does this work on Windows 64bit builds of KSP? A: As of KSP 1.1, yes. However, this is absolutely not something that is sure never to change. If the Winx64 builds of the game return to being unstable, buggy messes, you bet that the lock will absolutely return, and I reserve the right to bring it back at any moment I see fit, and at my discretion, and mine only. But, with the current look of things, I do not anticipate the need to do this in any foreseeable future. You have, however, been warned. Q: Do the parachutes hold on at 4x physical time warp? A: Depending on how fast you are coming down and which chute you are using, yes. Most often they will hold on just fine, but I really can't guarantee they will. However be careful, the chutes fully deployed added to high physical timewarp values can lead to bad stuff, you've been warned. Q: Is this FAR compatible? A: FAR has it's own built-in implementation of RealChute, added by me, providing basic RealChute-esque behaviour, minus all the fluff. If you want the in game editor and all the additional features RealChute provides, install this, it'll override the version built into far. Q: Can you make a ModuleManager file for *insert mod here*? A: I currently don't have much time to work on configs for mods, but if you make one and are 100% sure it works, send it to me, I'll see about including it. Q: I'm trying to add a secondary parachute to a part but it's not working! A: It's not working because you can't add a secondary parachute to any part. It needs a second parachute transform, a second set of parachute animations, etc. A modeller needs to make a part that has two parachute to allow it. Q: What is your favourite pie flavour? A: I love cherry and blueberry pie tbh. Special thanks to UbioZur, r4m0n, Sarbian, Cilph, sirkut, taniwha, NathanKell, ferram4, toadicus and the rest of #kspmodders for helping this mod happen The cut and repack sounds were graciously given by ymir9, big thanks to him! Very special thanks to @sumghai for those awesome parts, as well as the logos, icons, and flags!! GitHub repository (source) License: You are free to copy, fork, and modify RealChute as you see fit. However, redistribution is only permitted for unmodified versions of RealChute, and under attribution clause. If you want to distribute a modified version of RealChute, be it code, textures, configs, or any other asset and piece of work, you must get my explicit permission on the matter through a private channel, and must also distribute it through the attribution clause, and must make it clear to anyone using your modification of my work that they must report any problem related to this usage to you, and not to me. This clause expires if I happen to be inactive (no connection) for a period of 90 days on the official KSP forums. In that case, the license reverts back to CC-BY-NC-SA 4.0 INTL.