Jump to content

Search the Community

Showing results for tags 'plugin'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General
    • Announcements
    • The Daily Kerbal
  • Kerbal Space Program 2
    • KSP 2 Discussion
    • KSP 2 Dev Diaries
    • KSP 2 Suggestions & Development Discussion
    • Show and Tell
  • Kerbal Space Program
    • KSP Discussion
    • KSP Suggestions & Development Discussion
    • Challenges & Mission ideas
    • The Spacecraft Exchange
    • KSP Fan Works
  • Community
    • Welcome Aboard
    • Science & Spaceflight
    • Kerbal Network
    • The Lounge
  • 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
  • Making History Expansion
    • Making History Missions
    • Making History Discussion
    • Making History Support
  • Breaking Ground Expansion
    • Breaking Ground Discussion
    • Breaking Ground 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


About me


Location


Interests

  1. As from 2021-0930 and under @TheDarkBadger agreement, I'm the New Management forDOE. From now on, it's all officially my fault! (again) In a Hurry: Current Release: 2.1.1.6 for KSP >= 1.4 (2021-1020) Works from KSP 1.4.1 to 1.12.2. really! IMPORTANT read this post before updating! Announce for 2.1.0.0. (2.1.1.1 to 2.1.1.4 are experimental releases) Announce for 2.1.1.5. Downloads on GitHub (and KSP-AVC users). on CurseForge . on SpaceDock and CKAN . (Soon™) Relevant Notes ReStock is not supported (yet). Stay Tunned! Description: Distant Object Enhancement /L is a visual enhancement mod that makes objects realistically visible over large distances. BASIC FEATURES Flare effects for planets and nearby satellites, properly calculated by size, distances, phase angle, etc. Flare effects are colored for each planet, which makes for easy identification. On-rails vessels up to 750km away are visually rendered (no intensive physics calculations necessary) Background stars dim when looking at the bright surface of a nearby planet, just like in real life! If you have blizzy78's Toolbar plugin, a settings window is available with several options to improve performance or tweak visuals. Full compatibility with custom planet mods -- with flare color definitions included for Real Solar System, PlanetFactory, and Alternis Kerbol. It is the follow up from TheDarkBadger's Distant Object Enhancement Continued, that by itself is the follow up of MOARdV's Distant Object Enhancement bis, which is the follow up of Rubber Ducky's Distant Object Enhancement. Support: I need help in order to proper help you. Open the spoiler for instructions about how to get support:
  2. 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
  3. As from 2018-1016 and under @pellinor agreement, I'm the New Management for TweakScale. From now on, it's all officially my fault! In a Hurry: Help Wanted! See this post. Current Release: 2.4.6.1 for KSP >= 1.4.4 (2021-1016) It works fro KSP 1.3.0 to KSP 1.12.x! Seriously! How to check Compatibility on CurseForge. IMPORTANT Users of KSP 1.9.x need to install KSP Recall. Users of KSP 1.11.x need to install KSP Recall too. Users of KSP 1.12.x need to install KSP Recall. Am I detecting a pattern? read this post before updating! Downloads on GitHub (and KSP-AVC users). on CurseForge . on SpaceDock and CKAN . Soon™ TweakScale Companion Program Third Party support is going to be implemented into Companions, and all legacy patches are going End Of Life on TweakScale 2.4.4. Most of them are unusable anyway Check the TweakScale Companion Program's Thread for more information. New Companions are being released on a regular basis. Relevant Notes Kraken Food (unholy interactions between Add'Ons) is detected on startup, and a proper (and scary) Warning is shown when appropriated. Pay attention to that message, and reach me here for help! Overrules and HotFixes can be issued to workaround the problems if needed. See this post. A PhD thesis about the current problems can be found on this post. An article about how new patches will be handled is here. For users of Infernal Robotics: The Classic Infernal Robotics has a showstopper bug. See this post for details. TweakScale strongly advise using Infernal Robotics/Next where these issues were solved. Description: TweakScale lets you change the size of a part. Not just that, but it will figure out how much fuel is in the resized part. And if it's an engine, it will become more powerful by scaling it bigger, or weaker by scaling it smaller. (Pictures are eternal work in progress! ) Credits: Contributions From: Goodspeed and Biotronic. [original release thread] Pellinor [previous release thread] And future new features/bugs/mishaps from yours truly. Support: I need help in order to proper help you. Open the spoiler for instructions about how to get support: Scale Safe!
  4. Final Frontier kerbal individual merits current version: 1.10.0-3485 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 1.5.0-3380 KSP 1.5.1 1.5.1-3415 KSP 1.6.0 Squeezing of science points in hall of fame history (reduces data stored in save file) 1.5.3-3465 KSP 1.6.1 If a flight is reverted to EDITOR all ribbons are reverted too 1.8.0-3475 KSP 1.8.1 1.8.1-3479 Minor fix: sorting/statistics for ribbon count in hall of fame fixed 1.10.0-3485 KSP 1.10.0 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)
  5. 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!
  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 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. 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. (WIP, needs updating) 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 TexturesUnlimited Textures Unlimited is distributed under its own license (GPL3). Source code and licensing details may be found at: https://github.com/shadowmage45/TexturesUnlimited Forum Page: https://forum.kerbalspaceprogram.com/index.php?/topic/167450-18x-textures-unlimited-pbr-shader-texture-set-and-model-loading-api/ 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. Rocket Sound Enhancement Rocket Sound Enhancement "RSE" is a plugin for modders to add more detailed sound effects to the game. It features a robust Layering System for use of multiple sounds just like in other games. You can control sound effects' volume and pitch via Physics, Engine Thrusts, Wheel Physics, Mass of the Ship, and More™ Development Videos: Features: Documentation will be made soon on the github page. Basic Audio Muffler A Lightweight Lowpass Filter Vacuum and Interior Muffling Customizable in the Custom Game Settings Audio Limiter/Compressor Keeps the Loudness of the game consistent Customizable in the Custom Game Settings Custom Sound Part Modules Current Part Modules Include are: Engines Wheels Collisions Decouples Launch Clamps Docking Ports Physics Based Sound System (ShipEffects Rewritten) Allows you to layer different sound loops controlled by Physics Documentation: https://github.com/ensou04/RocketSoundEnhancement/wiki Settings: RSE Settings can be found under Game Difficulty Settings. Rocket Sound Enhancement Default Sound Library and Configs Stock Engines Stock Wheels Stock Decouplers and Launch Clamps Stock Docking Ports Collisions and Scrapes Ship Hull Sound Effects (Like ShipEffects but better) ReStock Supported Downloads: IMPORTANT: Remove the old v0.4.0 RSE entirely, nuke it. not a single code was carried over to v0.5.0 not deleting will result in an unexpected outcome. Dependencies: Module Manager Plugin and Configs: https://github.com/ensou04/RocketSoundEnhancement/releases Source: https://github.com/ensou04/RocketSoundEnhancement License: Rocket Sound Enhancement plugin is licensed under GNU General Public License v3.0 The Default Sound Library is licensed under CC BY-NC-SA 4.0 Sharing videos of your launches with this mod is mandatory. jk please share
  8. 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 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, thermal glow, and underwater fog functions: TU/Metallic - Unity Standard Metallic shader implementation, with full mapping compatibility with Unity Standard shader inputs. TU/Specular - Unity Standard Specular shader implementation, with full mapping compatibility with Unity Standard shader inputs. TU/Transparent - Unity Standard Metallic shader implementation with transparency support, with full mapping compatibility with Unity Standard shader inputs. TU/Legacy - Legacy Specular shader implementation that supports input of KSP mapped textures (e.g. specular in the diffuse-alpha channel). All TU/XXX shaders support recoloring, subsurface scattering, and have functional versions of icon-shaders. 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 (either the included shaders, or their own custom shaders) 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) 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 Uses the stock reflection system for reflection probes; so any issues present there will also manifest with TU reflective shaders. No EVE or Scatterer in reflections Issues with improperly authored SQUAD DXT5 normal maps (investigating solutions) 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 More comprehensive texture-replacement methods for technical textures and materials; skyboxes, ksc buildings? 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. @Manwith Noname for his work on the TexturesUnlimited Recoloring Depot, and patience while working on tracking down issues with normal maps.
  9. 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. Video review by @Kottabos 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.
  10. AtmosphereAutopilot plugin 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 F-35 post-stall piloting with FAR (no commentary): https://www.youtube.com/watch?v=Gi-zXRDfyAs Download links: SpaceDock or Github As usual, put .zip contents in gamedata. License: GNU GPL v3. The KSPUpgradeScriptFix.dll and its source can be found on this post (link for convenience) (alternative: https://github.com/net-lisias-ksph/KSPUpgradeScriptFix). Dependencies and compatibility: You'll need ModuleManager. 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 >My control surface settings are not respected - Make sure you reconfigure your crafts (set pitch, roll, yaw again) after mod installation, if you're using stock aero. You will not have to do that again, unless you delete the mod. >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. >How to make the plane follows surface-level pitch, instead of orbital, while using fly-by-wire? -Put navball in surface mode. >AFBW mod is not cooperating with the standard fly-by-wire. -Activate "AA compatibility" in AFBW's GUI. 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. KOS integration: 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. Hotel26 - multiple UI-related additions.
  11. Simplifies vessel design by adding a visual "laser" grid and an automatic alignment tool to SPH and VAB License: GPLv3 Source code: GitHub Description Citation: "You should make your drawings with a ruler and a pencil, not with your leg and a marker pen." -- A maths teacher Have you ever been annoyed by ending up with misaligned engines or clubfooted landing gear after spending half-an-hour trying just to guess where to rotate to get them right? This mod adds a grid to SPH and VAB and "laser" guides for an active part to let you clearly see where the things are wrong and align them in one click. Download from SpaceDock Here's a video on why do you need it and how to use it Installation Extract contents of the released archive into your KSP/GameData folder. Usage While in SPH or VAB press the button to enable the grid. Once there's a root part you'll see the grid with origin bound to the part. If you try to add or edit another one you'll see the red "laser" guides representing all the three axes for it and all of its symmetry counterparts. Now you have all the planes and axes visualized and it's the matter of several clicks to align the things. The guides have distinct colors for each direction. You can easily remember them in the following way: Red for Rechts (Right) Violet for Vorwarts (Forward) Pink for Up (almost the same as the thrust vector) Once you have rotated a part to approximately face the desired side, use the following hotkeys for autoalign the desired part's axis to be parallel to the closest grid line (regardless of direction): Period ( [.] ) - toggles the grid on and off L - aligns the part by a guide at the mouse pointer to the closest grid line J - aligns the part's up (pink guide) to the closest grid line N - aligns the part's forward (violet guide) to the closest grid line M - aligns the part's right (red guide) to the closest grid line G - select a part under mouse pointer as the grid's origin K - toggles guides for symmetry (deKlutter). May be useful when working with many radially symmetrical parts creating a bunch of guides which makes them complex to use. This button let's you see the ones for the original part only. When using the separate keys for alignment (J, N, M), if you are in the part's editing mode (rotation or offset) it is sufficient to just press a key. Otherwise you'll need to move the mouse pointer over the desired part and then press. You can change the keys by editing HangarGrid.cfg in the mod's folder. Valid values are listed inside the file. Know issues Autoalignment of a part desynchronizes it's rotation and position to the current rotation gizmo. So if you press an alignment key while in rotation mode, it is recommended to re-enable the mode by pressing "1" - "3", for example. Otherwise once you touch the gizmo again the part jumps to the gizmo's present position and rotation. Planned features * A GUI for grid customization that let's you change the look and declutter the view abit.
  12. This plugin allows for parts to have hollow insets that dont clip into other parts, ideal for engine nozzles, landing gear, air intakes, solar panel bays, and more. It is a standalone version of the depth mask module included in the Restock dll, along with the addition of depth masks to several stock parts ModuleDepthMask 1.1.2 requires KSP 1.11 or later. If you are using an older version of KSP, please use version 1.1.1. Downloads Source Code Usage Add a depth mask mesh to your part model. It should cover up the hollow area you want to prevent clipping in, without sticking out. Mark the depth mask object with the Icon_Hidden tag to prevent it from showing in the VAB part picker Add a new ModuleDepthMask to your part config Add the name of your mask object in the maskTransform property (Optional) Add the name of the object you want to restrict the mask effect to in the bodyTransform property An example config: MODULE { name = ModuleDepthMask maskTransform = mask bodyTransform = interior //Optional } Creating the depth mask model The depth mask will prevent any other parts from rendering behind it. Because of that, it should not be used on any kind of bay where other parts will be placed, or on any part you can look completely through. It also shouldn’t "bubble" out above the hole you want to cover, otherwise it would be possible to see through it from the side. Also double check your normal direction, since the depth shader only works one way. Screenshots mask meshes and configs for stock parts are included in Restock Licensing This plugin is licensed Creative Commons Sharealike Attribution. This means that you can redistribute it and its source code however you like under the same license as long as you include attribution and indicate the changes you made, if any. Redistribution You are free to redistribute this plugin in your mods, or embed the code in your own plugins (with a different module name for compatability of course.) To prevent duplicates of the plugin, please add the dll to the root gamedata directory. In general, treat this mod the same as Modulemanager for redistribution
  13. 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!
  14. What it does When the ship is in vacuum and on a collision course with the ground, it will automatically show time-to-impact, and the estimated burn time to kill your velocity at ground level. When the ship is in orbit and has an upcoming rendezvous with a target ship, it will automatically show time-to-closest-approach, and the estimated burn time to match velocity to the target. When the ship is on a course to enter or exit atmosphere in the next few minutes, shows time until the transition. For closest-approach, it shows a countdown indicator to tell you when to start your burn. When the ship's orbital period is close to geosynchronous, shows a time-delta-from-geosynchronous display, to make it easy to set up synchronous orbit. When the ship has a target and its orbital period is close to the target's, shows a time-delta-from-target-synchronous display, to make it easy to synchronize orbits. SRBs display their burn time. It's shown on the part tooltip in the vehicle editor, as well as on the part's right-click menu in the editor and in flight. What this means for landing on vacuum worlds: No more messing around with ground-level maneuver nodes to figure out when to start your retro-burn. What this means for target rendezvous: If you can set up a rendezvous that will take you within 10 km of the target, you'll see an estimated time-until-closest-approach, and an estimated burn time to match velocity with the target. What this means for setting up communications networks: It's really easy to set up synchronous satellites (either geosynchronous, or synchronous with each other). Download from SpaceDock License: CC-BY-NC-ND 4.0 Source code Notes The "countdown" indicator For closest-approach, the mod displays a "countdown" indicator. This is a little row of green dots, immediately below the estimated burn time. This row of dots counts down until it's time to start your burn: when the last dot disappears, start the burn. The display is logarithmic. The last three (biggest, leftmost) dots are in seconds: 3, 2, 1, go. After the first three dots, it's 5 seconds, 10 seconds, 15 seconds, then it doubles for each dot after that. Note: No countdown indicator is currently shown for the "time to impact" indicator; this is because "when should I start?" is more complex, depending on a lot of factors including your descent angle, TWR, etc. This feature may eventually be added, but until then, you're on your own. If you don't like this indicator, you can do any of the following (see mod page on SpaceDock for details): Customize its appearance Make it numeric rather than graphic (e.g. "Start burn in 43s" or "Burn-43s" or however you like) Turn it off completely The "insufficient fuel" warning Normally, the mod displays estimated burn time like this (48 seconds in this example): Est. Burn: 48s If the mod decides that you don't have enough dV to do the specified burn, it will display the time like this instead: Est. Burn: (~48s) Note that it won't do this if you have the "infinite fuel" cheat turned on (since then you always have enough dV!) The time-to-impact indicator Under the right circumstances, the mod will display a "time until impact" indicator (instead of "time until maneuver"), along with an estimated burn time which is how long your engine would need to kill your velocity at ground level. All of the following conditions must be met for this indicator to be displayed: The impact tracker isn't disabled via settings (see "Settings", below) The planet/moon whose SoI you're in has no atmosphere. (Someday I may release an update to enable the impact indicator when it's in atmosphere, but not right now. It gets ugly and would significantly complicate the calculations.) You're on a trajectory that intersects the surface. You're falling by at least 2 m/s. The time of impact is no more than 120 seconds away (though you can tweak this with settings, see below). Note that the time-to-impact is based on the assumption that you don't do a retro-burn and just coast to your doom. So if you're figuring out "when do I start my retro-burn to land," you'll generally want to wait a little bit after the point at which time-to-impact equals estimated burn time. The time-to-closest-approach indicator Under the right circumstances, the mod will display a "time until closest approach" indicator (instead of "time until maneuver"), along with an estimated burn time to match velocity with the target. All of the following conditions must be met for this indicator to be displayed: The approach tracker isn't disabled via settings (see "Settings", below) You don't have a maneuver node set The impact tracker (see above) isn't displaying time-to-impact You have a target, which is a vessel (e.g. not a planet) Neither you nor your target is landed You have an upcoming approach within 10 km distance The closest approach is no more than 15 minutes from now You're not within 200 meters of the target and going under 10 m/s, or within 400 meters and going under 1 m/s To slow your craft to a halt when it's close to the target, you should start your burn when the time-until-closest-approach is about half of the estimated burn time shown. The time-to-atmosphere indicator If you're imminently about to enter or exit atmosphere, it shows time remaining. The atmosphere tracker only shows time until transition (there's no burn time or countdown dots). Note that for time-until-exit, it assumes a ballistic trajectory and makes no attempt whatsoever to account for drag. There are config options for this feature in config.xml. If you don't like the default behavior, you can adjust how far ahead of time it displays the warning, or turn the feature off completely if you prefer. The synchrony tracker If you're in orbit, and you're reasonably close to being in synchronous orbit around the current celestial body, the mod will display a "geosynchrony tracker" that shows how close you are to perfect geosync. The tracker displays a time delta (positive or negative) showing how far off your current orbital period is from perfect geosynchrony. It shows hours/minutes/seconds until you get within 10 seconds, then switches to milliseconds display. (The transition point is configurable, see below.) If you're in orbit and you have a target, then you get a "target synchrony" indicator, that works the same as the geosynchrony one, but shows time delta relative to target rather than relative to the celestial body's rotation period. This makes it easy to put satellites in synchronous orbit. If the value is negative, thrust ; if positive, thrust . Goal is to get as close to zero as possible, for synchronous orbit. All of the following conditions must be met for this indicator to be displayed: No other tracker is currently active. You're in a stable orbit (e.g. not suborbital or escaping). The period of your current orbit is within 5% of the current celestial body's rotation period (this is configurable, see below). Your ship has been "idle" (defined as, no throttle and no control inputs) for less than 10 seconds (this is configurable, see below). In addition, this tracker also supports an override key that allows manually forcing it to display, even if the above conditions aren't met, as long as no other tracker is active. By default, the override key is the right Ctrl key (this can be changed via config). Also, by default, the override is only active while you're actually holding the key down; however, there's a config setting that lets you make it "sticky" (i.e. press once to turn on, press a second time to turn off). When the override key is active and you're not currently in a stable orbit, it will just say gsync ~. If the override key is active and geosynchronous orbit is actually impossible for the current celestial body (because the needed altitude would be outside the SoI), then it will say gsync X. (These are only shown when the override is active, since if it isn't, in this case the tracker's not shown at all.) See the "How to configure" section below for a list of these configuration settings. The SRB burn-time indicator SRBs display their burn time, in the following places: On the tooltip in the parts pane in the editor On the part's right-click menu (in the editor) On the part's right-click menu (in flight) (Note that the burn time calculation takes thrust limiter into account.) Caveats A few things to know about how the mod works. Summary presented here; please see the README for full details. It doesn't know about staging. It assumes that all fuel will be consumed by your current stage. Therefore, the burn time estimate and dV warning indicator may be inaccurate if you're going to be staging in the middle of the burn. (After you stage, though, it will immediately update itself.) It doesn't know about fuel flow. It assumes that all your fuel will be available to all your engines throughout the burn. Therefore, if any of your engines are going to run dry before others during the burn, the time estimate will be optimistic. (After the engines run dry, though, it will immediately update itself.) It ignores electrical supply, so make sure your ion engine has enough power. Time to impact is very simplistic. It looks at the elevation directly under the ship, and at your current vertical speed. It corrects for the acceleration of gravity, but nothing else. This means that if you're flying over rough terrain, the time-to-impact indicator will be irregular (it will suddenly get shorter when you're flying over an ascending slope, or longer when you're flying over a descending slope). If you're hurtling horizontally and about to smack into the side of a mountain range looming up in front of you, the mod has no clue. Be warned. The time-to-impact estimate takes into account your current velocity and the acceleration of gravity, and that's it. It deliberately does not take into account the acceleration of your engines, if you're firing them. It's an estimate of "how long would I take to smash into the ground if I turned off all my engines." So when you're retro-burning to land, the actual time to reach the ground will be longer than the displayed estimate, depending on things such as your TWR, throttle setting, angle of approach, etc. So if you want to time your burn so that you reach zero velocity right when you get to ground level, you'll need to wait a little bit past the point where the estimated time to impact equals the estimated burn time. How to configure After the first time you run KSP with the mod installed, there will be a configuration file located at under this location in your KSP folder, which you can edit to adjust settings: GameData/BetterBurnTime/PluginData/BetterBurnTime/config.xml Specific settings listed in spoiler. A historical note The original impetus for this mod was actually something that no longer is part of the mod! Before KSP 1.5, the stock burn-time indicator for maneuver nodes was... suboptimal. It had a variety of shortcomings that made it less useful than it could have been. BetterBurnTime was originally created to address those shortcomings and make the navball's burn-time indicator "just work better". That was the original purpose; that was originally the only thing that the mod did. Over time, I added some additional handy functions-- the landing, rendezvous, and atmosphere-transition information. Then, KSP 1.5 drastically improved the stock navball, and basically did all the improvements that BetterBurnTime was originally created to do. Yay! So that's stock now, which means I removed that functionality from BetterBurnTime after KSP 1.5. However, the additional functions are still convenient, and still not in stock, so those remain-- and are now what BetterBurnTime is about, since its original purpose (maneuver nodes) has become moot. If you're running a pre-1.5 version of KSP and want better navball functionality, you can run BetterBurnTime 1.6.1 and get the enhanced maneuver-node functionality. Acknowledgments Thanks to @FullMetalMachinist for the excellent suggestion of using a row of dots to show the countdown-to-start-burn. Ask and ye shall receive! Thanks also to @Gen. Jack D. Ripper for usability suggestions on the countdown timer's appearance.
  15. 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. NOTICE: I'm no longer developing this version, no new features are going in, only compatibility updates will be pushed out. I'm also not officially supporting this mod anymore, but plenty of people can help you, and I may pop in once in a while. My focus is on RealChute 2, which is coming Soon™ 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 Documentation 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.
  16. VesselMover Continued 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: Download Locations: https://github.com/jrodrigv/VesselMover/releases Installation: Extract the folder called "VesselMover" to KSP's GameData folder. For installation convenience, VesselMover is now CKAN listed, and supports KSP-AVC. 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!). License: MIT Source code: https://github.com/jrodrigv/VesselMover
  17. This is something I made for placing RCS thrusters in the right positions in the first try without having to go back and forth between the VAB and the hacked gravity launchpad. Features: Display thrust and torque forces caused by RCS or engines. ΔV readout for monopropellant RCS. Dry center of mass marker (DCoM). "Average" center of mass marker (ACoM). Center of drag marker (CoD) for assisting in parachute placement. Ability to resize editor's overlay markers. Display total mass of resources. Supports: blizzy78's toolbar KSP Add-on Version Checker Once enabled you should see RCS Build Aid's window, select the translation mode or press any of the translation flight control keys ("hnijkl" keys) and then you should see something like this: Cyan arrows represents thruster forces, the green arrow represents the translation motion (or thrust). The red arrow represents the torque force in your vessel, if you have a red arrow then your ship will rotate when trying to translate in docking mode. So all you have to do is place your RCS thrusters in a way that eliminates this force. The red circular arrow is an indication of how fast the vessel will rotate. The red CoM marker is the dry center of mass (DCoM) which represents the center of mass of your vessel when it doesn't have any fuel (in the picture, without liquid fuel, oxidizer or mono-propellant, but is configurable). Video explaining how to use RCSBA (version 0.5) by Geneborg This plugin only works with parts using stock modules such as ModuleRCS and ModuleEngines, mods that use custom modules will not be detected. Known issues: delta v readout will only show for monopropellant RCS, doesn't work for the new Vernor RCS. Parachute mode only works with stock aerodynamics and parachutes, will not work with mods such as FerramAerospaceResearch and RealChute. Download GitHub repository - Documentation - Changelog Licensed under LGPLv3. This program is free software: you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details. You should have received a copy of the GNU Lesser General Public License along with this program. If not, see <http://www.gnu.org/licenses/>.
  18. S.A.V.E automatic backup system current version: 1.10.0-3173 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. Folders containing a .nobackup file are not included in any backup. So if you do not want to backup a game or a subfolder of a game, just create a file of that name there. 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.
  19. KSP's aerodynamic shielding is wonky. You can hide parts from airflow and flames with cargo bays only - and it doesn't work all the times. Sometimes you don't even know it till spaceplane starts to drag extremely because of tiny robo arm in the bay. And FAR is not an option for everyone. TLDR - can someone please make a plugin that shows and changes part's Shielded status forcefully, by pressing a button in PAW? It may sound cheaty, but stock actually punishes you for having equipment clipped in hollow stuff. So, it's not more cheaty then toggleable autostruts.
  20. Deadly Reentry 7.8.2, for KSP 1.12.* - The Barbie 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! DRE menu icon created by lajoswinkler Download (latest official) Source on Github
  21. Hello Mod Community! I'm currently developing a mod which requires the selection of an or several image(s) by the player. Preferably I would like to do using the Windows File Explorer. I've tried two methods, using UnityEngine and another one using System.Windows.Forms. None of them worked and I've heard that apparently people have had issues with the file explorer when modding before... UnityEditor method EditorUtility.OpenFilePanel("Select reference image!", "", "png"); Which gave me this error: I heard the apparently KSP doesn't use UnityEditor so I added the UnityEditor.dll file into the plugins folder which changed the error from the beforementioned one to this one: Anyone have any experience with UnityEditor and KSP modding, please let me know! System Windows Forms method string refImgPath = ""; OpenFileDialog fileDialog_ = new OpenFileDialog(); fileDialog_.InitialDirectory = @"c:\"; fileDialog_.Filter = "png"; fileDialog_.RestoreDirectory = false; if (fileDialog_.ShowDialog() == DialogResult.OK) { refImgPath = fileDialog_.FileName; } Debug.Log(refImgPath); Which gave me this error: I didn't know where to continue from here, anyone know what's wrong? Basically I need help with getting an file (image) explorer window working to get the path to any given image. Thank you in advance for any help!
  22. I'm starting a new thread for the SRW mod I have recently rebuilt for a relativelly new KSP version 1.10.1. The mod has been abandoned by @Crzyrndm few years ago and then was kept rebuilt in a fork of @HebaruSan. I found out that fork being more updated and featuring a couple of improvements only after rebuilding the mod on my own with a change that is critical for me. If I find more time to spend on the mod - the first thing I will do is adding the QoL tweaks from that fork. The only reason for the first version released by me to be called 2.0.0 is to prevent the mod's version names from being confusing. (Semi-) Saturatable Reaction Wheels Dependency - ModuleManager Download from GitHub or via CKAN License - GPL v3 Features Reaction wheels accumulate momentum with use, torque output is modified based on the current stored momentum Stored momentum "magically" (ie. no basis in real physics) slowly decays over time, recovering the parts torque capabilities. The rate is configurable in the part configuration files (ie. you can turn it off, decrease the rate, or increase the rate to suit your play style) Stored momentum can also be discharged at the expense of propellant. Not enabled by default, change the file extension of ResourceDrain.txt to .cfg to enable Before you download I have not done much testing. Please report any problem you encounter with the mod. I have not marked KSP 1.8.1 as compatible but I use it in my 1.8.1 heavily modded career and I'm sure I'll have a reason to explicitly declare compatibility after some time. Changelog v2.1.3 Added: New custom ico for toolbar button (by @Tedd_Deireadh, thanks!). v2.1.2 Fixed: Non-EN KSP versions throwing exceptions or even failing to load. v2.1.1 Fixed: Each time you entered flight scene, you got one more toolbar button. v2.1.0 Added: RCS Fuel icon for "propelled" discharge toggle button. The button is now also red when the discharge is active. For-propellant discharge availability is now toggled not via file renaming, but mod's difficulty settings. Reasonless discharge can be both toggled and scaled in the difficulty settings (from no discharge up to 10 times faster than "default legacy speed"). Icon in mod toolbar to toggle RW Window (so you don't need to search for an RW part to access it). As of now the icon used is the icon of vessel controll science node found in GameData/Squad. Its copy is put in the modfolder, a "better" icon is planned. Fixed: RW Window is now a bit better spaced (the close button). RW Window treated in-physics craft with same names as a single one (probably it had some severe side-effects). v2.0.0 Built vs KSP 1.10.1 Added a patch to remove SaturatabeRW module if we find a part lacking ModuleRecationWheel on zzz_ prefixed pass Fixed severe NRE spam if ModuleReactionWheel is removed (in a wierd way) by SETI mods.
  23. Tired of asteroids hitting Kerbin every other month? Bored with your 10th identical playthrough of an asteroid redirect mission? Want bigger Δv challenges? Custom Asteroids is a rework of the stock asteroid/comet system. Just install the mod, load up a save game, and any newly spawned asteroids will appear in locations around the solar system, including an asteroid belt, a more varied near-Kerbin asteroid population, and suitable cometary orbits. No in-game configuration necessary once the included asteroid packs are installed, although nearly everything can be configured. Latest versions KSP 1.10-1.12: Version 1.9.0 (SpaceDock) (Curse) (Github) KSP 1.4-1.9: Version 1.8.0 (SpaceDock) (Curse) (Github) Custom Asteroids is available under the MIT license. Source code hosted by Github. Please report bugs on the issue tracker, and include the mod version, the KSP version, and your operating system. Public documentation, including both user's guide and public mod API. User's guide also included in the download in .md (plain-text) format. Optional Asteroid Packs I am happy to take config file submissions to go with popular solar system mods. Easy-to-reach belts around KSP 64k planets by @Sandworm Custom Asteroids version of Outer Planets Mod asteroids by @Eridan (also available from CKAN) Trans-Neidonian objects for Outer Planets Mod (also available from CKAN) Features (Optional) new spawn system that lets asteroids appear gradually over time, instead of any time there are no untracked asteroids. For players who prefer the stock spawner, set Spawner = Stock in the options file. Modular config files let you pick and choose asteroid packs, or write your own. Asteroids may appear in any number of groups, including planet intercept trajectories. All orbital elements and spawn rates are customizable. Asteroids may even be placed around planets or moons. Asteroids come in four classes: Stony, Metallic, Carbonaceous, and Icy-Organic. Different classes have different resource content (need 3rd-party mods to take advantage) and different science flavor text. Partial integration with the stock comet system, using Custom Asteroids to handle comet properties and detection but supporting the stock configuration system for comet orbit classes and science experiments. Supports update monitoring through KSP-AVC and CKAN. Known Issues There is currently no way to determine the asteroid class from the tracking station or during approach, though it will be displayed in the right-click menu once you're attached. If you install CA and Kopernicus, you can potentially have two independent asteroid systems running simultaneously. Kopernicus now offers a UseKopernicusAsteroidSystem flag that lets you use only Custom Asteroids for asteroids. Does not interact with Sentinel telescope; Sentinel-spawned asteroids and comets will follow stock rules. Credits Custom Asteroids started with some proof-of-concept code by xEvilReeperx for placing asteroids in specific orbits. I am eternally grateful for their help, as otherwise this mod would not exist. Many thanks to Thomas P. for improving the original method. Custom Asteroids was inspired by Trueborn's Custom Biomes and rbray89's Visual Enhancements, and follows a similar "customize everything" philosophy. While Custom Biomes is now defunct, I still recommend Visual Enhancements.
  24. Ever want to use bi- or tri-couplers but want to recombine the stacks before the next stage? Ever wish you could make circular stations in the VAB without having to spam struts to keep the open end closed? Here's the answer you've been looking for! ReCoupler works around the Vessel tree by identifying attach nodes that would have been connected but can't without a part having multiple parents or creating a circular structure. Once those nodes are identified, it hides them in the editor so that you don't accidentally connect anything else to that node. Then, in flight, it creates a structural link identical to the ones that normally hold parts together. But wait! There's more! When decoupling (or explosions) happens, it detects if one of the virtual connections would continue holding the vessel together and magically makes that the real connection point as if no funny business had been happening! Check out the rest of the album! And some new building styles you can use with ReCoupler: Interested? Get it from SpaceDock or GitHub now! Known bugs: Not a bug, necessarily, but it only works for stack attach nodes. Future plans: Make a decoupler that connects to 2-, 3-, or 4-engine clusters and makes their fairings work with it. Thanks Making History! Considered complete at this point. Please feel free to raise any suggestions!
×
×
  • Create New...