Mo3pp3l

Manually installed is fine but there are many problems related to ContractConfigurator. The last version of CC_RemoteTech.dll (KSP 1.3.1) I found was for max. RemoteTech v1.8.9. Spreadsheet by Bornholios Try to use the linked dll with RT 1.8.9 and give a short report. Maybe there is or come a dll backport for KSP 1.3.1 and RT 1.9.0 but for now I use the old version of RT Also delete all the MiniAVC.dll files. There is no need to have more than one. In general you don't need to check versions in an old KSP installation Your versions - My versions (maybe try it) ModuleManager v3.0.6.0 - ModuleManager v3.0.4.0 RemoteTech v1.9.0.0 / v1.9.0.131 - RemoteTech v1.8.0.0 / v1.8.9 KerbalConstructionTime v1.3.0.38 - KerbalConstructionTime v1.3.5.91 MagiCore v1.0.0.0 / v1.3.1.0 - MagiCore v1.3.1.3 / v1.0.0.0 / v1.3.1.0 TestFlightRF v1.0.6666.39406 - TestFlightRF v1.0.6713.40202 RealFuels v0.12.5.39405 / v0.12.5.0 - RealFuels v12.6.0.0 / v12.6.0 KSCSwitcher v1.0.6665.20706 - KSCSwitcher v1.4.5.0 aaa_Toolbar v1.7.16.3 - aaa_Toolbar v1.7.16.5 ConnectedLivingSpace v1.2.5.7 - ConnectedLivingSpace v1.2.6.2

2 short questions. 1. why depend the needed energy to heat or cool a vessel on the number of kerbals in it? Same volume on air that must heated or cooled. 2. On a part that has multiple Modules[Malfunction] can Kerbalsim handle these malfunctions and assign it to the right Module or will this increase the amount of failure and all Modules are affectet?

@Sigma88 That is a good idea. Will give it a try. To start and wait for MM Cache is build, only to compare to cached files, that is bad.

@sarbian Is it possible for you to make the Modulemanager working without loading KSP? Only parsing all configurations into a ModuleManager.ConfigCache This would be very helpfull because the massive time we can save if we only try to implement support for a wide range of mods.

Sorry, missed to quote. private double CalculateElectricityConsumptionRate(int numCrew, int numParts) { return (globalSettings.ElectricityConsumptionRate * numCrew) + (globalSettings.BaseElectricityConsumptionRate * numParts); } Thats the reason. In RealismOverhaul, all CommandModules have a minimum energyrequest per second and this can TACLS calculate. Fusebox / Kerbalism / AmpYear are good. There is no reason to calculate the future, but for the moment can all be calculated and displayed

Shown values of max time before energy runs out is not right handled by TACLS. Any generated or consumed energy from a part never counts. TACLS has only on math for displaying this values. private double CalculateElectricityConsumptionRate(int numCrew, int numParts) { return (globalSettings.ElectricityConsumptionRate * numCrew) + (globalSettings.BaseElectricityConsumptionRate * numParts); }

I think a good step will be to use TACLife and weight / electric / SAS changes from RO. Played a bit without the scales and model-changes and it feels good for me. Some minor changes that we can talk about, but in most cases 6.4Kerbol can be a small RO without the RL scales.

First of all thanks for for the tree. In order to also make RPL / RSS and RO working as a guide, i think the first two stages should be @start = 0.12 basicRocketry = 0.25 That than stand for 0.3m and 0.625m and match the given information on tree. After that we can think about a higher max value according to the stages in the tree to give the chance to use up to 7 engines under the tank. From heavierRocketry up it can be up to 30. Greatz Mo3pp3l

Alternate Recource Panel made by TriggerTech

As you can read in the changelog, there are no needed changes in the tree. So 19c is the actual version.