theersink
-
Posts
132 -
Joined
-
Last visited
Content Type
Profiles
Forums
Developer Articles
KSP2 Release Notes
Bug Reports
Posts posted by theersink
-
-
On 4/9/2021 at 1:06 AM, theersink said:
Anybody done an Aies Aerospace cfg since it has been reborn from years ago it seems? Good parts pack but need some reconfig on the tech tree for UKS and I unfortunately do not have the expertise.
@theonegalen Any chance of getting support for this in your next update? Aies was a very good part pack back in the day. Should fit nicely.
Good to hear your still working on this. Been away for awhile. Take your time and deal with RL first. We can wait.
-
Anybody done an Aies Aerospace cfg since it has been reborn from years ago it seems? Good parts pack but need some reconfig on the tech tree for UKS and I unfortunately do not have the expertise.
-
On 5/14/2020 at 12:03 PM, wyvernfink said:
I'm a long-time lurker but have never posted. I'm willing to help out as much as I can.
I have some working in-progress MM scripts for updates to Restock Plus (plus some others, notably @Nertea's Near Future updates), but they're not complete. I also have some interesting ideas of how to accommodate the recent updates to Near Future Launch Vehicles, etc.
I am even willing to take on attempting to adopt this mod, but I don't want to step on any toes (I'm not clear on the etiquette of how this works). I know @SpinkAkron hasn't been here in a few months and they originally set up a license to permit forking, so it looks like the prerequisites are there. If everyone is ok with it, do I simply start a new thread for a potential fork, create a github account, and go to town?
The licence is creative commons so anyone can pick it up. OP probably has real world stuff going on and may not be back for awhile.
-
Eh, thanks for looking. I think I am done with KSP for awhile. I get my install right where it works and then an update comes and whacks everything. (Not yours mind you, KSP in general).
-
On 2/27/2019 at 10:45 PM, AccidentalDisassembly said:
OK - I continue to believe something is messed up within TweakScale, perhaps (or not) related to only certain parts that use TWEAKSCALEBEHAVIORs - on that front, I just can't be sure. However, I can replicate this problem reliably. Here's what I do:
This is the picture I'll be referring to - this is what CERTAIN parts look like every time. Can't be scaled (except down by one step, but values in either slider do not change):
- KSP 1.6.1 with MH - GameData folder contains only MM 4.0.2, TweakScale 2.4.1.0, Squad, and SquadExpansion
- Start game, create new sandbox, go into editor, place any part, then place the 5m engine plate.
- Right click on engine plate to scale it - it appears as in above image.
- Just in case of MM screwiness (or something), delete all MM cache files, and also delete PartDatabse.cfg.
- Restart KSP, start new sandbox, do same thing in editor: problem remains.
- Restart KSP, start new sandbox without deleting anything, do same thing in editor, problem remains.
So something is going on here.
I believe I have an idea what is happening.Nope, I did not know what was happening, but looking at it again gives me a second theory - look at the second TWEAKSCALEEXPONENTS in this TWEAKSCALEBEHAVIOR - it has name = TweakScale... that can't be right, can it?The two TWEAKSCALEBEHAVIORs that have "name = TweakScale" in them (this one and the science one) are ones applied to parts that are borked for me...All of that was wrong too. I have no idea what's going on, but it's borked even in a purely stock/TweakScale install, so something is messed up for sure. I tried.
[Snippity]
On another note, for purposes of safety and reducing duplication, I would suggest that EVERY patch in TweakScale be edited to use "%type =" and similar rather than "type = " when doing patches - just in case someone else has already defined a type for a part (etc.).
Also - some patches have superfluous definitions, e.g. the engine plate's TS patch defines incrementSlide and scaleFactors, but does not need to because those are already defined by its scaletype (unless some custom increments are being used which I didn't catch).
I am getting this exact same issue on 1.8.1 install with "lots" of mods. I am almost sure it is one of them, forgive me I am not a modder, maybe going back and touching a patch after Tweakscale has already withdrawn support for it? Anyhow, here are the logs to see if you can make sense of it.
Thanks in advance.
https://drive.google.com/drive/folders/10_BRBt0WkSo6MeT7uFRM9YwqkGwMQhhr?usp=sharing
Side note for clarity - I am getting the same issue but not the exact same part. It is the EP-12 and EP -18, I think those may be new parts from Missing History.
EP-12 is added via Missing History, EP-18 is stock, it is happening on both. I took the liberty of screenshotting the ALT F12 Screen with the offending error too, not sure if that helps. It is in the shared folder now as well.
-
Getting continuous log spam from KER in the VAB and during flight. Using 1.8.1 and JNSQ. Any ideas what could be causing this? I can provide the full log if needed.
Spoiler[LOG 23:23:36.813] VesselSimulator -> SimManager.StartSimulation() // routine is null
[LOG 23:23:36.813] VesselSimulator -> at UnityEngine.MonoBehaviour.StartCoroutine (System.Collections.IEnumerator routine) [0x00007] in <5aeafee3fea24f37abd1315553f2cfa6>:0
at KerbalEngineer.VesselSimulator.SimManager.StartSimulation () [0x000f1] in <979676d180724d169128060aa6bde65d>:0
[LOG 23:23:36.982] VesselSimulator -> SimManager.StartSimulation() // routine is null
[LOG 23:23:36.982] VesselSimulator -> at UnityEngine.MonoBehaviour.StartCoroutine (System.Collections.IEnumerator routine) [0x00007] in <5aeafee3fea24f37abd1315553f2cfa6>:0
at KerbalEngineer.VesselSimulator.SimManager.StartSimulation () [0x000f1] in <979676d180724d169128060aa6bde65d>:0
[LOG 23:23:37.148] VesselSimulator -> SimManager.StartSimulation() // routine is null
[LOG 23:23:37.148] VesselSimulator -> at UnityEngine.MonoBehaviour.StartCoroutine (System.Collections.IEnumerator routine) [0x00007] in <5aeafee3fea24f37abd1315553f2cfa6>:0
at KerbalEngineer.VesselSimulator.SimManager.StartSimulation () [0x000f1] in <979676d180724d169128060aa6bde65d>:0
[LOG 23:23:37.314] VesselSimulator -> SimManager.StartSimulation() // routine is null
[LOG 23:23:37.314] VesselSimulator -> at UnityEngine.MonoBehaviour.StartCoroutine (System.Collections.IEnumerator routine) [0x00007] in <5aeafee3fea24f37abd1315553f2cfa6>:0
at KerbalEngineer.VesselSimulator.SimManager.StartSimulation () [0x000f1] in <979676d180724d169128060aa6bde65d>:0
[LOG 23:23:37.484] VesselSimulator -> SimManager.StartSimulation() // routine is null
[LOG 23:23:37.484] VesselSimulator -> at UnityEngine.MonoBehaviour.StartCoroutine (System.Collections.IEnumerator routine) [0x00007] in <5aeafee3fea24f37abd1315553f2cfa6>:0
at KerbalEngineer.VesselSimulator.SimManager.StartSimulation () [0x000f1] in <979676d180724d169128060aa6bde65d>:0
[LOG 23:23:37.651] VesselSimulator -> SimManager.StartSimulation() // routine is null
[LOG 23:23:37.651] VesselSimulator -> at UnityEngine.MonoBehaviour.StartCoroutine (System.Collections.IEnumerator routine) [0x00007] in <5aeafee3fea24f37abd1315553f2cfa6>:0
at KerbalEngineer.VesselSimulator.SimManager.StartSimulation () [0x000f1] in <979676d180724d169128060aa6bde65d>:0
[LOG 23:23:37.821] VesselSimulator -> SimManager.StartSimulation() // routine is null
[LOG 23:23:37.821] VesselSimulator -> at UnityEngine.MonoBehaviour.StartCoroutine (System.Collections.IEnumerator routine) [0x00007] in <5aeafee3fea24f37abd1315553f2cfa6>:0
at KerbalEngineer.VesselSimulator.SimManager.StartSimulation () [0x000f1] in <979676d180724d169128060aa6bde65d>:0
[LOG 23:23:37.986] VesselSimulator -> SimManager.StartSimulation() // routine is null
[LOG 23:23:37.986] VesselSimulator -> at UnityEngine.MonoBehaviour.StartCoroutine (System.Collections.IEnumerator routine) [0x00007] in <5aeafee3fea24f37abd1315553f2cfa6>:0
at KerbalEngineer.VesselSimulator.SimManager.StartSimulation () [0x000f1] in <979676d180724d169128060aa6bde65d>:0
[LOG 23:23:38.151] VesselSimulator -> SimManager.StartSimulation() // routine is null
[LOG 23:23:38.152] VesselSimulator -> at UnityEngine.MonoBehaviour.StartCoroutine (System.Collections.IEnumerator routine) [0x00007] in <5aeafee3fea24f37abd1315553f2cfa6>:0
at KerbalEngineer.VesselSimulator.SimManager.StartSimulation () [0x000f1] in <979676d180724d169128060aa6bde65d>:0 -
In addition, I see the AIES mod has been revived. Would love to see support for it as well. That was a staple back before it died. Lots of good engines and ant. parts.
-
Unfortunately due to the recent updates to many part mods, Ven's, restock ect. this mod probably needs a major update to fix some issues with placement of parts due to callbacks of some mods. Ven's and Restock are the major. I have tried to track down where the issues are but I am not a modder. Hopefully we can get an update that addresses this. IIt is my favorite tech tree mod but I just can't do without some of the other mods this does not play well with.
-
31 minutes ago, Lisias said:
I need the KSP.log to check it. It's on the same place where the .EXE is . Click the icon you use to launch KSP with the right click, select "locate the original" or something (long time since I used windows!). The KSP.log should be visible there together the .EXE
That simplify things.
Removing TweakScale "prevents" the crime by eliminating the victim from the crime scene. It works
if you don't mind not using TweakScale.
All Tweak patch is well behaving. It only adds the patch when no other one had patched it first. So we can conclude, with a very reasonable degree of confidence, that there're someone else borking on this one.
Well, let's check the victims:
[LOG 22:02:24.429] [TweakScale] ERROR: **FATAL** Part kv1Pod (KV-1 'Onion' Reentry Module) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). [LOG 22:02:24.430] [TweakScale] ERROR: **FATAL** Part kv2Pod (KV-2 ‘Pea’ Reentry Module) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). [LOG 22:02:24.430] [TweakScale] ERROR: **FATAL** Part kv3Pod (KV-3 'Pomegranate' Reentry Module) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). [LOG 22:02:24.434] [TweakScale] ERROR: **FATAL** Part HeatShield1p5 (Heat Shield (1.875m)) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ).3 issues affecting MH's Reentry modules, and one affecting the HeatShield1p5 . Sounds easy but… Dude, what a installment you have! There're 36 different patches being applied to the Onion Reentry Module!
Well, there're "only" 12 on the heat shield, let's try it first:
[LOG 21:50:42.991] Applying update BuoyancyControl/BuoyancyControl/@PART[*] to SquadExpansion/MakingHistory/Parts/Thermal/HeatShield1p5.cfg/PART[HeatShield1p5] [LOG 21:50:45.602] Applying update CollisionFXUpdated/ModuleManager_CollisionFX/@PART[*]:HAS[!MODULE[ModuleWheelBase],!MODULE[KSPWheelBase],!MODULE[KerbalEVA],!MODULE[CollisionFX],!MODULE[FSwheel],!MODULE[FSwheelAlignment],!MODULE[BDAdjustableLandingGear],!MODULE[TTModularWheel],!MODULE[Repulsor],!MODULE[ModuleTrack],!MODULE[TrackWheel],!MODULE[KFModuleWheel],!MODULE[KFWheel],!MODULE[KFTrackSurface]] to SquadExpansion/MakingHistory/Parts/Thermal/HeatShield1p5.cfg/PART[HeatShield1p5] [LOG 21:50:52.607] Applying update CriticalTemperatureGauge/Plugins/CriticalTemperatureGauge/@PART[*] to SquadExpansion/MakingHistory/Parts/Thermal/HeatShield1p5.cfg/PART[HeatShield1p5] [LOG 21:52:32.347] Applying update TweakScale/patches/SquadExpansion/MakingHistory/Thermal/@PART[HeatShield1p5] to SquadExpansion/MakingHistory/Parts/Thermal/HeatShield1p5.cfg/PART[HeatShield1p5] [LOG 21:52:33.776] Applying update TweakscaleMakingHistoryConfigs/Thermal/@PART[HeatShield1p5] to SquadExpansion/MakingHistory/Parts/Thermal/HeatShield1p5.cfg/PART[HeatShield1p5] [LOG 21:52:49.998] Applying update DeadlyReentry/DeadlyReentry/@PART[*]:HAS[@MODULE[ModuleAblator]]:AFTER[DeadlyReentry] to SquadExpansion/MakingHistory/Parts/Thermal/HeatShield1p5.cfg/PART[HeatShield1p5] [LOG 21:52:50.621] Applying update DecouplerShroud/DecouplerShroud/@PART[*]:FOR[DecouplerShroud]:HAS[@MODULE[ModuleDecouple],!MODULE[ModuleDecouplerShroud]] to SquadExpansion/MakingHistory/Parts/Thermal/HeatShield1p5.cfg/PART[HeatShield1p5] [LOG 21:52:52.752] Applying update EngineLightRelit/MM_Configs/decoupler-configs/@PART[*]:HAS[@MODULE[Module*Decouple*]]:FOR[EngineLight] to SquadExpansion/MakingHistory/Parts/Thermal/HeatShield1p5.cfg/PART[HeatShield1p5] [LOG 21:53:51.632] Applying update UnKerballedStart/Mod Support/MakingHistory/@PART[HeatShield1p5]:NEEDS[CommunityTechTree,SquadExpansion]:FOR[zzzUnKerballedStart] to SquadExpansion/MakingHistory/Parts/Thermal/HeatShield1p5.cfg/PART[HeatShield1p5] [LOG 21:53:58.628] Applying update DeadlyReentry/DeadlyReentry/@PART[*]:HAS[!MODULE[ModuleAeroReentry],#leaveTemp[*]]:FINAL to SquadExpansion/MakingHistory/Parts/Thermal/HeatShield1p5.cfg/PART[HeatShield1p5] [LOG 21:53:59.951] Applying update InterstellarFuelSwitch/PatchManager/ActiveMMPatches/IntegratedDecoupler/@PART[*]:FINAL to SquadExpansion/MakingHistory/Parts/Thermal/HeatShield1p5.cfg/PART[HeatShield1p5] [LOG 21:54:02.506] Applying update Kopernicus/Config/SolarPanels/@PART:FINAL to SquadExpansion/MakingHistory/Parts/Thermal/HeatShield1p5.cfg/PART[HeatShield1p5]And from that, we have a "Winner"!
TweakscaleMakingHistoryConfigs is an illustrious unknown already: I don't have a clue about what/who/where this thing are/came, but every time it's mentioned on the KSP.log, it is the perpetrator. Bluntly delete GameData/TweakscaleMakingHistoryConfigs and everything will be fine.
Scale Safe!
Ahh I thought that might have been the one. Thanks for the quick reply. That took care of it.
-
17 minutes ago, Lisias said:
Unfortunately, this file is useless for me. I need the KSP.log in order to help you!
My apologies here is the KSP log. Not sure which is causing the issue Tweakscale or All Tweak, If I remove one or the other the fatal error goes away.
https://drive.google.com/open?id=1zaevd-mSWH64XQj_sbybX6o4i0BAH3NL
-
I have 4 fatal errors going on. Logs are here:
https://drive.google.com/open?id=1QUHKz5Fz1X1PjbEndmk6XtpZoSWjW2qt
Any help would be appreciated.
-
16 hours ago, ExtremeApple97 said:
Use Twitch to download mods and it automatically places the files in the right place.
15 hours ago, VoidSquid said:I assume you're meaning CKAN?
Always a good idea to read the release posts anyway as some do not play well with CKAN and the authors recommend manual installs. They will usually say so on the release post. DoctorDavinci has the best advice, read through the first post for install instructions. Even when using CKAN you can always use the link to go to the mod page quickly.
-
4 hours ago, showell373 said:
Good morning Kerbalnauts!
I have the latest version of CKAN loaded and it is showing the Unmanned Before Manned is compatible with 1.7.3.
However, when I load it, the tech tree is not rearranged, and none of my parachutes show up on the default page when first starting career mode.
Have tried an uninstall clean sweep and reload and still doesn't work.
Any help or suggestions would be greatly appreciated.
Unfortunately the mod is basically dead. Yemo is no longer around and unlocked all his mods for future versions, you'd have to modify the patches yourself to get it to work. His license does not allow for someone to pick it up either so it is best to move on to one of the alternatives. Head over to the release thread and read through the last few pages and you will see that a few have released their own versions in the spirit of the original.
-
8 hours ago, SirMimbo said:
For some reason since I've moved to 1.7.3, I never get the KK option on the toolbar and Ctrl+K wont work. If I downgrade to 1.6.1 it works fine. Is there any new dependencies? Or am I doing something wrong? Any help would be greatly appreciated. Thanks!
See post by Ger_Space 4 posts above yours. There is a new version with new dependency CustomPrelaunchChecks. Don't use CKAN. Go manual. CKAN did not install correctly for me.
-
On 8/20/2019 at 12:16 PM, MacLuky said:
Love the mod. Question though: why do I need to build airplanes so that I can unlock aeroshells? can't we separate those? I'm not a fan of planes and it clutters the vab lists
You can use this mod to trim down parts you don't use. You can block part in VAB, SPH or both. Has ongoing list so if you need to unblock them later it is easy to do. Works excellent for trimming the fat in the VAB and SPH.
-
2 hours ago, SuicidalInsanity said:
Some people in the Mk2Expansion thread are reporting a
CKAN.InvalidModuleFileKraken: Mk2Expansion 2:1.8.6: D\Temp\tmpE01C.tmp has length 27702121, should be 27702381 at CKAN.NetModuleCache.Store(CkanModule module, String path, String description, Boolean move) at CKAN.NetAsyncModulesDownloader.ModuleDownload Complete(Uri url, String filename, Exception error)error following M2X updating to 1.8.6.
I am getting the same.
-
31 minutes ago, DerGolgo said:
I have no clue how to compile (though I will now try and educate myself).
I interpret your statement to mean that you have actually done this. If so, would you share your compiled work? Put it on Google-Drive or Dropbox or something, for those who would like to have this mod in a more up-to-date version of the game? There appear to be two of us, @JeffreyCor and myself, minimum, and I would be delighted to test it in 1.4.3.
If you don't wish to put it on your own Google-Drive or something, I would gladly PM you my email address and put it (with all attribution to yourself) on my own.It is a GPL3 license so I do not think it would be a violation. My concern is that if it is posted then some will expect support and start bugging the mod author. My testing has been limited so I am not sure if there are any major bugs that would require code work which I cannot do, I am not a coder. It appears as someone has asked DIazo to take over the upkeep judging from the public post on his profile. Let's give hime some time to respond. If he does not I can post the DLL here with the understanding it is as is, use at your own risk, with no support implied.
-
18 hours ago, DerGolgo said:
I loved this mod.
Small, simple enough, no fuss.
It doesn't work anymore. The button isn't there to be selected for display in Blitzy's toolbar, where it once was.
I, for one, would be rather delighted were this to come back for 1.4.3.
Or has an alternative to this materialized where I did not see it? Does anyone have any suggestions?If you know how to recompile the DLL it works in 1.4.2. Haven't tested on 1.4.3 yet.
-
8 hours ago, Jammer-TD said:
I had been using 1.4.3 with no issues when I add the 3 version this is what happens
previous version =2.13.3
the errors go away with the earlier version I have MM3.0.6, CRP 10,tweakscale 2.3.12 but I don't use patch manager.
any ideas?
thanks love this mod.(so i tried it with patch manager.. it too had errors.see log.)hope this helps
logs at: http://www.teamdemonic.com/photo/KSP/518/diag/Jammer-TD5_18-log.zip
Jammer
@FreeThinker I get the same 30 MM Errors.
Log and screenshot here: https://1drv.ms/f/s!Al6GOD6z9Sxci8IqsKqkfwFAzzxIJQ
MM cache cleared prior to load.
-
No it does not. Spams NREs. Although that is with a lot of other mods installed, I can't attest to just by itself.
-
45 minutes ago, Jacke said:
You've got some issue in your install. Despite having a copy of ToadicusTools.dll version 0.22.1.0, there's a log entry saying it's not being found by KSP. Is the directory of ToadicusTools laid out as I mentioned above? If it's not, that's an indication something is incorrect in the install.
Search under
GameDatathe KSP install directory for ToadicusTools.dll and be sure you only have one and it's version 0.22.1.0. As far as I know, it doesn't have code like ModuleManager.dll that disables earlier versions when a later version is present, so a copy of 0.22.0.0 could cause problems.If that's not the case, then I advise deleting the subdirectories "ToadicusTools/" and "TweakableEverything/" under "GameData/", download the Tweakable Everything install archive, and reinstall from it. This is to fix potentially damaged files, especially ToadicusTools.dll.
Already did that before posting. Everything is installed as directed. If the DLL itself was missing VOID would be throwing an error as well. Interesting though, I changed nothing else but I replaced the toadacious tools DLL with the last one released with the BETA VOID before linuxgurugamer took them over and it fixed both issues. I no longer have the log error and the gimbal is back to normal.
UPDATE: Uninstalled all 3, Toadacious Tools, VOID, and Tweakable everything. Re-installed via CKAN. Boom, same issue. Uninstalled again via CKAN, made sure no folders were left over. Re-installed via D/L manual unzip method and walla, issue resolved. Evidently CKAN is whacking the install of one of those 3. I am beginning to agree with others about the reliability of CKAN, the install time it saves may not be worth the issues it causes.
Thanks for the assistance Jacke.
-
3 minutes ago, Jacke said:
Be sure you have the version of Toadicus Tools that came with Tweakable Everything; it's the one that's version 0.22.1.0. It's also will have a ToadicusTools.version file and the plugin will be in a Plugins subdirectory.
I was setting up VOID at the same time, identified the later version of TT with Tweakable Everything, and though I'd grabbed it and put it into use. But when I recently enabled Tweakable Everything, the lag was massive and the App Launcher didn't show up in the VAB. Look at my logs and I saw errors similar to yours. Turned out I'd put in Toadicus Tools 0.22.0.0 that came with VOID.
Look at "GameData/ToadicusTools/" and make sure you have these files.
ToadicusTools.version
Plugins/ToadicusTools.dll
Right-click on ToadicusTools.dll and click Properties, then on the Properties window click the Details tab. Version should be 0.22.1.0.
It is the correct version for sure. I am getting the error and the gimbal issue reported above as well.
-
On 9/6/2017 at 0:58 PM, linuxgurugamer said:
Something is wrong, the log is filled with NullReference exceptions.
Did you do this with a new game, or an existing one?also, assuming this is an existing game, did you ever have Tweakscale installed?You are missing another mod:
Module ModuleTweakableReactionWheel threw during OnStart: System.IO.FileNotFoundException: Could not load file or assembly 'ToadicusTools, Version=0.22.1.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies.
File name: 'ToadicusTools, Version=0.22.1.0, Culture=neutral, PublicKeyToken=null'
at Part.ModulesOnStart () [0x00000] in <filename unknown>:0Find and install Toadicus Tools, that should solve your problem
I am getting the exact same issue on my install. Verified ToadicusTools is there. VOID loads fine, IIRC VOID uses this as well. After VOID has loaded it then starts putting out these errors for Tweakable Everything. I think this is a coincidence though. There is a conflict with a mod somewhere. I will try to narrow it down. Log is a bit of a mess as tweakscale is throwing a lot of errors I think with either Vens or SXT. https://1drv.ms/f/s!Al6GOD6z9Sxci8IqsKqkfwFAzzxIJQ < This one is with current Mods installed.
-
Couple of questions:
I know it has been a while but was anything ever figured out with TAC LS so that we can have integrated 3 day life support back on crewed parts. I think you had to disable that due to a math issue IIRC.
Would it be hard for you to integrate this mod into your Alkaline Fuel cells? This is sweet little mod that will automatically turn on and off fuel cells based on a configurable threshold.
Looks as if FuelCellTweaks already made the adjustment
if you don't mind not using TweakScale.
[1.12.3+] UnKerballed Start v1.3.1 (Happy New Year! Jan 01, 2022)
in KSP1 Mod Releases
Posted
It doesn't appear that the Blue Dog design patches are working. I think the names have been changed on some parts since the configs were written. I am getting the default Blue Dog part placements on the tree.
Taking a peek at the configs it does look like names were changed on Blue Dogs side at some point:
Snip from BDB Mercury - part name = bluedog_Mercury_Capsule
Snip from UKS config - @PART[bluedog_mercuryPod]
There are numerous others with similar nomenclature changes.