Tabris

I have the same issue too. I also have ZeroMiniAVC installed.

@Nertea Is there a wiki/docs for how to construct patches to integrate other mods?

Has anyone made a USI patch yet?

@TriggerAu With the new Alarm Clock in stock. is it "by design" that it is missing the close approach alarm that KAC has?

@PART[*]:HAS[@MODULE[kOSProcessor],!MODULE[KerbalEVA]]:final { %MODULE[ModuleScienceContainer] { //name = ModuleScienceContainer reviewActionName = #autoLOC_502201 //#autoLOC_502201 = Review Stored Data storeActionName = #autoLOC_502202 //#autoLOC_502202 = Store Experiments evaOnlyStorage = False // i.e. can nearby regular vessels also do this, or EVA only storageRange = 1.3 capacity = 30 canBeTransferredToInVessel = True canTransferInVessel = True showStatus = True +description = :^.*$: Adds a Science Container. %capacity = #$../MODULE[kOSProcessor]/diskSpace$ @capacity *= .1 } } ok, so this works. now to figure out how the translate the Capacity to MITS instead of Experiments.

yeah tried that also Tried KSP Discord, KOS Discord, KSP Reddit

Hey all, I've written a Module Manager patch that adds ModuleScienceContainer (i.e the Science Box) to KOS Processor parts. @PART[*]:HAS[@MODULE[kOSProcessor],!MODULE[KerbalEVA]]:final { %MODULE[ModuleScienceContainer] { //name = ModuleScienceContainer reviewActionName = #autoLOC_502201 //#autoLOC_502201 = Review Stored Data storeActionName = #autoLOC_502202 //#autoLOC_502202 = Store Experiments evaOnlyStorage = False // i.e. can nearby regular vessels also do this, or EVA only capacity = 500 storageRange = 1.3 canBeTransferredToInVessel = True canTransferInVessel = True showStatus = True +description ^= :^.*$: Adds a Science Container. } } however the line capacity = 500 means that it can hold 500 experiment results. i would like it to hold a percentage of the KOS diskspace (eg. if the KOS diskspace is 5000, the experiment space is 500Mits) also how can i make it so this information shows up in the VAB/SPH right click part info panel

Hey All, trying to make a MM patch that will add ModuleScienceContainer to anything with the module KOSProcessor This is what i have so far @PART[*]:HAS[@MODULE[kOSProcessor],!MODULE[KerbalEVA]] { %MODULE { Name = ModuleScienceContainer reviewActionName = #autoLOC_502201 //#autoLOC_502201 = Review Stored Data storeActionName = #autoLOC_502202 //#autoLOC_502202 = Store Experiments evaOnlyStorage = False // i.e. can nearby regular vessels also do this, or EVA only capacity = 0 storageRange = 1.3 canBeTransferredToInVessel = True canTransferInVessel = True showStatus = True } } This is from the ModuleManager.ConfigCache showing that the ModuleScienceContainer gets added to the part However when using print ship:partstagged("test"):modules. it doesn't list the module on the part or the actions on the PAW

You need to check if they have the USI_warehouse (i think) or USI_Recycleable Module. they might be able to store MatKits but are unable to accept the "recycled" Matkits

I'm getting a possible false positive with Windows Defender. i've logged a github issue https://github.com/KSP-CKAN/CKAN/issues/3310

are they going to be modular or monolithic

more like Ice Cubes for the Kraken's Hydrazine cocktails

1. Though was more along: Put Depot in LKO, and be able to access from Mun/Minmus at very little cost or Put Depot in Solar Orbit just outside of kerbin SOI and be able to access from Moho/Eeloo 2. Thought that might be the case. i might TRY to do a quick MM patch 4. i think in Career Mode there is a REP & Money hit, in sandbox i just don't like seeing my Kerbals Dead (without reason)

The Hoppers only output LF+Ox, Monoprop & Xenon for the multi-bays it wasn't about combining Life Support & Fuel into one but more like MaterialKits & Specialised Parts as one Hopper part instead of needing 2 hoppers

Enjoying WOLF so far. this is a bit of a mind dump of things i'm think about while playing. so i'll be editing and adding instead of cluttering up the thread. 1. Are the Orbit "biomes" (in space Low, In spcae High) counted as differnet biomes for WOLF or is it just "Orbit? 2. How hard is it to add outputs to the hoppers? (i.e H2 + Ox) 2a. Multiple Bays to the hoppers? 3. Can crew be transfered using the Transport routes? 4. Can the crew assigned to WOLF be marked as Assigned instead of Lost/Deceased?

@Tokamak as @DStaal said above Situation 2 is how it will work due to the 2.3 km physics bubble that KSP has. the default Logistics range is 150m but putting a rover in the middle simulates using that rover to travel between the bases.

@Smurfalot, i think the issue is probably parent = 0, which i think means that the docking port is the ROOT part of the craft that you are attaching to the station. you can't weld a root part because from memory the welding is more than graphical, it deletes the docking ports and directly attaches the parts on either side of the docking ports. the way to fix it is the launch a new module where the docking port isn't ROOT or use KAS(Kerbal Attachment System) to detach the part and re-attach it.

@HebaruSan @DMagic any idea when the CKAN issue will be fixed? as the new version still isn't showing up.

@DMagic is this update backwards compatible to previous KSP version or is it 1.9.1+ ?

would it be possible to bind the throttle on the rover wheels to a KAL controler or even just the new action groups? would something need to added via Module manager patch or would it require a custom plugin?

@linuxgurugamer, that might be Kopernicus with the ocean fix from a few versions back.

@Nertea, question regarding Near Future Construction. is there a reason why there isn't a 3.75 Truss "Family"?

ty @OhioBob @PART[InlineBallute*] { @MODULE[ModuleParachute] { @minAirPressureToOpen = 0.000001 @clampMinAirPressure = 0.000001 } } Would the above MM patch work? sorry for the thread derail also.

how would i go about removing the TweakChutes module from Inline Ballutes? i have tried this: @PART[InlineBallute*]:HAS[MODULE[TweakChute]]:FINAL { !MODULE[TweakChute] } but it doesn't seem to be working. i want the ballutes to deploy in the upper Atmo at the moment they only deploy @ ~ 10km AGL on Duna (atmo presure ~ 1kN/m2 (according to KER))

getting major log spam with latest release KSP 1.8.1 Part Commander 1.1.6