Jump to content

garwel

Members
  • Posts

    1,107
  • Joined

  • Last visited

Reputation

704 Excellent

3 Followers

Profile Information

  • About me
    Veteran KSP newbie

Recent Profile Visitors

7,564 profile views
  1. I haven't played with MKS for years so haven't really been following its development. You may use this spreadsheet to find the recommended values for the parts and even to generate patch code.
  2. KSP1 has been my most played game ever (4000+ hours on Steam), yet that game has never really been polished. It has lots of unfinished stuff that devs started and left half-baked (consider kerbals' useless "courage" and "stupidity" values for example). So I was really happy when KSP2 was announced. I hoped it would be an opporunity to make a great game even better by producing something of a professional quality with resources of a major company. I hoped KSP2 would be deeper and more realistic than the first installment. I realized things were going wrong when I saw almost no news about development for months. The few updates we were given were nothingburgers, they were discussing third-rate stuff like kerbals' emotions instead of serious development areas like the engine, gameplay, moddability etc. Things were obvsiously moving very slow. So when they announced the release date, I wasn't happy at all. It was clear to me that the development was still in an early stage, and it was pushed out half-baked by the impatient distributor in order to get at least some of its investments back before shutting the project down. I didn't buy KSP2 (I decided that I would do it after they had a working science system and, even more importantly, moddability), but I'm still very sad to see the game die. I don't know why the development was so slow: corporate games, Covid, not enough resources, inexperienced management team or something else. But I think this slow pace is the main culprit: no one was ready to wait 10 years to publish a sequel to an already existing game.
  3. Yes, I think I found that bug. I want to fix another issue before I publish a new release though. In the mean time, you can download this DLL and replace with it the one in GameData\KerbalHealth folder. Tell me if you encounter the issue again.
  4. The best way is to start by training them at KSC to the maximum. The training screen in the Editor and the status monitor in the KSC/flight scene show you the more or less accurate prediction when the training should end for each kerbal. The duration depends on how familiar they are already with respective parts and on their intelligence (or rather, stupidity) stats. You may disable the latter in the settings, then they will all take the same time to train. For especially challenging missions, you may indeed have some initial training in the orbit of Kerbin or at its moons. The training speed depends on the science modifier in the relevant situation, so the more challenging it is, the faster they train.
  5. @Syczek Could you share the whole log (not in the post, of course, use some cloud service)? Maybe sharing the save file will also help.
  6. And here is the hot fix: Kerbal Health 1.6.8 Fixed freezes on some radstorms (the problem was due to an error in handling numeric strings) Download here
  7. Today marks 7 years since Kerbal Health's original release, so I decided, why not make a small, long overdue update? Kerbal Health 1.6.7 Added: Support for RemoteTech's connected state, at last (as requested by @Syczek) Download here
  8. Kerbal Health 1.6.6 Added: Detailed quirk information (click ? next to the list of kerbal's quirks in Health Monitor) Added: Agoraphobic and Carefree quirks Changed: Kerbals now have a chance to acquire quirks when they first appear in game (i.e. at level 0). When you load your save for the first time after updating, the existing kerbals may acquire quirks (including bad ones), so be careful. Changed: Max number of quirks is now 5 by default instead of 2. Only affects new games. Changed: EVA factor now drains 18 HP/day instead of 8 Updated: BDB patch Improved: Some optimization and refactoring Fixed: Some factors weren't correctly affected by quirks, conditions etc. Fixed: Unstable quirk didn't affect panic attack chance Fixed: Syntax error in the MKS patch Fixed: CLS-related NRE Fixed: Minor memory leaks due to not releasing some event handlers Download here
  9. Can you make that doc publicly accessible?
  10. Thanks for catching this bug. I'll fix it in the next release, which I hope to post soon. The location of your logs depends on your OS and probably whether it's a Steam install. In the case of Windows + Steam, you can find it in the main game folder (something like C:\Program Files\Steam\steamapps\common\Kerbal Space Program) as KSP.log. I think that the problem in issue #169 should be fixed in the next release, although I haven't been able to reproduce it.
  11. It doesn't look like Kerbal Health's errors. Judging by the namespace (LifeSupport), a life support mod that you are using causes the errors. As to the multiple stars radiation, I haven't played with those mods and I don't know how they are configured exactly. The thing is, KH's native radiation calculations depend on the distance from the main star. I think in multi-star mods, it's either the invisible barycenter (in this case, you may see that radiation grows as you get closer to it and not to actual stars) or one of the stars (then the others won't produce any radiation unless they have special configuration). I guess, if you also use Kerbalism and revert to its calculations, it may work better. But you are welcome to test and see what works and what doesn't. In worst-case scenario you can just disable radiation in Kerbal Health.
  12. Depends on what you want to do. Some things, like default settings, conditions, quirks etc. can be changed with simple MM patches. They are provided in the cfg file. But if you mean actually directly altering the mechanics or adding new health factors, it can only be done using reflection and/or Harmony patches. I never quite got around to making a handy API, but at least tried to expose most things as public and extendable classes.
  13. Can you share the entire log as a file? And please place such long fragments of text under spoiler tags or share them elsewhere.
  14. Thanks for letting me know, will take a look.
×
×
  • Create New...