sarbian

[1.8.x] Module Manager 4.1.0 (October 16th 2019) - Right To Ludicrous Speed

Recommended Posts

I too would appreciate this discussion being moved to a different thread

Share this post


Link to post
Share on other sites

Consider this thread back on topic. The side conversation that you do not see above never happened, and if it did, it was somewhere else where it was on topic (which is where it should be continued please, not here

So MM eh? Awesome! More nyancats pls. 

Share this post


Link to post
Share on other sites

I agree. Sorry for starting a debate. Let's go back to my original question that was exactly related to MM, no less, no more:

Is there a way of filtering out duplicate root nodes using an MM patch?

Thanks,

Share this post


Link to post
Share on other sites
53 minutes ago, ioresult said:

Is there a way of filtering out duplicate root nodes using an MM patch?

AFAIK no, all root nodes are treated equally.  If the one you want to target has some unique feature, you can target only it with :HAS conditions

Share this post


Link to post
Share on other sites

I'm not sure this is even possible in MM and assuming it is I don't have the slightest idea how to do it, but; how can I change the "Manufacturer" for all parts, as seen in the VAB/SPH editor, so that they match the name of the mod folder (within GameData folder) the parts are contained in? For example, any parts from MechJeb would have a Manufacturer of "MechJeb2" and any parts from B9 Aerospace would have Manufacturer of "B9_Aerospace".

EDIT: Nevermind, I found this mod called PartInfo

 

Edited by Gorby1

Share this post


Link to post
Share on other sites

after I updated a long list of mods in ckan suddenly all mks parts got reset to default setting on swappable modules

and after I noiticed that some kpbs ls parts are not working at all(no ls options just autostrut and aim camera options)

also vessels in vab have warnings that "missing part modules"

this is the list of mods I have installed:

Spoiler

            "name": "SCANsat",
            "version": "v18.10"
        },
        {
            "name": "CommunityCategoryKit",
            "version": "4.1.0.0"
        },
        {
            "name": "CommunityResourcePack",
            "version": "1.1.0.0"
        },
        {
            "name": "ExtraPlanetaryLaunchpads",
            "version": "6.5.0.0"
        },
        {
            "name": "JanitorsCloset",
            "version": "0.3.4.6"
        },
        {
            "name": "Trajectories",
            "version": "v2.2.2"
        },
        {
            "name": "USITools",
            "version": "1.1.0.0"
        },
        {
            "name": "KerbalPlanetaryBaseSystems",
            "version": "v1.6.7"
        },
        {
            "name": "ModuleManager",
            "version": "4.0.2"
        },
        {
            "name": "Konstruction",
            "version": "1.1.0.0"
        },
        {
            "name": "GroundConstruction-Core",
            "version": "2.2"
        },
        {
            "name": "AT-Utils",
            "version": "v1.6.2"
        },
        {
            "name": "ConfigurableContainers-Core",
            "version": "2.4.3.4"
        },
        {
            "name": "KSPRescuePodFix",
            "version": "1.5.3.13"
        },
        {
            "name": "USI-Core",
            "version": "1.1.0.0"
        },
        {
            "name": "UKS",
            "version": "1:1.1.0.0"
        },
        {
            "name": "USI-FTT",
            "version": "1.1.0.0"
        },
        {
            "name": "USI-LS",
            "version": "1.1.0.0"
        },
        {
            "name": "FirespitterCore",
            "version": "v7.11.0"
        },
        {
            "name": "ClickThroughBlocker",
            "version": "0.1.6.10"
        },
        {
            "name": "KIS",
            "version": "1.18"
        },
        {
            "name": "KAS",
            "version": "1.1"
        },
        {
            "name": "KerbalAlarmClock",
            "version": "v3.10.0.0"
        },
        {
            "name": "EasyVesselSwitch",
            "version": "1.10"
        },
        {
            "name": "TriggerAu-Flags",
            "version": "v2.9.3.0"
        },
        {
            "name": "KerbalEngineerRedux",
            "version": "1.1.5.7"
        },
        {
            "name": "ContractConfigurator",
            "version": "1.27.1"
        },
        {
            "name": "Toolbar",
            "version": "1.7.17.15"
        },
        {
            "name": "NearFutureSolar",
            "version": "0.8.15"
        },
        {
            "name": "NearFutureSolar-Core",
            "version": "0.8.15"
        },
        {
            "name": "PreciseEditor",
            "version": "1.0.3"
        }

but I can't find "output_log.txt" in the location it should be
i really hope this bug sounds familiar to someone here so I can fix it

Share this post


Link to post
Share on other sites
37 minutes ago, alien_wind said:

but I can't find "output_log.txt" in the location it should be

It's location was moved in a recent KSP update.  Follow the red labelled link in my signature for info on where to find the logs.

Edited by Jacke

Share this post


Link to post
Share on other sites

Am I missing something  or some special day, or why are there nyancats on my loading screen,without there being any broken or incompatible mods?

Share this post


Link to post
Share on other sites
On 2/21/2019 at 2:14 AM, alien_wind said:

after I updated a long list of mods in ckan suddenly all mks parts got reset to default setting on swappable modules

and after I noiticed that some kpbs ls parts are not working at all(no ls options just autostrut and aim camera options)

also vessels in vab have warnings that "missing part modules"

this is the list of mods I have installed:

  Reveal hidden contents

            "name": "SCANsat",
            "version": "v18.10"
        },
        {
            "name": "CommunityCategoryKit",
            "version": "4.1.0.0"
        },
        {
            "name": "CommunityResourcePack",
            "version": "1.1.0.0"
        },
        {
            "name": "ExtraPlanetaryLaunchpads",
            "version": "6.5.0.0"
        },
        {
            "name": "JanitorsCloset",
            "version": "0.3.4.6"
        },
        {
            "name": "Trajectories",
            "version": "v2.2.2"
        },
        {
            "name": "USITools",
            "version": "1.1.0.0"
        },
        {
            "name": "KerbalPlanetaryBaseSystems",
            "version": "v1.6.7"
        },
        {
            "name": "ModuleManager",
            "version": "4.0.2"
        },
        {
            "name": "Konstruction",
            "version": "1.1.0.0"
        },
        {
            "name": "GroundConstruction-Core",
            "version": "2.2"
        },
        {
            "name": "AT-Utils",
            "version": "v1.6.2"
        },
        {
            "name": "ConfigurableContainers-Core",
            "version": "2.4.3.4"
        },
        {
            "name": "KSPRescuePodFix",
            "version": "1.5.3.13"
        },
        {
            "name": "USI-Core",
            "version": "1.1.0.0"
        },
        {
            "name": "UKS",
            "version": "1:1.1.0.0"
        },
        {
            "name": "USI-FTT",
            "version": "1.1.0.0"
        },
        {
            "name": "USI-LS",
            "version": "1.1.0.0"
        },
        {
            "name": "FirespitterCore",
            "version": "v7.11.0"
        },
        {
            "name": "ClickThroughBlocker",
            "version": "0.1.6.10"
        },
        {
            "name": "KIS",
            "version": "1.18"
        },
        {
            "name": "KAS",
            "version": "1.1"
        },
        {
            "name": "KerbalAlarmClock",
            "version": "v3.10.0.0"
        },
        {
            "name": "EasyVesselSwitch",
            "version": "1.10"
        },
        {
            "name": "TriggerAu-Flags",
            "version": "v2.9.3.0"
        },
        {
            "name": "KerbalEngineerRedux",
            "version": "1.1.5.7"
        },
        {
            "name": "ContractConfigurator",
            "version": "1.27.1"
        },
        {
            "name": "Toolbar",
            "version": "1.7.17.15"
        },
        {
            "name": "NearFutureSolar",
            "version": "0.8.15"
        },
        {
            "name": "NearFutureSolar-Core",
            "version": "0.8.15"
        },
        {
            "name": "PreciseEditor",
            "version": "1.0.3"
        }

but I can't find "output_log.txt" in the location it should be
i really hope this bug sounds familiar to someone here so I can fix it

In the last update breaking update were done

There was a worning this will happen

 

Share this post


Link to post
Share on other sites

[snip game update bug]

Edited by ssd21345

Share this post


Link to post
Share on other sites
8 hours ago, GrandProtectorDark said:

Am I missing something  or some special day, or why are there nyancats on my loading screen,without there being any broken or incompatible mods?

Sarbian thinks he's funny. He kind of is, but the only mod that ticks me off more is the virus that is AVC/MiniAVC.

The only two hard-coded days I could find in the source for the current version were today and April 1.

Come to think of it, I'm not running anything that requires Module Manager. Time to uninstall.

Share this post


Link to post
Share on other sites

Post like that just make me want to add new days when the cats shows up :D

Share this post


Link to post
Share on other sites
5 hours ago, danielboro said:

In the last update breaking update were done

There was a worning this will happen

 

well I updates through ckan
I don't think it has warnings there

but it's all good 
I guess the usi modules just got updated
and other mods need to update to return normal functions
too bad for old vessels and simple patch fix most of what didn't work

14 minutes ago, airtrafficcontroller said:

Hey Sarbian, just see the casts and came to ask, is it your birthday or something like that?

If it is, congrats man!

 

Luckly i'm not allergic.

yea I'm curious too
I freaked out a bit myself when the good ol' start screen started spitting out cats on rainbows(first instinct: VIRUSSSS) :sticktongue:

Share this post


Link to post
Share on other sites
46 minutes ago, airtrafficcontroller said:

Hey Sarbian, just see the casts and came to ask, is it your birthday or something like that?

If it is, congrats man!

 

Luckly i'm not allergic.

https://www.japantimes.co.jp/news/2019/02/22/national/media-national/cat-day/

 

Nowadays birthdays are a reminder that Star wars came out a while ago ;)

Share this post


Link to post
Share on other sites
2 hours ago, sarbian said:

Post like that just make me want to add new days when the cats shows up 

At least add in a popup that says that everything is ok.

I was working on a planet mod and principia and the cats Had me extremly worried and confused. For a bit

Share this post


Link to post
Share on other sites
14 hours ago, GrandProtectorDark said:

Am I missing something  or some special day, or why are there nyancats on my loading screen,without there being any broken or incompatible mods?

And so it begins. Again.

 

4 hours ago, sarbian said:

Post like that just make me want to add new days when the cats shows up

:D

Share this post


Link to post
Share on other sites

Be very afraid.

National Cat Day - Oct 29

International Cat Day - Aug 8

And Remember as far as Cats are concerned, Everyday is Caturday.

 

 

 

 

Share this post


Link to post
Share on other sites

spent last 15 minutes running virus checks

came >< that close to deleteing the user account ksp runs in, and re-installing from scratch

Share this post


Link to post
Share on other sites

Just run KSP with -ncats on the command line and you can have your Caturday.

Share this post


Link to post
Share on other sites

Hello, so I have the mods Mk2Expansion, Mk3Expansion, NearFutureElectrical, and KerbalAtomics

The Mk2Expansion and Mk3Expansion mods both introduce Nuclear Reactor parts, and as such they have a NearFutureElectrical patch that turns them into FissionReactors, however I would like to modify the ratio of INPUT_RESOURCE and OUTPUT_RESOURCE for the Reactor, as right now one has a core life of over 70 years and the other over 233 years.. Which seems excessive.. This is the patch that comes with the mod to add fission reactor modules to the reactors.

	@PART[M2X_Reactor]:NEEDS[NearFutureElectrical]:NEEDS[!KSPIntegration]:FOR[Mk2Expansion]
{
@mass = 2.0
@description = A stripped down experimental fission reactor intended for use aboard aerospace assets that produces up to 500kW of electric power. Comes with integrated radiators.
!MODULE[ModuleResourceConverter] {}
!MODULE[ModuleOverheatDisplay] {}
	MODULE
    {
        name = ModuleUpdateOverride
    }
	    MODULE
    {
        name = FissionReactor
        StartActionName = #LOC_NFElectrical_ModuleFissionReactor_Action_StartActionName
        StopActionName = #LOC_NFElectrical_ModuleFissionReactor_Action_StopActionName
        ToggleActionName = #LOC_NFElectrical_ModuleFissionReactor_Action_ToggleActionName
	        HeatGeneration = 45000
        NominalTemperature = 800
        CriticalTemperature = 1300
        CoreDamageRate = 0.01
	        EngineerLevelForRepair = 5
        MaxRepairPercent = 75
        MaxTempForRepair = 330
	        OverheatAnimation = Reactor_Heat
        FuelName = EnrichedUranium
	        // Heating
        UseSpecializationBonus = false
        AutoShutdown = true
        DefaultShutoffTemp = 0.90
        GeneratesHeat = false
        TemperatureModifier
        {
            key = 0 0
        }
	        INPUT_RESOURCE
        {
            ResourceName = EnrichedUranium
            Ratio = 0.000000126785
            FlowMode = NO_FLOW
        }
	        OUTPUT_RESOURCE
        {
            ResourceName = DepletedFuel
            Ratio = 0.000000126785
            DumpExcess = false
            FlowMode = NO_FLOW
        }
    }
	    !MODULE[ModuleCoreHeat] {}
    MODULE
    {
        name = ModuleCoreHeatNoCatchup
        CoreTempGoal = 800                
        CoreToPartRatio = 0.1                
        CoreTempGoalAdjustment = 0            
        CoreEnergyMultiplier = 0.1            
        HeatRadiantMultiplier = 0.05        
        CoolingRadiantMultiplier = 0        
        HeatTransferMultiplier = 0            
        CoolantTransferMultiplier = 0.01    
        radiatorCoolingFactor = 1            
        radiatorHeatingFactor = 0.01        
        MaxCalculationWarp = 1000            
        CoreShutdownTemp =  4500                    
        MaxCoolant = 900
    }
    MODULE
    {
        name = FissionGenerator
        PowerGeneration = 500
        HeatUsed = 800
    }
	    !RESOURCE[ElectricCharge] {}
    RESOURCE
    {
         name = ElectricCharge
         amount = 600
         maxAmount = 600
    }
    !RESOURCE[DepletedFuel] {}
    RESOURCE
    {
         name = DepletedFuel
         amount = 0
         maxAmount = 90
	    }
    !RESOURCE[EnrichedUranium] {}
    RESOURCE
    {
         name = EnrichedUranium
         amount = 90
         maxAmount = 90
	    }
    
    MODULE
    {
        name = RadioactiveStorageContainer
        DangerousFuel = DepletedFuel
        SafeFuel = EnrichedUranium
        // What enginer level is needed to transfer the safe fuel
        EngineerLevelForSafe = 1
        // What enginer level is needed to transfer the dangerous fuel
        EngineerLevelForDangerous = 3
        // Max temp for transferring fuel into or out of the part
        MaxTempForTransfer = 400
        // kW of heat per unit of waste
        HeatFluxPerWasteUnit = 5
    }
	}
	

And this is what I'm trying to do with an MM patch.

	@PART[M2X_Reactor]:NEEDS[NearFutureElectrical]:AFTER[Mk2Expansion]
{
    @MODULE[FissionReactor]
    {
        @INPUT_RESOURCE[EnrichedUranium]
        {
            @Ratio = 0.0000013889
        }
        @OUTPUT_RESOURCE[DepletedFuel]
        {
            @Ratio = 0.0000013889
        }
    }
}
	

When I checked the MM Log it says this

	[LOG 2019-02-25 22:04:38.324] Applying update Mk2Expansion/Patches/Mk2X_NFE_Functionality/@PART[M2X_Pluto]:NEEDS[NearFutureElectrical]:NEEDS[!KSPIntegration]:FOR[Mk2Expansion] to Mk2Expansion/Parts/Engines/Pluto/part.cfg/PART
[LOG 2019-02-25 22:04:38.372] Applying update Mk2Expansion/Patches/Mk2X_NFE_Functionality/@PART[M2X_AtomicJet]:NEEDS[NearFutureElectrical]:NEEDS[!KSPIntegration]:FOR[Mk2Expansion] to Mk2Expansion/Parts/Engines/Rontgen/part.cfg/PART
[LOG 2019-02-25 22:04:38.372] Applying update Mk2Expansion/Patches/Mk2X_NFE_Functionality/@PART[M2X_Reactor]:NEEDS[NearFutureElectrical]:NEEDS[!KSPIntegration]:FOR[Mk2Expansion] to Mk2Expansion/Parts/Utility/Reactor/part.cfg/PART
[LOG 2019-02-25 22:04:38.372] :AFTER[MK2EXPANSION] pass
[LOG 2019-02-25 22:04:38.372] Applying update Mk2Expansion/Patches/Mk2X_NFE_Functionality_Patch/@PART[M2X_Reactor]:NEEDS[NearFutureElectrical]:AFTER[Mk2Expansion] to Mk2Expansion/Parts/Utility/Reactor/part.cfg/PART
	

Which I assumed meant my patch had been applied, but when I go in game it had not been applied as the numbers hadn't changed (currently showing as 0.00/day when it should be showing around 0.03/day). When I checked the MM Config Cache it confirmed my suspicions as the values for the reactor parts stored in the cache had not been changed.

Anyone know what I'm doing wrong?

The only way I've found to successfully apply my numbers is by modifying the original patch that comes with the mod, but if the mod ever updates and changes the MM Config then I would have to update that again so I'd like to just use my own MM Patch that I can just drop into the folder.

EDIT: Also just checked and my patch is the very last patch mentioned in the MM log to modify these parts, which makes me believe more that it's a Syntax error.. I've tried everything I can think of to modify the values, but the best I've come up with is adding a duplicate of INPUT_RESOURCE and OUTPUT_RESOURCE which had the values I specified (Which still didn't work btw).. But still I've yet to be able to modify (or delete) the ones that already exist.

I even tried just using !INPUT_RESOURCE and !OUTPUT_RESOURCE and then re-adding my own ones from scratch, and that's what resulted in the duplication mentioned above.. Hence the original modules didn't get deleted.

EDIT: Does it have to do with the fact that I'm trying to patch a patch? Because the default part doesn't have the FissionReactor Module .. That's added in a patch and then I'm trying to modify that patch with another patch.

Edited by CoriW

Share this post


Link to post
Share on other sites

@CoriW @INPUT_RESOURCE[EnrichedUranium] looks for an INPUT_RESOURCE with name = EnrichedUranium, it knows nothing about ResourceName.  You probably want @INPUT_RESOURCE:HAS[#ResourceName[EnrichedUranium]]

Edited by blowfish

Share this post


Link to post
Share on other sites
16 hours ago, blowfish said:

@CoriW @INPUT_RESOURCE[EnrichedUranium] looks for an INPUT_RESOURCE with name = EnrichedUranium, it knows nothing about ResourceName.  You probably want @INPUT_RESOURCE:HAS[#ResourceName[EnrichedUranium]]

Huh now that you say that it seems so obvious .. That shows my inexperience with MM Patching Syntax. Thanks so much that worked like a charm!

Share this post


Link to post
Share on other sites

I'm writing a patch that modifies a significant number of blocks. It references each of them by name because I don't want to affect blocks in other mods with similar names, so using wildcards is not an option. I also have a significant list of mods this patch will not support. I have to apply it to every top level entry (PART in my case). Is it possible to specify a common need block for multiple entries or the whole file? I've read documentation on module manager and looked through a few mods that do similar things, but I have not found anything like this. Is it possible?

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.