Jump to content

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


sarbian

Recommended Posts

I'm working on simplifications to MKS, but I have some errors in my MM which I'm hoping someone can help me figure out.

I did this MM CFG

  Reveal hidden contents

But I keep getting this exception error when loading KSP, which I've been unable to track down so far.

  Reveal hidden contents

I'm sure the error is in my CFG and not MM itself, I just can't figure out what. The log looks like some might be up with my brackets, but I've run over them again and again and they seem balanced enough.... What am I missing?

EDIT:

I think it might be this node, but what is the problem with that?

  Reveal hidden contents

 

Edited by Warezcrawler
Link to comment
Share on other sites

  On 4/2/2017 at 5:38 PM, Warezcrawler said:

EDIT:

I think it might be this node, but what is the problem with that?

  Reveal hidden contents

 

Expand  

Have you tried to change "#" with "@"?

Link to comment
Share on other sites

  On 4/3/2017 at 9:26 PM, sebi.zzr said:

   @MODULE[ModuleResourceConverter_USI],*
    {
        !INPUT_RESOURCE:HAS[#ResourceName[Machinery]]{}
        !OUTPUT_RESOURCE:HAS[#ResourceName[Recyclables]]{}
        !REQUIRED_RESOURCE:HAS[#ResourceName[Machinery]]{}
    }

Expand  

have you tried using 

@MODULE:HAS[#name[ModuleResourceConverter_USI]]

instead of what you have?

Link to comment
Share on other sites

  On 4/3/2017 at 10:29 PM, Sigma88 said:

have you tried using 

@MODULE:HAS[#name[ModuleResourceConverter_USI]]

instead of what you have?

Expand  

I tried this just now. Same basic error.

  Reveal hidden contents

 

  On 4/3/2017 at 9:26 PM, sebi.zzr said:

Have you tried to change "#" with "@"?

Expand  

I tried this as well, and I still get the exception. Though I must say, that even without the exception in this try, I would not expect the value to have changed, since the syntax here is for nodes and not values, as @blowfish pointed out.

  Reveal hidden contents

If I change it to the below one, then I don't get the exception, but as expected it only changes the first nodes values and not them all as I need it to.

  Reveal hidden contents

That it does not hit all module can be seen from the "ModuleManager.ConfigCache".

  Reveal hidden contents

So what am I missing in the syntax?

EDIT:

I just tried two more ways

This one did not throw an exception, but did not finish the job (expected)

  Reveal hidden contents

This one threw the exception

  Reveal hidden contents

I counted the module nodes, and it does hold 4 nodes. So why is this one failing?

 

EDIT EDIT:

ARHHHHGGGG...... After 1700 tries I found it. Apparently there is a syntax error in the "MKS_Processor125.CFG" in MKS mod in one of the nodes. This means MM fails to do it's thing! It should have a "TemperatureModifier" nodes name, but it is missing. I will report this to @RoverDude

  Reveal hidden contents

 

Edited by Warezcrawler
Link to comment
Share on other sites

Is there a way to reference a value from a key within a node of another mod's node?

i.e. I want to reference Sigma Dimension's 'landscape' value and use it within an EVE node.

SigmaDimensions
{
	landscape = *value* //Terrain deformity multiplying factor
}

Call the above value and reference it in the following:

@EVE_CLOUDS:FINAL
{
	@OBJECT:HAS[#body[Sarnus,Urlum,Neidon,Tekto,Thatmo]]
	{
		@altitude *= value //REFERENCE TO 'landscape' VALUE FROM SIGMA DIMENSIONS
	}
}

Could you achieve it by using the following?

@SigmaDimensions
{
	landscape = *
}

@EVE_CLOUDS:FINAL
{
	landscapeMultiplier = #$@SigmaDimensions/landscape$
	@OBJECT:HAS[#body[Sarnus,Urlum,Neidon,Tekto,Thatmo]]
	{
		@altitude *= #$landscapeMultiplier$
	}
}
Edited by Poodmund
Link to comment
Share on other sites

  On 4/4/2017 at 7:15 PM, Poodmund said:

Is there a way to reference a value from a key within a node of another mod's node?

i.e. I want to reference Sigma Dimension's 'landscape' value and use it within an EVE node.

SigmaDimensions
{
	landscape = *value* //Terrain deformity multiplying factor
}

Call the above value and reference it in the following:

@EVE_CLOUDS:FINAL
{
	@OBJECT:HAS[#body[Sarnus,Urlum,Neidon,Tekto,Thatmo]]
	{
		@altitude *= value //REFERENCE TO 'landscape' VALUE FROM SIGMA DIMENSIONS
	}
}

Could you achieve it by using the following?

@SigmaDimensions
{
	landscape = *
}

@EVE_CLOUDS:FINAL
{
	landscapeMultiplier = #$@SigmaDimensions/landscape$
	@OBJECT:HAS[#body[Sarnus,Urlum,Neidon,Tekto,Thatmo]]
	{
		@altitude *= #$landscapeMultiplier$
	}
}
Expand  

almost,

the idea is correct, or you could bypass the "landscapeMultiplier" by doing directly 


        @altitude *= #$@SigmaDimensions/landscape$

 

biggest problem is that #body[Sarnus,Urlum] will fail

you want to use :HAS[#body[Sarnus]|#body[Urlum]|#body[Neidon]]

 

I don't even know if MM can handle OR there, so you might need to use multiple nodes 

Link to comment
Share on other sites

I need a little help here.  The following MM works, but I'd like to get it into a single stanza, but I can't get the "or" to work, so I have it separate.

@PART[*]:HAS[@MODULE[ModuleDecouple]]:NEEDS[StageRecovery]
{
	MODULE
	{
		name = RecoveryIDModule
	}
	MODULE
	{
		name = ControllingRecoveryModule
	}
}
@PART[*]:HAS[@MODULE[ModuleAnchoredDecoupler]]:NEEDS[StageRecovery]
{
	MODULE
	{
		name = RecoveryIDModule
	}
	MODULE
	{
		name = ControllingRecoveryModule
	}
}

 

Link to comment
Share on other sites

  On 4/4/2017 at 11:28 PM, linuxgurugamer said:

but I can't get the "or" to work

Expand  

would be extra helpful to see how you were going about trying to get the OR working :wink: This is how I would do it based off other configs I see using the operator

@PART[*]:HAS[@MODULE[ModuleAnchoredDecoupler|ModuleDecouple]]:NEEDS[StageRecovery]
{
	MODULE
	{
		name = RecoveryIDModule
	}
	MODULE
	{
		name = ControllingRecoveryModule
	}
}

Since I have to guess maybe you were trying

@PART[*]:HAS[@MODULE[ModuleAnchoredDecoupler]|@MODULE[ModuleDecouple]]:NEEDS[StageRecovery]

?

Link to comment
Share on other sites

  On 4/5/2017 at 12:32 AM, Drew Kerman said:

would be extra helpful to see how you were going about trying to get the OR working :wink: This is how I would do it based off other configs I see using the operator

@PART[*]:HAS[@MODULE[ModuleAnchoredDecoupler|ModuleDecouple]]:NEEDS[StageRecovery]
{
	MODULE
	{
		name = RecoveryIDModule
	}
	MODULE
	{
		name = ControllingRecoveryModule
	}
}

Since I have to guess maybe you were trying

@PART[*]:HAS[@MODULE[ModuleAnchoredDecoupler]|@MODULE[ModuleDecouple]]:NEEDS[StageRecovery]

?

Expand  

Your guess was correct (I found an old copy in a backup)

However, your suggestion did not work:

@PART[*]:HAS[@MODULE[ModuleAnchoredDecoupler|ModuleDecouple]]:NEEDS[StageRecovery]

No errors from MM that I can see, it shows the line in the log:

Config(@PART[*]:HAS[@MODULE[ModuleAnchoredDecoupler|ModuleDecouple]]:NEEDS[StageRecovery]) FMRS/FMRS_MM/@PART[*]:HAS[@MODULE[ModuleAnchoredDecoupler|ModuleDecouple]]:NEEDS[StageRecovery]

Just does nothing

Link to comment
Share on other sites

  On 4/5/2017 at 11:05 AM, linuxgurugamer said:

However, your suggestion did not work:

Expand  
  On 4/5/2017 at 5:05 PM, blowfish said:

unfortunately it doesn't look like there's an or operator inside a HAS block.  Just checked the code.

Expand  

D'oh! Yea, I built my example from seeing the OR used to detect multiple PART[] instances, which is why I didn't know it wouldn't work

 

Link to comment
Share on other sites

  On 4/5/2017 at 11:05 AM, linuxgurugamer said:

Your guess was correct (I found an old copy in a backup)

However, your suggestion did not work:

@PART[*]:HAS[@MODULE[ModuleAnchoredDecoupler|ModuleDecouple]]:NEEDS[StageRecovery]

No errors from MM that I can see, it shows the line in the log:

Config(@PART[*]:HAS[@MODULE[ModuleAnchoredDecoupler|ModuleDecouple]]:NEEDS[StageRecovery]) FMRS/FMRS_MM/@PART[*]:HAS[@MODULE[ModuleAnchoredDecoupler|ModuleDecouple]]:NEEDS[StageRecovery]

Just does nothing

Expand  

You could try

@PART[*]:HAS[@MODULE[Module*Decouple*]]:NEEDS[StageRecovery]

That should catch both ModuleAnchoredDecoupler and ModuleDecouple

Link to comment
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.

×
×
  • Create New...