Lisias

Yeah. And the fun begins. — — — @HawkEngineer, @Marut, @falcoon, @farnayway CKAN problems: that caught me with my pants down. I don't have the slightest idea about what's happening. Since I didn't changed anything on the CKAN configuration file, added one DLL on the Plugins folder, some .CFG files on the TweakScale folder, and a new folder called __LOCAL/TweakScale - so it's hardly something I can revert or control. I think this is most likely to be something wrong on CKAN itself. Did you guys reached the Maintainer? — — — That folder is being shipped (on Github, CurseForge and SpaceDock) empty with only a README.md. This is the place where I recommend placing eventual patches needed to "break things again" in a controlled way to keep current savegames ongoing if the need arises. Check if there's anything besides a README.md on that folder. It's meant to be populated by the user with custom patches made specially to that installation (since the __LOCAL thingy) — — — @Rafael acevedo your log file is truncated, it doesn't goes to the point in which I can help. With the full log I can say what the problems are, and if I can help or if we need to escalate it to someone else. — — — This is happening to some parts that lack proper support and I had to withdraw support for these parts because they were crashing KSP. TweakScale is doing it from some time already, this is the first time I'm displaying a message about. There's no other alternative but to support the parts or bluntly withdraw support for them. Some of these parts lacking support are Stock ones - they use ModulePartVariant with mass, and this is not implemented yet on TweakScale due the amount of issues I had to cope first. The TweakScale 2.4.4 series will be dedicated to implement support for these parts as also to add support to any other Stock part not supported yet. But some other parts are not Stock and are not under my control, since the need of the message. Such parts need to have this tacked down by the maintainer in way or another. — — — @whitespacekilla . I will review the pull request ASAP.

Didn't knew the original song - just the one from the Blue Brothers!

Wow…. TweakScale is not working at all on your installment. By your log, the "Scale.dll" is missing! Download TweakScale again from one of the links on the OP, delete the whole TweakScale folder on your GameData and install it again. I just checked the 3 links and eye balled the contents and the packages are fine. So something happened on your side of the cable-modem. After giving a second look on the KSP.log, I ask your permission do additionally advise you to: Install and use S.A.V.E. I'm doing my best to avoid breaking things, but there're a lot of Add'Ons "out there" and it's unfeasible I can check all of them for incompatibilities or mishaps with TweakScale. With S.A.V.E. we can be assured that such events, if happening, would be nuisances and not problems. I found some log entries about problems with "WildBlueIndustries.ModuleBreakableFuelTank.onFlowStateChanged" and "InterstellarFuelSwitch.InterstellarFuelSwitch" . I don't have a clue about what's happening neither if this is serious or not - but on the recent past, when TweakScale was caught on such exceptions, bad things happened to the game. Better safe than sorry, I would ask about directions to the Add'Ons maintainers. It can be something simple as an outdated or missing dependency. There's something broken on Kopernicus ("Could not load type 'System.Runtime.CompilerServices.ExtensionAttribute' from assembly 'KatLib"). Perhaps a missing dependency? Since you are using KSP-AVC, consider using ZeroMiniAVC. The more recent package I found is here. There's a lot of useless MiniAVC dlls on your installment. Not a problem at all, but I find them annoying. On a side note, there's a really awful ammount of log messages saying "-INFO- System.Boolean[0][1636.83]: LoadFromStock" . Tens of logs each Millisecond, thousands of logs each seacond. This thing is being a drag on your game, this awful amount of logging affects performance. If I manage to find the source, I'll let you know.

ANNOUNCE Impossible Innovations V0.8.8.6 is on the wild! 2019-0728: 0.8.8.6 (Lisias) for KSP >= 1.3.1 Using KSPe.Util.Image facilities update to the most recent KSPAPIExtensions (2.1.0.15 at the present moment). Dependencies are not more embedded. We are sorry for the inconvenience, but it’s unfeasible to keep various downloads to the same version when only the dependencies are KSP version locked. See INSTALL.md for detailed instructions. Avoiding runtime problems on TweakScale Certified for use from KSP 1.3.1 to KSP 1.7.3 Now Impossible Innovations works from KSP 1.3.1 to the latest. Using the same package, no changes. On the other hand, the dependencies are not being packed together anymore - there’s no point on making the Add'On multi KSP just to be forced to distribute multiple packages due Add'On restrictions. Most of the time, the Add'Ons are utterly outdated at the moment of the download anyway. Download on the OP. Cheers!

They don't use that feature that changed. Apparently they "leaked" the feature by accident, but since that feature is public for about 5 or 6 years, everybody that uses that took it for granted.

A simple cache in a dictionary would solve that. (I didn't realized it until now). Granted. They're not doing it right so. You did it for a reason. Sometimes, Murphy just happens - and this stand-up guy is quite busy.

I see a fourth reason: I remember that code checking the GameDatabase before (or after?) trying to read the file. So, for Add'Ons that choose to use textures on the GDB, Unblur users already have them "fixed" (after configuring the thing). Add'Ons that choose to load it manually from the PluginData folder would keep doing it (and since this texture, ideally, is used only for the toolbar, it should be loaded only once anyway). Add'Ons that manually load textures from outside a PluginData are doing it wrong, and they should be fixed - eventually.

I'm baffled!! However, now I have an idea where the problem can be. It's on the KSPe thing. Something is working somewhat differently on your machine, perhaps something on Windows 10, or due you using drive D, or both. Otherwise someone else would had already kicked me in the SAS due this stunt. Congrats. You opened the very second Issue for KSPe!

Can anyone explain to me how this Thread came to my Activities Stream without anyone posting anything here?

#facePalm There're something utterly flawed on the initialisation process (where such paths are defined). How in hell this worked for me is a mystery. Well, I will make some new coffee and take a look on it. I don't have the time to take this AddOn for good (and further develop it) by now, but these little pesky mistakes are something that I want to keep in check. People want to use this (me included) after all! — — POST EDIT — — Well… After finding bugs everywhere (including the coffee maker) but not on that Kraken Poo I call that code I remembered that Leaky Abstractions thingy and decided to do a… well… blind guess. There're only two places on that code where such things could go down to the tubes, so I changed both . Weirdly, but not unexpectedly, this made no difference on my machine. I'm doing some quick testings and will publish a new release in the next hour. — — POST POST EDIT — — @w00tguy - I reissued the current releases for UbioWeld and its dependency, KSPe. Please delete what you have and download them again. I don't have the slightest idea if this will do any good for you, however. All I can say is that this still "Works For Me". https://github.com/net-lisias-ksp/KSPAPIExtensions/releases https://github.com/net-lisias-ksp/UbioWeldContinuum/releases

Yeah, that Joystick stunt are still lingering. I though that by having help from Private Division, someone technically skilled on the matter would had stepped in on it by now. One probably explanation is, taking Steam Surveys as reference, 98% of gamers as on Windows. However, this is not applicable to a single game! KSP has support for MacOS and Linux, while most games don't. But without the specific figures for KSP, I can only guess. We can be facing a survivorship bias here. They can be looking to people currently satisfied to KSP, and overlooking people that are don't but could be - and then spending some more money on it. Since you are in so good mood. Would you try the Beta Release of TweakScale 2.5? I'm trying figures to scale correctly the Wheels and Landing Struts, and would appreciate ay advice. — — — Oh! About me? I'm trying to fix something on Ubiozur Welding Tool. Yeah. Mono and MonoDevelop. On a Mac. Yeah, I feel you bro.

It's my way to cope with frustration. Venting out helps on that Five Stages of Grief. (and that was idiotic anyway! ). That was unexpected. I'm on it. — — NEWS FROM THE FRONT — — I found this exception: [LOG 09:31:30.126] Autogen thumbnail for D:/Steam/steamapps/common/Kerbal Space Program/KSP_x64_Data/../Ships/@thumbs/SPH/Albatross 3.png (Stock) from D:\Steam\steamapps\common\Kerbal Space Program\Ships\SPH\Albatross 3.craft [ERR 09:31:43.830] [WeldingTool] ERROR: UbioWeldingLtd.UbioZurWeldingLtd raised Exception System.IO.IsolatedStorage.IsolatedStorageException: Could not find a part of the path "D:\__LOCAL\net.lisias.ksp\UbioWeldingLtd\Aero\weldedpart\weldedpart.cfg". at System.IO.FileStream..ctor (System.String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, Boolean anonymous, FileOptions options) [0x0000 0] in <filename unknown>:0 at System.IO.FileStream..ctor (System.String path, FileMode mode, FileAccess access, FileShare share) [0x00000] in <filename unknown>:0 at System.IO.File.Open (System.String path, FileMode mode) [0x00000] in <filename unknown>:0 at ConfigNode.Save (System.String fileFullName, System.String header) [0x00000] in <filename unknown>:0 at ConfigNode.Save (System.String fileFullName) [0x00000] in <filename unknown>:0 at UbioWeldingLtd.UbioZurWeldingLtd.WriteCfg (System.String pathname) [0x00000] in <filename unknown>:0 at UbioWeldingLtd.UbioZurWeldingLtd.HandleInfoWindow (Int32 windowID) [0x00000] in <filename unknown>:0 at UbioWeldingLtd.UbioZurWeldingLtd.OnInfoWindow (Int32 windowID) [0x00000] in <filename unknown>:0 Can you confirm to me if the file D:\__LOCAL\net.lisias.ksp\UbioWeldingLtd\Aero\weldedpart\weldedpart.cfg exists on your disk? If not, to what level of Subdirectories the tool managed to get into? If the file exisits, please delete it and try again and tell me what happened. There's something brittle on the code. It "Works For Me" (c) 2019 LisiasT, but I'm on MacOS and we can be looking to a Mono's Leaky Abstraction(c) 2002 Joel on Sofware. Or, perhaps, some change on the order in which some internal KSP events are being issued on Windows. Historically, KSP Add'Ons had a hard time coping to concurrency. It may be a new case of this.

There are some mysteries on Life, and this is one of them: how in hell this didn't blew up on my face before? This was an absolutely idiotic mistake of mine made a long time ago. I don't have the slightest idea how this didn't happened to me (or to anyone else) before! Fixed on 2.6.0.6 release of my personal fork.

Without a full log., it's hard to give any advice. All I can say is "works for me". The best I can do is guessing, and since some fellow Kerbonauts reported using the Welding Tool with moderate degrees of success (it works better by welding parts using KSP 1.4 or 1.5, and then copying the parts to the target KSP), my best guest at the moment is that you are using Module Manager 4. If I'm right, you need to read this post: TL;DR: You need to use MM3.1.3 with Welding Tool (being it my fork, of the Canonical one on the OP). Welded parts have no problems with MM4, it's a change that happened on MM4 that broke something on the Welding Tool. Since it's usually a better idea to weld parts on KSP 1.4 or 1.5 and then copy them to the desired KSP version, using MM3 for welding does't appears to be more than a nuisance for now.

Well… Things are (sort of) calm these days. So I got some time to play. Really play, no testing things. Given the 50 years of Apollo 11 and (good) news on SpaceX, I decided to try an Apollo 8 mission - on the SpaceX style. Launch and separation was interestingly easy by the way. Going to space is easy - it's the coming back that is hurting now! Long history made short: This is the booster after.. "splashing down" But hey, the spacecraft got to the Mün! And everybody came back home. Leaving behind some superfluous hardware on the way. Not too much to see, but the full report is here: http://ksp.lisias.net/screenshots/2019/07/25_Apollo-Falcon-Style/

I use Steam that keeps things tight for me. In another thread, I read someone fixing the problem by downloading the PKG file.

Given that MoarDV had licensed RPM under the GPLv3., is feasible that it can be maintained by some interested party. I don't think that phasing out RPM is so critical as it appears. And since a lot of Add'ons currently rely on RPM, I think it's pretty unlikely that this Add'On would be just forgotten in time.

The TacFuelBalancer calls directly a static method from the ToolbarController_NS (one on the Utils). I realized that while mangling with my experimental forks. The easiest way out is to use the old method as a facade to whatever you are using now.

Yeah. I'm that old. And I'm that sleepy.

ANNOUNCE Release 2.4.3.1 is available for downloading, with the following changes: This is an emergencial Release due a Emergencial Release. Adding KSPe Light facilites: Logging Closing or reworking the following issues: #31 Preventing being ran over by other mods A misbehaviour on detecting the misbehaviour was fixed. #47 Count failed Sanity Checks as a potential problem. Warn user. #48 Backport the Heterodox Logging system into Orthodox (using KSPe.Light) #49 Check the Default patches for problems due wildcard! #50 Check the patches for currently supported Add'Ons ModuleGeneratorExtended Behaviour #51 Implement a Cancel button when Actions are given to MessageBox Yeah. Doing it right this time. #54 [ERR ***FATAL*** link provided in KSP.log links to 404 Typo maldito, typo maldito - tralálálálálálá #56 Breaking Parts patches #57 Implement Warning Dialogs Warnings about Overrules, parts that couldn’t be checked and parts with TweakScale support withdrawn. Doing it right this time! #58 Mk4 System Patch (addendum) See OP for the links. Highlights A new TWEAKSCALEBEHAVIOUR, ModuleGeneratorExtended , is available for parts using ModuleGenerator that wants to scale the INPUT_RESOURCES too. This feature wasn’t introduced directly into the ModuleGenerator’s TWEAKSCALEEXPONENTS to prevent damage on Add'Ons (and savegames) that rely on the current behaviour (scaling only the output), as suddenly the resource consumption would increase on already stablished bases and crafts. Just add the lines as the example below (the output resources scaling is still inherited from the default patch!). @PART[my_resource_converter]:NEEDS[TweakScale] { #@TWEAKSCALEBEHAVIOR[ModuleGeneratorExtended]/MODULE[TweakScale] { } %MODULE[TweakScale] { type = free } } WARNINGS The last detected Unholy interaction between modules (Kraken Food), when rogue patches apply twice the same property on a part, are still detected on the Sanity Checks and a (now) proper (scaring) warning is being shown. Unfortunately, this issue is a serious Show Stopper, potentially (and silently) ruining your savegames. This is not TweakScale fault, but yet it’s up to it to detect the problem and warn you about it. If this happens with you, call for help. Now a Cancel button is available for the brave Kerbonauts willing to fly unsafe. TweakScale strongly recommends using S.A.V.E.. Special procedures for recovering mangled installments once the TweakScale is installed (triggering the MM cache rebuilding) are possible, but keep your savegames backed up. And DON`T SAVE your crafts once you detect the problem. Reach me on Forum for help. TweakScale stills mangles further affected crafts and savegames with some badly (but recoverable) patched parts so when things are fixed, your crafts preserve the TweakScale settings without harm. THIS DOES NOT FIX THE PROBLEM, as this is beyond the reach of TweakScale - but it at least prevents you from losing your crafts and savegames once the problem happens and then is later fixed. As usual, this version still drops support in runtime for some problematic parts. Any savegame with such problematic parts scaled will have them descaled. This is not a really big problem as your game was going to crash sooner or later anyway - but if you plan to return to such savegame later when TweakScale will fully support that parts again, it’s better to backup your savegames! Keep an eye on the Known Issues file. — — — — — This Release will be published using the following Schedule: GitHub (reaching first manual installers and users of KSP-AVC): Right now. CurseForge: Right now. SpaceDock (and CKAN users): Right now. The reasoning is to gradually distribute the Release to easily monitor the deployment and cope with eventual mishaps.

This got through my timeline on FB. It's stuck on my head for hours already. (reminicenses of my infancy).

Nah. Nailed already. You use Munar Industries and MarkIV system. It's the same problem that hit @Critter79606. Do what follows: Replace the following TweakScale files: GameData/TweakScale/patches/B9_HX.cfg with this file. Click in "Raw" then download the artifact and replace the offending file with it. GameData/TweakScale/patches/MarkIVSystem_TweakScale.cfg with this one. Same thing. Replace the following Munar Industries file: GameData/MunarIndustries/MFTX_TweakScale.cfg with this one. Ditto. TweakScale 2.4.3.1 will be released this week, and it will have the B9 and MarkIV fixes implemented. Keep an eye on the Munar Industries for the next release. I had applied a pull request with the fix. But keep using S.A.V.E . Just in case.

Use S.A.V.E. just in the mean time. I'm working on it.

I don't think they plan to support 1.7.2, as 1.7.3 came a month later with a lot of fixes. And there's a release for 1.7.3

You need to download KSP again. Then plain delete that Add'On (and that one), and Squad and SquadExpansion. Copy that last two again from a fresh download. If you use Steam, you can delete that Squad* folders and then ask SteamClient to verify the installment. It will redownload the missing parts for you.