Search the Community

Kinda tight on ram... and I dont really use the IVAs all too much..until I can purchase some more...i was wondering if there was some sort of way to remove the iva spaces without going through all the cfg files and removing the internal referencing(thatd be quite the task for me). what about an MM patch? saw a reddit post suggesting a mm patch may be able to, so then i can delete the spaces folder, saving a bit of ram for the meen time. i thought deleting the spaces folders would work by itself. but a quick google showed it wont work like that, and id most likely get game crashing since the mods part cant reference to a iva that wouldn't exist anymore. I've removed as many parts mods as i feel comfortable...and although my 'galactic neighborhood' takes a good portion of my ram..id like to keep it intact as I finally got it stable.(stock plus the entire Galactic Neighborhood I have takes 10-11gb, my current max is 16gb and ksp currently caps at 15gb when finished loading with all my mods excluding the larger ones btw. So I'm thinking the IVAs are the next big resource using item that I dont even use anyways lol. even if it saves 512mb...anything would help at this point...and ive determined texture converting isnt really worth it anymore so thats out the window lol. heres the link to the reddit discussion. any help would be appreciated. more precisly...if a MM patch exists for such a thing...link? otherwise im assuming id have to do this by hand eh?

Hi, I'm trying to reduce part counts (and build simplicity) by using Module Manager to add a little bit of battery, torque and other probe-core features to decouplers so that spent stages with leftover propellant can be switched to and de-orbited (think like Centaur or Falcon 9 second stages). I've got everything working EXCEPT that despite modding in an antenna they insist they're not in the comm network so I can't control them. Any tips on how to make that work. My MM config and a screenshot in game are below. Config file @PART[*]:HAS[@MODULE[ModuleDecouple],@MODULE[ModuleToggleCrossfeed]] { @description ^= :$: Includes HeiselCorp Guidance and Avionics package for control of spent stages. Reaction control not includes. Warrant void if used on a rocket or other aerocraft: @vesselType = Probe MODULE { name = ModuleProbeControlPoint minimumCrew = 1 multiHop = True } MODULE { name = ModuleCommand minimumCrew = 0 RESOURCE { name = ElectricCharge rate = 0.08 } hasHibernation = True hibernationMultiplier = 0.00125 } RESOURCE { name = ElectricCharge amount = 30 maxAmount = 30 } MODULE { name = ModuleReactionWheel PitchTorque = 1.5 YawTorque = 1.5 RollTorque = 1.5 RESOURCE { name = ElectricCharge rate = 0.15 } } MODULE { name = ModuleSAS SASServiceLevel = 3 } MODULE { name = ModuleDataTransmitter antennaType = INTERNAL packetInterval = 1.0 packetSize = 2 packetResourceCost = 12.0 requiredResource = ElectricCharge antennaPower = 5000 optimumRange = 2500 packetFloor = .1 packetCeiling = 5 } }

Hey, I have an issue with my ksp in which, if i have modulemanger installed solar panels will not deploy. I've tried in the VAB, in space, at the launchpad, it never deploys, i also tried it on a new save and it didnt work. I don't even get the tab that comes up. This isn't a massive issue, however i would like the mod to work without breaking my game as it is required for other mods. I know it is modulemanager because as soon as i delete modulemanager.dll from my game data it works again and i can deploy solar panels. Thank you in advance The other mods i have installed are: BoulderCO EVE (EnvironmentalVisualEnhancements) KerbalEngineer Kopernicus (doesn't work without modulemanager i believe) MechJeb2 scatterer STE(Stock Visual Enhancements) SVT(Stock Visual Terrain) - doesn't work without modulemanager TextureReplacer

Ever wanted your stock parts to be moved to Community Tech Tree nodes, but don't know how to do it yourself? WELL LOOK NO FARTHER! CTTStockRebalance is a simple mod where stock parts are moved to CTT categories, as well as putting parts in different tiers for sensible progression. Dependencies: -Community Tech Tree by Nertea. Link here. -ModuleManager by sarbian. Link here FAQ: Q: I want *insert part here* to be moved to a new node! A: Ask me! I'll see what I can do Q: Will you support mod parts? A: Maybe. Current list of parts changed: Mk1 Lander Can (Enhanced Survivability) Mk1 Crew Cabin (Enhanced Survivability) Kelus Mobility Enhancer (Space Exploration) Mk2 Lander Can (Simple Command Pods) Mk2 Service Bay (Simple Command Pods) Thermal Control System (Medium) (Heat Management Systems) 3.25m Heat Shield (Heat Management Systems) 10m Heat Shield (Advanced Heat Management) Thermal Control System (Large) (Advanced Heat Management) Known bugs: The Kelus Mobility Enhances has the wrong name in the config. Changelog: Download on Spacedock! License: GNU General Public License v3 (This is my first major mod, so let me know what I can do better in terms of my post layout.)

When Loading KSP, latest version of ModuleManager 3.0.0 gives me an error when loading? (nothing else seems to happen yet) and it points out to this file: \GameData\InterstellarFuelSwitch\PatchManager\CDT7Setups.cfg Anyone else having the same error? What should this mean? This is what it is inside that file: I think that It is calling for this InterstellarFuelSwitch/PatchManager/PluginData/CDT7Setups.cfg But there is no such file in that folder. There are only two files there. I redoanloaded IFS but it is the same.

Hello, I'm having a problem since I added a few Add-on to KSP. The game crashs while I'm building ships in the VAB or click Open At loading Module manager found 2 errors : GameData/InterstellarFuelSwitch/PatchManager/ActiveMMPatches/CDT7Setups.cfg GameData/WarpPlugin/Patches/RemoteTechFix.cfg I tried to reinstall the Adds-on without result, and can't find an answer in the forum or anywhere... https://www.dropbox.com/s/iq9gd0hdewru6v1/output_log.txt?dl=0 Can someone tell me what to do please ?

Using ModuleManager, I want to edit the tech tree or all the parts (including modded parts) to make everything be unlocked from the start of a career playthrough. This is to make a contract-focused mode that is basically the opposite of science mode

I'm re-installing mods for my KSP 1.2.2 install. I've got everything I need, but when I try to load the game, it crashes when the loading screen says MODULEMANAGER:FINAL and that's the end of it. I've got the logs, attached to this post. If anybody here can help me I will forever be in your debt.

Since 1.2 is about to start and I'm playing the pre for some time now I made some patches to enhance my gameplay a bit. This is mostly personal prefered stuff but in case someone likes it I thought I'll post it here so people can use it if they so desire. It's in AddonDevelopment because it's not a real mod or something I'd want to release and maintain, for now. Maybe later. It's just some patches with functionallity I don't want to miss. 1. ISRU and MiniISRU enhanced with the ability to convert Lf+Ox into EC. The rate stays roughly the same (900EC per 1Lf and Ox in the usual relation) as the one for FuelCells, but the EC/s is increased. 2. Crewreports for the MobileProcessingLab. 3. LaunchClamps with 1000EC/s powergeneration. 4. Start with empty MonoPropellant tanks on CommandPods. 5. Jettison fuel from ANY tank. 6. ALL science parts and basic RoverWheels at the start of career. Theyre all available as .ZIP via my GitHub. and need ModuleManager to work. Credit for some patches go back to the guys in this thread wich I started some time ago. And somehow this is a logical continuation/addition to it.

I'm trying to create a sound mod for KSP, aptly named JetSounds, which replaces stock jet engine sounds with that of some real-life counterparts. In addition, I'm trying learn the ropes of creating a proper ModuleManager patch while I'm at it. I've created custom soundfiles for my mod in Audacity, exported them as .wav files, and placed them into my JetSounds folder in GameData. The folder arrangement looks like this: GameData/JetSounds/Sounds/(soundfiles). Afterwards, I threw together a quick ModuleManager patch to integrate these soundfiles ingame. So far, I've only worked on the J-X4 "Whiplash" engine. Here's the code for my patch: //J-X4 "Whiplash" Sound Rework Patch for "JetSounds" @PART[turboFanEngine]:NEEDS[JetSounds] { @EFFECTS { @running_thrust { @AUDIO { clip = JetSounds/Sounds/RR_Olympus_Running_High volume = 0.0 0.0 volume = 0.3 0.2 volume = 0.5 0.4 volume = 0.7 0.9 volume = 1.0 1.1 pitch = 0.0 0.8 pitch = 1.0 1.4 loop = true } } @running_turbine { @AUDIO { clip = JetSounds/Sounds/RR_Olympus_Running_Low volume = 0.0 0.7 volume = 0.5 1.0 volume = 0.7 0.7 //Point at which the afterburner crackle starts to set in. volume = 0.8 0.3 volume = 1.0 0.2 pitch = 0.0 0.8 pitch = 0.05 0.8 pitch = 1.0 1.2 loop = true } } @engage { @AUDIO { clip = JetSounds/Sounds/RR_Olympus_Startup volume = 2.0 pitch = 2.0 } } @disengage { @AUDIO { clip = JetSounds/Sounds/RR_Olympus_Shutdown volume = 2.0 pitch = 2.0 } } } } My problem is that the new soundfiles for "running_turbine" and "running_thrust" are clearly audible ingame, yet the soundfiles for "engage" and "disengage" won't play. It's not that they're too quiet to hear ingame: I've tried turning up their respective volumes, both in Audacity and in the patch above, but to no avail. I'd also like to mention that I'm using vanilla KSP, aside from ModuleManager and my JetSounds mod. What can I do to fix this? Am I doing something wrong with the arrangement of folders in JetSounds, or is there a flaw in my patch? Any help would be greatly appreciated.

Hello all! I've been working on this project off and on for quite some time now. (tl;dr, magically rescale parts, follow instructions at bottom of post to install.) Backstory! I like to play on rescaled systems, 6.4x to be exact. But, this brings with it challenges as anyone who has tried it knows. Launch and Reentry are particularly trying. Several solutions exist for this problem, the two main ones that leap to mind are Realism Overhaul and SMURFF, both fantastic works that put mine to shame as far as sophistication goes. Realism Overhaul brings out the big guns as far as making the changes for a rescaled system go. SMURFF has a very comprehensive system while remaining lightweight. I admit I haven't tried it out in a while, but it's on my to-do list. Major props to @Kerbas_ad_astra for inspiration and some gleamed MM tricks. The solution presented here expands upon ROMini.cfg, from RO. It's not prominent, but available on their github page. It works by applying a similar methodology as RO does, to rescale parts more to a realistic scale size wise, along with some mass adjustments, such that density comes into line more or less naturally. A blanket scalar is applied, which was conveniently set at 1.6x times original size, so 1.25m becomes 2m, and so on. I instantly found it a blast to play with, as it kept things interesting without being too complicated to maintain. Major props to @NathanKell for this one, for originating the script/numerous other reasons. So, why is this post here? In 1.0.5, there exists a rather annoying bug in that rescaled root parts (specifically, those scaled by rescaleFactor) do not persist through load events. So, on vessel load or quickload, a rescaled part would revert to its original, smaller size. I never was able to ascertain if it was visual or if FAR was affected to. There exists a alternate method to scale parts in KSP, the model Scale variable. This one works correctly for loading, but doesn't rescale attach nodes to match. Boo! Module Manager (Props to @sarbian!) can do the appropriate scaling math on attach nodes perfectly well, but it has no means to do wildcard matching on them as far as I can tell. The MM patch looks funny, but works well to fix nodes. The problem is that a separate patch needs to exist for each kind of attach node that a part uses. This lead to a lot of copy and pasting to get a proof of concept working. So, I wrote some code. Specifically a python script to parse every cfg file in GameData, extract the node_* names, and write me the MM patch out. That's why we're here: The zip file below contains three components: A modified copy of ROMini.cfg with scaling code adjusted; a python script to generate a MM patch for said script, and a pre-generated patch file based off my install. (It's fairly large, but certainly it doesn't include every mod. It ought to cover the most common cases though, I would think.) Install! Install is easy: The config files can go anywhere in GameData. I would stick them in a directory named zzzzzzROMini, but I don't think it's strictly necessary. (We want it to run at the end of the MM passes, without using :FINAL.) The generateNodes.py ought to go in the base KSP directory (The one that GameData sits in) This also isn't strictly necessary, but it saves a step when running it, if you need to. If a node didn't scale right, and you don't wish to/aren't able to easily run the script, one or two nodes aren't too painful to edit in to the MM config: Find the part in question, and look for its "node_(whatever)" entries. Copy a block of patch and paste it to the end of the file, and adjust the text in the template. Requirements! KSP 1.0.5 Some sort of rescale, unless crazy OP is your goal semi-Optional: Python, minimum 2.7. (3 should work as far as I know.) Platform independent! Also as far as I know, this should work on Windows/OS X/Linux just fine. Optional: Having fun playing with your newly rescaled parts! Download!: Here Let me know if you have any trouble with it, i'd love to get feedback, as this is really the first 'addon' i've posted here. Good/Bad News! This will only be relevant/required for a few more weeks/couple months, as the aforementioned rescaleFactor bug has been fixed for 1.1, by, @NathanKell. (More props! And some jets, for that matter!) Still, if it is useful in the meantime, great! Also, it might serve as utility to someone who wants to write a similar helper script and/or learn python. (Which I kinda did to do this.) Snippets! These are just some extra tweaks I use, that you might all find handy. CustomBarnKit Config: This ups the mass and size limit on the level 1 and 2 launchpads to make it a little saner to blast off. Procedural Fairings: These are borrowed straight from RP-0, so all the credit goes over to them. They adjust the size limits and tech tree nodes at which the fairings unlock. It's only the front of it, just as an example, as I think this is something that might be a matter of taste as far as tech tree balance. In MM code, @ edits a value, % edits or ADDS a value if it is missing, ! deletes a value. The node names are fairly straight forward. If you're curious further, just drop a post here and lets see what we can work out. (Adjusting when the parts themselves unlock may be a worthwhile venture, as well.) Starting Launch Clamps: This one is from the 64x pack. It adjusts the launch clamps in the tree such that you start with them in the 'Start' node, as they may be of some significant utility for oversized craft. ... I swear there was another one. Blah Known Issues: If a Node needs to be added to the list manually, double check that it's the correct one; a duplicate entry will quite happily end up scaling twice (that is, squaring the scale). Procedural Fairings are still WIP: They certainly work, but they play a little bit of 'man behind the curtain', as the numbers displayed don't jive with the visuals presented elsewhere in the game. I'm still seeing what can be done about this, so its WIP. Not an "Issue" Issue, but be aware that SRBs are scaled to a VERY high TWR out of the box: This is so launch escape systems and the like can work properly. For regular "SRB-ing", you'll likely find that they're a little much. (Your Kerbalnaut may find that they're a little bit 'chunky guacamole', in other words.) Aim for 10-25% on the thrust limiters. This is easily adjustable, at the top of ROMini.cfg, in the first config block, look for @maxThrust, and tweak the multiplier to taste. Changelog: License:

So, what's the record for MM patches? Today I got 15,350(!), but I'm sure that some people have had more.

I have been trying to add Mechjeb module to some computerized parts such as SAS modules and probe cores, but I cannot get it working. I would be most grateful for advice from more experienced community members. Here is the code I am using (unsuccessfully): @PART[probeStackSmall],!MODULE[MechJebCore]]:Final { @MODULE { name = 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 = specializedControl } MechJebModuleLandingGuidance { unlockTechs = specializedControl } MechJebModuleSpaceplaneGuidance { unlockTechs = hypersonicFlight } MechJebModuleDockingGuidance { unlockTechs = specializedControl } MechJebModuleRendezvousAutopilotWindow { unlockTechs = specializedControl } MechJebModuleRendezvousGuidance { unlockTechs = specializedControl } } }

So I only want to install KIS and KAS through CKAN. Of course, Module Manager comes along with that. Only installing KIS does not require module manager. KAS, on the other hand, does. So, while I am fairly certain this is a problem with Module Manger, since I have tried it with many other mods on CKAN and the same problem is happening. The problem is, when loading the game, the loading completely stops at Mk.1-2 Command Pod. I was wondering what the problem is and how could I fix it. Thanks M8

Sorry. Figured it out. @DuoDex please delete this thread.

OK so I today I noticed quite a few of my command pods do not have aero/thermal re-entry effects. In my physics tab in the alt+f12 menu show that the ModuleManager physics is loaded an not physics.cfg. I can't seem to figure out how to set physics.cfg as the default. Is there a way to do it? I'm running the 64bit work around and have a ton of mods. I hope it's an easy fix and I won't have to go mod by mod to find the culprit.