Lisias

What part? Please name the part with problems and publish your KSP.log file. Chances are that it's an "unholy interaction" with a third-party Add'On that doesn't expects a stack as scale type.

A small resume for my whole week.

Well, it's 10 years since my last Deutschunterricht, but from what I got to understand, CKAN is complaining that some installed Add'Ons are not compatible to 1.6.1 - the version between parenthesis is the KSP version that Add'On is known to support. Better burn time, for example, was compiled to work on 1.7.1 This doesn't mean, necessarily, that the Add'On will not run on the 1.6.1, but the Maintainer will probably dismiss bug reports due it. Usually, you should install a older version, usually the last version with official support for the KSP you are running. You can also tell CKAN to ignore this, if you known the Add'On will run for sure - what usually means you need to run and check things for yourself and then check an option somewhere. You will need to ask for Details on the CKAN thread. It's certainly a old patch playing havoc with newest versions of some Add'Ons. As long you don't use a Part with a broken patch, you are safe - the hard part is to remember all that parts, so usually is safer to fix the patches. Not every bad patching ends in disaster, but some do - and since it's way easier to fix everything than to cherry pick each possible bug to classify them into "safe" and "unsafe", this is the approach I'm taking. In a way or another, use S.A.V.E. . It's a good preventive measure. That said, I run into some difficulties while trying to download your LOG. The Mega site shows message about Requesting Account Data, then Receiving Account Data, then Decrypting. But then my own files are displayed, without any trace of a shared KSP.log somewhere.I searched for it on the Activities Log, Incoming Shares, etc, but no dice. Perhaps you forgot to grant permissions to the file be read by third parties? A way to check for yourself is to search for "[TweakScale] ERROR:" on the log file, take note of the partnames being mentioned on the log line, and then search for every "Applying update" mentioned on the same log line as the partname you took notes. This will list every single patch that was applied to the part, and with that information you can eye ball the patch looking for problems. It's a bit cumbersome without some tools as GREP to help you, but good Text Editors as Notepad++ or TextWrangler work with regular expresions what's essentially what GREP does (on the shell prompt).

Got it: [LOG 09:26:14.222] [TweakScale] INFO: WriteDryCost Concluded : 1511 parts found ; 0 checks failed ; 0 parts with hotfixes ; 0 parts with issues overruled ; 51 Show Stoppers found; 9 Sanity Check failed; 560 unscalable parts. As usual, 9 Sanity Check failed meaning 9 parts that TweakScale needs to be updated to learn how to cope with them, and until there I had withdraw support to prevent some carnage. TweakScale 2.4.4.x series will solve that. About that 51 Show Stoppers: [LOG 09:26:13.710] [TweakScale] ERROR: **FATAL** Part Decoupler.1p5 (TD-18 Decoupler) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). [LOG 09:26:13.711] [TweakScale] ERROR: **FATAL** Part Decoupler.4 (TD-50 Decoupler) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). [LOG 09:26:13.711] [TweakScale] ERROR: **FATAL** Part Separator.1p5 (TS-18 Stack Separator) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). [LOG 09:26:13.712] [TweakScale] ERROR: **FATAL** Part Separator.4 (TS-50 Stack Separator) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). [LOG 09:26:13.712] [TweakScale] ERROR: **FATAL** Part Size1p5.Strut.Decoupler (Size 1.5 Decoupler) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). [LOG 09:26:13.713] [TweakScale] ERROR: **FATAL** Part LiquidEngineKE-1 (Kerbodyne KE-1 "Mastodon" Liquid Fuel Engine) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). [LOG 09:26:13.714] [TweakScale] ERROR: **FATAL** Part LiquidEngineLV-T91 (LV-T91 "Cheetah" Liquid Fuel Engine) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). [LOG 09:26:13.715] [TweakScale] ERROR: **FATAL** Part LiquidEngineLV-TX87 (LV-TX87 "Bobcat" Liquid Fuel Engine) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). [LOG 09:26:13.717] [TweakScale] ERROR: **FATAL** Part LiquidEngineRE-I2 (RE-I2 "Skiff" Liquid Fuel Engine) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). [LOG 09:26:13.717] [TweakScale] ERROR: **FATAL** Part LiquidEngineRE-J10 (RE-J10 "Wolfhound" Liquid Fuel Engine) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). [LOG 09:26:13.719] [TweakScale] ERROR: **FATAL** Part LiquidEngineRK-7 (RK-7 "Kodiak" Liquid Fueled Engine) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). [LOG 09:26:13.720] [TweakScale] ERROR: **FATAL** Part LiquidEngineRV-1 (RV-1 "Cub" Vernier Engine) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). [LOG 09:26:13.720] [TweakScale] ERROR: **FATAL** Part monopropMiniSphere (Stratus-V Minified Monopropellant Tank) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). [LOG 09:26:13.720] [TweakScale] ERROR: **FATAL** Part Size1p5.Monoprop (FL-R5 RCS Fuel Tank) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). [LOG 09:26:13.720] [TweakScale] ERROR: **FATAL** Part Size1p5.Size0.Adapter.01 (FL-A150 Fuel Tank Adapter) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). [LOG 09:26:13.721] [TweakScale] ERROR: **FATAL** Part Size1p5.Size1.Adapter.01 (FL-A151L Fuel Tank Adapter) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). [LOG 09:26:13.721] [TweakScale] ERROR: **FATAL** Part Size1p5.Size1.Adapter.02 (FL-A151S Fuel Tank Adapter) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). [LOG 09:26:13.721] [TweakScale] ERROR: **FATAL** Part Size1p5.Size2.Adapter.01 (FL-A215 Fuel Tank Adapter) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). [LOG 09:26:13.722] [TweakScale] ERROR: **FATAL** Part Size1p5.Tank.01 (FL-TX220 Fuel Tank) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). [LOG 09:26:13.722] [TweakScale] ERROR: **FATAL** Part Size1p5.Tank.02 (FL-TX440 Fuel Tank) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). [LOG 09:26:13.722] [TweakScale] ERROR: **FATAL** Part Size1p5.Tank.03 (FL-TX900 Fuel Tank) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). [LOG 09:26:13.722] [TweakScale] ERROR: **FATAL** Part Size1p5.Tank.04 (FL-TX1800 Fuel Tank) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). [LOG 09:26:13.722] [TweakScale] ERROR: **FATAL** Part Size1p5.Tank.05 (FL-C1000 Fuel Tank) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). [LOG 09:26:13.722] [TweakScale] ERROR: **FATAL** Part Size3.Size4.Adapter.01 (Kerbodyne S3-S4 Adapter Tank) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). [LOG 09:26:13.723] [TweakScale] ERROR: **FATAL** Part Size4.EngineAdapter.01 (Kerbodyne Engine Cluster Adapter Tank) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). [LOG 09:26:13.723] [TweakScale] ERROR: **FATAL** Part Size4.Tank.01 (Kerbodyne S4-64 Fuel Tank) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). [LOG 09:26:13.723] [TweakScale] ERROR: **FATAL** Part Size4.Tank.02 (Kerbodyne S4-128 Fuel Tank) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). [LOG 09:26:13.723] [TweakScale] ERROR: **FATAL** Part Size4.Tank.03 (Kerbodyne S4-256 Fuel Tank) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). [LOG 09:26:13.723] [TweakScale] ERROR: **FATAL** Part Size4.Tank.04 (Kerbodyne S4-512 Fuel Tank) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). [LOG 09:26:13.723] [TweakScale] ERROR: **FATAL** Part roverWheelM1-F (RoveMax M1-F Rover Wheel) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). [LOG 09:26:13.723] [TweakScale] ERROR: **FATAL** Part Size1to0ServiceModule (SM-6A Service Module) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). [LOG 09:26:13.724] [TweakScale] ERROR: **FATAL** Part ServiceModule18 (SM-18 Service Module) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). [LOG 09:26:13.724] [TweakScale] ERROR: **FATAL** Part ServiceModule25 (SM-25 Service Module) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). [LOG 09:26:13.724] [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 09:26:13.725] [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 09:26:13.725] [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 09:26:13.725] [TweakScale] ERROR: **FATAL** Part Mk2Pod (Mk2 Command Pod) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). [LOG 09:26:13.726] [TweakScale] ERROR: **FATAL** Part MEMLander (Munar Excursion Module (M.E.M.)) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). [LOG 09:26:13.726] [TweakScale] ERROR: **FATAL** Part EquiTriangle0 (SP-T06 Structural Panel) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). [LOG 09:26:13.726] [TweakScale] ERROR: **FATAL** Part EquiTriangle1 (SP-T12 Structural Panel) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). [LOG 09:26:13.726] [TweakScale] ERROR: **FATAL** Part EquiTriangle1p5 (SP-T18 Structural Panel) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). [LOG 09:26:13.726] [TweakScale] ERROR: **FATAL** Part EquiTriangle2 (SP-T25 Structural Panel) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). [LOG 09:26:13.727] [TweakScale] ERROR: **FATAL** Part Panel0 (SP-S06 Structural Panel) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). [LOG 09:26:13.727] [TweakScale] ERROR: **FATAL** Part Panel1 (SP-S12 Structural Panel) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). [LOG 09:26:13.727] [TweakScale] ERROR: **FATAL** Part Panel1p5 (SP-S18 Structural Panel) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). [LOG 09:26:13.727] [TweakScale] ERROR: **FATAL** Part Panel2 (SP-S25 Structural Panel) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). [LOG 09:26:13.727] [TweakScale] ERROR: **FATAL** Part Triangle0 (SP-R06 Structural Panel) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). [LOG 09:26:13.728] [TweakScale] ERROR: **FATAL** Part Triangle1 (SP-R12 Structural Panel) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). [LOG 09:26:13.728] [TweakScale] ERROR: **FATAL** Part Triangle1p5 (SP-R18 Structural Panel) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). [LOG 09:26:13.728] [TweakScale] ERROR: **FATAL** Part Triangle2 (SP-R25 Structural Panel) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). [LOG 09:26:13.729] [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 ). However… I know these 51 parts, this had happen before! And looking for the right substring on your log, I found 51 instances of this log line: [LOG 09:22:10.606] Config(@PART[Decoupler_1p5]) TweakscaleMakingHistoryConfigs/Coupling/@PART[Decoupler_1p5] [LOG 09:22:10.606] Config(@PART[Decoupler_4]) TweakscaleMakingHistoryConfigs/Coupling/@PART[Decoupler_4] <49 more> So yeah. TweakscaleMakingHistoryConfigs strikes again. Delete GameData/TweakscaleMakingHistoryConfigs and everything will be fine. If you are using CKAN, make sure to uninstall it from there, so CKAN don't install it back. Welcome! Me too!

Well, since the CKAN guys released a ready to use APP for the Mac, I though exactly as you and made a test on my machine to see if it was a bug on the CKAN ou netkan files. Well, at least for TweakScale it worked as expected on my tests, so things are a bit more complicated than that. If this is a CKAN bug, it's something very hairy hidden somewhat on the code - simple tests worked fine for me. I don't think it's something on the netkan file because on my test TweakScale was installed correctly - and on the past, when I messed up the netkan, what ended up installed was the Extras directory contents, not the TweakScale binaries. Talk to the CKAN guys about this issue, explain every step you did and give this same KSP.log to them so they can try to reproduce the problem.

I just installed CKAN (it now works fine on Mac! Nice!), but didn't found a way to install it yet. I will try to forge an entry for the TMHC and see what happens. Chances are that CKAN is using a local cache for that file, however - I think it's hairy for Spacedock allowing downloading of deleted Add'Ons. About the original author, it's not his fault and I don't see why I should bother him - at least, yet. He deleted his Add'On from the Scene, he had act to prevent the mess. I don't think it's reasonable to tell the CKAN guys to delete the entry from the CKAN database neither. This Add'On once existed, it's part of the CKAN's history, and I don't like deleting history as a way to solve present problems. Not to mention that this one may had bit me in the SAS now, but who knows if this would not be useful later? The inherent problem is older, deprecated Add'Ons being installed and breaking things, not TMHC - and, definitively, not the older, deprecated Add'Ons that still work. I think that a new feature on CKAN would be a better idea: a blacklist to be updated by the Community, not by the Add'On Authors, listing incompatibilities that are discovered over time. But I'm brainstorming on the thing, perhaps a yet better idea exists.

Your installment is somewhat messy. There're some missing dependencies for some Add'Ons, but your man source of problems right now is two different TweakScale installments on your GameData! [WRN 13:24:34.521] Cannot create config from file 'D:\Games\Steam\steamapps\common\Kerbal Space Program\GameData\GameData\TweakScale\Examples.cfg'. <CUT> [WRN 13:24:38.486] Cannot create config from file 'D:\Games\Steam\steamapps\common\Kerbal Space Program\GameData\TweakScale\Examples.cfg'. <CUT> Version 4.0.2.0 D:\Games\Steam\steamapps\common\Kerbal Space Program\GameData\GameData\ModuleManager.4.0.2.dll Version 3.1.1.0 D:\Games\Steam\steamapps\common\Kerbal Space Program\GameData\ModuleManager.3.1.1.dll There are some Add'Ons mistakenly installed on GameData/GameData . Move everything inside GameData/GameData to GameData (delete what's duplicated), and at least the worst problems should go way. If anything persists, publish a new KSP.log and ModuleManager.ConfigCache for further analysis.

The hard part of the deal is that, in reality, things were probably "broke" for almost a year. What's changing on the TweakScale 2.4.3 series is that, now, TweakScale knows about the breakage and yells every time it finds something that can do some damage. A (somewhat) comprehensive essay about the known issues can be found here. There're many reasons these things happens, but IMHO the most commons are: People borks. All the time. But sometimes we fail to detect and fix the borks. Things change. Not always for better, but they change. But usually we fail to cope with the changes. The Eco System changed. The Add'On Scene we have today is way different from the Scene at the 1.3.1 times. Some things are better, some others are "worse". Usual stuff, nothing special about it. Communication failures. And Language Barrier can be a Sun on our Beach sometimes. Not to mention cultural differences. Complexity. Boy, this KSP thingy is complex, believe me. Windows 95 level of complexity. Yes, I'm that old. Most (if not virtually all) problems, nowadays, are happening due the interaction between Add'Ons. Every single one of them usually works pretty fine by themselves (we are not too much stupid , we detect obvious problems fast), but when you shove a bunch on them on an installment, friction starts and eventually the subsequent heat melts something. What makes things hard is that we can easily detect what had melted, but it's pretty hard to detect what was causing the heat, when the engine stops and everything is cool down (assuming the thing didn't exploded, right Elon?). What doesn't means that we cannot do something about. The key word is "we". We need to work together to be able to detect and fix most of the problems we have now. Please publish your KSP.log and ModuleManager.ConfigCache so we can try to figure out what's happening. In the worst case scenario, we can cook HotFixes and Overrules to keep your savegame ongoing in a sane way while we can't effectively fix the problem (it can happens sometimes, and until the moment, always by non technical reasons).

I will need your full KSP.log and ModuleManager.ConfigCache in order to check what's happening. It sounds like something patched these parts with "type = free", that it's the scaling that does what you describes. The Standard TweakScale distribution is working fine for Mk2. The Add'On I know that does that is All Tweak!! . Did you have it installed? ERRATA Nope, All Tweak uses stack, just checked. I need your KSP.log and ModuleManager.ConfigCache to figure out what's happening

Hi I found this idiosyncrasy on the Advanced Search: "Curse Representative" and "New Members" are duplicated. This can be or not a problem - if this duplication is happening on the DB, you may have two different IDs for the same thing. In time, there's a Thread for Forum bugs? I don't thing creating a new thread just for this is a productive measure. Cheers.

I'm toast!

Uh… I completely missed this: Folders and files in GameData: AirplanePlus B9AnimationModules B9PartSwitch B9_Aerospace B9_Aerospace_HX B9_Aerospace_Legacy BDArmory Firespitter GameData JSI SMArmory SmokeScreen Stock folder: Squad Do you see that "GameData" below Firespitter? It should not be there. It's probably a mistake on installing things. You have some Add'Ons there: [LOG 13:37:56.318] AssemblyLoader: Loading assembly at C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program\GameData\GameData\KTech\Plugins\KTechCategoryMaster.dll <cut> [WRN 13:40:38.470] Texture resolution is not valid for compression: 'C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program\GameData\GameData\LShipPartsRequired\Agencies\FNE_scaled.png' - consider changing the image's width and height to enable compression Please move KTech and LShipPartsRequired (and everything else if more) from GameData\GameData to GameData. This doesn't appears to be related to this issue, but this can cause some other problems (mainly on parts trying to reuse assets). I'll try an installment using the currently available Add'Ons (some of yours are not available for downloading anymore, and they are ARR!). I'm specially curious about some parts having TweakScale shoved on it without an "Applying update" log from Module Manager!

RealChutes, as far as I know, use its own Module. So you will need a custom TWEAKSCALEEXPONENTS to it. Something like this in a CFG file somewhere. TWEAKSCALEEXPONENTS { name = RealChuteModule caseMass = 3 // Cubic expoent spareChutes = 2 // Quadratic expoent PARACHUTE { preDeployedDiameter = 1.8 // You can use fractional expoents too, but this can be tricky! deployedDiameter = 2.5 // You need to make a lot of tests on it! } } Then you need to add the TweakScale module to the part: @PART[RC_cone]:NEEDS[RealChute] { %MODULE[TweakScale]:NEEDS[TweakScale] { %type = stack %defaultScale = 1.25 // Or whatever is the default size of the part } } Please note that I made this from heart, I don't have a clue if this will work as is - it will probably not. Good luck!

I understood. And I joked back, "advising" you to use another stunt that would trigger another Alert Box - I was hopping you would try it... But I thought it would be a good opportunity to explain why this thing is lingering for so much time. Murphy was a prophet!

When I did this stunt, I was thinking everything would be fixed by now. I thought the really heavy lifting on support would happen on 2.5, then I will shove :FOR[TweakScale] on the patches and then getting TweakScale out of the LEGACY patching. I jokingly "advise" to add a HOTFIX value so an AlertBox would remind you about the hack, so you don't risk forgetting this when TweakScale starts supporting them.

Granted. Unfortunately Clint Eastwood shot you and took it back. I wish I had a few dollars more.

So it was good news and great news! Silly mistakes are my favorite kind of mistakes - they can be easily fixed. Yep, it's what the Sanity Check does. The FATALities, however, can't be automatically handled as this can be injected at any time, i.e., you have a sane installment, start a savegame, then you install something and a FATALity is issued. If TweakScale withdraw itself on this situation, the savegame can get corrupted as any craft using the affected part will suddenly have that part descaled. Been there, done that - very entertaining. So the only safe measure is that scary Message Box. You install something and if a Houston happens, you know that whatever you installed triggered something bad (not always the thing is broken, sometimes is something else that it's triggered by it). And with the logs, we can check who had broken what and take action on it. About FASA, good! Hit me here if you need any help! Thanks. This will make handling it a bit easier, as I'm expecting a lot of similar occurrences. (TweakScale 2.5 will be a water divisor for a lot of classic Add'Ons, by the way). There's a command line option that tells Module Manager to save its logs on a file there and not on the KSP.log (or something like that - I don't remember, I never used this option myself). It surely made sense for some people, but for me is a drawback as my tools are designed to extract what I need from a sequential stream of data (what's a log is, essentially), not from scattered files around the filesystem. Anyway, if you don't know what it is, you are not using it. Ok, let's give it another shot. [LOG 13:53:59.726] [TweakScale] INFO: WriteDryCost Concluded : 1136 parts found ; 0 checks failed ; 0 parts with hotfixes ; 0 parts with issues overruled ; 118 Show Stoppers found; 0 Sanity Check failed; 478 unscalable parts. Check. Same result. Let's see the patching for smallwingConnector1: [LOG 13:49:30.631] Config(PART) AirplanePlus/Parts/Aero/smallwings/halfwing/smallwingConnector1 [LOG 13:49:37.129] PartLoader: Compiling Part 'AirplanePlus/Parts/Aero/smallwings/halfwing/smallwingConnector1' [LOG 13:49:37.282] PartLoader: Part 'AirplanePlus/Parts/Aero/smallwings/halfwing/smallwingConnector1' has no database record. Creating. [LOG 13:49:37.291] DragCubeSystem: Creating drag cubes for part 'smallwingConnector1' [LOG 13:53:59.472] [TweakScale] WARNING: **FATAL** Found a showstopper problem on smallwingConnector1 (Wing Connector Type F). [LOG 13:53:59.472] [TweakScale] ERROR: **FATAL** Part smallwingConnector1 (Wing Connector Type F) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). Damn. I was wrong, I got the very same results from the last time. I also confirmed that there's only one Module Manager on your installment, so definitively we had rule out a MM glitch or misbehaviour. Mod DLLs found: Stock assembly: Assembly-CSharp v0.0.0.0 ModuleManager v4.0.2.0 B9AnimationModules v1.3.2.0 / vv1.3.2 <cut> @DodoOnTheMün, I will need to handle this the hard way - by manually inspecting the Add'Ons patches, this is going to take more time than I have available right now. I will come back to it by night.

Excellent! I didn't know about that. Someone should add it to the Module Manager's Handbook and Syntax!

My apologies to anyone that witnessed that sad exchange of… opinions. I'll try not to be drawn again to such things. Now, let's get back to business. Got it. [LOG 18:57:27.124] [TweakScale] INFO: WriteDryCost Concluded : 1429 parts found ; 0 checks failed ; 0 parts with hotfixes ; 0 parts with issues overruled ; 6 Show Stoppers found; 9 Sanity Check failed; 488 unscalable parts. You can ignore that 9 "Sanity Check failed", these are parts that were patched but since some things had changed over time, TweakScale was not doing a proper job on supporting them. Please be patient as these parts will be supported on the next Iteration (2.4.4.x) of TweakScale. Let's get our pawns dirty on that 6 FATALities: [LOG 18:57:27.020] [TweakScale] ERROR: **FATAL** Part M2X.Endcap (Mk2 Airlock Adapter Endcap) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). [LOG 18:57:27.041] [TweakScale] ERROR: **FATAL** Part SecuBot16bad (SecuBot16bad) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). [LOG 18:57:27.043] [TweakScale] ERROR: **FATAL** Part M50FixedAero (M50FixedAero) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). [LOG 18:57:27.044] [TweakScale] ERROR: **FATAL** Part Single30TurretAlpha (Single 30 Turret) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). [LOG 18:57:27.045] [TweakScale] ERROR: **FATAL** Part M30StreamlinedAero (SM30 Auto Cannon) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). [LOG 18:57:27.046] [TweakScale] ERROR: **FATAL** Part GeneralDynamicsXM301 (GD_XM301 Gatling) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). The first one, M2X.EndCap, was already identified before. It is/was a glitch on Mk2 Expansion. My pull request was closed and the fixes applied. The 1.8.6. release has the fixes. Please update Mk2Expansion. The remaining 5, SecuBot16bad; M50FixedAero; Single30TurretAlpha; M30StreamlinedAero and GeneralDynamicsXM301 are being patched by SM_Armory, an Add'On that is not available anymore for downloading. One of them are being patched twice by SM_Armory: [LOG 18:53:22.644] Applying update SM_Armory/Patches/tweakscale/@PART[Single30TurretAlpha] to SM_Armory/Parts/Config/Single30Ball.cfg/PART[Single30TurretAlpha] [LOG 18:53:22.877] Applying update SM_Armory/Patches/tweakscale/@PART[Single30TurretAlpha] to SM_Armory/Parts/Config/Single30Ball.cfg/PART[Single30TurretAlpha] So I think it's reasonable to conclude that the source of the rogue patching appears to be SM_Armory. However, this Add'On is ARR and it's not available anymore for downloading, so I can't even inspect the patches myself, so we are in the dark on this issue. What doesn't means I can't try to help. Please send me your ModuleManager.ConfigCache so I can eye-ball it. With some luck, and by analysing the other Add'Ons those patches are available, I can infer the SM_Armory's original intent and then provide you with a HotFix for SM_Armory. Alternatively, if you have a GitHub account, we can move this "ticket" to the Issue #63, as more than one fellow Kerbonaut are getting some problems with it. Ugh.. [LOG 13:53:20.773] [TweakScale] INFO: WriteDryCost Concluded : 1136 parts found ; 0 checks failed ; 0 parts with hotfixes ; 1 parts with issues overruled ; 118 Show Stoppers found; 0 Sanity Check failed; 478 unscalable parts. 118 show stoppers. And some of them are, indeed, badly patched. Three tines in a row, as this part I got from the ConfigCache: MODULE { name = TweakScale type = free type = free type = free_square } Yep, we have some work to do! However, I have a problem. Your KSP.log appears to be incomplete! See: [LOG 13:50:40.451] Config(PART) AirplanePlus/Parts/Aero/smallwings/halfwing/smallwingConnector1 [LOG 13:50:43.427] PartLoader: Compiling Part 'AirplanePlus/Parts/Aero/smallwings/halfwing/smallwingConnector1' [LOG 13:50:43.491] PartLoader: Part 'AirplanePlus/Parts/Aero/smallwings/halfwing/smallwingConnector1' has no database record. Creating. [LOG 13:50:43.494] DragCubeSystem: Creating drag cubes for part 'smallwingConnector1' [LOG 13:53:20.641] [TweakScale] WARNING: **FATAL** Found a showstopper problem on smallwingConnector1 (Wing Connector Type F). [LOG 13:53:20.642] [TweakScale] ERROR: **FATAL** Part smallwingConnector1 (Wing Connector Type F) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). Do you see? There are no "Applying updates" lines on the log! (see the previous ones to see how they list every patch on a part using a log line with "Applying update"). Initially I thought you were being running from a ConfigCache, but I found: [LOG 2019-09-16 13:15:16.312] Checking Cache [LOG 2019-09-16 13:15:20.683] SHA generated in 4.379s [LOG 2019-09-16 13:15:20.683] SHA = 65-EC-B7-DC-C2-42-FD-12-56-78-D8-A1-68-23-F0-54-F1-46-FE-7C-B6-B1-F9-BE- [LOG 2019-09-16 13:15:23.180] Changes : Added : GameData/AM6E1engine/AM6E1engine.cfg <cut> [LOG 2019-09-16 13:15:23.185] Cache SHA = 4D-CE-A9-99-5B-2A-A7-DC-98-3F-FA-30-41-F5-71-AA-BC-E5-26-A8-40-4F-94-5C- [LOG 2019-09-16 13:15:23.185] useCache = False What means that no, you are not loading from cache. But then I found some parts with the log message, and others without: [LOG 2019-09-16 13:46:09.429] Applying update SMArmory/SM_OSTandT/Patches/Armor_SMI_OST/@PART[Tiger1Hull]:FINAL to SMArmory/SM_OSTandT/Parts/Tiger1Hull/Tiger1Hull.cfg/PART [LOG 2019-09-16 13:46:09.479] Applying update TweakScale/BreakingParts/B9_HX/@PART[B9_Structure_HX1_S_HS]:NEEDS[TweakScale]:FINAL to B9_Aerospace_HX/Parts/Structure_HX/model_hx_size1_structure_hub_support.cfg/PART And this can explain why some parts are terribly patched - the BreakingParts are a stunt to prevent ongoing savegames to break by fixing the parts. Not all double patching leads to a crash, so initially I was trying to keep some parts broke in order to prevent losing ongoing savegames. So, unless I had told you to use this stunt, please delete GameData/TweakScale/BreakingParts . You have a some SM Add'ons on your installment, and there's a chance that some of them can be doing something wrong are the previous guy. But since your KSP.log is… weird… I can't be sure. Your list of DLLs says: Mod DLLs found: Stock assembly: Assembly-CSharp v0.0.0.0 ModuleManager v3.1.1.0 ModuleManager v3.1.2.0 ModuleManager v4.0.2.0 B9AnimationModules v1.3.2.0 / vv1.3.2 B9PartSwitch v2.5.1.0 / vv2.5.1 BDArmory.Core v1.3.1.0 BDArmory v1.3.1.0 Firespitter v7.3.6867.18541 KTechCategoryMaster v0.0.0.1 SMI_APUcontroller v0.0.0.1 RasterPropMonitor v0.30.5.22792 KTechCategoryMaster v0.0.0.1 SMI_APUcontroller v0.0.0.1 SM_MalFuncIndustries v0.1.0.5 SMI SmallArms v0.0.1.0 HoverCraft v1.0.4.4 SMIndustries v0.1.0.6 VLSLauncher v0.1.0.0 SM_ParaMotor v0.0.0.1 StrykerAA v0.1.0.5 SmokeScreen v2.8.1.0 Stock assembly: KSPSteamCtrlr v0.0.1.35 KSPe.Light.TweakScale v2.1.0.13 Scale v2.4.3.4 Scale_Redist v1.0.0.0 / v2.4.3.4 With three different versions for Module Manager available. Perhaps having all of them installed leaded to this glitch? This is a blocking issue for me, because without a log that tells me every "Applying Update", I cant trace who is patching who and then I'm on the dark without the option of detecting the source of the problems and propose fixes. So I need to ask you to: Delete all Module Maneger DLLs but the 4.0.2 one. Make sure you are not logging Module Manager into separate log files. I need all the logs into the KSP.log file, my tools are designed to work this way. Delete ModuleManager.ConfigCache Delete the directory <KRP_ROO>/Logs Launch KSP.exe As soon the FATAL Alert Box appears, just shutdown KSP Send me again KSP.log, ModuleManager.ConfigCache, and just to be on the safe side, everything under <KRP_ROO>/Logs Hopefully this will provide me with the information I need to check things. To avoid accidentally deleting them, I propose to save the files on: hacks GameData/__LOCAL/TweakScale/hacks Hot Fixes GameData/__LOCAL/TweakScale/HotFixes Overrules GameData/__LOCAL/TweakScale/Overrules You can put them anywhere, but these locations are easy to remember, to check and are out of the way of the installers tools so you don't risk losing anything when update things. [LOG 17:14:30.249] [TweakScale] INFO: WriteDryCost Concluded : 1630 parts found ; 0 checks failed ; 0 parts with hotfixes ; 0 parts with issues overruled ; 554 Show Stoppers found; 0 Sanity Check failed; 476 unscalable parts. Yeah, you have about 554 Show Stoppers!! Dude, you are definitively the Winner on this contest! But I need the full Log. I need to track down evert patch being applied to get into the problem. Please publish the full KSP.log (and also the ModuleManager.ConfigCache) on Google Drive, Drop Box or something like that. My hands are tied without all that information!

So go back to use KSP 1.3.1 Things had changed, dude. KSP changed, a lot of Add'Ons changed, and things are how they are now. RO does not support TweakScale. I can't support an Add'On that doesn't supports me. I will omit the Source for obvious reasons, but this is what I was told about: [snip] if you are willing to help me on fixes for the mess, I'm accepting Pull Requests for HotFixes like this. https://github.com/net-lisias-ksp/TweakScale/blob/dev/emergencial/2.4.3.4/Extras/TweakScale/HotFixes/RO-Stock_Electrical.cfg

I could not agree less. The main reason for RO problems with TweakScale is RO bad patches. RO fix their patches, problems go away - people using RO had reached me in private asking me how to fix RO patches, since the RO guys said they don't support TweakScale, besides having a lot of bad patches on the distribution. The root cause for this is you not following Maintainers advices. RO guys don't support TweakScale, and I already have my hands full supporting Add'Ons that support TweakScale. What I gladly do creating Pull Requests when the license terms are acceptable and the Maintainer are kind enough to accept the contribution. This is the same as trying to cure Malarya with antipyretics. And this doesn't covers manual installing. This is shoving on my … shoulder the burden to fix things did by third parties. It's unfair and unfeasible to expect that an Add'On Maintainer to be responsible for the (bad) behaviour misbehaviours from third parties. [snip] I just checked the NetKAN file for TweakscaleMakingHistoryConfigs: { "spec_version": "v1.4", "identifier": "TweakscaleMakingHistoryConfigs", "$kref": "#/ckan/spacedock/1806", "license": "WTFPL", "x_via": "Automated SpaceDock CKAN submission", "depends": [ { "name": "TweakScale" }, { "name": "MakingHistory-DLC" } ] } No Author informed. The SpaceDock entry 1806 returns 404 Not Found. I didn't found it on the web archive neither. By all means, this is a "bogus" entry that describes an Add'On that doesn't exists and CKAN guys know about it, as it was frozen. So, no. I'm not making CKAN accountable for this mess neither - they are, also, just messengers. — — — — — That said, I'm not sitting on my hands on this. I will tackle this problem down. I just will not play Cat and Mouse with the problem - if I'm going to use yet some more of my scarce free time solving third parties problems again, I will do it on my terms. TL;DR : I will support who supports me, and I will work out a soft ban on non forum compliant Add'Ons. (please don't take it as an argument on you - you are another messenger on this problem! )

It's what I was wandering. But TweakScale has MH support for more than an year already. This is playing cat and mouse with the World, and I'm not even sure I'm the cat on this. What's triggering my grumpiness is that I could not even download the thing because this damned thing has no presence on the Web! I managed to find a page with a link to Spacedock, but that was all. I don't know who's the Author, I don't know the contents (but now that some kind user cared to provide me with the ConfigCache, I can Infer it by reverse engineering). But at least I can check it now that I know it's still available on CKAN. Unsupported Add'Ons should be marked as such. And it's pretty unfeasible to expect me to detect and mark every single Add'On created in the past to avoid having my Toes stomped by zoombies. on the other hand, people using CKAN use it for a reason, to do not have to handle such idiosyncrasies him/her/itself. I think that unsupported Add'Ons on CKAN should be marked as such, with a very nice alert on installing. Alternatively, a List of Endorsed Add'Ons could be implemented. Curators would be responsible to maintain such lists to avoid this mess. well, now that I know what's this, I can write a nice Show Stopper message detecting "Unholly Add'Ons", freezing the game until the thing is uninstalled. Ideally, I should not have so much of my free time wasted diagnosing things that would be hugely simpler to prevent by other means, as the installation tool. There are real problems still happening on the wild, and I wasting time diagnosing the same problems over and over. Please note that this is not a complain about the people reporting the same problems over and over - don't shoot the messenger. The problem is the need to report the problem at first place. We solve the root cause, people stops complaining about the same issues, because the issues are solved for good. We have a flaw on our Distribution Process. We need to locate it, and tackle it down.

Last time I saw something like this, in a distant Web 2.0 company I once worked on, it was a problem with the cache (we used MEMCACHED at that time) to cache the dynamic pages. Someone had the "bright" idea to use MD5 on the URLs to use as cache ids in a (desperate and fruitless) attempt to speed up things, as our URLs were getting bigger and bigger. Stupid move, you can't expect to shrink a sample space of 1024, 2048 bits into 256 without collisions, and the ending result was very similar to what you describes. Check if the URL is not being truncated somewhere in the stack, perahps on the cache too.

This just got to my attention. MSI Afterburner, RIVA Tuner and perhaps others adding layers to the Unity application can lead to a crash similar to the ones on this thread. Steam also adds a layer. It may be another trigger to the problem.

This is going to make my life a bit harder. I was using the likes to mark already handled support requests on TweakScale thread.