aislas

This looks great! It looks really intuitive, organized and it makes sense. I just have a question, by lifeSupport which mods are we talking about? Otherwise this looks really good, great job!

There is in fact a problem with kerbal engineer, here is a quick dirty fix: Go to the cfg file and on the third module you should see "name = FlightEngineer". KER changed the module name in the last update so it has to read now "name = FlightEngineerModule". It should look like this: @PART [*]:HAS[@MODULE[ModuleCommand]]:Final { %MODULE[MechJebCore] { MechJebLocalSettings { MechJebModuleCustomWindowEditor { unlockTechs = flightControl } MechJebModuleSmartASS { unlockTechs = flightControl } MechJebModuleManeuverPlanner { unlockTechs = advFlightControl } MechJebModuleNodeEditor { unlockTechs = advFlightControl } MechJebModuleTranslatron { unlockTechs = advFlightControl } MechJebModuleWarpHelper { unlockTechs = advFlightControl } MechJebModuleAttitudeAdjustment { unlockTechs = advFlightControl } MechJebModuleThrustWindow { unlockTechs = advFlightControl } MechJebModuleRCSBalancerWindow { unlockTechs = advFlightControl } MechJebModuleRoverWindow { unlockTechs = fieldScience } MechJebModuleAscentGuidance { unlockTechs = unmannedTech } MechJebModuleLandingGuidance { unlockTechs = unmannedTech } MechJebModuleSpaceplaneGuidance { unlockTechs = unmannedTech } MechJebModuleDockingGuidance { unlockTechs = advUnmanned } MechJebModuleRendezvousAutopilotWindow { unlockTechs = advUnmanned } MechJebModuleRendezvousGuidance { unlockTechs = advUnmanned } } } } @PART [*]:HAS[@MODULE[ModuleCommand]]:Final { MODULE { name = BuildEngineer } } @PART [*]:HAS[@MODULE[ModuleCommand]]:Final { MODULE { name = FlightEngineerModule } }