siimav

Members
  • Content Count

    86
  • Joined

  • Last visited

Community Reputation

58 Excellent

About siimav

  • Rank
    Rocketry Enthusiast

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. But anyone doing so shouldn't come back complaining about slow timewarp rates or missing ground tiles on re-entry because those are guaranteed to not be working correctly.
  2. In that case I think you need to browse the source code to figure out the formula parameters. The letters can even mean completely different things between 2 formulas. See here and here, for example.
  3. You should start with a fresh KSP install that only have Squad and possibly SquadExpansion inside the GameData. RO is definitely available on CKAN for KSP 1.6.1.
  4. @linuxgurugamer Just letting you know that we on the RO fork will no longer be supporting KSP versions <1.6.1. So if plan on doing a PR back to RO fork with your changes then you don't have to account for older KSP versions. Also feel free integrate your clickthrough blocker into this mod.
  5. KJR Continued v3.4.1 now also has basic support for robotic parts. It doesn't do anything to make the joints between them stronger but at least the robotic parts shouldn't get locked up either.
  6. The pull request is now up on your fork. But please also consider making the releases compatible with KSP versions starting from 1.5 up to 1.7. This would be especially important for RP-1 because it will be updated for KSP 1.6.1 soon and my fixes are absolutely mandatory for [x] science to be usable.
  7. As I said previously, it doesn't matter whether you observe the Goos over different biomes or over the same one. Although you do get diminishing returns with each subsequent result until you reach the science cap. I can't remember how many experiment results it takes to hit it it though. --------------------------- On a different note - @Flupster, do you take pull requests on your fork? On my own fork, I have mostly solved the performance issues that this mod has. Previously when using it on a RSS/RO/RP-1 install, there was a second long freeze each time the experiment results were refreshed. These made using this mod pretty much unusable. My changes have made the freezes unnoticeable and can now only happen when opening up [x] Science for the first time. Among other thing, I have also fixed the integration with DMModuleScienceAnimateGeneric.
  8. The Goo experiment is not biome-specific for flying and in-space situations. The experiment storage is correct in the sense that your second sample is a duplicate of the first. The reason why [X] Science is offering you to take another sample is because you actually need to return multiple samples to get the full available science value for the Goo experiment. This means you need to either bring multiple science containers or just run multiple missions.
  9. The Golden Spreadsheet for KSP v1.6.1 can be found here. Most of the dependencies have been updated by now but there are still some that need a bit of work. Overall with a bit of tinkering it's possible to get the RSS/RO/RP-1 suite working on 1.6.1. There's also an install guide on how to get the latest RP-1 master running on KSP 1.3.1. Unfortunately it involves installing quite a lot of backports and unofficial forks to get the most out of it.
  10. If you overwrote both the xml config file and the DLL then it should work just fine.
  11. No, KSP-RO fork has neither the KJR-aware additions or the alleged performance improvements because it is based directly on Ferram's work. Meirumeiru did do a PR to Ferram's original KJR repo but unfortunately that PR was a bit of a mess and touched things that it shouldn't have. Ferram did merge it at first but then probably found out that the PR is not clean enough and then reverted the changes. This explains why meirumeiru is listed under the contributors on GitHub.
  12. I'm probably not the best example for diagnosing this issue because I'm on KSP 1.3.1 and using the RO fork of KCT. Anyway's my specs are 6600K@4.4GHz/16G ram/GTX1660Ti. My guess is that the people who reported that issue, have some kind of mod in their list that periodically marks the vessel as dirty and causes all other mods to recalculate their data.