Jump to content

Starcatcher2009 - Modder

Members
  • Posts

    15
  • Joined

  • Last visited

Reputation

4 Neutral

Recent Profile Visitors

282 profile views
  1. I don't recall the LVT-30 ever show something around 40 mins. Mind sending me a screenshot? As for your question, yes, the burn times are fixed. Things like reliability decreases the chance of a failure, but does not grant additional rated burn times. Am doing a new update soon. Sorry for being so lazy lol, I'm at school now anyways, plus also trying some new games The amount of contents in BDB is just so large lol
  2. You should only download the GitHub RELEASE. However the source should work properly, not sure why it’s like that. Mind sending me the log file?
  3. Ok, first off, NEVER type while driving. Secondly, yes, I may use a generic config using MM to apply to all parts. In fact, the majority of setting up generic settings for TestFlight is done in Generic.cfg which is patched to multiple parts at the same time. I may consider setting up placeholder TF configs to unconfigured parts, but it can only work with liquid/solid/monoprop propellers since all of the other engine types has to be done manually.
  4. I'm replying this because I have decided to NOT leave out ignition failures to other engine types. However, the probabilities will vary. As I've said before, the ignition failure shall be used as a start-up failure, regardless of engines. (Also you can also see that nuclear thermal engines in RO do have ignition failures)
  5. Thank you for your help. This will be something I'll work on later, sorry if this bothers you since I'm just in my early days of programming. I don't think I'll be interested in your mod any time, though. Mine works on a different principle.
  6. I’ll consider it. Also I’ve switched your failure curve for the actual RO one in order to implement continuousRatedBurnTime and testedBurnTime. However, the curve is still “10x failure in first 5 seconds” and so I can balance TestFlightFailure_EngineShutdown in those 5 seconds so that they have the same effect as “engine failed to startup”
  7. They show 100% reliability in the TF UI, even tho I set them to be 1%. Asking for a friend. The stock 0.625m shield is used for testing. Requires the latest TestFlight version to work. https://www.dropbox.com/s/kqa57c9zslmdius/Generic_Heatshield.cfg?dl=0
  8. Anyone got a problem where the mod keeps telling that the plugin files are in the wrong place? RSS/RO/Principia with FAR.
  9. @Starstrider42It actually shouldn't be called "ignition failures" anymore, more like "engine start-up failures" for me. Many things can go wrong in the start-up sequence, even monopropellant engines can have a poorly assembled valve that cannot handle high enough pressures. Though, different propulsion methods have their own chance of failures. Nuclear thermal engines are approximately the same as chemical ones, while electric and monoprop have something like 99.9% and higher. Balance is still underway.
  10. I have RSSExpansion. I have RP-1. RP-1 gives RSS career support. But not RSSExpansion. So I make a mod that makes RP-1 give RSSExpansion career support. DOWNLOAD: Github: https://github.com/Starcatcher2009/Realistic-Progression-For-RSSExpansion/releases/tag/v1.1.1 SpaceDock: https://spacedock.info/mod/3062/Realistic Progression For RSSExpansion No CKAN yet. SOURCE: https://github.com/Starcatcher2009/Realistic-Progression-For-RSSExpansion LICENSE: GNU General Public License v3.0 1.1.1 Changelog: Bugfix: Mod now shows up in the KSP-AVC modlist
  11. Originally created by Starstrider42: https://github.com/Starstrider42/TestFlight-Configs The mod was never updated again since 2020. So, I've decided to adopt the config pack to revive, update, modify and expand it. This will be known under the new name "TestFlight-Stock" although you can still call it "TestFlight-Configs Revived" if you like. What is TestFlight? TestFlight is an add-on originally made for the RSS/RO/RP-1 massive mod-suite that gives engines failure rates and modes, just like OhScrap and Kerbalism, and records reliability and ignition chance seperately. However, it also includes two unique features of it's own: Rated burn time and throttle curve. The former refers to the ability of an engine to perform reliably for a certain amount of time: After it passed that threshold, the failure chance increases significantly. Some engines also have TESTED burn time, which provides another certain amount of time where you can keep burning the engine after the rated burn time safely, and culmulative burn time, which means that the engines' rated burn time will be reset again after being shut down for a while. Throttle curve is an entirely new feature of TestFlight that provides unique throttle response rate for some liquid fuel engines. Just like OhScrap, an engine will become more reliable the more you fly and test it out. An engine can acquire at most 10000 "du" points through launches/flights that can help increase the reliability of the part. I thought TestFlight already have it's own config pack, why use this? TestFlight Config Stock, the official non-RO pack for TestFlight, is no ModuleManager config add-on. It's actually a set of JSON files written in order to lazily attach configs to the stockalike parts, and does not make full use of TestFlight's true potential. With TestFlight-Stock, failure rates are much more balanced and individualized: They will depend on the complexity, propellant type and tech level of the engines, whether being written in the part description itself (whether the part is stated to be explode-y or not is also taken in mind) or from the actual real-life designs of those engines. It also allows tech transfers, which is when an engine shares some of it's "du" with another identical/similar part. Parts can only share technology to those in the same manufacturer, propellant types, design/engineering principles and part families. For more information, visit the GitHub repository down below. What's different between Starstrider's original mods and your's fork? Visit the GitHub page for more info. For a short summary, I have decided to retreat TestFlight support for heat shields, add even more mod supports, balance starting and ending failure rates, fixing the MM blocks originally written by Starstrider to be compatitable with TestFlight 2.0, and more. NOTE: This is a BETA release, do not expect things to work flawlessly. Suggestions are always welcome. If you see a bug that shouldn't be there, feel free to open an issue on Github. DOWNLOAD: Github: https://github.com/Starcatcher2009/TestFlight-Stock/releases/tag/v0.3.0-beta SpaceDock: https://spacedock.info/mod/3077/TestFlight-Stock (TestFlight-Configs-Revived Now available on CKAN! SOURCE: https://github.com/Starcatcher2009/TestFlight-Stock LICENSES: MIT + GNU General Public License v3.0 Supported mods: Near Future Launch Vehicles/Propulsion/Spacecraft USI Exploration/Survival Pack, Sounding Rockets Extraplanetary Launchpads Kerbal Atomics Taerobee ...More to come! CONFLICTS: OhScrap/ScrapYard TestFlight Config Stock (the official one) 0.3.0 Changelog: Updated configs to work with TestFlight 2.0 and beyond Added support for Taerobee, USI Sounding Rockets, Near Future Launch Vehicles and Making History DLC Removed support for heat shields Future plans Add support for moar mods Further balancing TestFlight for career gameplay Add throttle curves
  12. Line 266, Module TestFlightReliability_Engine Cycle. bt15 and btPlus are supposed to be set to the rated burn time. Yet MM could not parse this variable, while it obviously could with every other variable with the same format. https://drive.google.com/file/d/1M1vG9pzdl381N_SrAgHXM7Zf3PAKL5xm/view?usp=sharing (MMPatch.log) For testing, please use this file: https://drive.google.com/file/d/1zkib0Gv3kJhUlmcCayKI3IROrw1CmXRU/view?usp=sharing and paste it into GameData. Requires TestFlight and MM.
  13. Yep, you heard the title. I've decided to adopt TestFlight-Configs and is now trying to make it up-to-date. All you need to do is download TestFlight and download this file, paste it into GameData. [snip] MMPatch.log: [snip]
  14. I wouldn't usually post an introduction about myself since I personally saw it as "cringe", but I think I should give it a try. I'm a proud KSP RSS/RO/RP-1/Principia player, but sometimes I play stockalike as well. I'm also an amateur config modder, in which my first published mod can be found here: [snip] (Go and check it out if you're interested). I really hope I can have fun here.
×
×
  • Create New...