Jump to content

lordcirth

Members
 View Profile  See their activity

  • Posts

    501

  • Joined

  • Last visited

 Content Type 

Everything posted by lordcirth

  1. lordcirth
    I am not sure what you mean by "automatically". Perhaps Kerbalism is not installed correctly. Did you install it manually or with CKAN?
  2. lordcirth
    Stock science experiments are all replaced with Kerbalism experiments, which take time. For the geiger counter, or any science part, just enable it in the right-click menu; if there's science to do, it will say "running", otherwise "waiting".
  3. lordcirth
    It looks like there was a bug that makes Breaking Ground experiments take 10x longer than intended, which was fixed in July: https://github.com/Kerbalism/Kerbalism/commit/f66d7865388cbcefd97e78bc5235e779dd891184 However, the last release (3.14) was in July, so I guess it's not fixed yet. Thankfully, that's a tiny change that you should be able to make manually in your install. I also think that using a scientist to deploy the experiment is supposed to help, but I can't find a reference to it in the config.
  4. lordcirth
    Did you use a scientist to deploy it, and if so, what rank?
  5. lordcirth
    Yes, CKAN just downloads the mods and copies them to GameData; but it checks dependencies, version compatibility, and makes updating easy.
  6. lordcirth
    You can stick a supply container (food/water) between the pod and chute. For more than that, or O2, you probably need a service bay. Universal Storage II is also great for this, but isn't updated for 1.12 quite yet. I've also stuck O2 tanks beside the engines, inside the fairing.
  7. lordcirth
    I believe you can disable the mk1 pod as a habitat instead of detaching it?
  8. lordcirth
    Just to clarify, Kerbalism calculates the number of ignitions simply based on how powerful the engine is, and whether it's a vacuum or sea-level engine: https://github.com/Kerbalism/Kerbalism/blob/6fc4503048dd766d6d29aece9f167214bdfae24f/GameData/KerbalismConfig/System/Reliability.cfg But you should be able to override this in a separate file using FINAL. Create a file in GameData, eg raptor.cfg, containing something like: @PART[myPart]:NEEDS[FeatureReliability]:FOR[KerbalismDefault]:FINAL { @MODULE[Reliability]:HAS[#type[ModuleEngines*]] { @rated_ignitions = 5 } }
  9. lordcirth
    Did the file ownership and permissions stay the same? Are both drives formatted NTFS? Any NTFS settings changed on either?
  10. lordcirth
    If you want the fix to be separate from the mod, you could make an MM patch to change useGimbalResponseSpeed instead.
  11. lordcirth
    Is there a difference in whether you use engine plates between the two?
  12. lordcirth
    Taking a quick look at the config and copy pasting relevant bits, something like this might work: @PART[*]:HAS[@MODULE[ModuleEngines*]:HAS[#maxThrust,@atmosphereCurve]]:NEEDS[FeatureReliability]:FOR[KerbalismDefault]:FINAL { @MODULE[Reliability]:HAS[#type[ModuleEngines*]] { @rated_ignitions /= 2 @rated_ignitions ^= :\.\d+:: // Floor value to get an integer @rated_ignitions += 1 } } This will (hopefully) do vaguely what you want - halve ignition values, round down, add 1. That should leave 1 and 2 ignition engines alone, reduce 3 to 2, etc. I haven't tested it...
  13. lordcirth
    Yes, you need a pressurized pod to safely do the 30 day contract. You can see the comfort / projected stress in the VAB, in the Kerbalism tab.
  14. lordcirth
    The mk1 pod is not pressurized, so it will not lose atmosphere when you EVA. Other pods will.
  15. lordcirth
    The total mass of the ship at the instant KSP changes your status to "orbit".
  16. lordcirth
    Mods go in KSP/Gamedata
  17. lordcirth
    Had a weird issue with Cryo Tanks where selecting a foil tank would cause FPS to drop below 1, and the tanks had both foil and polyhedral textures. I reverted to 1.5.3 and the performance was fixed, but not the textures. (Reverting Core also didn't seem to make a difference)
  18. lordcirth
    Rescale = orbit size, Resize = body size.
  19. lordcirth
    In reality, you would probably keep the mass ratio the same, and increase delta-v, then remove a stage if possible. But that's too complex and specific for this rough estimate. It was intended more as a demonstration of how these efficiency gains grow exponentially.
  20. lordcirth
    Which, if you assume that each LFO stage is normally 2.5x the mass of it's payload (3.5x including it's payload), and you have a 10ton final payload on a 3-stage rocket, means that a LF/O rocket might be: 10*3.5^3 = 428.75t [1]. If you make all 3 stages cryo, your stage ratio is (2.5*.8)+1 = 3, so 10*3^3 = 270t. 63% the mass. The rocket equation adds up! (In practice you might increase Dv instead and go to a 2.5 stage design, but that's more complicated) EDIT: You can compute any hybrid, assuming there is no LFO stage above a cryo stage, as: (P*3^C)*3.5^L, where P is payload mass, C is the number of cryo stages on top, and L is the number of LFO stages below.
  21. lordcirth
    30% science sounds like an awful grind, why would you do that? (If you want to turn difficulty up, I recommend JNSQ).
  22. lordcirth
    Swapping the stock solar panel module for a Kopernicus one could do that, yeah.
  23. lordcirth
    That's a pretty broad question - generally just that they don't both try to change the same thing in different ways.
  24. lordcirth
    The part config actually specifies what tech node it's in, not the other way around. So as long as the node exists, a new part can place itself in that node. And UKS moves parts between nodes, it doesn't change the internal names of the nodes.
  25. lordcirth
    It's also licensed under the LGPL, so it would be legal even without explicit permission.
×
×
  • Create New...