linuxgurugamer

well, that's always a good option. Sorry I can't help more

Yes, it would be. Do you want to do the work?

Are you running 32 or 64 bit Windows (& KSP)?

I'll look into it, may take a day or so Refresh your CKAN, I just updated it to CKAN, apparently I missed that one.

New release, 0.1.13: Added activate/deactivate for radiators

So that is a feature request :-)

Are you talking about turning them all on? or just extending them? I just tested, they are extending properly, but there isn't any code to turn them on (yet)

Which radiator panels, specifically, please. Regarding the USI LS, would be better to speak to @RoverDude about that. I'll add compatibility for mods which extend stock functionality (such as science experiments), but not going to add a module specifically for one mod. Note that I'm including my mods in that statement, so that IFI-LS will not be added to this, etc.

New release, 0.9.6: Added TexturesUnlimited patch by @MeCripp

New release, 0.1.3: Added optional patches: Add KER & Mechjeb to KAL9000 Add TexturesUnlimited patch thanks to @MeCripp Fixed typo in Farscape patch

First impression, looks like I need to clean my glasses

New release, 0.11.12: Localization, thanks @CN_Warren Added control of Fuel Cell Added Science activation for DMagic science parts

Oh yuck! Well, thanks for the answer

I love MM for what it does, but it's syntax is, ummm, obscure? Another, supposedly simple patch isn't working. This one should add the module if ANY of the specified modules are in the mod. Doesn't work, so what did I miss this time?: @PART[*]:HAS[@MODULE[DMReconScope]|@MODULE[DMSIGINT]|@MODULE[DMAsteroidScanner]|@MODULE[DMModuleScienceAnimate]|@MODULE[DMSoilMoisture]|@MODULE[DMSolarCollector]|@MODULE[DMBathymetry]|@MODULE[DMBioDrill]|@MODULE[DMRoverGooMat]|@MODULE[DMSeismicSensor]|@MODULE[DMSeismicHammer]|@MODULE[DMXRayDiffract]|@MODULE[DMAsteroidScanner]|@MODULE[DMAnomalyScanner]] { MODULE { name = AYA_Science } }

Thank you

A little help, please I'm writing a patch which should be applied to fuel cells, but I don't want to use the name. So, it's looking for ModuleResourceConverter which has Electric Charge as an output resource, and not having engine modules, see below: @PART[*]:HAS[!MODULE[ModuleEngines],!MODULE[ModuleEnginesFX],@MODULE[ModuleResourceConverter]:HAS[@OUTPUT_RESOURCE[ElectricCharge]]] //@PART[*FuelCell*] { MODULE { name = AYA_FuelCell } } But it's not working. If I use the name, it works, but I don't want this to be tied to a part name. Thanks in advance

Thanks, Ill look at the for inspiration.

Not that i know of. What about Bluedog? And TAC?

So which do you do manually?

Are you sure the Bluedog is available in CKAN? I'm pretty sure that @Angel-125 doesn't allow it, which would mean that it's a manual install, and not CKAN related CKAN is a tool. If you misuse it, it will break. Once you start mixing manual installs with CKAN, the chances of problems increase. Personally, I do installs of over 200 mods with CKAN, without any problems.

Are you using the Rebalanced version? If so, you can delete it, I tend to keep old copies of files around for a while

They were originally designed for tiny sized probes

Take a look at this:

Given the utter lack of feedback (other than cheers), I'll assume that values are ok and release this weekend

I've added this to the PatchManager directory, it will be available in the next release. I'm not sure about the SAS levels, I'll look into it