Lisias

And I complemented your the speculations using my own knowledge from some support I'm doing not only on TweakScale, but from users that also don't have it and had similars problems. Now it's a bug report.

Your professionalism on handling bug reports are remarkable.

None of the TSCo adds anything to the Toolbar, only the TweakScale itself does it - on Editor, never on Flight. So I think you found a bug on the KSPCF code that tries to fix the Assembly Loader/Resolver! Some of the TSCo (very few) ends up tied to a specific TS's dll that if changes too much, borks. It's the reason I'm delay some releases on CurseForge and SpaceDock - so when I do it, everything is updated. It's the only thing I can think may be influencing your problem - a dependency loading problem. Since you mangled the Assembly Loader/Resolver, it makes it a problem caused by KSPCF. The TSCo was the trigger for the problem, but the problem itself is that your interventions on Assembly Loader/Resolver are not working as expected. So, it's a problem being caused by KSPCF now.

I don't believe it's up to you do decide. If there's someone willing to maintain it, and the previous owner was willing to transfer it, and a third one is willing to publish it, I really fail to see where the problem is. Let users choose. Fuel Switches can be problematic. B9PS have a myriad of support tickets caused by 3rd parties. Not their fault, but the user can't play the game the same until the thing is fixed and it's hard to criticise a user that decides to look for alternatives and avoid the hassle for little things like a oxidiser tank. (it's exactly what I did too, by the way.) Not to mention KSP squashing the resources to prefab itself, forcing Fuel Switches to do things that make coexistence even harder - I know what I'm talking, I maintain TweakScale. Check the Companion's Source Code to see some borderlines situations and how I had to cope with them. Installing a Fuel Switch with the sole purpose of having a pure oxidiser tank can be a way overkill and expand the user's surface for attacks by unexpected (and surely undesired) problems.

@Spike88, I purposely installed an older UberPacket to see what happens on my rig by using the 2.4.7.0 TweakScale release, and nothing bad happened. Everything just worked fined. But then I remembered that I had uninstalled Waterfall from the test bed - and, so, the older Waterfall support just didn't was loaded at all. Well, bingo. Once I installed Waterfall, I got exactly the same Exceptions you got on your log, but my Toolbar didn't got any duplicated Icons!!! There's something else happening in your rig, one of the add'ons you have installed is the one borking on this one. This Companion mess up may be a trigger, but the real problem is somewhere else, hidden as a land mine, waiting someone to step on it!!

On the Kerbal way! Someone needs to create a Eiffel mod for KSP now! https://theaviationgeekclub.com/the-story-of-bill-overstreets-p-51b-berlin-express-the-mustang-that-flew-under-the-eiffel-tower-in-hot-pursuit-of-a-luftwaffe-messerschmitt-bf-109/amp/

Hummm… Now I understand… You may had found a "bug" on the improved Companion Checker I just coded. Checking it… <hack, hack, slice and hack again> EXACTLY. I shipped 2.4.7.0 with the wrong definitions file! GameData::KIS Kerbal Inventory System (KIS) TweakScaleCompanion_KIS KIS Thank you very much for your persistence, @ngx, sometimes my dull thick skull is a bit too thick for my own good. I'm fixing this and publishing 2.4.7.1 in the next few hours. In the mean time, please ignore the message. It should not pesky you too much, it will be shown only when the ModuleManager's ConfigCache is rebuilt to remember you about the respective Companion (or when it finds one of the very few add'ons that demands a Companion installed to prevent breakage, a rare situation but at least two 3rd parties add'ons fall on this class). Cheers and thanks again!

You also need to remove GameData/TweakScaleCompanion/Frameworks , or update to the latest one: https://github.com/net-lisias-ksp/TweakScaleCompanion_Frameworks/releases . @ngx, you probably need to do it too. Forgetting to update the Uberpaket was a bad move, my apologies. [edit]: Nope! Only the github repos were updated, both the Companion and TweakScale will be updated at the same time on CurseForge and Spacedock!!! I'm rushing it into the repository now.

ARGH… I forgot update CurseForge and SpaceDock!!! [edit] Nope! The UberPaket will be updated on CurseForge and SpaceDock when I update TweakScale, both need to be updated at the same time there. Currently only the github were updated!! You can ignore the message for while, and please keep an eye on https://github.com/net-lisias-ksp/TweakScaleCompanion/releases . I will update it in the next few hours!!!\ Or install KIAS manually (remember to delete the older KIS): https://github.com/net-lisias-ksp/TweakScaleCompanion_KIAS/releases That's weird, TweakScale only creates an Icon on the Editor's Toolbar. I'm inspecting your log. Same thing, you need to install the (futurely) latest TweakScaleCompantion UberPacket, that I forgot to upload. Ignore the message for some more hours, or update manually to KIAS using the link above. (Remember to remove the old KIS directory)

It's a known issue: you left the auto-scale feature activated. The parts didn't disapeared, they got too small to be seen. Undo the last action (ctrl-z or cmd-z or meta-z - depending of the OS you are using) and then turn off AutoScale as a work around. This issue is fixed on the beta branch, by the way. Or should be... I need to verify it again.... Cheers!

Yep, it's exactly this. [LOG 12:15:33.170] [AddonLoader]: Instantiating addon 'WaterfallData' from assembly 'Waterfall' [ERR 12:15:33.198] [AssemblyLoader] Exception when getting assembly attributes: Exception of type 'System.Reflection.ReflectionTypeLoadException' was t hrown. Additional information about this exception: System.TypeLoadException: Could not load type of field 'KerbalFoundries.KFGUIManager:appButton' (10) due to: Could not resolve type with token 01000017 (from typeref, class/assembly ApplicationLauncherButton, Assembly-CSharp, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null) assembly:Assembly-CSharp, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null type:ApplicationLauncherButton member:(null) signature:<none> What happens: there's a nasty bug on a thingy called Assembly Loader/Resolver inside KSP that is triggered everytime something fails to be loaded due a missing or inadequate dependency. From this point, everything and the kitchen's sink starts to bork while loading DLLs or using a thingy called Reflection, and TweakScale makes heavy use of both. In your specific case, the "Could not resolve type with token" thingy is telling us that whatever is the dependency KerbalFoundries needs, it's there but it's from a different revision from what KF was compiled because something the code is swearing it will find on that Assembly, it's not there! You need to reach Kerbal Foundries maintainers and ask them about that it's this DLL and what the version KF needs to have installed in order to work. Things can get messy pretty fast when some other add'on installs an older version of that DLL, because now, out of the blue, something that used to work is now broken and no one have a hint about the reason without some digging… Anyway, there's no other option: you need to reach KF maintainers in order to undestand what is too old (or too new) for KF and then fix the thing. In the mean time, KF is not working and you may want to remove it in order to get everything else to work again (including TweakScale). Good luck!

And all your base are belong to us!!!!

Feedback time! I (think) I fixed the problem here: https://github.com/net-lisias-ksp/KSP-Recall/issues/61 I managed to understand what and where the misbehaviour was happening, but I confess that why this was happening is still eluding me. Anyway, I'm counting my blesses on this right now. On the not so bright side, I need to cook a workaround to allow KSP-Recall users to use the newest workaround on Refunding - since a 3rd party decided that they should bluntly deactivate it no matter the user prefer their solution or not. https://github.com/net-lisias-ksp/KSP-Recall/milestone/24 I hope to have something published by the of the week. Cheers!

This is the ModuleManager log. It helps, but not by itsefl. Please publish the KSP.log and I will take a look on it.

I would love to nominate this for thread the "Thread of the Decade" is something like that existed around here. @adsii1970?

Ahh!! Great news! So I don't need a Steam Deck after all… I did my best to void breakage while shifting from Mainstream to Beta and vice versa, so most of the time you can switch between releases without fuss - but now and then I miss a detail or two, and then things go havoc. So the need to keep backups (what is not a bad idea even on mainstream, to tell you the true). Keep in mind that bugs are expected on Beta, but they should report the same - otherwise the bugs will reach mainstream and then I will have to handle them anyway. To tell you the true, the Beta is essentially a Release Candidate now (I prefer to avoid "Early Access" - this term is somewhat tainted lately…) Cheers! --------- The problem is not consistent on every part. Some parts are getting clipped instead. Damn. — — — — — — It's a new (old) bug on KSP Editor. (sigh). https://github.com/net-lisias-ksp/KSP-Recall/issues/61 So, it wasn't TweakScale (2.5) neither Recall fault. TweakScale 2.4.6.x has a glitch, indeed - but this glitch is a collateral effect from the problem, and somehow TS 2.5 Beta is not prone to it (I refactored that thing a lot)

B9 Procedural Wings is badly installed, you forgot to install a dependence. This triggers a nasty bug inside KSP on a thingy called Assembly Loader/Resolver that, once triggered, screws everything and everybody that tries to load something, being TweakScale one of them. Post your KSP.log here and @linuxgurugamerwill gladly check it and tell you what's missing.

You didn't removed MiniAVC v1 from your system. Please do it, it's pointless to try to support your system with it installed. Plase find and remove all MiniAVC from your GameData.

I'm seeing that gap between the second cockpit and the third. Are you merging two crafts, each one with two Cockpits, right? [EDIT]: YEAH, it's exactly this. I confirm the problem, and it's happening downto KSP 1.4.3. It's something on me for sure! Additionally, it's not KSP-Recall, or perhaps not only it. Tweakscale 2.5 Beta behaves better - with TS 2.5 is installed, you can save and reload the craft, and manually adjust the parts by detaching and reattaching. So the source of the problem appears to be TweakScale, while Recall just blindly tries to reapply the attachment nodes that TS kinda screwed up. So you are essentially brute forcing a reset on the PartModule. An easier way would be to rename the AttachedOnEditor PartModule from the craft file and load it. By renaming the thing to anything else, KSP will get rid of the data and replace it with a fresh AttachedOnEditor one, that will so "renew" its internal data. [EDIT] Scrap that, it didn't made any difference. In fact, it doesn't appears to be KSP-Recall at all. It's a old problem on TweakScale that it's already fixed on TweakScale 2.5 beta, but I had to cope with some things in the past month that prevented me to publish the fixes! I'm assuming you are on KSP 1.12.5, right? I don't remember this problem last time I gave this a look, I think on the 1.11.x times... (I'm not telling the problem isn't there, I'm telling I don't remember it - two different things) Krap!!! I need the (more or less) same Version of SteamOS and SteamClient that it's being used on Steam Deck right now, because I need to have that @$@#!#$ PWD vc AppRoot problem figured out as once. It's more then due time someone nail this problem, we need to have closure to this crapness! Anyone in Brazil's are willing to lend me a old SteamDeck for some weeks? The thing can be half-broken, as long it boots, can install KSP on it and the touchscreen is useable so I can do terminal checkings on it. [edit]: not needed. SteamOS works on any X64 hardware. Problem is that I need something that I can install on a crappy old PC. I don't plan to run games, I just want to install KSP on it using the Steam Client, check how things works on the filesystem, fire KSP once and again, and then toy a bit with the file system again. I don't have access to a Steam Deck right now (3rd world countries worst problem: too much taxes). Yes, it does! Thanks for the heads up (in both accounts)! Cheers! — — — post edit -- — — @AZZlyTheAZZome, it's not Recall, it is just doing what it's being told to do. TweakScale is the one screwing things on Merging crafts! https://github.com/net-lisias-ksp/TweakScale/issues/294 — — — POST POST EDIT — — — Aaaaand… It's a new bug on KSP's Editor that I wasn't aware!

I'm a bit nostalgic today. Played this one with my little brother a lot when we were younger. (as a team, because on death match I was dead before the third chord…)

You forgot about a continuously growing event- the Sun. That thing is getting hotter and hotter as time passes. In the past, the Sun was dimmer. A lot dimmer, it's brightness at the time Earth was forming was about 70% of what we have now. When the first monocelular lifeforms happened around here, the Sun was yet about 75% of the current brightness and Earth wasn't a snowball (yet) because the Earth Crust was still too thin and the Mantle's heat kept things warm enough. By the time the first photosynthesis happened, the Sun probably was shining at 80% of today standards. In the mean time, Venus could be a Paradisical Planet fit to breed life. Perhaps the lost Eden? --------- Source.

How? It would help to document the issue here so people could easily find the solution by searching the Forum!

Ah!!! Things are way less problematic than I was fearing! It's a silly problem, to tell you the true... Fix is simple: look for and remove every directory called @thumbs inside your KSP's directories. You should find a bunch - remove everything, they will be regenerated next time you fire up KSP. What's happening is that KSP caches thumbnails of images so it doesn't need to recreated the little images all the time, but the code that preloads them inside KSP is less than ideally coded, and it shameless fail when anything goes wrong while loading a precomputed thumbnail - halting the game loading. Removing all thumbnails will guarantee this code will not bite you again - until something happens and another thumbnail gets corrupt again (by any reason, from filesystems trying to recover from a bad block to energy going out while writing the file into disk). Every time your KSP locks up while loading anything having @thumbs in the pathname, you just remove all of them and restart KSP and everything will be fine (assuming the KSP files are intact, what you already had assured by doing a Steam verify). Cheers!

The hack is ugly, but it works and it's auditable and deactivatable if needed. And it can also be positive , it depends from the affected part being overrefunded or underrefunded. Additionally, that ugly hack is, currently, the only workaround for really very expensive parts that are being hit by the lack of precision of floats. It's still a hack, but the hack aims to shift the burden into bonus: if the correct amount of Funds can't be refunded due the float problem, the thing tries to refund you the next higher possible value instead of you having the lowest possible float representation as it happens now (where you can lose huge amounts of Funds in the process). Back to Refunding, there's a catch, granted. Code that doesn't honors the Resource flags that says the Resource is not visible, not transferable, not drainable and not tweakable will obviously misbehave. But this is over the 3rd party's shoulders, not on Recall. Recall does the Right Thing(tm) and correctly follows the KSP's Resources Conventions. You find someone misbehaving on the thing, you found something in need to be fixed to follow such conventions. WBI uses specialized PartModules that TweakScale doesn't knows about. I need to write a Companion for the thing. Keep an eye on the TweakScale Companion Program. I'm adding support for more and more 3rd parties as time allows. Cheers!

Are you using steam? If yes, do a Install Verify. Are you using spinning disks or SSDSs? If using magnetic media, you should do a media verify because parts of disk may be dying on you and you need to block them before more damage happens. SSDs also suffers from dying macro-cells too, but the mitigation is automatic- other than having some files corrupted in the process. In a way or another, do full backups of everything and be prepared for a disk replacement in the near future - better safer than sorry!