Lisias

Hi! You got bitten by a nasty KSP bug on a thingy Assembly Resolver yada yada yada. TL;DR. when something borks being loaded due a faulty dependence, everything else trying to load something (or to use a thingy called Reflection) borks relentlessly due the bug. And since TweakScale makes heavy and critical use of exactly these two things. TweakScale yells when it detects this happened (because a faulty TweakScale will ruin your whole savegame). Unfortunately, it's not TweakScale that it's getting more complicated to install. It's KSP that it's getting buggier. I need your full KSP.log in order to check who is triggering the problem. By fixing the 3rd party add'on that it's triggering this KSP bug, TweakScale will be able to run. Keep in mind that this bug doesn't affects only TweakScale - there's a lot of add'ons currently being victim of this problem - but since TweakScale is extremely sensitive to this problem, it's the one yelling when it happens. Same thing, dude! Send me your full KSP.log and I will check who is borking on us! Humm… This is new for me. Checking…. (hacking and slicing my poor KSP test beds) Nope, just checked the latest TweakScale with the latest KSP-Recall on the latest KSP, and I could not reproduce the problem. I tried with and without symmetries and mirror. Then I alt+clicked the part and attached it stacked on another. In all cases, the fuel settings were correctly scaled and kept. If you have a github account, may I suggest to create a new issue on https://github.com/net-lisias-ksp/TweakScale/issues ? It's way easier to exchange screenshots and KSP logs on github - but we can keep the research here if you prefer, it's not a problem. In a way or another, I will need your full KSP.log, ModuleManager's config cache, module manager's patch log and a simple craft with 2 or 3 parts with the problem happening. The ConfigCache will be found on GameData, together the ModuleManager.dll (just pack all the files, chances are that they might be useful). The Patch Log you will find it on KSP_ROOT/Logs/ModuleManager/* , ditto: pack the whole directory and call it a day Hummm... By saving the craft and reloading it, the problem goes away? And by launching the craft directly into the Launch Pad or Runway, the part is still screwed or it is launched with the correct values for the fuel? Not this one. Things are working fine on a minimal KSP installment. There's something else happening on the user's machine!

ANNOUNCE Release 7.0.1.0 is available for downloading, with the following changes: HLAirshipsCore goes gold! Officially licensed under the MIT (Expat) #HURRAY* See OP for the links. Notes Besides a new Icon, the Part's Menu Category is now correctly iconised too. When using an older (FULL) Release of HLAirships, after installing you need t9o remove the folders GameData/HLAirships/Parts/Aero/AirshipCap GameData/HLAirships/Parts/Aero/HL_AirshipEnvelope GameData/HLAirships/Parts/Aero/HL_AirshipEnvelope_Cirrus GameData/HLAirships/Parts/Aero/HL_AirshipEnvelope_Cirrus_Real GameData/HLAirships/Parts/Aero/HL_AirshipEnvelope_Dodec GameData/HLAirships/Parts/Aero/HL_AirshipEnvelope_Hecto GameData/HLAirships/Parts/Aero/HL_AirshipEnvelope_LudoBlimp GameData/HLAirships/Parts/Aero/HL_AirshipEnvelope_Octo GameData/HLAirships/Parts/Aero/HL_AirshipEnvelope_Ray GameData/HLAirships/Parts/Aero/HL_AirshipEnvelope_Una GameData/HLAirships/Parts/Aero/OMG Airship GameData/HLAirships/Parts/Aero/Probe Envelope GameData/HLAirships/Parts/TweakScale.cfg GameData/HLAirships/Plugins in order to use Core with the full set of HL Airships parts. When Core is installed together HLAirships (full), the Parts from the Core will be deactivated in favour of the full package (so the need to remove any older assets from it when using older releases). TweakScale support will not be affected. This is not a Release Candidate anymore. This is the real deal! — — — — — A hot fix was published, I didn't liked the final looking of the DeathStarBattery part and reworked it. — — — — — This Release will be published using the following Schedule: GitHub, reaching first manual installers and users of KSP-AVC. Right now. On SpaceDock. Right now.

There's this new Modus Operandi on KSP.log since a few months ago where the Exceptions I need to diagnose the problem appears to be filtered from KSP.log. MechJeb uses to invert some logging somehow, so when MechJeb is installed, the first Reflection Exception is not the culprit, as the real troublemaker somehow is logged some time later. There're some add'ons that some people like to use to show Exceptions on the screen instead of the log, and so when something bad happens, the KSP doesn't have anymore the information I need. But you are not using any of the ones I know BDArmory used to cause some trouble in the past (some mishap on one of the dependencies), but it used to log a hint on KSP.log about, and there's none on yours. So we have no choice but going Combinatorial Analysis. Remove the following add'ons from your rig and see if the problem goes away: B9AnimationModules v1.6.0.0 / vv1.6.0 B9PartSwitch v2.18.0.0 / vv2.18.0 B9-PWings-Fork v0.43.0.10 BahaTurret v1.0.0.0 BDArmory.Core v1.3.4.0 BDArmory v1.3.5.0 I have absolutely no evidence on the KSP.log that they could be misbehaving, but these ones already triggered this problem in the past, so it's a good bet to start with them. If the problem vanishes, we found where the problem is. So, install back them one by one until the problem happens again. The last one installed will be culprit, and then you will need to reach the maintainer for further help. Keep in mind that your KSP.log is littered with exceptions, TweakScale is only the one complaining about: [LOG 18:17:25.316] Load(Texture): BDArmory/Parts/ABL/texture [EXC 18:17:25.321] TypeLoadException: Failure has occurred while loading a type. UnityEngine.DebugLogHandler:LogException(Exception, Object) ModuleManager.UnityLogHandle.InterceptLogHandler:LogException(Exception, Object) UnityEngine.Debug:CallOverridenDebugHandler(Exception, Object) [EXC 18:17:25.322] TypeLoadException: Failure has occurred while loading a type. UnityEngine.DebugLogHandler:LogException(Exception, Object) ModuleManager.UnityLogHandle.InterceptLogHandler:LogException(Exception, Object) UnityEngine.Debug:CallOverridenDebugHandler(Exception, Object) [EXC 18:17:25.329] TypeLoadException: Failure has occurred while loading a type. UnityEngine.DebugLogHandler:LogException(Exception, Object) ModuleManager.UnityLogHandle.InterceptLogHandler:LogException(Exception, Object) UnityEngine.Debug:CallOverridenDebugHandler(Exception, Object) [EXC 18:17:25.330] TypeLoadException: Failure has occurred while loading a type. UnityEngine.DebugLogHandler:LogException(Exception, Object) ModuleManager.UnityLogHandle.InterceptLogHandler:LogException(Exception, Object) UnityEngine.Debug:CallOverridenDebugHandler(Exception, Object) [EXC 18:17:25.337] TypeLoadException: Failure has occurred while loading a type. UnityEngine.DebugLogHandler:LogException(Exception, Object) ModuleManager.UnityLogHandle.InterceptLogHandler:LogException(Exception, Object) UnityEngine.Debug:CallOverridenDebugHandler(Exception, Object) So you really need to solve this problem in order to have a stable KSP to play.

The "free everything forever" is a problem only because KSP failed on expanding the userbase beyound the initial sell, as it appears. IMHO opinion, they failed on expanding the userbase beyound the inicial early adopters exactly due the lack of compromise on fixing bugs at first place. It worths to mention that is more or less consensus that KSP 1.3.1 was functional and good enough, what implies that KSP started to go downhills on KSP 1.4.0 and after - KSP 1.4.0 was a huge change, they migrated from Unity 5 to Unity 2017 and a lot of things had to be rewritten. This rewrite appears to be the the beginning of the race to the bottom. So, nope. The "free forever policy" is not the source of the problems here. It's the symptom.

Dude, you were bitten by a nasty KSP bug on a thingy called Loader/Resolver yada yada yada . TL;DR. when something borks being loaded due a faulty dependence, everything else trying to load something (or to use a thingy called Reflection) borks relentlessly due the bug. And since TweakScale makes heavy and critical use of exactly these two things. TweakScale yells when it detects this happened (because a faulty TweakScale will ruin your whole savegame). Usually the first Reflection Exception pinpoints the unlucky DLL that stepped on that landmine, but your LOG is weird: [LOG 18:17:06.117] [TitleNotAvailable] Version B9-PWings-Fork, Version=0.43.0.10, Culture=neutral, PublicKeyToken=null [EXC 18:17:06.124] FileNotFoundException: Could not load file or assembly 'KSPUtil, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. UnityEngine.DebugLogHandler:LogException(Exception, Object) ModuleManager.UnityLogHandle.InterceptLogHandler:LogException(Exception, Object) UnityEngine.Debug:CallOverridenDebugHandler(Exception, Object) KSPUtil is a internal KSP Assembly, it's always there. So somehow we have this new way of triggering the problem. On a pretty wild guess, remove B9-Wings-Fork and restart KSP to see if the problem goes away.

Work for free it's absolutely misleading. I DO NOT work for free. I work for myself. It only happens that once the work is done, I don't mind other people using it too - since it's essentially cost free for me and not rarely users help me on finding bugs on the code that once fixed will benefit me too. I do not blindly hunt bugs on the Internet to be fixed. I do what I can to fix KSP bugs because I WANNA PLAY THE GAME I BOUGHT, and if the only way of doing it is to fix myself the damned thing, so be it.

Hi! I think you sent me the wrong link. DropBox has an option somewhere to generate a link for downloading. This one you sent appears to be the one you use to managed the content, and it's available only to you.

A chariot race. But with motorcycles... (any roman around?)

Well… It mostly is, see the quantity of fixes on the most different mods needed to fix them. And yes, you can fix 10 years old codebase. See the mentioned mods. I do software for living. I have fixed or updated code older than KSP, as well I wrote some new ones that.. geez.. I'm not willing to put them on my Resume. It happens, we do a living writing a mix of excellently written code with others that, frankly, I would like to forget I ever wrote it. It's the end result that matters - you would be surprised about the crapness of some code that are pretty lucrative on this industry. You may have a point by arguing that it would not be lucrative to have KSP1 fixed - and perhaps you are right. But, by then, so it's @steve_v.

It's easier than you think. Open your KSP folder, look for the folder called 'save Inside 'save' Look for a folder with the name of the savegame you are running. Inside this folder there's a file named 'persistentsfs'. BACKUP IT. (Do a ctrl-c followed by a ctrl-v). Now open the persistent.sfs file using notepad.exe or, better, notepad++. Do a find using the name of the kerbals you want to remove. You will find something like this: KERBAL { name = <Something> Kerman gender = Male type = Crew trait = Pilot brave = 0.5 dumb = 0.5 badS = False veteran = False tour = False state = Available inactive = False inactiveTimeEnd = 0 gExperienced = 0 outDueToG = False ToD = 0 idx = -1 extraXP = 0 hasHelmetOn = False hasNeckRingOn = False hasVisorDown = False lightR = 1 lightG = 0.5176 lightB = 0 completedFirstEVA = False suit = Default hero = False CAREER_LOG { flight = 0 } FLIGHT_LOG { flight = 0 } } Now you can edit the gender directly (male to female or viceversa) or you can delete everything - the KERBAL string and all lines from the fist "{" until the respective "}" (note that they are always in pairs with stuff inside). Be carefull to do not delete to much or too few, the savegame is sensitive to these brackets and will fail lo load if you make a mistake - since the absolute need to have a backup (even me screw up something now and then). Cheers!

ANNOUNCE Release 2.4.6.13 is available for downloading, with the following changes: Fixes a nasty bug about scaling down crewed parts, reported by robi_243 on Forum. Thanks, dude!! Closes Issues: #247 Scaling down a crewed part makes the crew go M.I.A. and the crew capacity is not restored later! See OP for the links. Our fellow Kerbonaut @Robi_243 detected a potentially nasty problem on TweakScale and thankfully reported it, so I could fix it! Thanks, dude! Disclaimer By last, but not the least... — — — — — 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. (All your Distribution Channels are belong to us! - Updating everything almost at once this time)

He did! He purchased the thing at first place. He was one of the very first early adopters. I think he had appreciated it exactly at that times in which it was a tiny project made by a teenager. What's not exactly what KSP is now, after 10 years - and yet, it's not a finished product neither. I will save you from the long and tedious sequence of absolute and unbelievable mishaps KSP is littered with (ping me in PVT if you are interested). Anyway, his argument is "I will not do it again", and not "I advocate that no one do it". And I totally see his point, there's life happening out there, he prefers to live it instead of eternally handling KSP, DRM and a lot more of the crapness that litters the game industry nowadays. — — MY TURN — — 1: After I see reviews from people I trust and I like what they say. Or having a downloadable demo for my own evaluation of the mechanics and the behaviour of the game (now that I know where and what to look). 2: Inflation and current exchange makes 60USD** about 25 to 30% of the minimum wage where I live. Not cheap, I expect a lot less KSP players on Brazil unless some aggressive discount prices are applied. And I miss playing a game with people that talks the same language as me. 3: Not on this life. — — POST EDIT — — For the sake of comparison, 60USD is almost twice the price MS is asking for Windows 11 Professional around here (and you can pay in 3 installments without interest). Source (google translator)

The Demo I downloaded from Steam was very good. I played on it the whole holidays in 2017 before deciding to buy the thing next year! (limited, but functional)

The best KSP videos were made on the "worst" KSP versions!!

WAIT! I got curious and tried to find a way to reproduce the issue. And I found it!! If you downscale a Mark 1 Cockpit two notches, two things happens: If the part is crewed, the Kerbals go M.I.A.!!!! Once you scale back the part, the crew capacity is not restored!! I'm absolutely sure I had tested the Item 2 when I first released this feature - but don't remember if I had tested the item 1. In a way or another, I have to work on this: https://github.com/net-lisias-ksp/TweakScale/issues/247 As a workaround for the problem 2, remove the part and attach a new one from the Palette. There's no workaround for the problem 1, however. I will see what I can do on this weekend. — — POST EDIT — — Loading and saving the Craft is also an workaround for the problem 1. — — POST POST EDIT — — It is fixed! Thanks for the report!

Had you scaled up or down? If the part has only one crew position, and you scale it down, then there will be no space left for a Kerbal.

That would completely destroy the market. Nope. It will shakedown the Industry - the market will still be there. See Doom, Quake et all. That said, a compromise may be possible: most of the KSP is CIL anyway, what we need in reality are really portable runtimes - see ScumVM, Zork VM and etc. To tell you the true, at least Quake1 "applications" are also wrote in a VM, something called QuakeC IIRC. Distributing precompiled platform independent blobs that could be cross-linked locally to a platform specific runtime is feasible - to tell you the true, it's essentially what KSP1 is nowadays (apart from the C++ specific code). My DLLs runs on Mac, Linux and Windows without hassle. Well, almost In a few years, RISC-V machines will hit the market (or, at least, it's my bet). Way more versatile than ARM, probably cheaper and hopefully more efficient and perhaps even faster. Being able to play KSP1 or even KSP2 would not be a bad idea at all, it potentially can expand the audience for these games significantly (to tell you the true, ARM devices nowadays are reaching the point of being able to run KSP1! ) on markets that are progressively pushing away x86 and ARM. And, boy, these are some really big markets...

Hi! You was bitten by a nasty KSP bug on a thingy called Assembly Loader/Resolver yada yada yada . TL;DR. when something borks being loaded due a faulty dependence, everything else trying to load something (or to use a thingy called Reflection) borks relentlessly due the bug. And since TweakScale makes heavy and critical use of exactly these two things. TweakScale yells when it detects this happened (because a faulty TweakScale will ruin your whole savegame). The only way out of the mess is to diagnose and fix the real cause of the problem (as TweakScale is only the splash damage). Publish your full KSP.log here using dropbox or something, and I will give it a look - further instructions about how to do it can be found on this link.

A protective (and absolutely non critical) piece of the Boeing Starliner fell from the capsule while transportation. Really not serious. But it looked so terribly Kerbal...

Well, I build a table with all textures from 1.6.1 and 1.12.3 with the respective sizes and compared. For the UNIX freaks, the following command line does the trick for one GameData: find . -name "*.dds" -exec identify {} \; | sed -nr "s/^(.+) DDS ([0123456789x]+) .*$/\2 \1/p" These are the conclusions at this moment: 618 textures didn't changed size!! 40 textures from 1.12.3 are "easy picks". They are direct related to lower resolution textures from 1.6.1 and will be just downgraded to the "original" resolution. 278 textures are shining new, and I will need to manually eye ball the respective parts on 1.6.1 (when revamps) or compare with some other similar 1.6.1 part to decide the new resolution. I really didn't understood why some textures are 4096x4096 (~22MB on disk!), as the Normal for the WeatherStation from Serenity... Spread sheet on Google Drive. See Sheet 4. The zDeprecated ones were not included on the main analysis, but they are available o the Sheet 5 - interesting enough, or I made a mistake somewhere, or some deprecated textures were downgraded on KSP 1.12.3… I will not copy & paste the data this time, as the sheet got almost 1200 lines and this will clog Forum.

Interesting fact... Find by accident this report of mine, probably the first time I got one of the glitches fixed by Core!

It's a "Contract" interface between TweakScale and Modules willing to handle the scaling themselves instead of using a Scale Exponent. It's the same for years, and in the event I need to update the Interface, the current Interface will be still there to keep backwards compatibility. Having multiple DLLs with the same feature was never a good idea - it was not on Windows on the "good old times", it's not nowadays. But since we don't have on this landscape a mechanism to safely maintain shared libraries, I had to keep a copy of the Scale_Redist directly on GameData to be absolutely sure this copy will be the first KSP will load and use - from 1.8.0 to nowadays, all the other copies are short-circuited to the first one! This can make things extremely nasty to diagnose if someone shoves a changed Interface on the system - since the need to be the first to be loaded. In a way or another, I removed the Scale_Redist.dll from IR for the tests (MM Watch Dog barked on me, as it is keeping a look on these duplicates for me nowadays). Yep, I almost didn't test it, because I was pretty sure 3.0.6 would be the troublemaker - but, as we can see… I also gave a peek on the commits, and found nothing obvious on them. It may be something subtle that changed the order of some event. Gladly it's only 3 commits, so worst case will be 3 compilations tests max to see where things broke. The first one to be loaded is always the one that ends up being used by everybody - being the reason I put it on the GameData the way I did. All the duplicates will be short-circuited as they were loaded from this first one. So, definitively, this is not the problem - and since MM Watch Dog barks on me every time it finds a duplicate, I removed it anyway before testing. Big time!!!

Yep, Known issue, and theoretically fixed too on KSP-Recall. Just to be sure, if you launch the affected vessel directly into Launch Pad or Runway, the problem manifests itself or not? If by launching the thing into LP or Runway the problem happens, then it's a new thingy and I need to investigate. Otherwise, it's the old bug from KSP 1.9.0's Editor bitting your SAS and it should not had happening because KSP-Recall should had been able to work around the Editor's bug, preventing TweakScale from borking on bugs data... I'm betting on that KSP >= 1.9.0 Editor bug, but I'm on it to be sure. — — POST EDIT — — Interestingly, I used IR 3.0.1 (the latest one to run on 1.7.3) on KSP 1.9.1, and I could not reproduce the behaviour besides doing exactly what the video shows. Of course, Recall and TweakScale are up to date. So I tried IR 3.0.1 on KSP 1.12.3, and it worked perfectly too. OUKEY. Recall and TweakScale were cleared from the problem. Now we need to find who is the real troublemaker. @Youen is more than probably using the latest IR, 3.0.7, so I'm trying it on the same KSP 1.9.1 test bed I cleared our IR 3.0.1. On KSP 1.9.1, IR 3.0.7 borked with this exception So I moved directly into 1.12.3 with IR 3.0.7. AND YES, the problem was reproduced. So, to be absolutely sure, I reverted back to IR 3.0.1 and redid the test. Unsurprisingly, it worked fine again. So I conclude it's a bug on IR 3.0.7 , probably introduced on IR 3.0.6 - it was a huge change set… No!! IR 3.0.6 works fine too!!! — — — @Youen, I suggest you downgrade to 3.0.6 if possible until @Rudolf Meier can check and fix this! Cheers!

The Module Manager Watch Dog "is my fault" Due some ways things changed on KSP and didn't coped too well on how things were done in the past about Module Manager, I had to code this thing in order to prevent the bad situations that could screw you. As a beneficial side effect, it also detects some users (or installers) mishaps as you just detected. However... It's only distributed on KSP-Recall and TweakScale, as these ones are the most common victims of that bad coping I mentioned above. So I'm concluding that at least one of these two was installed on your install fest. There's nothing wrong on Curseforge installer, as long you use only zip packages tailored to be used by it - all my add'ons are distributed with two zip packages, one of them ending with "-Curseforge" exactly due that - these last ones are Curse Installer friendly. Using Curse Installer to install any of my packages that does not ends with "-Curseforge" may lead to this problem.

Announce! TweakScale Companion for KIS 1.0.0.2 is on the wild. Fixes a NRE that was happening due the new TweakScale’s Upgrade Pipeline. Closes issues: #5 NRE when TweakScale dispatches OnRescale after upgrading a Scale Type that was changed on some patch ALL USERS OF TSC-KIS are advised to update ASAP. Download here or in the OP.