Spagoose

What's the situation with installing/uninstalling this mid-save? Will it work with existing rockets already in flight or only work on new ones?

Thanks, that's what I suspected, I assume then that all new rockets, and saved rockets where I have deleted and replaced the stock chutes after uninstalling the mods should then work as stock? I need to get them back to stock behaviour because I'm having weird parachute behaviour I suspect may be a module manager conflict and this will help me identify if/which mods could be the cause. Edit: since I'm here, is there a deploy when safe option like stock? Unless I'm blind I don't see it.

Is it safe to to uninstall realchute mid save? Or will I have to start a new save to get stock behaviour? All my flights have stock chutes on them but they have been tweaked by realchute, will they revert to stock or break?

Is there any way of hiding the biome from being displayed when you are picking a location on the map? I want to use satscan for locating biomes.

As it currently stands, the best way to make rovers is using the modular girder/octagonal strut parts to make up them main body with structural panels. They do the job fine, but their hollow and empty appearance sort of ruins it. What I suggest is that alternate solid skins be made. That way it would be possible to make better looking rover bodies more akin to that of the RoveMate probe core. It would be more believable that wiring to the attached parts are hidden inside them rather than parts working through space magic. Squad has added scanner arms, so why not parts to make actual decent looking rovers for them to go on?

If you read my other posts on this page I outline the whole issue. But effectively this mod has it's own version of boiloff which breaks the CE version, and you can't cool stock tanks either for some reason. If you want those features you need to remove CC and use the b9 fuel switch which is bundled with cryo engines. You might find that less complicated for swapping fuels too.

You can set up the fuel tanks with the right ratios easily. Open up the tank editor, delete the LF and OX, choose the cryogenic fuel option at the top and select max. The tanks will then be filled with LH2 + Ox for cryogenic engines in the correct ratio. I suspect you are just removing the liquid fuel part and swapping LH2 in, which doesn't work because LH2 uses less Ox than the same volume of LF. However currently the actual fuel boiloff element that comes with cryo engines will not work with CC.

A modulemanager patch could easily add a day of resources to each command module. But considering there is a 15 day period you can go without supplies, you can get to the Mun without any supplies on board, and by the time you do actually need them, a days worth offers no benefit. You can change the time before power outage affects kerbals in the life spport settings under EC Time in seconds. personally I have it at 7200, which is 2 hours, the same as TAC life support. As for food, 15 days is reasonable.

Okay that makes sense, thanks for the help, that fixes my headcanon issues. I also didn't consider that it makes for a great reason to build habitat stations. Cheers.

Fair enough, I always assumed that the idea was that you needed to take all your habitation requirements with you on your actual mission rather then just having a stay in a luxury space hotel beforehand. What is the actual benefit of taking habitation with you? All I can think of is that it reduces how often you need to EVA but otherwise kerbals are happy to be cooped up providing they get some fresh air every once in a while? Thanks for answering btw, it's making a lot more sense now.

The main issue is that at the moment, it is definitely 100% possible to kick a kerbal into a rover for months at a time providing there are 2 or more kerbals in it. You can easily go to any planet in a ship with just a 2 seater command pod and no other hab modules if you wanted to, all you would need to do is get a high home timer from a station in kerbin orbit before you started the voyage. After that every so often one kerbal quickly does a 1 second EVA out and back into the exact same ship to reset the other kerbals hab timer. That kerbal then has a refreshed hab timer without ever leaving the ship. So effectively you can last for years by just EVAing each kerbal once every few days. Effectively as it stands the hab timer is irrelevant on any ship/rover/etc with 2 or more kerbals on board. I made the last post about a mechanic change but thinking about it now, the only fix really needed is that the hab timer isn't reset on a kerbal who hasn't moved into a new vessel. I think this whole issue stems from the fact that the hab time on a vessel increases when a kerbal EVAs, any kerbals still inside the ship have their remaining hab time updated and reset along with the ship when in reality JUST the ship hab time should change. The ditching habitation modules as the home timer runs out is also something that wouldn't happen in normal missions either, if anything it would liquid kerbals off and reduce their habitation even more, while it is beneficial currently to shed the mass and EC usage.

That's true but there are some other significant issues that stem from this beyond what I posted as well which I'm surprised are not mentioned more. For instance as home time decreases, you can effectively dump excess habitation modules so that hab time stays in line with remaining home time. Likewise you can just put a load of hab time on the ship and dump it on the launch pad, you effectively have that home time for the whole trip as long as you EVA. I have been thinking about how the system could be fixed and one idea was to have each kerbal have a habitation percentage that drops from 100% to 0%. Hab modules would decrease the rate of decline rather than just adding n days. That way hab time isn't a static amount that can be reset via EVA and if you dropped hab modules or tried stocking up home time, it would have no effect as your actual hab time would depend on how much you actually have on your ship. You also wouldn't need to differentiate hab and home time any more which would reduce confusion. And finally the only way to increase hab percentage would be to use habitats like it currently is. This method would probably require the least amount of rework compared to other fixes, you just need to swap the timer attached to kerbals with a percentage (which in reality would still be a timer) and change it so that hab parts just act as a multiplier to the kerbals percentage/timer rather than adding time themselves. The only potential issue would be after a very long voyage, if a kerbal has very low hab time moves into a reentry capsule, the might end up with just a few minutes of time before striking. But this could be dealt with like supplies and electric charge with a few days grace period after its empty. Unfortunately I doubt RoverDude has much time to do this himself and I am not in a position to take the time out of my day to sift through the code myself to do it.

It has been like this for ages. Infact it was reported here: https://github.com/UmbraSpaceIndustries/USI-LS/issues/199 but was never actually fixed. Have you activated all the habitation modules manually? It should tell you how much actualy hab time your ship can give at the top of the life support window, but you can only see how it is calculated in the VAB.

I'm trying to make an unmanned rover but I'm having issues with the Rovemate body (what a shocker). It's has odd behaviour with the core drill, where the drill doesn't decide if it needs to be angled or not correctly. Is there any way to toggle this manually. Alternatively, what better alternatives are there for probe bodies? Seeing as the Rovemate is fairly small to begin with, are there any better options that could be better scaled up? Also what is the probe body used in the image on the OP in two of the images, the one in the top centre?

So there is some pretty odd behaviour with EVA and hab time which is fairly broken. When you EVA a kerbal, the total hab time of a ship changes to reflect how many kerbals are still inside as expected. However when it does this, the kerbals inside a ship have their hab times reset to the ships current maximum. Effectively by EVAing a kerbal, you can reset the hab timer for the rest of the kerbals in a ship. Normally this wouldn't be a problem because the home timer never resets. HOWEVER If you dock at a station with lots of hab, then you may have a high home time, and with the ability to reset hab time you can potentially last years without actually having any habitation increasing parts on a ship. All you would need to do is EVA when the hab timer is low to reset it. TL;DR EVAing a kerbal resets the hab timer for other kerbals in a ship when the total ship hab time changes which is potentially a broken mechanic.

Sorry I should have been more specific: If you have CC installed, it's version of cryogenics works as expected (as far as I can tell). However if you wanted to use the CryoTanks version of cryogenics instead, you can't as it's own boiloff stops working and you lose the ability to cool tanks in right click context menu at the cost of electric charge which CT adds. The only way to restore CT cryogenic functionality is to remove ConfigurableContainers.dll, as removing Cryogenics.cfg leaves you with both versions of cryogenics non-functional. As for why this happens, I have no idea. Also B9 part switch toggle in the VAB also no longer appears but I am assuming that is intended behaviour.

Thanks for that, after a bit more testing, I think my issues seem to be due to the fact that I also have Nertea's CryoTanks. As it stands you can't use the CryoTanks cryogenics implementation while also having this mod installed, simply removing or modifying Cryogenics.cfg stops any boiloff full stop while the rest of your cryogenics code, I'm assuming, is bundled in ConfigurableContainers.dll rather than having it's own plugin so you can't disable it without breaking CC, which is a darn shame because it's a load better than B9 part switcher.

Yeah I just tested, removing it has given me the cooling toggle and normal boiloff. The annoying thing is that this is a dependency of global construction which itself is a dependency of USI MKS. So if you want MKS, it will install this without letting you know. Just deleting the cryo config alone stops any boiloff at all which is obviously not ideal, while deleting the whole mod could potentially break MKS. Again I need to play around with it and find a way to disable the boiloff without disabling the whole mod. Configurable containers also disables b9 part switch, so this mod definitely has its fingers in a lot of honey jars. But here is the cause for anybody trying to figure out this issue in the future.

Is there any documentation on how cryogenic cooling in this mod works? I suspect this is why boiloff with cryogenic engines has been acting weird but can't figure out how it is supposed to act in this mod. As it stands if I leave a stock fuel tank filled with LH2 on the launch pad, nothing happens for about ~115 days. After that point boiloff finally starts. I suspect it has to do with the LH2 temperature reaching around 248 degrees. Temperature only drops 0.1 degree per day on kerbin which seems excessively slow. Is this the intended behaviour?

I will do that when I finish work, in the meantime after looking through some of the mods I have found that Global Construction contains Configurable Containers as a dependency, which happens to have its own cryogenics.cfg: CRYOGENICS { // used when no VaporizationHeat is provided for a resource SpecificHeat2VaporizationHeat = 100 // limits energy transfer between the resource volume and the rest of the part InsulationConductivity = 3.2e-9 // kW/m/K; this looks like Dewar bottle, as normal insulators are five orders of magnitude less efficient // the fraction of the tank's volume that is used for insulation InsulationVolumeFraction = 0.06 // how much kJs does 1 electric charge contain? ElectricCharge2kJ = 10 // maximum total power consumption of any cooler (Ec/s) MaxAbsoluteCoolerPower = 500 // maximum power consumption of a cooler (Ec/s) per unit thermal mass MaxSpecificCoolerPower = 1 // if the power supply drops below this fraction, the cooler is automatically disabled ShutdownThreshold = 0.99 RESOURCE { name = LqdHydrogen BoiloffTemperature = 25 // ~boiling point + 5 VaporizationHeat = 447000 // kJ/t http://www.engineeringtoolbox.com/hydrogen-d_1419.html CoolingEfficiency = 0.1 // how far the cooler is from the Carnot cycle } RESOURCE { name = LqdDeuterium BoiloffTemperature = 27 // ~boiling point + 5 VaporizationHeat = 322215 // kJ/t http://encyclopedia.airliquide.com/Encyclopedia.asp?GasID=20 CoolingEfficiency = 0.1 // how far the cooler is from the Carnot cycle } RESOURCE { name = LqdTritium BoiloffTemperature = 27 // ~boiling point + 5 VaporizationHeat = 322215 // kJ/t stub; same as deuterium CoolingEfficiency = 0.1 // how far the cooler is from the Carnot cycle } RESOURCE { name = LqdMethane BoiloffTemperature = 120 // ~boiling point + 10 VaporizationHeat = 510000 // kJ/t http://www.engineeringtoolbox.com/methane-d_1420.html CoolingEfficiency = 0.3 // how far the cooler is from the Carnot cycle } RESOURCE { name = LqdCO2 BoiloffTemperature = 220 // ~boiling point + 3, at 5atm VaporizationHeat = 574000 // kJ/t http://www.engineeringtoolbox.com/fluids-evaporation-latent-heat-d_147.html CoolingEfficiency = 0.6 // how far the cooler is from the Carnot cycle } RESOURCE { name = LqdCO BoiloffTemperature = 90 // ~boiling point + 10 VaporizationHeat = 214680 // kJ/t http://encyclopedia.airliquide.com/Encyclopedia.asp?GasID=45#LiquidGasConversion CoolingEfficiency = 0.3 // how far the cooler is from the Carnot cycle } RESOURCE { name = LqdHe3 BoiloffTemperature = 5 // ~boiling point + 1 VaporizationHeat = 20754 // kJ/t stub; same as He4 CoolingEfficiency = 0.07 // how far the cooler is from the Carnot cycle } RESOURCE { name = LqdHelium BoiloffTemperature = 5 // ~boiling point + 1 VaporizationHeat = 20754 // kJ/t http://www.engineeringtoolbox.com/methane-d_1420.html CoolingEfficiency = 0.07 // how far the cooler is from the Carnot cycle } RESOURCE { name = LqdNitrogen BoiloffTemperature = 80 // ~boiling point + 10 VaporizationHeat = 199180 // kJ/t http://encyclopedia.airliquide.com/Encyclopedia.asp?LanguageID=11&CountryID=19&Formula=&GasID=5&UNNumber=&EquivGasID=32&VolLiquideBox=&MasseLiquideBox=&VolGasBox=&MasseGasBox=&RD20=29&RD9=8&RD6=64&RD4=2&RD3=22&RD8=27&RD2=20&RD18=41&RD7=18&RD13=71&RD16=35&RD12=31&RD19=34&RD24=62&RD25=77&RD26=78&RD28=81&RD29=82 CoolingEfficiency = 0.2 // how far the cooler is from the Carnot cycle } RESOURCE { name = LqdOxygen BoiloffTemperature = 100 // ~boiling point + 10 VaporizationHeat = 213050 // kJ/t http://www.engineeringtoolbox.com/methane-d_1420.html CoolingEfficiency = 0.3 // how far the cooler is from the Carnot cycle } } //:mode=c#: Needless to say I wasn't expecting a fuel switcher type mod to have it's own cryogenics, so currently I suspect this could be what is causing the issue, I'll run a clean instance of ksp with just cryo engines with and without this mod later this evening to see if it is the culprit.

Thats how I was testing it after I realised something was up, ~115 days on the launchpad then suddenly boiloff begins. The curious thing is that none of the other mods I use have their own boiloff implementation, at most they rely on your CryoTanks like USI mods, and I'm not using anything like realism overhaul, kerbalism, real fuels etc. Narrowing down what mod is causing this is likely going to be a nightmare, but I guess the fact that boiloff does happen after fuel reaches a certain temperature is probably a clue that something else is playing with boiloff or there is some weird incompatibility. I'm guessing SimpleBoiloff.dll does not display the temperature of the LH2 in the right click context menu on the tanks if that is irrelevant in your mods, so if I can figure out what mod is adding that, then I may find what is causing it. Heres my modlist excluding graphical mods incase anyone happens to know what could be the cause: Real Chutes USI mods Near Future Mods Cryo Engines Kerbal Atomics KIS KAS SCANSAT Universal storage Global Construction Restock Restock+ Remotetech Deadly Reentry Joint Reinforcement Bon Voyage Real Plumes EVA fuel KER Dmagic orbital science

How exactly does boil-off work? I have a ship that has standard tanks with no cooling and there is absolutely no boil-off for the first 90 days or so of a journey. After that point boil-off starts. What is triggering the boil-off and why doesn't it start as soon as a ship launches? Edit: It seems like it has something to do with the temperature of the LH2 in the fuel tanks, but I can't figure out what affects the temperature. It takes roughly 115 days in Kerbin for the LH2 temp in a Rockomax X200-32 tank to drop to about 248 degrees, at which point boiloff will then start. What affects the temperature of the LH2? 115 days seems a long time to store LH2 without any boiloff.

I'm having issues with the tracking station range, I'm playing root mode with the range modifier set to 0.5 and yhe tracking station is level 3 so I'm guessing the range is 75,000km for that. With a communotron 16 alone I was connecting straight to the KSC from the Mun when in sight. I turned off the tracking station upgrade range in the remotetech settings but that didn't cut the connection either so what is going on? Either the range of an unupgraded station is also huge or that setting doesn't do what I thought it did? Also what even is the range of the base tracking station?

I have been playing with instant resource scan turned on and I want to turn it off to make things a bit more involved and I have 2 questions: Will changing this setting mid game work? Will future planets I scan with the M700 require each biome to be covered or will I need to start a new game? What happens to planet maps that have been scanned and filled out automatically with the instant resource scan? Does it stay filled out or does it go back and remove resource data that wasn't scanned? Or would I need to delete the resource data and rescan?

I'm hoping someone can explain how to best use these engines. I have unlocked the Volcano, but can not find an instance where it is better than the Swivel or Reliant engines. If I make a basic ship with just a command pod with a fuel tanks and and reliant engine, it weighs 4.4 tonnes with 1820m/s dV, while if I use a ship with the Volcano engine with 2 LH2 fuel tanks, I get a ship at 5.3 tonnes with 1583m/s dV. I have experimented with various amounts of fuel and at no point was the Volcano worth using. I can only assume I am doing something wrong, so could someone shed some light on what is going on? Do I need to remove some oxidiser? Edit: So apparently I need to change the LH2/Oxidizer ratio, what is the best way to balance this properly?