[1.8.x-1.12.x] Module Manager 4.2.3 (July 03th 2023) - Fireworks season

liquidhype · December 21, 2014

I just released version 2.5.5.
Bug fix for value with dot or dash in their name (Like Kopernicus cfg)

All I get when I try downloading 2.5.5 is a 404 Error message

sarbian · December 21, 2014

Fixed now, thanks !

Gaalidas · December 21, 2014

Yeah, apparently your newest release does not exist. Which means... something that does not exist does not exist. Which means... I have no idea what I'm talking about... because it doesn't exist. Do I exist? Who am I.. where am I... and most importantly... no wait... it doesn't exist... what doesn't exist? If existence does not exist... then what is this? Hellooo... is anybody there? I'm not defective... honest....

The user writing this message has just encountered a fatal error. Reason: it doesn't exist.

EDIT: Oh, it exists now. Disregard.

jlcarneiro · December 21, 2014

sarbian, I'm sorry to inform that I use NEAR and it loaded fine with MM 2.5.4. After MM 2.5.5, I get 14 errors.

[LOG 16:36:59.420] [ModuleManager] ModuleManager: 1581 patches applied, found 14 errors
14 errors in GameData/NEAR/NEAR.cfg

Unfortunately, I don't find anything else on KSP.log and don't know how to debug NEAR.cfg...

Can you help me?

Edited December 21, 2014 by jlcarneiro
Added excerpt from KSP.log

Kowgan · December 21, 2014

Thank you once again, Sarbian! :sticktongue:

Starwaster · December 21, 2014

Yeah, apparently your newest release does not exist. Which means... something that does not exist does not exist. Which means... I have no idea what I'm talking about... because it doesn't exist. Do I exist? Who am I.. where am I... and most importantly... no wait... it doesn't exist... what doesn't exist? If existence does not exist... then what is this? Hellooo... is anybody there? I'm not defective... honest....
The user writing this message has just encountered a fatal error. Reason: it doesn't exist.
EDIT: Oh, it exists now. Disregard.

Did anyone hear something?

sarbian · December 21, 2014

sarbian, I'm sorry to inform that I use NEAR and it loaded fine with MM 2.5.4. After MM 2.5.5, I get 14 errors.
[LOG 16:36:59.420] [ModuleManager] ModuleManager: 1581 patches applied, found 14 errors
14 errors in GameData/NEAR/NEAR.cfg
Unfortunately, I don't find anything else on KSP.log and don't know how to debug NEAR.cfg...
Can you help me?

I just launched with the current NEAR and I had no errors. You'll need to put KSP.log somewhere like dropbox so I can have a look.

Recca · December 21, 2014

Here are errors I get with new Module Manager and FAR. Guess it will be similar to these with NEAR.

[LOG 20:22:08.002] [ModuleManager] Applying node FerramAerospaceResearch/FerramAerospaceResearch/@PART[*]:HAS[@MODULE[ModuleResourceIntake]&!MODULE[FARBasicDragModel]&!MODULE[FARWingAerodynamicModel]&!MODULE[FARControllableSurface]]:FOR[FerramAerospaceResearch] to Squad/Parts/Mk1/mk1fuselageIntake/MK1IntakeFuselage
[LOG 20:22:08.005] [ModuleManager] Cannot parse variable search command: area
[LOG 20:22:08.006] [ModuleManager] Cannot parse variable search when inserting new key S = #$../MODULE[ModuleResourceIntake]/area$
[LOG 20:22:08.009] [ModuleManager] Applying node FerramAerospaceResearch/FerramAerospaceResearch/@PART[*]:HAS[@MODULE[ModuleResourceIntake]&!MODULE[FARBasicDragModel]&!MODULE[FARWingAerodynamicModel]&!MODULE[FARControllableSurface]]:FOR[FerramAerospaceResearch] to Squad/Parts/Structural/engineBodyRadial/engineBodyRadial/radialEngineBody
[LOG 20:22:08.012] [ModuleManager] Cannot parse variable search command: area
[LOG 20:22:08.013] [ModuleManager] Cannot parse variable search when inserting new key S = #$../MODULE[ModuleResourceIntake]/area$
[LOG 20:22:08.014] [ModuleManager] Applying node FerramAerospaceResearch/FerramAerospaceResearch/@PART[*]:HAS[@MODULE[ModuleResourceIntake]&!MODULE[FARBasicDragModel]&!MODULE[FARWingAerodynamicModel]&!MODULE[FARControllableSurface]]:FOR[FerramAerospaceResearch] to Squad/Parts/Structural/engineNacelle/engineNacelle/nacelleBody
[LOG 20:22:08.017] [ModuleManager] Cannot parse variable search command: area
[LOG 20:22:08.018] [ModuleManager] Cannot parse variable search when inserting new key S = #$../MODULE[ModuleResourceIntake]/area$
[LOG 20:22:08.020] [ModuleManager] Applying node FerramAerospaceResearch/FerramAerospaceResearch/@PART[*]:HAS[@MODULE[ModuleResourceIntake]&!MODULE[FARBasicDragModel]&!MODULE[FARWingAerodynamicModel]&!MODULE[FARControllableSurface]]:FOR[FerramAerospaceResearch] to Squad/Parts/Utility/airIntakeRadialXM-G50/airIntakeRadialXM-G50/airScoop
[LOG 20:22:08.023] [ModuleManager] Cannot parse variable search command: area
[LOG 20:22:08.024] [ModuleManager] Cannot parse variable search when inserting new key S = #$../MODULE[ModuleResourceIntake]/area$
[LOG 20:22:08.025] [ModuleManager] Applying node FerramAerospaceResearch/FerramAerospaceResearch/@PART[*]:HAS[@MODULE[ModuleResourceIntake]&!MODULE[FARBasicDragModel]&!MODULE[FARWingAerodynamicModel]&!MODULE[FARControllableSurface]]:FOR[FerramAerospaceResearch] to Squad/Parts/Utility/CircularIntake/circularIntake/CircularIntake
[LOG 20:22:08.028] [ModuleManager] Cannot parse variable search command: area
[LOG 20:22:08.029] [ModuleManager] Cannot parse variable search when inserting new key S = #$../MODULE[ModuleResourceIntake]/area$
[LOG 20:22:08.032] [ModuleManager] Applying node FerramAerospaceResearch/FerramAerospaceResearch/@PART[*]:HAS[@MODULE[ModuleResourceIntake]&!MODULE[FARBasicDragModel]&!MODULE[FARWingAerodynamicModel]&!MODULE[FARControllableSurface]]:FOR[FerramAerospaceResearch] to Squad/Parts/Utility/ramAirIntake/ramAirIntake/ramAirIntake
[LOG 20:22:08.035] [ModuleManager] Cannot parse variable search command: area
[LOG 20:22:08.036] [ModuleManager] Cannot parse variable search when inserting new key S = #$../MODULE[ModuleResourceIntake]/area$
[LOG 20:22:08.038] [ModuleManager] Applying node FerramAerospaceResearch/FerramAerospaceResearch/@PART[*]:HAS[@MODULE[ModuleResourceIntake]&!MODULE[FARBasicDragModel]&!MODULE[FARWingAerodynamicModel]&!MODULE[FARControllableSurface]]:FOR[FerramAerospaceResearch] to Squad/SPP/IntakeRadialLong/part/IntakeRadialLong
[LOG 20:22:08.041] [ModuleManager] Cannot parse variable search command: area
[LOG 20:22:08.042] [ModuleManager] Cannot parse variable search when inserting new key S = #$../MODULE[ModuleResourceIntake]/area$
[LOG 20:22:08.045] [ModuleManager] Applying node FerramAerospaceResearch/FerramAerospaceResearch/@PART[*]:HAS[@MODULE[ModuleResourceIntake]&!MODULE[FARBasicDragModel]&!MODULE[FARWingAerodynamicModel]&!MODULE[FARControllableSurface]]:FOR[FerramAerospaceResearch] to Squad/SPP/ShockConeIntake/part/shockConeIntake
[LOG 20:22:08.047] [ModuleManager] Cannot parse variable search command: area
[LOG 20:22:08.048] [ModuleManager] Cannot parse variable search when inserting new key S = #$../MODULE[ModuleResourceIntake]/area$
[...]
[LOG 20:22:12.982] [ModuleManager] ModuleManager: 72 patches applied, found 8 errors
8 errors in GameData/FerramAerospaceResearch/FerramAerospaceResearch.cfg

Sturmgeschutz · December 21, 2014

You're the man!

sarbian · December 21, 2014

I'd be the man if I did not make such stupid mistake.

2.5.6 is here. Thanks for the log.

Edited December 21, 2014 by sarbian

BLUAV8R · December 21, 2014

So i'm looking for a config that will take any tanks with stock liquid fuel and oxidizer and convert them into modular tanks by doing ([volume of liq. fuel) + [volume of oxidizer]) x 5 = Modular Fuel Tank Volume

I know there was a config for this at one point here: https://github.com/NathanKell/ModularFuelSystem/blob/master/RealFuels/Fallback.cfg

But that link no longer works I wanna write my own but i'm having some trouble, can anybody help?

I'm basically looking for a config that will have the stock volumes (of the entire tank combined) multiplied by 5 and turned into a modular fuel tank for Real Fuels

sarbian · December 21, 2014

Have a look at the post that explain Variable (I had the marvelous idea of linking it in the first post just now).

BLUAV8R · December 21, 2014

Have a look at the post that explain Variable (I had the marvelous idea of linking it in the first post just now).

Thanks a lot! That helped explain a lot of stuff I couldn't figure out form the original few posts, but I have some questions about the search functions, so if I understand the syntax, this is what I have so far (please correct me if i'm wrong)

@PART[*]:NEEDS[RealFuels]:HAS[@RESOURCE[LiquidFuel]]:HAS[@RESOURCE[Oxidizer]]]:Final
{
	MODULE
	{
		name = ModuleFuelTanks
		volume = #$/RESOURCE[LiquidFuel]/amount$
		@volume += #$/RESOURCE[Oxidizer]/amount$
		@volume *= 5
		type = default
	}

	!RESOURCE[LiquidFuel]

	!RESOURCE[Oxidizer]
}

@PART[*]:NEEDS[RealFuels]:HAS[@RESOURCE[MonoPropellant]]:Final
{
	MODULE
	{
		name = ModuleFuelTanks
		volume = #$/RESOURCE[MonoPropellant]/amount$
		@volume *= 5
		type = ServiceModule
	}

	!RESOURCE[MonoPropellant]
}

I think I got a little confused with the search functions, would this current config work?

Keep it cool :cool:

Edited December 21, 2014 by Sippyfrog
bracket error

sarbian · December 21, 2014

Looks OK, beside the R from RESOURCE that went west

BLUAV8R · December 21, 2014

Looks OK, beside the R from RESOURCE that went west

Ok now i'm worried because I don't see what you're talking about :sticktongue: I did some edits after looking at it, did I fix whatever it was? lol

sarbian · December 21, 2014

Yes, it's ok now.

BLUAV8R · December 21, 2014

Yes, it's ok now.

Thank you very much for the help!

Keep it cool :cool:

BLUAV8R · December 21, 2014

Okay, so i've been testing out the config and seeing how it works. I've found a few syntax errors, fixed them, MM reports no errors on game load, however, I can't seem to make tanks that hold LF/OX into modular ones, they just stay normal

Here is my code so far:

[COLOR="#FF0000"]@PART[*]:NEEDS[RealFuels]:HAS[@RESOURCE[LiquidFuel]:HAS[@RESOURCE[Oxidizer]]]:Final[/COLOR] // Turns tanks with LiquidFuel and Oxidizer as resources into ModuleFuelTanks
{
	MODULE
	{
		name = ModuleFuelTanks // sets module
		volume = #$/RESOURCE[LiquidFuel]/amount$ // searches for amount of LiquidFuel
		@volume += #$/RESOURCE[Oxidizer]/amount$ // adds amount of Oxidizer to that number above
		@volume *= 5 // multiplies entire volume by 5, this is standard conversion procedures for RealFuels
		type = default // makes default tank because it's easiest and simple
	}

	!RESOURCE[LiquidFuel] // removes old LiquidFuel resources

	!RESOURCE[Oxidizer] // removes old Oxidizer resources
}

@PART[*]:NEEDS[RealFuels]:HAS[@RESOURCE[MonoPropellant]]:Final // Does exact same process above except for RCS tanks
{
	MODULE
	{
		name = ModuleFuelTanks
		volume = #$/RESOURCE[MonoPropellant]/amount$
		@volume *= 5
		type = ServiceModule // this is best type to use for RCS tanks, holds more specialized stuff like Hydrazine
	}

	!RESOURCE[MonoPropellant] // removes old MonoPropellant resources
}

@PART[*]:NEEDS[RealFuels]:HAS[@MODULE[ModuleRCS*]:HAS[@resourceName[MonoPropellant]]]:Final // turns all RCS thrusters not explicitly changed to use Hydrazine instead of MonoPropellant
{
	@MODULE[ModuleRCS*]
	{
		@resourceName = Hydrazine
	}
}

If anything I suspect it's an error in the search for a part line;

[COLOR="#FF0000"]@PART[*]:NEEDS[RealFuels]:HAS[@RESOURCE[LiquidFuel]:HAS[@RESOURCE[Oxidizer]]]:Final      <<--------- This stuff[/COLOR]

I want it to search for and edit parts like these (for example):

PART
{

name = TLV_LFO_A
module = Part
author = Tantares

mesh = model.mu
scale = 1

node_stack_bottom = 0.0, -2.475, 0.0, 0.0, 1.0, 0.0, 2
node_stack_top    = 0.0,  2.475, 0.0, 0.0, 1.0, 0.0, 2
node_attach = 0.5, 0.0, 0.0, 1.0, 0.0, 0.0, 1

TechRequired = advRocketry
entryCost = 2200
cost = 2200

category     = Propulsion
subcategory  = 0
title        = Tavio SA(1)
manufacturer = Tavio Engineering
description  = The SA(1) offers double the fuel capacity of some leading competitors. It's double the weight too, but we can't change that.
attachRules = 1,1,1,1,0

mass = 1

dragModelType  = default
maximum_drag   = 0.20
minimum_drag   = 0.15
angularDrag    = 2
crashTolerance = 10
maxTemp        = 3400

RESOURCE
{
 name = LiquidFuel
 amount = 720
 maxAmount = 720
}

RESOURCE
{
 name = Oxidizer
 amount = 880
 maxAmount = 880
}

}

Any help?

Edited December 21, 2014 by Sippyfrog

sarbian · December 21, 2014

Oh yes, I did not look at that line properly

@PART[*]:HAS[@RESOURCE[LiquidFuel],@RESOURCE[Oxidizer]]:NEEDS[RealFuels]:Final

Yours was looking for RESOURCE[Oxidizer] inside the RESOURCE[LiquidFuel].

BLUAV8R · December 21, 2014

Oh yes, I did not look at that line properly
@PART[*]:HAS[@RESOURCE[LiquidFuel],@RESOURCE[Oxidizer]]:NEEDS[RealFuels]:Final
Yours was looking for RESOURCE[Oxidizer] inside the RESOURCE[LiquidFuel].

Ohhhhhhhhh okay that makes a lot of sense now, and I see what I did wrong lol thanks!!!!!!

NathanKell · December 21, 2014

Here's the fallback config from dreadicon, before I removed it for now.

https://github.com/NathanKell/ModularFuelSystem/blob/856d39c746a396bdc63f33de1b75ac187d1319de/RealFuels/Fallback.cfg

Pondafarr · December 22, 2014

I've done several searches for KAS, and KASModuleGrab, but I can't seem to find a current answer. Is there a way to check for all parts under a certain mass, so I can apply KASModuleGrab to it? I've seen some examples of code that might work, but have not found if a [mass < 1] call would work. Ultimately, looking for an easy MM fix/replacement for A_Mechanic_is_Jeb, which has not been updated for .90.


@PART[*]:HAS[#mass < 1]
{
	MODULE
	{
		name = KASModuleGrab
		evaPartPos = (0.0, 0.0, -0.09)
		evaPartDir = (0, 0, -1)
		storable = true
		storedSize = 5
		attachOnPart = True
		attachOnEva = False
		attachOnStatic = True
		attachSendMsgOnly = False
	}
}

BudgetHedgehog · December 22, 2014

While i don't use A Mechanic Is Jeb, if it's just ModuleManager configs, they should still work without needing to update.

Streetwind · December 23, 2014

I'm looking to change a 0.625m engine into a 0.5m engine using ModuleManager.

Is it enough to just do "@rescaleFactor = 0.8" and call it a day? Or is there perhaps a different, more recommended method? How does changing the model size affect the node placement on the top and bottom of said engine, or the engine exhaust effect (and do I perhaps have to change them too)?

Pondafarr · December 23, 2014

Unfortunately, A Mechanic is Jeb was created with a PHP (?) script to manually build a MM file adding KAS functionality to many (not all) parts in the creator's install. I'm hoping to create a simple MM that will scour any install, and add KAS functionality to all the parts under a certain mass, without having to manually enter each and every part individually, as AMIJ did.

If MM has basic math capabilities, such as determining if a random part has a mass under X, then this might work? Just don't know if it does, or the correct code to do it.

.

While i don't use A Mechanic Is Jeb, if it's just ModuleManager configs, they should still work without needing to update.

[1.8.x-1.12.x] Module Manager 4.2.3 (July 03th 2023) - Fireworks season

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Join the conversation