TranceaddicT

Here's the original Documentation for the extension ... https://github.com/Crzyrndm/FilterExtension/wiki Note: It IS OLD, so you WILL have to figure out what applies still.

My read of the patch is to create the new MODULE[ModuleGrappleNode]. You're right the '|' pipe only works in the :NEEDS[ ] dependency checking. In @PART [ ] there is no optioning, it's always 'and'; so, it would properly be @PART[myNewPart, yourNewPart, theirNewPart] -or- @PART[*NewPart] RAG, this is all you should need. You didn't need to duplicate the info changes twice. @PART[petra_docking_port_s0p5_1_*] { @category = Structural @title = #LOC_tantares_petra_docking_plate_s0p5_1 @description = #LOC_tantares_petra_docking_plate_s0p5_1_description @tags = #LOC_tantares_petra_docking_plate_s0p5_1_tags !MODULE[ModuleDockingNode] { @PART[petra_docking_port_s0p5_1_male] { %MODULE { %name = ModuleGrappleNode %nodeTransformName = dockingNode %deployAnimationController = 0 %nodeType = petra_basic_s0p5_1 %captureRange = 0.05 %captureMinFwdDot = 0.5 %captureMaxRvel = 0.5 %pivotRange = 0 } } The first is applied to BOTH female & male parts. The second will only be applied to the male part.

It should. You just need the correct version of kOS for 1.8 to run it.

Concur. You're calling the folder name not the part name. @PART[petra_basic_docking_port_s0p5_1_female|petra_basic_docking_port_s0p5_1_male] You want this: @PART[petra_docking_port_s0p5_1_female|petra_docking_port_s0p5_1_male] I believe, best practice is to: use @ to mark a node for change (https://github.com/sarbian/ModuleManager/wiki/Module-Manager-Syntax#edit----). use % when changing or adding values (https://github.com/sarbian/ModuleManager/wiki/Module-Manager-Syntax#edit-or-create---). @PART[petra_docking_port_s0p5_1_female|petra_docking_port_s0p5_1_male] { %category = Structural %title = #LOC_tantares_petra_docking_plate_s0p5_1 %description = #LOC_tantares_petra_docking_plate_s0p5_1_description %tags = #LOC_tantares_petra_docking_plate_s0p5_1_tags !MODULE[ModuleDockingNode] { } } @PART[petra_docking_port_s0p5_1_male] { %category = Coupling %title = #LOC_tantares_petra_docking_grapple_s0p5_1 %description = #LOC_tantares_petra_docking_grapple_s0p5_1_description %tags = #LOC_tantares_petra_docking_grapple_s0p5_1_tags @MODULE { %name = ModuleGrappleNode %nodeTransformName = dockingNode %deployAnimationController = 0 %nodeType = petra_basic_s0p5_1 %captureRange = 0.05 %captureMinFwdDot = 0.5 %captureMaxRvel = 0.5 %pivotRange = 0 } }

Try a less malicious site.

How about a KSP.log and a MMConfig so we can see what's happening. But, my first guess, you want to use % not @

My first rule for anything new I get my hands on ... play with the knobs, levers, and sliders. The one constant in my life is "Should Can I do that?"

You still have that craft.file on my Google Drive.

Always provide a log and and additional files that can help. Oh, and don't ever use the "If you want." You don't want to ever hear that NO, on the tip of everyone's tongue.

Nicely done.

Yeah, I just wanted to get that out to him because it had been a while since he posted. I was hoping to complete the log analysis this morn before he launched. Looks like you beat me to the punch.

Craft file fixed. https://drive.google.com/drive/folders/1X87TN3kak12VcnQNcgrKUVRmBcKg407x?usp=sharing

Can you direct me to those tutorials? I'm having a hell of a time translation the old ones into the latest Unity. I may end up picking your brain a bit too.

@PART[bluedog_LEM_Descent_Tanks]:NEEDS[KIS]:FINAL // Sina-MEM-DST Descent Stage Assembly { %MODULE[ModuleKISInventory] { maxVolume = ### } } There's a patch that won't get overwritten when the mod updates. Just replace ### with the desired volume, name it whateverYouLike.cfg, and drop it in a personal folder.

If you go to the GitHub repository you can download the new skidtex.dds As for the other two, they are baked-in the .my files. They are there to stay. (Helpful hint, never use "ASAP" when seeking assistance with a voluntary project.)

That means you have a double-patched part with a TS module that was deactivated. Drop your craft.file and KSP.log, we can figure it out. Until then, no harm by it.

And yet, if they had done so ...

Hey, gang, I was trying to help another Kerbonaut with this very problem. Then, I came across this jewel... https://forum.unity.com/threads/jobs-lags-jobtempalloc-has-allocations-that-are-more-than-4-frames-old.513124/

I've never gotten a refund in 30+ years. I prefer to owe a few hundred.

Logs?

Has anyone noticed anything odd with the "Adapter 25-12x3 (Tri-Adapter)"? [adapterLargeSmallTri.cfg] From what I can tell , Magpie patches it twice in the StockStackCouplers.cfg.

@FreeThinker Oops. Looks like your fix kicked the can down the code. [WRN 13:49:45.550] [PersistentThrust]: Loaded without saved config node [ERR 13:49:45.550] [PersistentThrust]: OnLoad part.partInfo == null KSP.log

PaytoPlay v1.5 is being indexed by KSP-AVC and listed AVAILABLE for download.

This allows you to use your engines during timewarp. BTW handles the timewarping.

[ERR 03:31:32.367] [PersistentThrust]: OnLoad node == null 392 instances in my KSP.log