Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

27 Excellent

About emerald

  • Rank
    Rocketry Enthusiast

Recent Profile Visitors

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

  1. The optics are good only for the stock (or a similar sized) system, a system modifying mod with kopernicus (other worlds, ...) will easily reach distances where the optics magnification is not enough. Ideally there should be another optics with a much higher magnification but very expensive and/or very energy hungry so one has the possibility to operate it under higher difficulties.
  2. I experience the same frame rate issue, documented with plain KSP 1.4.2/1.4.3 with the only mod installed ShowFPS (https://forum.kerbalspaceprogram.com/index.php?/topic/172692-141-showfps/) and either once without Kopernicus and once with Kopernicus. https://imgur.com/a/hpxaBwm The frame rate is displayed in the top right corner.KSP 1.4.3 with Kopernicus displayed a considerable frame rate drop. Player.log of 1.4.3 with Kopernicus https://drive.google.com/open?id=1e1LicezgB0y3tLhitYMCqlavAJaUAlYQ
  3. It will probably not prevent a memory crash, since 24GB of RAM is not so much anymore, applying some padding will easily increase the RAM usage of KSP (with many mods) to 50+GB.
  4. Just use the CKAN menu and set compatible version to 1.3.0, install it, be happy. it will not be automatically uninstalled even if compatible version is restored to 1.3.0 not being compatible again.
  5. The integration patches should exclude all parts with WBIConvertibleStorage module installed, so !MODULE[WBIConvertibleStorage] is missing in the list.
  6. Its a problem in KSP itself, not the parts on their own (every crewable part without a hatch has the same risk), a mod 'KSP Rescue Pod Fix' by shadowmage45 fixes this.
  7. Set the angle snap to 'no snap' before repositioning and they will no longer move into a snapped position.
  8. I've just seen now, FOR: on patches is seen quite rare and most people expect it to do domething else than it does - it makes the patch behave as if it were (in this case) USILifeSupport or at least part of USILifeSupport and not just modifying some properties! FINAL: is just bad behaviour, FOR: is outright dangerous if not known exactly what it does.
  9. Only use :FINAL if you are absolutely require this patch to be the last and you have to deny further modifications! Otherwise use AFTER and co.
  10. There are alot of traces coming out of X-Science: [LOG 21:25:46.852] [6/18/2017 9:25:46 PM [x] Science!]: <Trace> (StatusWindow) - ScienceThisBiome: 5 / 0 [LOG 21:25:50.012] [6/18/2017 9:25:50 PM [x] Science!]: <Trace> (StatusWindow) - Finding Module for Science Report: SRExperiment03 [LOG 21:25:50.012] [6/18/2017 9:25:50 PM [x] Science!]: <Trace> (StatusWindow) - Running Experiment SRExperiment03 on part SR.Payload.01 [LOG 21:25:50.012] [Experiments]: Setting FX Modules to 1... [LOG 21:25:50.012] [Experiments]: FX Modules set: 1 [LOG 21:25:50.702] [6/18/2017 9:25:50 PM [
  11. Ok, so as long as the energy of the charged particles is converted there's no energy left to convert in the first place, heat and charged particles are not treated as different kinds of energy and counted and treated separately of each other. I misunderstood the direct energy conversion, which i assumed would only ever convert charged particles and leave the thermal energy to be used/converted otherwise. Thanks
  • Create New...