Jump to content

N70

Members
  • Posts

    282
  • Joined

  • Last visited

Everything posted by N70

  1. Yeah the 2.2.0 on CKAN (now frozen) was released WAYYY too early
  2. if you wanna try to give KSP a go with 1.7, just literally copy Kerbalism16.bin to Kerbalism17.bin also, wait for Module Manager!!!!
  3. He's right though. 2.2 was far from ready, I just realized it too late. Have fun with your unbalanced game though, it's your choice after all. 2.2 won't work. Why? Because the next release is 3.0.
  4. 2.2 may be unstable. If so, please feel free to revert to 2.1.x, it's still on Spacedock/Github. big text is so people getting ready to post see this. I've reverted Kerbalism's latest version to 2.1.2. Ckan users, have fun.
  5. also, [x] science and stuff like that won't work anymore. don't worry, you can use the automation stuff with the new experiment. also, THIS WILL BREAK ANY ACTIVE MISSIONS
  6. Kerbalism 2.2.0 is dropping KSP 1.3 support. Why? Maintaining backwards compatibility is slowing down development. ## v2.2.0 for all versions of KSP from 1.4.0 to 1.6.x - 2019-03-31 ### Changes since the last release * Add Reliability to USI Nuclear Reactors (PiezPiedPy) * Fix ISRU capacities for CryoTanks and USI (PiezPiedPy) * Correct LH2 storage capacities of the Radial container for AirlineKuisine, CryoTanks and USI (PiezPiedPy) * Near Future Electrical tweaks: Uranite drilling, storage and ISRU processing added (PiezPiedPy) * Textures Unlimited support (HaullyGames) * Update habitats for the new V2 and DLC pods (PiezPiedPy) * Recalculated habitat atmosphere leakage, was originally calculated for a Human day which is 4x longer (PiezPiedPy) * Added an 'EVA's available' indicator to the Planner and Monitor (PiezPiedPy) * Optimized Planner: Part 1 - Chill the stuttering in VAB/SPH (PiezPiedPy) * Reduced Mass of ECLSS and Chemical Processors from 450kg to 40kg (Sir Mortimer) * CO2 poisoning warning message will pop up sooner to give you some time to fix the issue (Sir Mortimer) * Preemptive maintenance: if a component is found not to be in very good condition during inspection, it can be serviced to avoid a failure (Sir Mortimer) * Fixed emitters (shields) can be used in automation tab again (Sir Mortimer) * Processes ECLSS, Fuel Cells, Chemical Plant etc. can be controlled from automation tab again (Sir Mortimer) * Added Kerbalism flags (Mzxs) * Adjusted N2 leakage (Sir Mortimer) * When analyzing science in a lab, don't drive people crazy with the "Transmission finished" message for every bit of researched data (Sir Mortimer) * Going to EVA will now loose a nominal amount of nitrogen to the airlock. The amount can be changed in the settings (Sir Mortimer) * Fixed the bug where monoprop appeared out of nowhere when leaving a vessel that had none in it (#288) (Sir Mortimer) * Monoprop+O2 fuel cell is now available sooner in the tech tree. Basic Science unlocks this process along with the fuel cell (Sir Mortimer) * Added LSS system diagrams, and a small guide on how to set up O2 + water recycling (Sir Mortimer) * Hide Sickbay from automation if it is unavailable (Sir Mortimer) * New Science system (Sir Mortimer, Arthur)
  7. The Experiments would likely break any active missions
  8. @Kastruss Thank you! Make a PR on the Github repository please, at https://github.com/steamp0rt/Kerbalism @CanOmer Also about the memgraph issues: could you try the latest experimental builds at https://builds.steamport.xyz Experiments are going to be massively changed in 2.2. Thanks, but see the PRs on github.
  9. CC_RemoteTech.dll? wasn't that from like, Kerbalism 1.8?
  10. oh, i found it. Piez's build. https://cdn.discordapp.com/attachments/418222516386004994/548544454584303634/Kerbalism-v2.2.0.zip
  11. yup Kerbalism16.bin is built against KSP 1.6.1 samples can't be transmitted without being processed through a lab, iirc there hasn't been a new version in the past week or so are you high? because that's the only rational reason i can think of where someone would try to use 3 LS mods at once.
  12. hmmmm [WRN 2019-02-10 11:01:09.917] Cannot find key displayName in RESOURCE_DEFINITION [ERR 2019-02-10 11:01:09.917] Error - Cannot parse variable search when inserting new key objectDisplayNames = #$@RESOURCE_DEFINITION[LqdHydrogen]/displayName$ [WRN 2019-02-10 11:01:09.917] Cannot find key displayName in RESOURCE_DEFINITION [ERR 2019-02-10 11:01:09.917] Error - Cannot parse variable search when inserting new key defaultTank = #$@RESOURCE_DEFINITION[LqdHydrogen]/displayName$ [LOG 2019-02-10 11:01:09.917] Applying update InterstellarFuelSwitch/Patches/IFSCTmodular/@PART[CT250?]:HAS[@RESOURCE[LiterVolume]]:FOR[IFS010] to InterstellarFuelSwitch/Parts/TankRevamp/CT2501.cfg/PART [WRN 2019-02-10 11:01:09.917] Cannot find key displayName in RESOURCE_DEFINITION [ERR 2019-02-10 11:01:09.917] Error - Cannot parse variable search when inserting new key objectDisplayNames = #$@RESOURCE_DEFINITION[LqdHydrogen]/displayName$ [WRN 2019-02-10 11:01:09.917] Cannot find key displayName in RESOURCE_DEFINITION [ERR 2019-02-10 11:01:09.917] Error - Cannot parse variable search when inserting new key defaultTank = #$@RESOURCE_DEFINITION[LqdHydrogen]/displayName$ [LOG 2019-02-10 11:01:09.917] Applying update InterstellarFuelSwitch/Patches/IFSCTmodular/@PART[CT250?]:HAS[@RESOURCE[LiterVolume]]:FOR[IFS010] to InterstellarFuelSwitch/Parts/TankRevamp/CT2502.cfg/PART [WRN 2019-02-10 11:01:09.917] Cannot find key displayName in RESOURCE_DEFINITION [ERR 2019-02-10 11:01:09.917] Error - Cannot parse variable search when inserting new key objectDisplayNames = #$@RESOURCE_DEFINITION[LqdHydrogen]/displayName$ [WRN 2019-02-10 11:01:09.917] Cannot find key displayName in RESOURCE_DEFINITION [ERR 2019-02-10 11:01:09.917] Error - Cannot parse variable search when inserting new key defaultTank = #$@RESOURCE_DEFINITION[LqdHydrogen]/displayName$ [LOG 2019-02-10 11:01:09.917] Applying update InterstellarFuelSwitch/Patches/IFSCTmodular/@PART[CT250?]:HAS[@RESOURCE[LiterVolume]]:FOR[IFS010] to InterstellarFuelSwitch/Parts/TankRevamp/CT2503.cfg/PART [WRN 2019-02-10 11:01:09.917] Cannot find key displayName in RESOURCE_DEFINITION [ERR 2019-02-10 11:01:09.917] Error - Cannot parse variable search when inserting new key objectDisplayNames = #$@RESOURCE_DEFINITION[LqdHydrogen]/displayName$ [WRN 2019-02-10 11:01:09.917] Cannot find key displayName in RESOURCE_DEFINITION [ERR 2019-02-10 11:01:09.917] Error - Cannot parse variable search when inserting new key defaultTank = #$@RESOURCE_DEFINITION[LqdHydrogen]/displayName$ [LOG 2019-02-10 11:01:09.917] Applying update InterstellarFuelSwitch/Patches/IFSCTmodular/@PART[CT250?]:HAS[@RESOURCE[LiterVolume]]:FOR[IFS010] to InterstellarFuelSwitch/Parts/TankRevamp/CT2504.cfg/PART [WRN 2019-02-10 11:01:09.917] Cannot find key displayName in RESOURCE_DEFINITION [ERR 2019-02-10 11:01:09.917] Error - Cannot parse variable search when inserting new key objectDisplayNames = #$@RESOURCE_DEFINITION[LqdHydrogen]/displayName$ [WRN 2019-02-10 11:01:09.917] Cannot find key displayName in RESOURCE_DEFINITION [ERR 2019-02-10 11:01:09.917] Error - Cannot parse variable search when inserting new key defaultTank = #$@RESOURCE_DEFINITION[LqdHydrogen]/displayName$ [LOG 2019-02-10 11:01:09.917] Applying update InterstellarFuelSwitch/Patches/IFSISTLmodular/@PART[IST250?lqd]:HAS[@RESOURCE[LiterVolume]]:FOR[IFS010] to InterstellarFuelSwitch/Parts/TankRevamp/IST2501lqd.cfg/PART [WRN 2019-02-10 11:01:09.917] Cannot find key displayName in RESOURCE_DEFINITION [ERR 2019-02-10 11:01:09.917] Error - Cannot parse variable search when inserting new key objectDisplayNames = #$@RESOURCE_DEFINITION[LqdHydrogen]/displayName$ [LOG 2019-02-10 11:01:09.917] Applying update InterstellarFuelSwitch/Patches/IFSPGTmodular/@PART[PGT250?]:HAS[@RESOURCE[LiterVolume]]:FOR[IFS010] to InterstellarFuelSwitch/Parts/TankRevamp/PGT2501.cfg/PART [WRN 2019-02-10 11:01:09.917] Cannot find key displayName in RESOURCE_DEFINITION [ERR 2019-02-10 11:01:09.917] Error - Cannot parse variable search when inserting new key objectDisplayNames = #$@RESOURCE_DEFINITION[Hydrogen]/displayName$
  13. lmao did you just get stuck cuz the top folder of the zip wasn't "GameData"?
  14. Kerbalism's BP versions have been frozen on CKAN now. 2.x should now show up properly on older versionf of KSP in CKAN.
  15. If you're using Kerbalism with MM 4.0.2, ensure you're using Kerbalism 2.1.2 or above! Do not use MM 4.0.0 or 4.0.1!
  16. Ok, kerbalism 2.1.2 is out. Supports MM 4.0.2 and above.
  17. This requires me to release Kerbalism 2.1.2 too. I'll release it tonight.
  18. WARNING: Do not use Module Manager 4.x for now! There is an incompatibility. Use 3.x versions of MM. Kerbalism 2.1.2 and Module Manager 4.0.2 and above are compatible.
  19. there is an ongoing effort to integrate RO and RP-1 better-ly with Kerbalism, but @pap1723 is the one doing most of it.
  20. big "maybe" with RO... but duh it works with KSP 1.6, did you not notice the title?
×
×
  • Create New...