Judicator81

Not sure, but I think there is some misunderstanding here. And it's actually my fault: mod description could be more clear. So, button "Copy part CFG node" copies actual in-game part representation, not text from original part CFG-file. That means, whole PART{} node with all MM-patches already applied. You can think of it as of copy of respective PART{} from ModuleManager.ConfigCache file. Apart from the fact, that actual ModuleManager.ConfigCache is not required. Thus, this feature is likely more useful for "inspecting" your own or third-party changes to specific part(s) (made with MM-patches), rather than creating new MM-patches. But it's up to you, how you would like to use it, of course.

PartInfoInPAW [0.2.2] Mod for Kerbal Space Program intended for mod creators and advanced players. Get useful information about part from PAW menu, copy part ID or full part CFG node to clipboard with one click. What does this mod do? 1. It displays part name (basically, part ID) and path to part CFG file in the parts list (in VAB/Hangar): This feature is more or less identical to PartInfo mod by linuxgurugamer. 2. PartInfoInPAW also adds some information to PAW menu (right-click menu) for alls parts (works only in VAB/SPH). This information include: part name (basically, part ID); part mod (GameData folder name); dry/wet mass; cost; entry cost; dry engine TWR ("dry" means TWR is only calculated for this specific part, not craft or stage). And of course, it is shown only for engines. For engines, mod also display formatted string of additional data about engine (the same you can see in parts list in VAB/SPH). If part has more than one ModuleEngines (for example, multi-mode engine like RAPIER), information for first two ModuleEngines will be displayed. 3. Finally, mod adds two buttons to PAW menu (see screenshot above), which allows you to copy part name (part ID) or whole part config (in-game part representation in human-readable text) to clipboard. This is my favorite feature, and I hope other players and modders will find it useful (as did I). NB: button "Copy part CFG node" copies actual in-game part representation, not text from original part CFG-file. That means, whole PART{} node with all MM-patches already applied to it. Dependencies Module manager (preferably last version). Version 4.2.2 is bundled as part of download. Licensing The MIT License (MIT) Copyright (c) 2022 Alexander Rogov Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. Bundled Module Manager is licensed under a "CC share-alike license". More information can be found here. Changelog Downloads Spacedock GitHub CKAN Source: https://github.com/judicator/PartInfoInPAW

Yes, logs would be of help.

Yep, it looks like some parts from VaporVents mod are not compatible with B9PartSwitch. Fixed in 0.4.1. Version 0.4.1 released. Changelog: Added some parts from VaporVent mod to greylist. Added blacklist for Bluedog_DB mod (about 600 parts are blacklisted from more than a thousand total in BDB). Mod is marked as 1.12.4 compatible. P.S. It looks like spacedock.info is temporally down now. Get new mod version from github or CKAN, if you are in a hurry.

Yes, your spacecraft will be fine in such situation. Version 0.4.0 released. Changelog: Changed MM patch order to get rid of problems, caused by interaction with other mods' patches, updating B9PS switchers (i.e. Kerbalism + SSPX). Black and grey lists are now moved to separate folder (IgnoreParts). List of blacklisted parts is expanded, parts from several mods added.

Version 0.3.3 released. Changelog: Added some unsupported parts to blacklist (thanks to @Hohmannson). Marked mod as KPS 1.12.3 compatible. Fixed in 0.3.3.

No, I'am aware what SystemHeat is, and actually have been asking about that specific information. ) Anyway, will be waiting for more details.

Wow, that's really interesting! How would it work?

What Module Manager version are you using? If 3.*, you could upgrade to some 4.* version, for example, last one (4.2.1).

NFE support have been removed from KerbalAtomics in version 1.3.0 of the mod: NearFutureElectrical NTRs Extra has been removed forever https://github.com/post-kerbin-mining-corporation/KerbalAtomics/releases/tag/1.3.0 You could: 1. use earlier version of the mod, 2. or just install SystemHeat and SystemHeatFissionEngines from SystemHeat/Extras.

Yes, it works with ReStock, as well as with absolute majority of other mods.

Could you be more specific? Actually, this mod is an MM config (bunch of configs, actually), but the color switching itself is implemented by B9PartSwitch.

That's strange. All parts, having SSTU modules, should be blacklisted and therefore should not have SimpleRepaint functionality. I'll check this.

Interesting idea! It's impossible without some coding: SimpleRepaint is nothing more than just few Module Manager configs, and relies on power of B9PartSwitch and stock PartVariants. I'll do some coding experiments, but no promises yet.

Unfortunately, it's not so easy (if possible at all) to implement within current approach. Shiny parts (or parts variants) use special "specular" textures. And SimpleRepaint just changes color property for any textures of part, but contains no additional textures on it's own. Yes, it's a known issue. Stock PartsVariants partmodule is not fully compatible with B9PartSwitch, and I can't really fix that.