Lisias Posted February 9, 2021 Author Share Posted February 9, 2021 23 hours ago, viperwolf said: The wheels I use are scaled down a bit, so that may be it. Ill get a short video and the file for you soon. Ill also test out regular size and things like that before hand. I zeroed in on the problem, and it's not TweakScale code - it's something on the collider in the Mesh. On the 1.0 scale, that difference is negligible - but as we scale up or down, that collider starts to show differences - be it allowing the wheel to "sink" on the ground, be it making the wheel "float" over it. In a way or another, however, I had no translation drifting on the scaled wheels, besides still having some pretty small angular drifting - check the images below and note the MET between them. Spoiler So you have something more on your rig. There are some exceptions on your KSP.log? If not, the only thing remaining to be checked are the Meshes you are using on your installment. On 2/8/2021 at 7:14 AM, viperwolf said: Thank you for your time and where is your donate page? Holly Krap, I completely forgot about it! I had opened an account on Patreon to be used when TweakScale 2.4.4.0 and some Compantions would had gone gold, but I completely forgot about it! #facePalm. I'm adding my patreon link to my github repos where appropriated, updated the pages on SpaceDock and I will update the Forum pages as time allows. Thanks! 5 hours ago, Qyst said: Glad to hear you managed to fix it and it's good to know it's safe to use. Thanks for your hard work on this really useful mod! Welcome! I had planned to publish new versions for KSP Recall and TweakScale yesterday night, but RL happened. I will try again this night. Cheers! Quote Link to comment Share on other sites More sharing options...
viperwolf Posted February 9, 2021 Share Posted February 9, 2021 12 hours ago, Lisias said: Reveal hidden contents So you have something more on your rig. There are some exceptions on your KSP.log? If not, the only thing remaining to be checked are the Meshes you are using on your installment. Holly Krap, I completely forgot about it! I had opened an account on Patreon to be used when TweakScale 2.4.4.0 and some Compantions would had gone gold, but I completely forgot about it! #facePalm. I'm adding my patreon link to my github repos where appropriated, updated the pages on SpaceDock and I will update the Forum pages as time allows. Thanks! Ill go ahead get the video,logs, and craft file. I do have restock. On a side note, I hate asking, but do you have a paypal? Im not signed up to patreon. Quote Link to comment Share on other sites More sharing options...
Lisias Posted February 11, 2021 Author Share Posted February 11, 2021 (edited) News from the Front I was finishing the next release of TweakScale when I was caught with my pants down due the following: One fix for a problem ended up breaking another use case, and thanks Kraken I noticed it before the release. Working on it I'm resurrecting some very interesting TweakScale features from the 1.3.1 era, but just realised that some KSP API calls are not working or are just short circuited to return NUL and now I need to reimplement the Kraken damned thing in order to carry on the task I think I got a tendinitis on my right arm, and I will need to avoid keyboards, mouses and joysticks for some days Well, Kerbal proposes, Kraken disposes. C'est la vie. In the mean time: @Qyst, I made a hot fix for you. The fix for your problem was already ready, but with the problems I described above, I decided to hot fix 2.4.4.5 instead of a new release. Download the hotfix and replace the KSPe.Light.TweakScale.dll with the one from the hotfix's zipfile https://github.com/net-lisias-ksp/TweakScale/releases/tag/RELEASE%2F2.4.4.5 Let me know if it works for you @viperwolf, there's something cheesy going on, paypal.me ceased to work (it's plain vanished for me!), and there's no way anymore to provide you with a link. In a way or another, my paypal account for this is {funding at lisias dot net}. Cheers. Edited February 14, 2021 by Lisias Writing on foreign languages in a hurry never ends well.... Quote Link to comment Share on other sites More sharing options...
Lisias Posted February 12, 2021 Author Share Posted February 12, 2021 (edited) Announce! Warning!!!Lasciate ogne speranza, voi ch'intrate I just released 2.5.0.30 **BETA** for the brave Kerbonauts willing to risk theirs SAS... for Science TweakScale! This last beta catches up with the mainstream up to 2.4.4.5, and ressurrects a long gone TweakScale feature!!!! #HURRAY!! The new old kid on the block is Auto Scale, and it works as follows: 1 - Make sure AutoScale is enable hitting CONTROL-L: 2- Attach parts and note how they are automatically scaled for you!! 3 - And again!!! 4 - And AGAIN!!!!! Uhhh... Whoops This codebase is the current bleeding hedge, what include some bugs on the symmetries when using Variants. Please use it only on disposable savegames, and I really meant it this time. Reports about where else the AutoScale is borking are highly appreciated, my tendinitis is preventing me to play too much KSP these days. I need to build a knowledge base with the cases where the Auto Scale borks so I can handle them on the code! Please report any problems with this Feature in Test on https://github.com/net-lisias-ksp/TweakScale/issues/166 Good Luck! Edited June 19, 2021 by Lisias Of cuorse, tyops! Quote Link to comment Share on other sites More sharing options...
Qyst Posted February 13, 2021 Share Posted February 13, 2021 On 2/11/2021 at 6:10 AM, Lisias said: News from the Front I was finishing the next release of TweakScale when I was caught with my pants down due the following: One fix for a problem ended up breaking another use case, and thanks Kraken I noticed it before the release. Working on it I'm resurrecting some very interesting TweakScale features from the 1.3.1 era, but just realised that some KSP API calls are not working or are just short circuited to return NUL and now I need to reimplement the Kraken damned thing in order to carry on the task I think I got a tendinitis on my right arm, and I will need to avoid keyboards, mouses and joysticks for some days Well, Kerbal proposes, Kraken disposes. C'est la vie. In the mean time: @Qyst, I made a hot fix for you. The fix for your problem was already ready, but with the problems I described above, I decided to hot fix 2.4.4.5 instead of a new release. Download the hotfix and replace the KSPe.Light.TweakScale.dll with the one from the hotfix's zipfile https://github.com/net-lisias-ksp/TweakScale/releases/tag/RELEASE%2F2.4.4.5 Let me know if it works for you @viperwolf, there's something cheesy going on, paypal.me ceased to work (it's plain vanished for me!), and there's no way anymore to provide you with a link. In a way or another, my paypal account for this is {me at lisias dot net}. Cheers. Really sorry for the delay! This does not fix the problem. I'll attach the new player.log file just in case there's valuable data in there that hints at some change, but on the user end it seems to be the same. I double-checked (more like quintuple because I'm paranoid) that the new dll was installed properly and it does show as v2.2.2.3 in the logfile: https://www.dropbox.com/s/qwxj1ltf6dpcw43/BugReport-Tweakscale-2-4-4-5-HotFix-Player.log?dl=0 In any case, take care of your tendinitis first! Quote Link to comment Share on other sites More sharing options...
Lisias Posted February 13, 2021 Author Share Posted February 13, 2021 (edited) On 2/13/2021 at 1:07 AM, Qyst said: Really sorry for the delay! This does not fix the problem. I'll attach the new player.log file just in case there's valuable data in there that hints at some change, but on the user end it seems to be the same. I double-checked (more like quintuple because I'm paranoid) that the new dll was installed properly and it does show as v2.2.2.3 in the logfile: https://www.dropbox.com/s/qwxj1ltf6dpcw43/BugReport-Tweakscale-2-4-4-5-HotFix-Player.log?dl=0 In any case, take care of your tendinitis first! I will need to compile a debug version for you, and I will need your KSP.log using it. I suspect something different is happening on mount points - or perhaps something is missing on your Manjaro distribution. Since using the mouse with the left hand is not a problem , I compiled a 2.2.2.3 DEBUG release for you. https://github.com/net-lisias-ksp/TweakScale/releases/tag/RELEASE%2F2.4.4.5 Please install it over the current KSPe.Light.TweakScale, then fire up the thing. Once the problem happens, you can quit KSP, then send me your KSP.log and Player.log (Player.log doesn't have what I need) and restore the previous DLL, as this DEBUG stunt will shove pornographic amounts of log entries on the KSP.log, and this may hinder the game on the long run. On 2/11/2021 at 6:10 AM, Lisias said: @viperwolf, there's something cheesy going on, paypal.me ceased to work (it's plain vanished for me!), and there's no way anymore to provide you with a link. In a way or another, my paypal account for this is {funding at lisias dot net}. Found my way on the mess Paypal is nowadays. For some reason, Paypal choose to do not provide PayPal.me for Brazil, and I lost this option somewhere in the past when I had to migrate my account to Brazil due fiscal reasons. Not sure if I ever had, though - I never had the need before. However, there's a similar feature called Donation Buttons, and I finally found my way on how to use it. Use this link for such. I will update everything and the kitchen's sink as time allows with this new link. Edited February 14, 2021 by Lisias updating links and contacts Quote Link to comment Share on other sites More sharing options...
Qyst Posted February 13, 2021 Share Posted February 13, 2021 11 hours ago, Lisias said: I will need to compile a debug version for you, and I will need your KSP.log using it. I suspect something different is happening on mount points - or perhaps something is missing on your Manjaro distribution. Since using the mouse with the left hand is not a problem , I compiled a 2.2.2.3 DEBUG release for you. https://github.com/net-lisias-ksp/TweakScale/releases/tag/RELEASE%2F2.4.4.5 Please install it over the current KSPe.Light.TweakScale, then fire up the thing. Once the problem happens, you can quit KSP, then send me your KSP.log and Player.log (Player.log doesn't have what I need) and restore the previous DLL, as this DEBUG stunt will shove pornographic amounts of log entries on the KSP.log, and this may hinder the game on the long run. Okay so, I serendipitously found out that this problem is likely not from your mod, but indirectly and at least partly caused/exposed by the Linux file manager I use (Nemo). I was able to find the problem partly because of the extra information in the logs from your debug .dll, and partly because while testing different things, I found that in some circumstances the bug did not manifest. Some context: I have several KSP installations that I use for different purposes. Two left over from 1.9.1 for testing and safekeeping purposes (I'm trying to build a scenario/gamemode), and three 1.11.1: one is an untouched fresh install that I copy whenever I need to bug-hunt, another has all the mods I use, and a third one that has a reduced subset of mods for when I want to test things like MM patches without having to go through repeated 15-minute game loads. I keep them each inside its own folder, and all inside a bigger folder. The entire thing looks like this: Spoiler You'll notice that my file manager has an integrated tree-style thing going on. That means I can open folders and then open files from inside those folders without having to actually navigate into them. I use this all the time. That's what's causing the problem. When I launch the KSP executable nested inside several open folders like that, its working directory is not the directory the actual file is placed in, but the directory that is currently open in the file manager. In the screenshot's case, that is the folder where I keep all my KSP installs. I found out because your debug library put this in my KSP.log file: Spoiler [LOG 17:54:00.378] [AddonLoader]: Instantiating addon 'ModuleManager' from assembly 'ModuleManager' [LOG 17:54:00.395] [ModuleManager] Adding post patch to the loading screen 4 [LOG 17:54:00.398] [ModuleManager] Patching started on a new thread, all output will be directed to /mnt/LinuxData/KSP/KSP1-11-1-BUGTEST/game/KSP_Data/../Logs/ModuleManager/ModuleManager.log [LOG 17:54:00.401] [AddonLoader]: Instantiating addon 'Startup' from assembly 'KSPe.Light.TweakScale' [LOG 17:54:00.402] [AddonLoader]: Instantiating addon 'TweakScaleRegister' from assembly 'Scale' [LOG 17:54:00.403] [AddonLoader]: Instantiating addon 'Startup' from assembly 'Scale' [LOG 17:54:00.403] [AddonLoader]: Instantiating addon 'ModuleManagerListener' from assembly 'Scale' [LOG 17:54:01.257] Load(Audio): Squad/Sounds/editorLoop01 [LOG 17:54:01.295] [KSPe.Light.TweakScale] Version 2.2.2.3 /L DEBUG [LOG 17:54:01.365] [KSPe] KSPe.cfg does not exists. Using defaults. [LOG 17:54:01.366] [TweakScale] Version 2.4.4.5 /L [LOG 17:54:01.367] KSPe.Util.UnityTools: KSPe.Util.UnityTools: 2019.2.2f1 [LOG 17:54:01.371] [KSPe.IO.Path] Calculating Origin for /mnt/LinuxData/KSP/KSP1-11-1-BUGTEST/game/KSP_Data/Managed/Assembly-CSharp.dll [LOG 17:54:01.372] [KSPe.IO.Path] Normalized path /mnt/LinuxData/KSP/KSP1-11-1-BUGTEST/game/ [LOG 17:54:01.372] [KSPe.IO.Path.process_dir] path is /mnt/LinuxData/KSP/KSP1-11-1-BUGTEST/game/ [LOG 17:54:01.372] [KSPe.IO.Path.process_dir] dir is /mnt/LinuxData/KSP/ <------ !!!!!!! This causes several issues and strangenesses; for example, the KSP.log file is placed in the root folder and not the game folder (I found that weird before but wasn't able to realize what the cause was). It also messes with specific mods. Tweakscale and Recall are two of them, but I've seen others have issues with the places they save their files to: BOSS, ResearchBodies, and TooManyOrbits specifically. There might be silent issues with other mods too. Everything works fine if I open the game's folder normally and then run the executable inside it, or otherwise pass the proper working directory. I have no idea what I should do with this, besides making sure to run the executable in a way that it gets its proper working directory from now on. Is this still an actionable bug or should we blame the file manager and move on? Do you still want those logs? Should I report this in those other mods I mentioned? Should I report this to my file manager's devs? Quote Link to comment Share on other sites More sharing options...
Lisias Posted February 13, 2021 Author Share Posted February 13, 2021 (edited) On 2/13/2021 at 6:14 PM, Qyst said: Okay so, I serendipitously found out that this problem is likely not from your mod, but indirectly and at least partly caused/exposed by the Linux file manager I use (Nemo). I was able to find the problem partly because of the extra information in the logs from your debug .dll, and partly because while testing different things, I found that in some circumstances the bug did not manifest. Now I'm worried. I can cope with deterministic disasters, but inconsistent bugs really scares me... On 2/13/2021 at 6:14 PM, Qyst said: Some context: I have several KSP installations that I use for different purposes. Two left over from 1.9.1 for testing and safekeeping purposes (I'm trying to build a scenario/gamemode), and three 1.11.1: one is an untouched fresh install that I copy whenever I need to bug-hunt, another has all the mods I use, and a third one that has a reduced subset of mods for when I want to test things like MM patches without having to go through repeated 15-minute game loads. I keep them each inside its own folder, and all inside a bigger folder. <cut by me> You'll notice that my file manager has an integrated tree-style thing going on. That means I can open folders and then open files from inside those folders without having to actually navigate into them. I use this all the time. I'm so used to Midnight Commander that I barely touch the Finder nowadays... On 2/13/2021 at 6:14 PM, Qyst said: This causes several issues and strangenesses; for example, the KSP.log file is placed in the root folder and not the game folder (I found that weird before but wasn't able to realize what the cause was). It also messes with specific mods. Tweakscale and Recall are two of them, but I've seen others have issues with the places they save their files to: BOSS, ResearchBodies, and TooManyOrbits specifically. There might be silent issues with other mods too. Everything works fine if I open the game's folder normally and then run the executable inside it, or otherwise pass the proper working directory. UGH!!! You know, the whole idea of the KSPe's abstract file system is exactly to work around these weirdness.... You ask KSPe "save this file on the USER LOCAL DATA", and whatever this folder is, it will be used for saving and loading. This aims to be a real abstract file system (something like Eclipse does on the IDE), not the half baked solution Unity tries to provide.... I have a hypothesis for what's happening, more later.... On 2/13/2021 at 6:14 PM, Qyst said: That's what's causing the problem. When I launch the KSP executable nested inside several open folders like that, its working directory is not the directory the actual file is placed in, but the directory that is currently open in the file manager. In the screenshot's case, that is the folder where I keep all my KSP installs. I found out because your debug library put this in my KSP.log file: Hide contents <cut> [LOG 17:54:01.371] [KSPe.IO.Path] Calculating Origin for /mnt/LinuxData/KSP/KSP1-11-1-BUGTEST/game/KSP_Data/Managed/Assembly-CSharp.dll [LOG 17:54:01.372] [KSPe.IO.Path] Normalized path /mnt/LinuxData/KSP/KSP1-11-1-BUGTEST/game/ [LOG 17:54:01.372] [KSPe.IO.Path.process_dir] path is /mnt/LinuxData/KSP/KSP1-11-1-BUGTEST/game/ [LOG 17:54:01.372] [KSPe.IO.Path.process_dir] dir is /mnt/LinuxData/KSP/ <------ !!!!!!! Yep, you found the problem! This is mine: [LOG 04:31:13.728] [KSPe.IO.Path] Calculating Origin for /.users/lisias/Workspaces/KSP/runtime/1.11.1/KSP.app/Contents/Resources/Data/Managed/Assembly-CSharp.dll [LOG 04:31:13.728] [KSPe.IO.Path] Normalized path /.users/lisias/Workspaces/KSP/runtime/1.11.1/ [LOG 04:31:14.009] [KSPe.IO.Path.process_dir] path is /.users/lisias/Workspaces/KSP/runtime/1.11.1/ [LOG 04:31:14.009] [KSPe.IO.Path.process_dir] dir is /.users/lisias/Workspaces/KSP/runtime/1.11.1/GameData [LOG 04:31:14.015] [KSPe.Multiplatform.FileSystem] realpath found on NOT FOUND! [LOG 04:31:14.015] [KSPe.Multiplatform.FileSystem] readlink found on /usr/bin/readlink On 2/13/2021 at 6:14 PM, Qyst said: This causes several issues and strangenesses; for example, the KSP.log file is placed in the root folder and not the game folder (I found that weird before but wasn't able to realize what the cause was). It also messes with specific mods. Tweakscale and Recall are two of them, but I've seen others have issues with the places they save their files to: BOSS, ResearchBodies, and TooManyOrbits specifically. There might be silent issues with other mods too. Everything works fine if I open the game's folder normally and then run the executable inside it, or otherwise pass the proper working directory. I have no idea what I should do with this, besides making sure to run the executable in a way that it gets its proper working directory from now on. Is this still an actionable bug or should we blame the file manager and move on? Do you still want those logs? Should I report this in those other mods I mentioned? Should I report this to my file manager's devs? (sigh). I know what's happening. (sigh) When you launch the KSP binary, the current directory IS NOT BEING SET CORRECTLY, and something that handles directories somewhere just gets lost on the problem. Since this is affecting both KSP and KSPe, that piece of... hummm... "code".... must be from Microsoft, as I derive the root path from the running Assembly-CSharp.dll what should be a full pathname - and then everything goes kaput for a reason still to be detected. Yes, I want the full KSP.log so I can fully compare it with mine and try to figure out exactly why this is borking this way. At a first glance, yes, it appears to be a problem on the File Manager - but it may be also Microsoft being Microsoft. Let me analyse your KSP.log so I can be sure. Perhaps it's something I can work around on KSPe - unfortunately, the Software Industry nowadays thinks that users are nothing but a resource to be exploited for money or for pleasing him/herself, and breaking standards and expected behaviours are acceptable if these saves the guy/gal even a bit of work... Edited February 15, 2021 by Lisias Not exactly related rant obfuscated. :) Quote Link to comment Share on other sites More sharing options...
Qyst Posted February 14, 2021 Share Posted February 14, 2021 2 hours ago, Lisias said: (sigh). I know what's happening. (sigh) When you launch the KSP binary, the current directory IS NOT BEING SET CORRECTLY, and something that handles directories somewhere just gets lost on the problem. Since this is affecting both KSP and KSPe, that piece of... hummm... "code".... must be from Microsoft, as I derive the root path from the running Assembly-CSharp.dll what should be a full pathname - and then everything goes kaput for a reason still to be detected. Yes, I want the full KSP.log so I can fully compare it with mine and try to figure out exactly why this is borking this way. At a first glance, yes, it appears to be a problem on the File Manager - but it may be also Microsoft being Microsoft. Let me analyse your KSP.log so I can be sure. Perhaps it's something I can work around on KSPe - unfortunately, the Software Industry nowadays thinks that users are nothing but a resource to be exploited for money or for pleasing him/herself, and breaking standards and expected behaviours are acceptable if these saves the guy/gal even a bit of work... Here they are: Bugged player.log: https://www.dropbox.com/s/x29sr6lo6r4o8kp/BugReport-TweakScale-2-4-4-5-DEBUG-Player.log?dl=0 Bugged KSP.log: https://www.dropbox.com/s/g6cqvsnx0wfsg5m/BugReport-TweakScale-2-4-4-5-DEBUG-KSP.log?dl=0 And just in case, the logs for when it's run with the working directory set correctly: Player.log: https://www.dropbox.com/s/zjiwhm3y6g3fhzr/OKReport-TweakScale-2-4-4-5-DEBUG-player.log?dl=0 KSP.log: https://www.dropbox.com/s/c1ggxjuiel5prcv/OKReport-TweakScale-2-4-4-5-DEBUG-KSP.log?dl=0 Quote Link to comment Share on other sites More sharing options...
Lisias Posted February 14, 2021 Author Share Posted February 14, 2021 (edited) 15 hours ago, Qyst said: Here they are: Bugged player.log: https://www.dropbox.com/s/x29sr6lo6r4o8kp/BugReport-TweakScale-2-4-4-5-DEBUG-Player.log?dl=0 Bugged KSP.log: https://www.dropbox.com/s/g6cqvsnx0wfsg5m/BugReport-TweakScale-2-4-4-5-DEBUG-KSP.log?dl=0 And just in case, the logs for when it's run with the working directory set correctly: Player.log: https://www.dropbox.com/s/zjiwhm3y6g3fhzr/OKReport-TweakScale-2-4-4-5-DEBUG-player.log?dl=0 KSP.log: https://www.dropbox.com/s/c1ggxjuiel5prcv/OKReport-TweakScale-2-4-4-5-DEBUG-KSP.log?dl=0 Yep, you had nailed it (and thanks for the "OkReports", they helped to confirm the thesis!) This is when things went badly: [LOG 21:37:08.937] [KSPe.IO.Path] Origin is /mnt/LinuxData/KSP/KSP1-11-1-BUGTEST/game/ [LOG 21:37:08.937] [KSPe.IO.Path] PWD is /mnt/LinuxData/KSP/ And this is when things are fine: [LOG 21:44:54.928] [KSPe.IO.Path] Origin is /mnt/LinuxData/KSP/KSP1-11-1-BUGTEST/game/ [LOG 21:44:54.928] [KSPe.IO.Path] PWD is /mnt/LinuxData/KSP/KSP1-11-1-BUGTEST/game/ In both cases, the Origin is right: [LOG 21:44:54.844] [KSPe.IO.Path] Calculating Origin for /mnt/LinuxData/KSP/KSP1-11-1-BUGTEST/game/KSP_Data/Managed/Assembly-CSharp.dll [LOG 21:44:54.845] [KSPe.IO.Path] Normalized path /mnt/LinuxData/KSP/KSP1-11-1-BUGTEST/game/ Well... Microsoft is innocent on this one (By The Krakens, I think this is the first time I say something like that... ) I find it hard to pinpoint KSP as the source of the fault either, as it's expected that the current directory is set to the directory where the executable is by default on launching applications (even Windows does that - damn, two in a day!). However, there're situations where you want the current directory to be different - so I'm not really sure if this is a bug of the Manjaro's File Manager, or just am unusual feature biting your SAS. Reaching the File Manager's devs appears to be a good idea, I doubt this is happening only to you. But not necessarily for a bug report, but for a feature request to implement your use case or at least warn the user when this happens. From KSPe point of view, I can "fix" the problem by brute force my way out of the mess, setting the PWD to the Origin internally - but that would not solve KSP's problem, as it will still be looking for files on unexpected places. To tell you the true, there's some opportunities for improvement on the KSP side too - usually, the game binaries, the game data, and the user data are set to different places on UNICes (/usr/local/libexec/<game>and /home/<user>/Library/<game> -- or similar), so blindly relying on the current directory to fecth important data is not the best of the ideas anyway. But again, it's not necessarily a bug. So what I will do is cook a new FATAL on KSPe to halt the game loading when the PWD is different from the Origin, as this is an unacceptable situation without a possible work around. Thanks for the report, @Qyst, you are helping to make KSP safer for everybody! -- -- POST EDIT -- -- I opened an Issue for tracking this down: https://github.com/net-lisias-ksp/KSPAPIExtensions/issues/9 (I may take a bit to implement, I have some promises to fulfil first on the Companions) Edited February 14, 2021 by Lisias Issue tracking Quote Link to comment Share on other sites More sharing options...
Fletch4 Posted February 16, 2021 Share Posted February 16, 2021 it says that i have about 17 fatal problems in my osx do not know where. Quote Link to comment Share on other sites More sharing options...
Lisias Posted February 16, 2021 Author Share Posted February 16, 2021 4 hours ago, Fletch4 said: it says that i have about 17 fatal problems in my osx do not know where. Bad patching - something is messing up with a thing called "patch", that it's a way to inject new things on the current parts. Sometimes more than one guy tries to patch the same part, and then you risk TweakScale using the wrong data and then your savegame can get corrupted (not always, but it happens enough to be better to track down the problem and fix them). There's a file called KSP.log on the same place KSP.app is. I need that file to check what's wrong on your rig. Please post it on dropbox or something like that and send me the link. I will inspect it to find the problem and propose a fix. Cheers! Quote Link to comment Share on other sites More sharing options...
Fletch4 Posted February 16, 2021 Share Posted February 16, 2021 never mind, fixed it myself. thx tho. Quote Link to comment Share on other sites More sharing options...
AccidentalDisassembly Posted February 18, 2021 Share Posted February 18, 2021 Getting some exceptions maybe related to TweakScale plus B9PartSwitch - or not, I have a heavily modded install with (apparently) many problems and I'm trying to track down what's causing them. Is this meaningful? Log here: https://www.dropbox.com/s/bp4we0wbf9cx1wf/KSPlog_SysHeatOrSomethingElse.log?dl=0 Example here, which may or may not be TweakScale's fault at all (but something seems to make TS cough a bit), given the other problems in the (gigantic, sorry) log: Quote [LOG 16:11:39.471] [SystemHeat][DebugUI]: Initializing [LOG 16:11:39.472] [SystemHeat][UI]: Loaded Assets [LOG 16:11:39.477] [SystemHeat][SystemHeatEditor]: Vessel MODIFIED [LOG 16:11:39.477] [SystemHeat][SystemHeatSimulator]: Building heat loops from 0 ModuleSystemHeat modules [ERR 16:11:39.478] Exception handling event onEditorShipModified in class ModuleB9PartInfo:System.NullReferenceException: Object reference not set to an instance of an object at TweakScale.TweakScale.IPartMassModifier.GetModuleMass (System.Single defaultMass, ModifierStagingSituation situation) [0x00010] in <6c196c229b7b407390d4d14556b33c91>:0 at Part.GetModuleMass (System.Single defaultMass, ModifierStagingSituation sit) [0x00046] in <2afc64dea36946459d4707808bdac511>:0 at B9PartSwitch.ModuleB9PartInfo.UpdateFields () [0x00019] in <b85eabe067044bcb9aeabe863954a5ce>:0 at B9PartSwitch.ModuleB9PartInfo.EditorShipModified (ShipConstruct construct) [0x00006] in <b85eabe067044bcb9aeabe863954a5ce>:0 at EventData`1[T].Fire (T data) [0x000b0] in <2afc64dea36946459d4707808bdac511>:0 [EXC 16:11:39.480] NullReferenceException: Object reference not set to an instance of an object TweakScale.TweakScale.IPartMassModifier.GetModuleMass (System.Single defaultMass, ModifierStagingSituation situation) (at <6c196c229b7b407390d4d14556b33c91>:0) Part.GetModuleMass (System.Single defaultMass, ModifierStagingSituation sit) (at <2afc64dea36946459d4707808bdac511>:0) B9PartSwitch.ModuleB9PartInfo.UpdateFields () (at <b85eabe067044bcb9aeabe863954a5ce>:0) B9PartSwitch.ModuleB9PartInfo.EditorShipModified (ShipConstruct construct) (at <b85eabe067044bcb9aeabe863954a5ce>:0) EventData`1[T].Fire (T data) (at <2afc64dea36946459d4707808bdac511>:0) UnityEngine.DebugLogHandler:LogException(Exception, Object) ModuleManager.UnityLogHandle.InterceptLogHandler:LogException(Exception, Object) UnityEngine.Debug:LogException(Exception) EventData`1:Fire(ShipConstruct) KIS.<>c:<RefreshContents>b__163_4() KSPDev.ProcessingUtils.<WaitForEndOfFrameCoroutine>d__4:MoveNext() UnityEngine.SetupCoroutine:InvokeMoveNext(IEnumerator, IntPtr) [ERR 16:11:39.480] Exception handling event onEditorShipModified in class ModuleB9PartInfo:System.NullReferenceException: Object reference not set to an instance of an object at TweakScale.TweakScale.IPartMassModifier.GetModuleMass (System.Single defaultMass, ModifierStagingSituation situation) [0x00010] in <6c196c229b7b407390d4d14556b33c91>:0 at Part.GetModuleMass (System.Single defaultMass, ModifierStagingSituation sit) [0x00046] in <2afc64dea36946459d4707808bdac511>:0 at B9PartSwitch.ModuleB9PartInfo.UpdateFields () [0x00019] in <b85eabe067044bcb9aeabe863954a5ce>:0 at B9PartSwitch.ModuleB9PartInfo.EditorShipModified (ShipConstruct construct) [0x00006] in <b85eabe067044bcb9aeabe863954a5ce>:0 at EventData`1[T].Fire (T data) [0x000b0] in <2afc64dea36946459d4707808bdac511>:0 Quote Link to comment Share on other sites More sharing options...
Lisias Posted February 18, 2021 Author Share Posted February 18, 2021 (edited) 2 hours ago, AccidentalDisassembly said: Getting some exceptions maybe related to TweakScale plus B9PartSwitch - or not, I have a heavily modded install with (apparently) many problems and I'm trying to track down what's causing them. Is this meaningful? Log here: https://www.dropbox.com/s/bp4we0wbf9cx1wf/KSPlog_SysHeatOrSomethingElse.log?dl=0 Example here, which may or may not be TweakScale's fault at all (but something seems to make TS cough a bit), given the other problems in the (gigantic, sorry) log: Whoa! Hell of a log! ~73Mb. Tons of exceptions, most of them (37755 to be precise) appears to be: [EXC 18:33:28.280] NullReferenceException: Object reference not set to an instance of an object FlightInputHandler.FixedUpdate () (at <2afc64dea36946459d4707808bdac511>:0) UnityEngine.DebugLogHandler:LogException(Exception, Object) ModuleManager.UnityLogHandle.InterceptLogHandler:LogException(Exception, Object) UnityEngine.Debug:CallOverridenDebugHandler(Exception, Object) But there're also 35602 of what follows: [EXC 18:33:28.284] NullReferenceException: Object reference not set to an instance of an object KerboKatz.ASS.AutomatedScienceSampler.Update () (at <5a8cf6fa51b341e5a2b9633bfcfe406f>:0) UnityEngine.DebugLogHandler:LogException(Exception, Object) ModuleManager.UnityLogHandle.InterceptLogHandler:LogException(Exception, Object) UnityEngine.Debug:CallOverridenDebugHandler(Exception, Object) I also found 702 occurrences from these one: [ERR 18:21:40.172] getFlightRecording(): System.NullReferenceException: Object reference not set to an instance of an object at KSTS.RecordingVesselStats.FindPayloadAssemblies (KSTS.FlightRecording recording, Part part, Part parent, System.Collections.Gener at KSTS.RecordingVesselStats.GetStats (KSTS.FlightRecording recording, Vessel vessel) [0x00406] in <3146a686e3104c58a1fd6935e4c4267b at KSTS.FlightRecording.Update (Vessel vessel) [0x00000] in <3146a686e3104c58a1fd6935e4c4267b>:0 at KSTS.FlightRecording..ctor (Vessel vessel) [0x000f8] in <3146a686e3104c58a1fd6935e4c4267b>:0 at KSTS.FlightRecorder.GetFlightRecording (Vessel vessel) [0x0007c] in <3146a686e3104c58a1fd6935e4c4267b>:0 Then I quit. These are not causes, they are consequences. Something else borked on a pretty critical piece of code, and since the thread is killed when an non caught exception happens (and catching exceptions on hot code is a FPS killer, and we are talking about a game were FPS counts), a lot of code that should had run were not - and this explains all these exceptions - something pretty important for these add'ons is borking on them. One good guess to try to dignose the cause is hunting for the first exceptions on the log. It's not sure they are the cause of the problem, but sometimes the bork happens some layers behind the ground zero, so let's try this one: [LOG 14:38:22.632] [AddonLoader]: Instantiating addon '_BuildManager' from assembly '_BuildManager' [EXC 14:38:22.642] NotSupportedException: The invoked member is not supported in a dynamic module. System.Reflection.Emit.AssemblyBuilder.get_Location () (at <ad04dee02e7e4a85a1299c7ee81c79f6>:0) _BuildManager._BuildManager+<>c__DisplayClass2_0.<logVersion>b__0 (System.Reflection.Assembly x) (at <3f485ce99d7e479c99f0f040223f System.Linq.Enumerable+WhereSelectArrayIterator`2[TSource,TResult].ToList () (at <fbb5ed17eb6e46c680000f8910ebb50c>:0) System.Linq.Enumerable.ToList[TSource] (System.Collections.Generic.IEnumerable`1[T] source) (at <fbb5ed17eb6e46c680000f8910ebb50c> _BuildManager._BuildManager.logVersion () (at <3f485ce99d7e479c99f0f040223fbad6>:0) _BuildManager._BuildManager.Awake () (at <3f485ce99d7e479c99f0f040223fbad6>:0) UnityEngine.DebugLogHandler:LogException(Exception, Object) ModuleManager.UnityLogHandle.InterceptLogHandler:LogException(Exception, Object) UnityEngine.GameObject:AddComponent(Type) AddonLoader:StartAddon(LoadedAssembly, Type, KSPAddon, Startup) AddonLoader:StartAddons(Startup) <LoadObjects>d__90:MoveNext() UnityEngine.MonoBehaviour:StartCoroutine(IEnumerator) <CreateDatabase>d__71:MoveNext() UnityEngine.MonoBehaviour:StartCoroutine(IEnumerator) GameDatabase:StartLoad() <LoadSystems>d__11:MoveNext() UnityEngine.MonoBehaviour:StartCoroutine(IEnumerator) LoadingScreen:Start() [LOG 14:38:22.643] [AddonLoader]: Instantiating addon 'UILoader' from assembly 'FarFutureTechnologies' This last one is the first exception on your log. _BuildManager (whatever it is) is borking its loading. Apparently its Awake is doing something illegal. Don't have further information about this, so I don't have to be sure about this. Well, let's try the next Exception: [LOG 14:41:40.372] PartLoader: Compiling Part 'AirplanePlus/Parts/Engine/Rotorwing/chinookprop/part/chinookprop' [WRN 14:41:40.374] PartLoader Warning: Variable totalCap not found in Part [WRN 14:41:40.374] PartLoader Warning: Variable rationalBuoyancy not found in Part [WRN 14:41:40.374] PartLoader Warning: Variable rationalPressure not found in Part [ERR 14:41:40.383] Module TweakScale threw during OnLoad: System.ArgumentException: An item with the same key has already been added. Key: Part at System.Collections.Generic.Dictionary`2[TKey,TValue].TryInsert (TKey key, TValue value, System.Collections.Generic.InsertionBehavior behavior) [0x000c1] in <ad04dee0 at System.Collections.Generic.Dictionary`2[TKey,TValue].Add (TKey key, TValue value) [0x00000] in <ad04dee02e7e4a85a1299c7ee81c79f6>:0 at System.Linq.Enumerable.ToDictionary[TSource,TKey] (System.Collections.Generic.IEnumerable`1[T] source, System.Func`2[T,TResult] keySelector, System.Collections.Gener at System.Linq.Enumerable.ToDictionary[TSource,TKey] (System.Collections.Generic.IEnumerable`1[T] source, System.Func`2[T,TResult] keySelector) [0x00000] in <fbb5ed17eb at TweakScale.ScaleExponents.CreateExponentsForModule (ConfigNode node, System.Collections.Generic.Dictionary`2[TKey,TValue] parent) [0x00040] in <6c196c229b7b407390d4d at TweakScale.ScaleType..ctor (ConfigNode partConfig) [0x00312] in <6c196c229b7b407390d4d14556b33c91>:0 at TweakScale.TweakScale.SetupPrefab (Part prefabPart) [0x00041] in <6c196c229b7b407390d4d14556b33c91>:0 at TweakScale.TweakScale.OnLoad (ConfigNode node) [0x0001b] in <6c196c229b7b407390d4d14556b33c91>:0 at PartModule.Load (ConfigNode node) [0x001ab] in <2afc64dea36946459d4707808bdac511>:0 And yeah, TweakScale may be involved on the mess. It's borking on the first time it's invoked, when compiling a part into the prefab. This is a pretty critical situation, as TweakScale does not have a full working environment (it is being built!), so a lot of things are "faked" to simulate a running module, just enough to satisfy the part compiler. If this critical thingy borks, that part is left inconsistent and once TweakScale is latter initialized on a real running environment, it borks. And since TweakScale (for reasons not important for the issue at hand) has to initialise itself on the first Update, and since half the problesm you ave are happening on the Update, we may had found the smoking gun. This exception has happened while compiling "Part 'AirplanePlus/Parts/Engine/Rotorwing/blackhawkprop/part/blackhawkprop'", so there's a good chance that something on this part is the problem. What does not means the part itself is faulty, it could be something that was injected on it on patching. So let's see who had patched it: [LOG 14:38:47.540] Applying update 002_CommunityPartsTitles/Localization/patch_airplane-plus/@PART[blackhawkprop]:NEEDS[AirplanePlus] to AirplanePlus/Parts/Engine/Rotorwing/blackhawkprop/part.cfg/PART[blackhawkprop] [LOG 14:38:48.517] Applying update GU/Configs/GU_Resources/GU_Settings/IntakeAtm/@PART[*]:HAS[@MODULE[ModuleResourceIntake],@RESOURCE[IntakeAir],!RESOURCE[IntakeAtm]]:NEEDS[!WarpPlugin,!GTI] to AirplanePlus/Parts/Engine/Rotorwing/blackhawkprop/part.cfg/PART[blackhawkprop] [LOG 14:38:48.908] Applying update KerbalInventoryForAll/AllowModPartsInStock/@PART[*]:HAS[!MODULE[ModuleCargoPart],#mass] to AirplanePlus/Parts/Engine/Rotorwing/blackhawkprop/part.cfg/PART[blackhawkprop] [LOG 14:39:03.743] Applying update UmbraSpaceIndustries/MKS/Patches/ScrapParts/@PART[*]:HAS[!MODULE[FlagSite],!MODULE[KerbalEVA]] to AirplanePlus/Parts/Engine/Rotorwing/blackhawkprop/part.cfg/PART[blackhawkprop] [LOG 14:39:08.449] Applying update RationalHydroDynamics/RationalBuoyancy/@PART:HAS[#category[Engine],~rationalBuoyancy]:FOR[00RationalBuoyancy] to AirplanePlus/Parts/Engine/Rotorwing/blackhawkprop/part.cfg/PART[blackhawkprop] [LOG 14:39:09.832] Applying update RationalHydroDynamics/RationalBuoyancy/@PART:HAS[@MODULE[ModuleResourceIntake],#rationalBuoyancy]:FOR[00RationalBuoyancy] to AirplanePlus/Parts/Engine/Rotorwing/blackhawkprop/part.cfg/PART[blackhawkprop] [LOG 14:39:10.725] Applying update RationalHydroDynamics/RationalPressure/@PART:HAS[#category[Engine],~maxPressure]:FOR[00RationalPressure] to AirplanePlus/Parts/Engine/Rotorwing/blackhawkprop/part.cfg/PART[blackhawkprop] [LOG 14:39:17.210] Applying update TweakScaleCompanion/APP/patches/000_CleanUp/@PART[b29cockpit,b29gear,bellcockpit,bellprop,belltail,bigwing,biplanegear,blackhawkgear,blackhawkprop,bombardiercockpit]:BEFORE[TweakScaleCompanion_APP] to AirplanePlus/Parts/Engine/Rotorwing/blackhawkprop/part.cfg/PART[blackhawkprop] [LOG 14:39:17.757] Applying update TweakScaleCompanion/APP/patches/AirplanePlus-Engine_TweakScale/@PART[blackhawkprop]:NEEDS[AirplanePlus,TweakScale]:FOR[TweakScaleCompanion_APP] to AirplanePlus/Parts/Engine/Rotorwing/blackhawkprop/part.cfg/PART[blackhawkprop] [LOG 14:39:23.030] Applying update RationalHydroDynamics/RationalBuoyancy/@PART:HAS[#rationalBuoyancy]:FOR[zRationalBuoyancy] to AirplanePlus/Parts/Engine/Rotorwing/blackhawkprop/part.cfg/PART[blackhawkprop] [LOG 14:39:24.430] Applying update RationalHydroDynamics/RationalBuoyancy/@PART:HAS[#rationalBuoyancy]:FOR[zRationalBuoyancy] to AirplanePlus/Parts/Engine/Rotorwing/blackhawkprop/part.cfg/PART[blackhawkprop] [LOG 14:39:24.986] Applying update RationalHydroDynamics/RationalPressure/@PART:HAS[#maxPressure]:FOR[zRationalPressure] to AirplanePlus/Parts/Engine/Rotorwing/blackhawkprop/part.cfg/PART[blackhawkprop] [LOG 14:39:28.801] Applying update PartInfo/PartInfo/@PART[*]:HAS[~name[TCAModule*],~name[Deployed*]]:FINAL to AirplanePlus/Parts/Engine/Rotorwing/blackhawkprop/part.cfg/PART[blackhawkprop] So, and assuming that educated guess above is right, the source of the problem could be one of the following: 002_CommunityPartsTitles GU KerbalInventoryForAll UmbraSpaceIndustries/MKS RationalHydroDynamics TweakScaleCompanion/APP what implies TweakScale PartInfo Some other APP parts also borked on this exception: Compiling Part 'AirplanePlus/Parts/Engine/Rotorwing/chinookprop/part/chinookprop' Compiling Part 'AirplanePlus/Parts/Engine/Rotorwing/coaxialprop/part/coaxialprop' But it also happened on: Compiling Part 'Mk2Expansion/Parts/Utility/RCS/StabilityControl/M2X_SCRCS' So this appears to not be something bad on APP itself. Let's check who is patching M2X_SCRCS: [LOG 14:38:48.989] Applying update KerbalInventoryForAll/AllowModPartsInStock/@PART[*]:HAS[!MODULE[ModuleCargoPart],#mass] to Mk2Expansion/Parts/Utility/RCS/StabilityControl.cfg/PART[M2X_SCRCS] [LOG 14:39:03.810] Applying update UmbraSpaceIndustries/MKS/Patches/ScrapParts/@PART[*]:HAS[!MODULE[FlagSite],!MODULE[KerbalEVA]] to Mk2Expansion/Parts/Utility/RCS/StabilityControl.cfg/PART[M2X_SCRCS] [LOG 14:39:04.729] Applying update Workshop/MM_Patches/_OSE_PartRecipes/@PART[*]:HAS[@MODULE[ModuleReactionWheel]] to Mk2Expansion/Parts/Utility/RCS/StabilityControl.cfg/PART[M2X_SCRCS] [LOG 14:39:04.974] Applying update Workshop/MM_Patches/_OSE_PartRecipes/@PART[*]:HAS[@MODULE[ModuleRCSFX]] to Mk2Expansion/Parts/Utility/RCS/StabilityControl.cfg/PART[M2X_SCRCS] [LOG 14:39:08.835] Applying update RationalHydroDynamics/RationalBuoyancy/@PART:HAS[#category[Control],~rationalBuoyancy]:FOR[00RationalBuoyancy] to Mk2Expansion/Parts/Utility/RCS/StabilityControl.cfg/PART[M2X_SCRCS] [LOG 14:39:23.283] Applying update RationalHydroDynamics/RationalBuoyancy/@PART:HAS[#rationalBuoyancy]:FOR[zRationalBuoyancy] to Mk2Expansion/Parts/Utility/RCS/StabilityControl.cfg/PART[M2X_SCRCS] [LOG 14:39:24.508] Applying update RationalHydroDynamics/RationalBuoyancy/@PART:HAS[#rationalBuoyancy]:FOR[zRationalBuoyancy] to Mk2Expansion/Parts/Utility/RCS/StabilityControl.cfg/PART[M2X_SCRCS] [LOG 14:39:24.883] Applying update RationalHydroDynamics/RationalPressure/@PART:HAS[~maxPressure,~rationalPressure]:FOR[zRationalPressure] to Mk2Expansion/Parts/Utility/RCS/StabilityControl.cfg/PART[M2X_SCRCS] [LOG 14:39:25.254] Applying update RationalHydroDynamics/RationalPressure/@PART:HAS[#maxPressure]:FOR[zRationalPressure] to Mk2Expansion/Parts/Utility/RCS/StabilityControl.cfg/PART[M2X_SCRCS] [LOG 14:39:28.522] Applying update Mk2Expansion/Patches/M2X_Tweakscale/@PART[M2X_SCRCS]:NEEDS[TweakScale]:FINAL to Mk2Expansion/Parts/Utility/RCS/StabilityControl.cfg/PART[M2X_SCRCS] [LOG 14:39:28.992] Applying update PartInfo/PartInfo/@PART[*]:HAS[~name[TCAModule*],~name[Deployed*]]:FINAL to Mk2Expansion/Parts/Utility/RCS/StabilityControl.cfg/PART[M2X_SCRCS] [LOG 14:39:29.637] Applying update zzzCustomPatches/TweakScale_ChangeReactionWheels/@PART[*]:HAS[@MODULE[TweakScale],@MODULE[ModuleReactionWheel]]:Final to Mk2Expansion/Parts/Utility/RCS/StabilityControl.cfg/PART[M2X_SCRCS] Humm... Now we have: KerbalInventoryForAll UmbraSpaceIndustries/MKS Workshop RationalHydroDynamics Mk2Expansion/Patches/M2X_Tweakscale PartInfo zzzCustomPatches/TweakScale_ChangeReactionWheels What's essentially the same list of suspects above, with the exception of Workshop. I think it's safe to rule this one out. I also found an Exception on TexturesUnlimited - but I found this exception before on others KSP.logs without this problem, so let's rule it out too for now. Now, on Editor Mode, I found something else interesting: [LOG 15:14:29.453] [PartSet]: Failed to add Resource -669128669 to Simulation PartSet:3 as corresponding Part Mk2 Crew Cabin (Long)-3357189321 SimulationResource was not found. [EXC 15:14:30.817] ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index System.ThrowHelper.ThrowArgumentOutOfRangeException (System.ExceptionArgument argument, System.ExceptionResource resource) (at <ad04dee02e7e4a85a1299c7ee81c79f6>:0) System.ThrowHelper.ThrowArgumentOutOfRangeException () (at <ad04dee02e7e4a85a1299c7ee81c79f6>:0) Part.OnCopy (Part original, System.Boolean asSymCounterpart) (at <2afc64dea36946459d4707808bdac511>:0) EditorLogic.<SetupFSM>b__190_23 () (at <2afc64dea36946459d4707808bdac511>:0) KerbalFSM.RunEvent (KFSMEvent evt) (at <2afc64dea36946459d4707808bdac511>:0) KerbalFSM.updateFSM (KFSMUpdateMode mode) (at <2afc64dea36946459d4707808bdac511>:0) KerbalFSM.UpdateFSM () (at <2afc64dea36946459d4707808bdac511>:0) EditorLogic.Update () (at <2afc64dea36946459d4707808bdac511>:0) UnityEngine.DebugLogHandler:LogException(Exception, Object) ModuleManager.UnityLogHandle.InterceptLogHandler:LogException(Exception, Object) UnityEngine.Debug:CallOverridenDebugHandler(Exception, Object) So now I understood why you mentioned SystemHeat. You have something bad injected on your prefab as it appears, and since we have at least 4 borks on compiling parts above (and remembering that uncaught exceptions aborts the thread, and some things that should had been done weren't), I think this fire is really coming from where we first found the smoke - on that add'ons that patched that borked parts above. I found some more exceptions as this last one on the log, by the way. And then something new when you fire the flight scene: [LOG 15:28:24.587] [HighLogic]: =========================== Scene Change : From EDITOR to FLIGHT (Async) ===================== [EXC 15:28:25.110] NullReferenceException: Object reference not set to an instance of an object Waterfall.ModuleWaterfallFX.LateUpdate () (at <a22c557aeb9241888535018c7ddec62a>:0) UnityEngine.DebugLogHandler:LogException(Exception, Object) ModuleManager.UnityLogHandle.InterceptLogHandler:LogException(Exception, Object) UnityEngine.Debug:CallOverridenDebugHandler(Exception, Object) And also [LOG 15:28:33.274] [AddonLoader]: Instantiating addon 'TexturesUnlimitedDebug' from assembly 'TexturesUnlimited' [EXC 15:28:33.274] NullReferenceException: Object reference not set to an instance of an object KSP.UI.Screens.ApplicationLauncher.RemoveModApplication (KSP.UI.Screens.ApplicationLauncherButton button) (at <2afc64dea36946459d4707808bdac511>:0) KSPShaderTools.Addon.TexturesUnlimitedDebug.Awake () (at <d05d146f0f32458d9a30cf17e61f35a8>:0) UnityEngine.DebugLogHandler:LogException(Exception, Object) ModuleManager.UnityLogHandle.InterceptLogHandler:LogException(Exception, Object) UnityEngine.GameObject:AddComponent(Type) AddonLoader:StartAddon(LoadedAssembly, Type, KSPAddon, Startup) AddonLoader:StartAddons(Startup) AddonLoader:OnLevelLoaded(GameScenes) AddonLoader:OnSceneLoaded(Scene, LoadSceneMode) UnityEngine.SceneManagement.SceneManager:Internal_SceneLoaded(Scene, LoadSceneMode) Probably unrelated or just splash damage from the real problem. But doesn't hurt to uninstall them to see what happens. I also found this one (that also demonstrates how useless is the ADDON BINDER ERR log ): [ERR 15:28:34.662] ADDON BINDER: Cannot resolve assembly: AutomatedScienceSampler.XmlSerializers, Culture=neutral, PublicKeyToken=null [ERR 15:28:34.663] ADDON BINDER: Cannot resolve assembly: AutomatedScienceSampler.XmlSerializers, Culture=neutral, PublicKeyToken=null [ERR 15:28:34.663] ADDON BINDER: Cannot resolve assembly: AutomatedScienceSampler.XmlSerializers [ERR 15:28:34.700] ADDON BINDER: Cannot resolve assembly: DMagic, Culture=neutral, PublicKeyToken=null [ERR 15:28:34.700] ADDON BINDER: Cannot resolve assembly: DMagic, Culture=neutral, PublicKeyToken=null [ERR 15:28:34.702] ADDON BINDER: Cannot resolve assembly: DMModuleScienceAnimateGeneric, Culture=neutral, PublicKeyToken=null [ERR 15:28:34.702] ADDON BINDER: Cannot resolve assembly: DMModuleScienceAnimateGeneric, Culture=neutral, PublicKeyToken=null [ERR 15:28:34.703] ADDON BINDER: Cannot resolve assembly: StationScience, Culture=neutral, PublicKeyToken=null [ERR 15:28:34.703] ADDON BINDER: Cannot resolve assembly: StationScience, Culture=neutral, PublicKeyToken=null [WRN 15:28:34.708] System.RuntimeType Could not load file or assembly 'DMagic, Version=1.4.2.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. at KerboKatz.ASS.AutomatedScienceSampler.CheckTypeForScienceActivator (System.Type type) [0x00060] in <5a8cf6fa51b341e5a2b9633bfcfe406f>:0 at KerboKatz.Utilities.LoopTroughAssemblies (System.Action`1[T] CheckType) [0x00030] in <a9fd0328e42c42c683680f8ee94d4e7e>:0 System.RuntimeType Could not load file or assembly 'DMModuleScienceAnimateGeneric, Version=0.21.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. at KerboKatz.ASS.AutomatedScienceSampler.CheckTypeForScienceActivator (System.Type type) [0x00060] in <5a8cf6fa51b341e5a2b9633bfcfe406f>:0 at KerboKatz.Utilities.LoopTroughAssemblies (System.Action`1[T] CheckType) [0x00030] in <a9fd0328e42c42c683680f8ee94d4e7e>:0 System.RuntimeType Could not load file or assembly 'StationScience, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. at KerboKatz.ASS.AutomatedScienceSampler.CheckTypeForScienceActivator (System.Type type) [0x00060] in <5a8cf6fa51b341e5a2b9633bfcfe406f>:0 at KerboKatz.Utilities.LoopTroughAssemblies (System.Action`1[T] CheckType) [0x00030] in <a9fd0328e42c42c683680f8ee94d4e7e>:0 KerboKats is trying to load AutomatedScienceSampler, DMagic, DMModuleScienceAnimateGeneric and StationScience. Probably is successful on searching for it, as we have to ADDON BINDER messages for each one - one for looking for it, and another for loading it. Look how AutomatedScienceSampler is mentioned three times, but does not throws up an error. I'm reasonably sure to say KerboKatz is missing some dependencies, and this solves for sure at least half of your problems above! Uninstall KerboKatz and see what changes. At least half of that awful amount of exceptions will vanish. (the ones on Update - a place where TweakScale is also sensitive). Keep in mind that you may have more than one problem on your instalment. The borks on the FlightInputHandler.FixedUpdate suggests you have a problem on your Input Device! Are you using some fancy GamePad with custom drivers? --- POST EDIT ----- I think that uninstalling RationalHydroDynamics may solve that 4 parts failing being compiled. If this will solve some of the other exceptions, only time will tell... Edited February 18, 2021 by Lisias Tyops, of cuorse! Quote Link to comment Share on other sites More sharing options...
AccidentalDisassembly Posted February 18, 2021 Share Posted February 18, 2021 (edited) 1 hour ago, Lisias said: Whoa! Hell of a log! ~73Mb. Tons of exceptions, most of them (37755 to be precise) appears to be: [EXC 18:33:28.280] NullReferenceException: Object reference not set to an instance of an object FlightInputHandler.FixedUpdate () (at <2afc64dea36946459d4707808bdac511>:0) UnityEngine.DebugLogHandler:LogException(Exception, Object) ModuleManager.UnityLogHandle.InterceptLogHandler:LogException(Exception, Object) UnityEngine.Debug:CallOverridenDebugHandler(Exception, Object) But there're also 35602 of what follows: [EXC 18:33:28.284] NullReferenceException: Object reference not set to an instance of an object KerboKatz.ASS.AutomatedScienceSampler.Update () (at <5a8cf6fa51b341e5a2b9633bfcfe406f>:0) UnityEngine.DebugLogHandler:LogException(Exception, Object) ModuleManager.UnityLogHandle.InterceptLogHandler:LogException(Exception, Object) UnityEngine.Debug:CallOverridenDebugHandler(Exception, Object) I also found 702 occurrences from these one: [ERR 18:21:40.172] getFlightRecording(): System.NullReferenceException: Object reference not set to an instance of an object at KSTS.RecordingVesselStats.FindPayloadAssemblies (KSTS.FlightRecording recording, Part part, Part parent, System.Collections.Gener at KSTS.RecordingVesselStats.GetStats (KSTS.FlightRecording recording, Vessel vessel) [0x00406] in <3146a686e3104c58a1fd6935e4c4267b at KSTS.FlightRecording.Update (Vessel vessel) [0x00000] in <3146a686e3104c58a1fd6935e4c4267b>:0 at KSTS.FlightRecording..ctor (Vessel vessel) [0x000f8] in <3146a686e3104c58a1fd6935e4c4267b>:0 at KSTS.FlightRecorder.GetFlightRecording (Vessel vessel) [0x0007c] in <3146a686e3104c58a1fd6935e4c4267b>:0 Then I quit. These are not causes, they are consequences. Something else borked on a pretty critical piece of code, and since the thread is killed when an non caught exception happens (and catching exceptions on hot code is a FPS killer, and we are talking about a game were FPS counts), a lot of code that should had run were not - and this explains all these exceptions - something pretty important for these add'ons is borking on them. One good guess to try to dignose the cause is hunting for the first exceptions on the log. It's not sure they are the cause of the problem, but sometimes the bork happens some layers behind the ground zero, so let's try this one: [LOG 14:38:22.632] [AddonLoader]: Instantiating addon '_BuildManager' from assembly '_BuildManager' [EXC 14:38:22.642] NotSupportedException: The invoked member is not supported in a dynamic module. System.Reflection.Emit.AssemblyBuilder.get_Location () (at <ad04dee02e7e4a85a1299c7ee81c79f6>:0) _BuildManager._BuildManager+<>c__DisplayClass2_0.<logVersion>b__0 (System.Reflection.Assembly x) (at <3f485ce99d7e479c99f0f040223f System.Linq.Enumerable+WhereSelectArrayIterator`2[TSource,TResult].ToList () (at <fbb5ed17eb6e46c680000f8910ebb50c>:0) System.Linq.Enumerable.ToList[TSource] (System.Collections.Generic.IEnumerable`1[T] source) (at <fbb5ed17eb6e46c680000f8910ebb50c> _BuildManager._BuildManager.logVersion () (at <3f485ce99d7e479c99f0f040223fbad6>:0) _BuildManager._BuildManager.Awake () (at <3f485ce99d7e479c99f0f040223fbad6>:0) UnityEngine.DebugLogHandler:LogException(Exception, Object) ModuleManager.UnityLogHandle.InterceptLogHandler:LogException(Exception, Object) UnityEngine.GameObject:AddComponent(Type) AddonLoader:StartAddon(LoadedAssembly, Type, KSPAddon, Startup) AddonLoader:StartAddons(Startup) <LoadObjects>d__90:MoveNext() UnityEngine.MonoBehaviour:StartCoroutine(IEnumerator) <CreateDatabase>d__71:MoveNext() UnityEngine.MonoBehaviour:StartCoroutine(IEnumerator) GameDatabase:StartLoad() <LoadSystems>d__11:MoveNext() UnityEngine.MonoBehaviour:StartCoroutine(IEnumerator) LoadingScreen:Start() [LOG 14:38:22.643] [AddonLoader]: Instantiating addon 'UILoader' from assembly 'FarFutureTechnologies' This last one is the first exception on your log. _BuildManager (whatever it is) is borking its loading. Apparently its Awake is doing something illegal. Don't have further information about this, so I don't have to be sure about this. Well, let's try the next Exception: [LOG 14:41:40.372] PartLoader: Compiling Part 'AirplanePlus/Parts/Engine/Rotorwing/chinookprop/part/chinookprop' [WRN 14:41:40.374] PartLoader Warning: Variable totalCap not found in Part [WRN 14:41:40.374] PartLoader Warning: Variable rationalBuoyancy not found in Part [WRN 14:41:40.374] PartLoader Warning: Variable rationalPressure not found in Part [ERR 14:41:40.383] Module TweakScale threw during OnLoad: System.ArgumentException: An item with the same key has already been added. Key: Part at System.Collections.Generic.Dictionary`2[TKey,TValue].TryInsert (TKey key, TValue value, System.Collections.Generic.InsertionBehavior behavior) [0x000c1] in <ad04dee0 at System.Collections.Generic.Dictionary`2[TKey,TValue].Add (TKey key, TValue value) [0x00000] in <ad04dee02e7e4a85a1299c7ee81c79f6>:0 at System.Linq.Enumerable.ToDictionary[TSource,TKey] (System.Collections.Generic.IEnumerable`1[T] source, System.Func`2[T,TResult] keySelector, System.Collections.Gener at System.Linq.Enumerable.ToDictionary[TSource,TKey] (System.Collections.Generic.IEnumerable`1[T] source, System.Func`2[T,TResult] keySelector) [0x00000] in <fbb5ed17eb at TweakScale.ScaleExponents.CreateExponentsForModule (ConfigNode node, System.Collections.Generic.Dictionary`2[TKey,TValue] parent) [0x00040] in <6c196c229b7b407390d4d at TweakScale.ScaleType..ctor (ConfigNode partConfig) [0x00312] in <6c196c229b7b407390d4d14556b33c91>:0 at TweakScale.TweakScale.SetupPrefab (Part prefabPart) [0x00041] in <6c196c229b7b407390d4d14556b33c91>:0 at TweakScale.TweakScale.OnLoad (ConfigNode node) [0x0001b] in <6c196c229b7b407390d4d14556b33c91>:0 at PartModule.Load (ConfigNode node) [0x001ab] in <2afc64dea36946459d4707808bdac511>:0 And yeah, TweakScale may be involved on the mess. It's borking on the first time it's invoked, when compiling a part into the prefab. This is a pretty critical situation, as TweakScale does not have a full working environment (it is being built!), so a lot of things are "faked" to simulate a running module, just enough to satisfy the part compiler. If this critical thingy borks, that part is left inconsistent and once TweakScale is latter initialized on a real running environment, it borks. And since TweakScale (for reasons not important for the issue at hand) has to initialise itself on the first Update, and since half the problesm you ave are happening on the Update, we may had found the smoking gun. This exception has happened while compiling "Part 'AirplanePlus/Parts/Engine/Rotorwing/blackhawkprop/part/blackhawkprop'", so there's a good chance that something on this part is the problem. What does not means the part itself is faulty, it could be something that was injected on it on patching. So let's see who had patched it: [LOG 14:38:47.540] Applying update 002_CommunityPartsTitles/Localization/patch_airplane-plus/@PART[blackhawkprop]:NEEDS[AirplanePlus] to AirplanePlus/Parts/Engine/Rotorwing/blackhawkprop/part.cfg/PART[blackhawkprop] [LOG 14:38:48.517] Applying update GU/Configs/GU_Resources/GU_Settings/IntakeAtm/@PART[*]:HAS[@MODULE[ModuleResourceIntake],@RESOURCE[IntakeAir],!RESOURCE[IntakeAtm]]:NEEDS[!WarpPlugin,!GTI] to AirplanePlus/Parts/Engine/Rotorwing/blackhawkprop/part.cfg/PART[blackhawkprop] [LOG 14:38:48.908] Applying update KerbalInventoryForAll/AllowModPartsInStock/@PART[*]:HAS[!MODULE[ModuleCargoPart],#mass] to AirplanePlus/Parts/Engine/Rotorwing/blackhawkprop/part.cfg/PART[blackhawkprop] [LOG 14:39:03.743] Applying update UmbraSpaceIndustries/MKS/Patches/ScrapParts/@PART[*]:HAS[!MODULE[FlagSite],!MODULE[KerbalEVA]] to AirplanePlus/Parts/Engine/Rotorwing/blackhawkprop/part.cfg/PART[blackhawkprop] [LOG 14:39:08.449] Applying update RationalHydroDynamics/RationalBuoyancy/@PART:HAS[#category[Engine],~rationalBuoyancy]:FOR[00RationalBuoyancy] to AirplanePlus/Parts/Engine/Rotorwing/blackhawkprop/part.cfg/PART[blackhawkprop] [LOG 14:39:09.832] Applying update RationalHydroDynamics/RationalBuoyancy/@PART:HAS[@MODULE[ModuleResourceIntake],#rationalBuoyancy]:FOR[00RationalBuoyancy] to AirplanePlus/Parts/Engine/Rotorwing/blackhawkprop/part.cfg/PART[blackhawkprop] [LOG 14:39:10.725] Applying update RationalHydroDynamics/RationalPressure/@PART:HAS[#category[Engine],~maxPressure]:FOR[00RationalPressure] to AirplanePlus/Parts/Engine/Rotorwing/blackhawkprop/part.cfg/PART[blackhawkprop] [LOG 14:39:17.210] Applying update TweakScaleCompanion/APP/patches/000_CleanUp/@PART[b29cockpit,b29gear,bellcockpit,bellprop,belltail,bigwing,biplanegear,blackhawkgear,blackhawkprop,bombardiercockpit]:BEFORE[TweakScaleCompanion_APP] to AirplanePlus/Parts/Engine/Rotorwing/blackhawkprop/part.cfg/PART[blackhawkprop] [LOG 14:39:17.757] Applying update TweakScaleCompanion/APP/patches/AirplanePlus-Engine_TweakScale/@PART[blackhawkprop]:NEEDS[AirplanePlus,TweakScale]:FOR[TweakScaleCompanion_APP] to AirplanePlus/Parts/Engine/Rotorwing/blackhawkprop/part.cfg/PART[blackhawkprop] [LOG 14:39:23.030] Applying update RationalHydroDynamics/RationalBuoyancy/@PART:HAS[#rationalBuoyancy]:FOR[zRationalBuoyancy] to AirplanePlus/Parts/Engine/Rotorwing/blackhawkprop/part.cfg/PART[blackhawkprop] [LOG 14:39:24.430] Applying update RationalHydroDynamics/RationalBuoyancy/@PART:HAS[#rationalBuoyancy]:FOR[zRationalBuoyancy] to AirplanePlus/Parts/Engine/Rotorwing/blackhawkprop/part.cfg/PART[blackhawkprop] [LOG 14:39:24.986] Applying update RationalHydroDynamics/RationalPressure/@PART:HAS[#maxPressure]:FOR[zRationalPressure] to AirplanePlus/Parts/Engine/Rotorwing/blackhawkprop/part.cfg/PART[blackhawkprop] [LOG 14:39:28.801] Applying update PartInfo/PartInfo/@PART[*]:HAS[~name[TCAModule*],~name[Deployed*]]:FINAL to AirplanePlus/Parts/Engine/Rotorwing/blackhawkprop/part.cfg/PART[blackhawkprop] So, and assuming that educated guess above is right, the source of the problem could be one of the following: 002_CommunityPartsTitles GU KerbalInventoryForAll UmbraSpaceIndustries/MKS RationalHydroDynamics TweakScaleCompanion/APP what implies TweakScale PartInfo Some other APP parts also borked on this exception: Compiling Part 'AirplanePlus/Parts/Engine/Rotorwing/chinookprop/part/chinookprop' Compiling Part 'AirplanePlus/Parts/Engine/Rotorwing/coaxialprop/part/coaxialprop' But it also happened on: Compiling Part 'Mk2Expansion/Parts/Utility/RCS/StabilityControl/M2X_SCRCS' So this appears to not be something bad on APP itself. Let's check who is patching M2X_SCRCS: [LOG 14:38:48.989] Applying update KerbalInventoryForAll/AllowModPartsInStock/@PART[*]:HAS[!MODULE[ModuleCargoPart],#mass] to Mk2Expansion/Parts/Utility/RCS/StabilityControl.cfg/PART[M2X_SCRCS] [LOG 14:39:03.810] Applying update UmbraSpaceIndustries/MKS/Patches/ScrapParts/@PART[*]:HAS[!MODULE[FlagSite],!MODULE[KerbalEVA]] to Mk2Expansion/Parts/Utility/RCS/StabilityControl.cfg/PART[M2X_SCRCS] [LOG 14:39:04.729] Applying update Workshop/MM_Patches/_OSE_PartRecipes/@PART[*]:HAS[@MODULE[ModuleReactionWheel]] to Mk2Expansion/Parts/Utility/RCS/StabilityControl.cfg/PART[M2X_SCRCS] [LOG 14:39:04.974] Applying update Workshop/MM_Patches/_OSE_PartRecipes/@PART[*]:HAS[@MODULE[ModuleRCSFX]] to Mk2Expansion/Parts/Utility/RCS/StabilityControl.cfg/PART[M2X_SCRCS] [LOG 14:39:08.835] Applying update RationalHydroDynamics/RationalBuoyancy/@PART:HAS[#category[Control],~rationalBuoyancy]:FOR[00RationalBuoyancy] to Mk2Expansion/Parts/Utility/RCS/StabilityControl.cfg/PART[M2X_SCRCS] [LOG 14:39:23.283] Applying update RationalHydroDynamics/RationalBuoyancy/@PART:HAS[#rationalBuoyancy]:FOR[zRationalBuoyancy] to Mk2Expansion/Parts/Utility/RCS/StabilityControl.cfg/PART[M2X_SCRCS] [LOG 14:39:24.508] Applying update RationalHydroDynamics/RationalBuoyancy/@PART:HAS[#rationalBuoyancy]:FOR[zRationalBuoyancy] to Mk2Expansion/Parts/Utility/RCS/StabilityControl.cfg/PART[M2X_SCRCS] [LOG 14:39:24.883] Applying update RationalHydroDynamics/RationalPressure/@PART:HAS[~maxPressure,~rationalPressure]:FOR[zRationalPressure] to Mk2Expansion/Parts/Utility/RCS/StabilityControl.cfg/PART[M2X_SCRCS] [LOG 14:39:25.254] Applying update RationalHydroDynamics/RationalPressure/@PART:HAS[#maxPressure]:FOR[zRationalPressure] to Mk2Expansion/Parts/Utility/RCS/StabilityControl.cfg/PART[M2X_SCRCS] [LOG 14:39:28.522] Applying update Mk2Expansion/Patches/M2X_Tweakscale/@PART[M2X_SCRCS]:NEEDS[TweakScale]:FINAL to Mk2Expansion/Parts/Utility/RCS/StabilityControl.cfg/PART[M2X_SCRCS] [LOG 14:39:28.992] Applying update PartInfo/PartInfo/@PART[*]:HAS[~name[TCAModule*],~name[Deployed*]]:FINAL to Mk2Expansion/Parts/Utility/RCS/StabilityControl.cfg/PART[M2X_SCRCS] [LOG 14:39:29.637] Applying update zzzCustomPatches/TweakScale_ChangeReactionWheels/@PART[*]:HAS[@MODULE[TweakScale],@MODULE[ModuleReactionWheel]]:Final to Mk2Expansion/Parts/Utility/RCS/StabilityControl.cfg/PART[M2X_SCRCS] Humm... Now we have: KerbalInventoryForAll UmbraSpaceIndustries/MKS Workshop RationalHydroDynamics Mk2Expansion/Patches/M2X_Tweakscale PartInfo zzzCustomPatches/TweakScale_ChangeReactionWheels What's essentially the same list of suspects above, with the exception of Workshop. I think it's safe to rule this one out. I also found an Exception on TexturesUnlimited - but I found this exception before on others KSP.logs without this problem, so let's rule it out too for now. Now, on Editor Mode, I found something else interesting: [LOG 15:14:29.453] [PartSet]: Failed to add Resource -669128669 to Simulation PartSet:3 as corresponding Part Mk2 Crew Cabin (Long)-3357189321 SimulationResource was not found. [EXC 15:14:30.817] ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index System.ThrowHelper.ThrowArgumentOutOfRangeException (System.ExceptionArgument argument, System.ExceptionResource resource) (at <ad04dee02e7e4a85a1299c7ee81c79f6>:0) System.ThrowHelper.ThrowArgumentOutOfRangeException () (at <ad04dee02e7e4a85a1299c7ee81c79f6>:0) Part.OnCopy (Part original, System.Boolean asSymCounterpart) (at <2afc64dea36946459d4707808bdac511>:0) EditorLogic.<SetupFSM>b__190_23 () (at <2afc64dea36946459d4707808bdac511>:0) KerbalFSM.RunEvent (KFSMEvent evt) (at <2afc64dea36946459d4707808bdac511>:0) KerbalFSM.updateFSM (KFSMUpdateMode mode) (at <2afc64dea36946459d4707808bdac511>:0) KerbalFSM.UpdateFSM () (at <2afc64dea36946459d4707808bdac511>:0) EditorLogic.Update () (at <2afc64dea36946459d4707808bdac511>:0) UnityEngine.DebugLogHandler:LogException(Exception, Object) ModuleManager.UnityLogHandle.InterceptLogHandler:LogException(Exception, Object) UnityEngine.Debug:CallOverridenDebugHandler(Exception, Object) So now I understood why you mentioned SystemHeat. You have something bad injected on your prefab as it appears, and since we have at least 4 borks on compiling parts above (and remembering that uncaught exceptions aborts the thread, and some things that should had been done weren't), I think this fire is really coming from where we first found the smoke - on that add'ons that patched that borked parts above. I found some more exceptions as this last one on the log, by the way. And then something new when you fire the flight scene: [LOG 15:28:24.587] [HighLogic]: =========================== Scene Change : From EDITOR to FLIGHT (Async) ===================== [EXC 15:28:25.110] NullReferenceException: Object reference not set to an instance of an object Waterfall.ModuleWaterfallFX.LateUpdate () (at <a22c557aeb9241888535018c7ddec62a>:0) UnityEngine.DebugLogHandler:LogException(Exception, Object) ModuleManager.UnityLogHandle.InterceptLogHandler:LogException(Exception, Object) UnityEngine.Debug:CallOverridenDebugHandler(Exception, Object) And also [LOG 15:28:33.274] [AddonLoader]: Instantiating addon 'TexturesUnlimitedDebug' from assembly 'TexturesUnlimited' [EXC 15:28:33.274] NullReferenceException: Object reference not set to an instance of an object KSP.UI.Screens.ApplicationLauncher.RemoveModApplication (KSP.UI.Screens.ApplicationLauncherButton button) (at <2afc64dea36946459d4707808bdac511>:0) KSPShaderTools.Addon.TexturesUnlimitedDebug.Awake () (at <d05d146f0f32458d9a30cf17e61f35a8>:0) UnityEngine.DebugLogHandler:LogException(Exception, Object) ModuleManager.UnityLogHandle.InterceptLogHandler:LogException(Exception, Object) UnityEngine.GameObject:AddComponent(Type) AddonLoader:StartAddon(LoadedAssembly, Type, KSPAddon, Startup) AddonLoader:StartAddons(Startup) AddonLoader:OnLevelLoaded(GameScenes) AddonLoader:OnSceneLoaded(Scene, LoadSceneMode) UnityEngine.SceneManagement.SceneManager:Internal_SceneLoaded(Scene, LoadSceneMode) Probably unrelated or just splash damage from the real problem. But doesn't hurt to uninstall them to see what happens. I also found this one (that also demonstrates how useless is the ADDON BINDER ERR log ): [ERR 15:28:34.662] ADDON BINDER: Cannot resolve assembly: AutomatedScienceSampler.XmlSerializers, Culture=neutral, PublicKeyToken=null [ERR 15:28:34.663] ADDON BINDER: Cannot resolve assembly: AutomatedScienceSampler.XmlSerializers, Culture=neutral, PublicKeyToken=null [ERR 15:28:34.663] ADDON BINDER: Cannot resolve assembly: AutomatedScienceSampler.XmlSerializers [ERR 15:28:34.700] ADDON BINDER: Cannot resolve assembly: DMagic, Culture=neutral, PublicKeyToken=null [ERR 15:28:34.700] ADDON BINDER: Cannot resolve assembly: DMagic, Culture=neutral, PublicKeyToken=null [ERR 15:28:34.702] ADDON BINDER: Cannot resolve assembly: DMModuleScienceAnimateGeneric, Culture=neutral, PublicKeyToken=null [ERR 15:28:34.702] ADDON BINDER: Cannot resolve assembly: DMModuleScienceAnimateGeneric, Culture=neutral, PublicKeyToken=null [ERR 15:28:34.703] ADDON BINDER: Cannot resolve assembly: StationScience, Culture=neutral, PublicKeyToken=null [ERR 15:28:34.703] ADDON BINDER: Cannot resolve assembly: StationScience, Culture=neutral, PublicKeyToken=null [WRN 15:28:34.708] System.RuntimeType Could not load file or assembly 'DMagic, Version=1.4.2.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. at KerboKatz.ASS.AutomatedScienceSampler.CheckTypeForScienceActivator (System.Type type) [0x00060] in <5a8cf6fa51b341e5a2b9633bfcfe406f>:0 at KerboKatz.Utilities.LoopTroughAssemblies (System.Action`1[T] CheckType) [0x00030] in <a9fd0328e42c42c683680f8ee94d4e7e>:0 System.RuntimeType Could not load file or assembly 'DMModuleScienceAnimateGeneric, Version=0.21.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. at KerboKatz.ASS.AutomatedScienceSampler.CheckTypeForScienceActivator (System.Type type) [0x00060] in <5a8cf6fa51b341e5a2b9633bfcfe406f>:0 at KerboKatz.Utilities.LoopTroughAssemblies (System.Action`1[T] CheckType) [0x00030] in <a9fd0328e42c42c683680f8ee94d4e7e>:0 System.RuntimeType Could not load file or assembly 'StationScience, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. at KerboKatz.ASS.AutomatedScienceSampler.CheckTypeForScienceActivator (System.Type type) [0x00060] in <5a8cf6fa51b341e5a2b9633bfcfe406f>:0 at KerboKatz.Utilities.LoopTroughAssemblies (System.Action`1[T] CheckType) [0x00030] in <a9fd0328e42c42c683680f8ee94d4e7e>:0 KerboKats is trying to load AutomatedScienceSampler, DMagic, DMModuleScienceAnimateGeneric and StationScience. Probably is successful on searching for it, as we have to ADDON BINDER messages for each one - one for looking for it, and another for loading it. Look how AutomatedScienceSampler is mentioned three times, but does not throws up an error. I'm reasonably sure to say KerboKatz is missing some dependencies, and this solves for sure at least half of your problems above! Uninstall KerboKatz and see what changes. At least half of that awful amount of exceptions will vanish. (the ones on Update - a place where TweakScale is also sensitive). Keep in mind that you may have more than one problem on your instalment. The borks on the FlightInputHandler.FixedUpdate suggests you have a problem on your Input Device! Are you using some fancy GamePad with custom drivers? --- POST EDIT ----- I think that uninstalling RationalHydroDynamics may solve that 4 parts failing being compiled. If this will solve some of the other exceptions, only time will tell... That was... extensive! Thank you for that, I will give it a shot. _BuildManger.dll is from Environmental Visual Enhancements (the latest version), hopefully that's not the root issue, because I quite like EVE! By the time I closed the game, the log was ~1 Gigabyte. Ugh. Very unfortunate re: KerboKatz, because KerboKatz (Automated Science Sampler) is the only mod I know of that has the functionality of dropping you out of warp when there's science you can do in a given biome (as opposed to doing what X Science! seems to do, for instance, which is dropping you out of warp upon every change of biome regardless of science availability). EDIT: No fancy control devices, just a generic keyboard and a logitech mouse... Edited February 18, 2021 by AccidentalDisassembly Quote Link to comment Share on other sites More sharing options...
Lisias Posted February 18, 2021 Author Share Posted February 18, 2021 3 hours ago, AccidentalDisassembly said: Very unfortunate re: KerboKatz, because KerboKatz Diagnosing is one thing, fixing is another. If by removing something we stop the problems, we have a confirmation. With the confirmation, we can zero into the cause and then try a fix on the troublemaker if wanted. 3 hours ago, AccidentalDisassembly said: EDIT: No fancy control devices, just a generic keyboard and a logitech mouse... Damn. I hope we don't get a new incarnation from the Xinput.dll problem from the Unity2017 times... Quote Link to comment Share on other sites More sharing options...
AccidentalDisassembly Posted February 18, 2021 Share Posted February 18, 2021 3 minutes ago, Lisias said: Diagnosing is one thing, fixing is another. If by removing something we stop the problems, we have a confirmation. With the confirmation, we can zero into the cause and then try a fix on the troublemaker if wanted. Damn. I hope we don't get a new incarnation from the Xinput.dll problem from the Unity2017 times... So far, I can at least confirm that I can now load and fly a vessel that was causing VERY strange behavior before (and is what made me start looking at the logs) - when launching it into the flight scene, the camera would go under the runway, control was lost, camera couldn't be rotated, all sorts of strange behavior, launch clock was at -16 days or something... Now, I can manipulate that vessel in the editor and also fly it; there are still some exceptions, but they're different and A LOT fewer after removing KerboKatz/ASS, RationalHydrodynamics, and PartInfo. I still notice an exception from TweakScale, but I think I have narrowed it down: At first, there were no TweakScale related exceptions in the log. Then I loaded the problematic craft into the editor, manipulated only the OPTdropTank part on it, and reloaded the log - saw exceptions after this action. I changed tank size slightly, picked it up, placed it again, launched craft, I think. I have a theory about a possible reason related to B9PartSwitch patches. The B9 Part Switch patch configs that ship with OPT make me think the drop tank is meant to have two switchers: one for fuel contents, and one more for tank style - either plain, heat shielded, or 'super' (something like that). However, the 'tank style' options do not appear in game - only the ones for switching the contents of the tank. This makes me think there's some issue with a patch, or with B9PartSwitch, or with the combination of these two switchers plus TweakScale on the same part... Or maybe one of those patches is somehow not unlocked yet (upgrades? don't even know if that's possible with B9PS) - this is a career game. Unfortunately, B9 Part Switch related patches are split over many files in OPT and OPT Reconfig and therefore difficult to round up. However, I included a new log and at least the patch related to OPTdropTank's 'tank style' in this ZIP: https://www.dropbox.com/s/e1rmzua7u6hjxwa/KSPLog2020-02-18-second.zip?dl=0 Maybe closer... Thank you for your help! Quote Link to comment Share on other sites More sharing options...
alphaprior Posted February 18, 2021 Share Posted February 18, 2021 I'm having errors in VAB with TweakScale whenever I touch something. Here is KSP.log Quote Link to comment Share on other sites More sharing options...
Lisias Posted February 18, 2021 Author Share Posted February 18, 2021 1 hour ago, alphaprior said: I'm having errors in VAB with TweakScale whenever I touch something. Here is KSP.log Yep, apparently a friction between B9PS and TweakScale. However, I didn't managed to reproduce this problem, yet, on my rig - where I try to figure out the minimum set of add'ons that trigger a problem. A too crowded installment makes specific things almost impossible to diagnose due the combinatorial explosion. However, I found something else on your rig that may be contributing, and perhaps we have a third add'on borking something on B9PS that so borks TweakScale? Or perhaps the third add'on is screweing up TweakScale, that so borks B9PS... There must be a reason I didn't reproduce the problem using only B9PS and TweakScale. In a way or another, I found this: [LOG 01:10:18.756] liquidEngine2-2.v2 added to ship - part count: 25 [LOG 01:10:27.346] KerbalEngineer -> Exception // System.NullReferenceException: Object reference not set to an instance of an object at KerbalEngineer.UIControls.PopOutElement.Update () [0x0003f] in <f7b97258edac489d9f763fc3ebcf33c6>:0 [LOG 01:10:27.346] KerbalEngineer -> at KerbalEngineer.UIControls.PopOutElement.Update () [0x0003f] in <f7b97258edac489d9f763fc3ebcf33c6>:0 KER borking on Update is bad because TweakScale needs the first Update of each part on a scene to initialise itself (it's a racing condition problem on the Awake/Start Unity thingies, the only way out of the mess was to not to race at all...), and once someone borks on the Update, it breaks the chain of Updates - anything that would run after is not run at all, and this may include TweakScale - and an uninitialised TweakScale will bork B9PS for sure on [ERR 03:01:50.064] Exception handling event onEditorShipModified in class ModuleB9PartInfo:System.NullReferenceException: Object reference not set to an instance of an o at TweakScale.TweakScale.IPartMassModifier.GetModuleMass (System.Single defaultMass, ModifierStagingSituation situation) [0x00010] in <6c196c229b7b407390d4d14556b33c91 at Part.GetModuleMass (System.Single defaultMass, ModifierStagingSituation sit) [0x00046] in <2afc64dea36946459d4707808bdac511>:0 at B9PartSwitch.ModuleB9PartInfo.UpdateFields () [0x00019] in <b85eabe067044bcb9aeabe863954a5ce>:0 at B9PartSwitch.ModuleB9PartInfo.EditorShipModified (ShipConstruct construct) [0x00006] in <b85eabe067044bcb9aeabe863954a5ce>:0 at EventData`1[T].Fire (T data) [0x000b0] in <2afc64dea36946459d4707808bdac511>:0 [EXC 03:01:50.067] NullReferenceException: Object reference not set to an instance of an object TweakScale.TweakScale.IPartMassModifier.GetModuleMass (System.Single defaultMass, ModifierStagingSituation situation) (at <6c196c229b7b407390d4d14556b33c91>:0) Part.GetModuleMass (System.Single defaultMass, ModifierStagingSituation sit) (at <2afc64dea36946459d4707808bdac511>:0) B9PartSwitch.ModuleB9PartInfo.UpdateFields () (at <b85eabe067044bcb9aeabe863954a5ce>:0) B9PartSwitch.ModuleB9PartInfo.EditorShipModified (ShipConstruct construct) (at <b85eabe067044bcb9aeabe863954a5ce>:0) EventData`1[T].Fire (T data) (at <2afc64dea36946459d4707808bdac511>:0) UnityEngine.DebugLogHandler:LogException(Exception, Object) ModuleManager.UnityLogHandle.InterceptLogHandler:LogException(Exception, Object) UnityEngine.Debug:LogException(Exception) EventData`1:Fire(ShipConstruct) EditorLogic:SetBackup() EditorLogic:StartEditor(Boolean) EditorLogic:ShipToLoadSelected(ConfigNode, LoadType) KSP.UI.Screens.CraftBrowserDialog:onPipelineFinished(ConfigNode, CraftEntry, LoadType) KSP.UI.Screens.<>c__DisplayClass126_0:<pipeSelectedItem>b__0(ConfigNode) KSPUpgradePipeline:Process(ConfigNode, String, LoadContext, Callback`1, Callback`2) KSP.UI.Screens.CraftBrowserDialog:pipeSelectedItem(CraftEntry, LoadType) KSP.UI.Screens.CraftBrowserDialog:ConfirmLoadCraft() KSP.UI.Screens.CraftBrowserDialog:onButtonLoad() UnityEngine.EventSystems.EventSystem:Update() [LOG 03:01:50.261] [Part truss-spinal-02] [ModuleB9PartSwitch 'meshSwitch'] Switched subtype to None On the other hand, and I may had missed it in the past... The KSPUpgradePipeline:Process is involved on the mess! THIS may be trigger for the problem and the reason I can't reproduce the problem on my rig - my test beds are most of the time "clean", I usually don't have artefacts from previous KSP versions around - that it's when the KSPUpgradePipeline thingy is invoked... With that on mind, I suspect that all the remaining Exceptions from B9PS and TweakScale from the same part is a consequence from that first one (for each affected part) - TweakScale just didn't initialised itself, so every call to it will bork! Oukey, now I have something to work on. https://github.com/net-lisias-ksp/TweakScale/issues/168 I also found: [WRN 02:53:06.157] [ProceduralSRB] proceduralTankSRB (ProceduralParts.ProceduralSRB):** Exception within SetBellRotation: [EXC 02:53:06.158] NullReferenceException: Object reference not set to an instance of an object ProceduralParts.ProceduralSRB.RotateAttachedPartAndNode (UnityEngine.Vector3 rotAxis, System.Single delta, System.Single adjustedDeflection) (at <997a0967cd08456e9bb ProceduralParts.ProceduralSRB.SetBellRotation (System.Single oldThrustDeflection) (at <997a0967cd08456e9bbb8ae704888efd>:0) UnityEngine.DebugLogHandler:LogException(Exception, Object) ModuleManager.UnityLogHandle.InterceptLogHandler:LogException(Exception, Object) UnityEngine.Debug:LogException(Exception) ProceduralParts.ProceduralSRB:SetBellRotation(Single) ProceduralParts.ProceduralSRB:InitializeBells() ProceduralParts.ProceduralSRB:GetInfo() KSP.UI.Screens.Editor.PartListTooltip:CreateExtendedInfo(Boolean) KSP.UI.Screens.Editor.PartListTooltip:DisplayExtendedInfo(Boolean, String) KSP.UI.Screens.Editor.PartListTooltipController:CreateTooltip(PartListTooltip, EditorPartIcon) KSP.UI.Screens.Editor.PartListTooltipController:OnTooltipSpawned(Tooltip) KSP.UI.UIMasterController:SpawnTooltip(ITooltipController) KSP.UI.PinnableTooltipController:OnPointerEnter(PointerEventData) KSP.UI.Screens.Editor.PartListTooltipController:OnPointerEnter(PointerEventData) UnityEngine.EventSystems.EventSystem:Update() But it happened only once, so I don't think Procedural Parts are involved on the mess. But it will hinder your game sooner or later, because it's borking on the Update() thingy. --- --- BEING A CHEAP stand-up guy AND SAVING A POST --- --- 6 hours ago, AccidentalDisassembly said: So far, I can at least confirm that I can now load and fly a vessel that was causing VERY strange behavior before (and is what made me start looking at the logs) - when launching it into the flight scene, the camera would go under the runway, control was lost, camera couldn't be rotated, all sorts of strange behavior, launch clock was at -16 days or something... Now, I can manipulate that vessel in the editor and also fly it; there are still some exceptions, but they're different and A LOT fewer after removing KerboKatz/ASS, RationalHydrodynamics, and PartInfo. Yeah, a lot of Exceptions had vanished from the log, including the FlightInputHandler.FixedUpdate one. I think it was a victim of the "aborted chain of events" problem when a thread dies suddenly. However, now we have a new one on the beginning of the Flight Scene: [LOG 00:33:05.347] [Scatterer][Info] Skynode switch effects to scaled mode [EXC 00:33:05.349] NullReferenceException: Object reference not set to an instance of an object UIPartActionControllerInventory.UpdateCursorOverPAWs () (at <2afc64dea36946459d4707808bdac511>:0) UIPartActionController.Update () (at <2afc64dea36946459d4707808bdac511>:0) UnityEngine.DebugLogHandler:LogException(Exception, Object) ModuleManager.UnityLogHandle.InterceptLogHandler:LogException(Exception, Object) UnityEngine.Debug:CallOverridenDebugHandler(Exception, Object) This may or be not be a problem, but I'm pretty jumpy on exceptions on event handlers nowadays. 6 hours ago, AccidentalDisassembly said: I still notice an exception from TweakScale, but I think I have narrowed it down: At first, there were no TweakScale related exceptions in the log. Then I loaded the problematic craft into the editor, manipulated only the OPTdropTank part on it, and reloaded the log - saw exceptions after this action. I changed tank size slightly, picked it up, placed it again, launched craft, I think. I just checked your previous log again, and the KSPPipelineUpgrade is not involved on your problem. So we have something else happening. Life is fun, eh? 6 hours ago, AccidentalDisassembly said: I still notice an exception from TweakScale, but I think I have narrowed it down: At first, there were no TweakScale related exceptions in the log. Then I loaded the problematic craft into the editor, manipulated only the OPTdropTank part on it, and reloaded the log - saw exceptions after this action. I changed tank size slightly, picked it up, placed it again, launched craft, I think. I have a theory about a possible reason related to B9PartSwitch patches. The B9 Part Switch patch configs that ship with OPT make me think the drop tank is meant to have two switchers: one for fuel contents, and one more for tank style - either plain, heat shielded, or 'super' (something like that). However, the 'tank style' options do not appear in game - only the ones for switching the contents of the tank. This makes me think there's some issue with a patch, or with B9PartSwitch, or with the combination of these two switchers plus TweakScale on the same part... Or maybe one of those patches is somehow not unlocked yet (upgrades? don't even know if that's possible with B9PS) - this is a career game. Nice shot. I will investigate this hypothesis. But I think this is not the only problem, as TweakScale is still borking on the following parts: AirplanePlus/Parts/Engine/Rotorwing/chinookprop/part/chinookprop AirplanePlus/Parts/Engine/Rotorwing/coaxialprop/part/coaxialprop Mk2Expansion/Parts/Utility/RCS/StabilityControl/M2X_SCRCS Interestingly, one less part than the last log. Can you send me also the MM cache for these parts? Or just the whole shebang, way easier for you and I have tools to find and extract what I want without too much fuss. 6 hours ago, AccidentalDisassembly said: Unfortunately, B9 Part Switch related patches are split over many files in OPT and OPT Reconfig and therefore difficult to round up. However, I included a new log and at least the patch related to OPTdropTank's 'tank style' in this ZIP: https://www.dropbox.com/s/e1rmzua7u6hjxwa/KSPLog2020-02-18-second.zip?dl=0 The MM Cache for the part will help a lot on this, as I can forfeit things on it and reload to make quick tests instead of play cat and mouse with the patches themselves. Boy, I would love Module Manager adding support for "hot patches" - i.e., patches you can apply with KSP running. That would make my life way easier. Something to think about. 6 hours ago, AccidentalDisassembly said: Maybe closer... Thank you for your help! Definitively closer. We are gradually zeroing on the problems. Welcome! Quote Link to comment Share on other sites More sharing options...
alphaprior Posted February 18, 2021 Share Posted February 18, 2021 It's a strange thing. Don't know what happens in KSP.log during the game but those errors in VAB screen don't appear always. What I do when I see errors is to clean Module Manager cache files, and PartDatabase. Then game seems to run smoothly. But not for long. After some VAB editing, errors re-appear. Something else, that happened 2 weeks ago during a spotlight installation on my Space Station... well it exploded! The entire station exploded. I reloaded several times and station was exploding every time not matter where I was installing the spotlight. At first I thought it was a USI greenhouse issue because I had seen an error related to it and something about IScalarModule. I told RoverDude but he said something else not related to his mod was responsible. Maybe it's TweakScale? I can't provide more info related to this or any log but TweakScale is a possibillity since modifies other parts. Quote Link to comment Share on other sites More sharing options...
Lisias Posted February 18, 2021 Author Share Posted February 18, 2021 1 hour ago, alphaprior said: It's a strange thing. Don't know what happens in KSP.log during the game but those errors in VAB screen don't appear always. What I do when I see errors is to clean Module Manager cache files, and PartDatabase. Then game seems to run smoothly. But not for long. After some VAB editing, errors re-appear. It's one of the reasons I'm considering races conditions on the whole system. Without the MM cache files, things need to be rebuilt from scratch, what takes time, that can be somewhat inducing delays that are masking the racing conditions. With the MM caches, a lot of processing is not executed, so that lucky delays are not issued, and then things start to stomp each other's toes. 1 hour ago, alphaprior said: Something else, that happened 2 weeks ago during a spotlight installation on my Space Station... well it exploded! The entire station exploded. I reloaded several times and station was exploding every time not matter where I was installing the spotlight. This is an already known problem, and it's on KSP 1.11 for sure. Hummm... It was reported by you! 1 hour ago, alphaprior said: At first I thought it was a USI greenhouse issue because I had seen an error related to it and something about IScalarModule. I told RoverDude but he said something else not related to his mod was responsible. Maybe it's TweakScale? I can't provide more info related to this or any log but TweakScale is a possibillity since modifies other parts. TweakScale is a hell of a nosy Module, we shove this thing on everything and it's pretty used - and so, its exposition is huge, as it's almost always present when something bad happens. Ok, some times it's TweakScale, but most of the times, it's not - TweakScale is usually the messenger of the Bad News - it needs a bullet proof vest, as it appears. This specific error appears to be facilitated by TweakScale, as it makes easier to create the conditions in which it happens. I made a hell of a research with a specific use case I detected while playing a bit, and by any angle I observe it, my conclusion is the same: something is borking up specific use cases on the code that looks for the heaviest part of the vessel. There're some reports about this happening with Same Vehicle Interaction active when there are some specific parts on the craft (curiously, some os these parts are also part of the problem I detected above), you can see about it here and on this video: https://www.twitch.tv/ej_sa/clip/SweetDarkTarsierYouWHY There were also reports about ICAs (Instantaneous Craft Annihilations ) on some add'ons on KSP 1.11.0, that I worked around using KSP Recall pretty easily, what suggests there're a lot of failed initialisations on KSP (KSP 1.11.1 just covered the specific use case detected, there're lot more things exploding at similar situations, what hints the failing initialisation process). Another possible source of problems for the affected Add'On is that nowadays KSP has harcoded support for some features, making it impossible to replace them with alternatives - and most of the time, these new features are completely incompatible with third-party add'ons, so you can't have both on the same part! (and with at least one hardcoded, you can't replace it on the part...) In all these cases, removing the TweakScale from the equation when it was there didn't solved the problem - at the best, made the problem hard to be detected, but the problem it's still there. So, for these very specific set of problems you describe on your last post, there's no hard evidence that TweakScale is involved - it's the other way around, removing TweakScale when it was installed didn't solved the problems. Quote Link to comment Share on other sites More sharing options...
alphaprior Posted February 18, 2021 Share Posted February 18, 2021 40 minutes ago, Lisias said: This is an already known problem, and it's on KSP 1.11 for sure. Hummm... It was reported by you! Yeap I find the issue and reported still don't know the cause but those spotlights were reverted to older version probably another patch. But recently I had the same behaviour on a ship while I was attaching parachutes. I'm not a programmer so my understanding the issues are limited. But I have a good experience or perhaps bad... with mods in various games. At least in KSP it keeps working instead of entirely ruining the game. I can alwas reload and continue even with errors. To remove TweakScale or some other mods it's not possible because they remove their dependecies then I won't be able to load my savegame. Anyway I made my report I hope it helps and you solve problems as long it takes. Quote Link to comment Share on other sites More sharing options...
AccidentalDisassembly Posted February 18, 2021 Share Posted February 18, 2021 3 hours ago, Lisias said: Nice shot. I will investigate this hypothesis. But I think this is not the only problem, as TweakScale is still borking on the following parts: AirplanePlus/Parts/Engine/Rotorwing/chinookprop/part/chinookprop AirplanePlus/Parts/Engine/Rotorwing/coaxialprop/part/coaxialprop Mk2Expansion/Parts/Utility/RCS/StabilityControl/M2X_SCRCS Interestingly, one less part than the last log. Can you send me also the MM cache for these parts? Or just the whole shebang, way easier for you and I have tools to find and extract what I want without too much fuss. The MM Cache for the part will help a lot on this, as I can forfeit things on it and reload to make quick tests instead of play cat and mouse with the patches themselves. Boy, I would love Module Manager adding support for "hot patches" - i.e., patches you can apply with KSP running. That would make my life way easier. Something to think about. Definitively closer. We are gradually zeroing on the problems. Welcome! Here is the (sadly, also huge) MM cache - I notice on OPTdropTank that there *are* two B9PartSwitch modules, but only one appears in game... very strange: https://www.dropbox.com/s/myiu2ng5vbkam9e/ModuleManager_TSTracking.ConfigCache?dl=0 Quote Link to comment Share on other sites More sharing options...
Lisias Posted February 18, 2021 Author Share Posted February 18, 2021 1 hour ago, alphaprior said: Yeap I find the issue and reported still don't know the cause but those spotlights were reverted to older version probably another patch. But recently I had the same behaviour on a ship while I was attaching parachutes. Send me that ship! With a concrete case on hands, I can torture KPS into a confession test it again and again until I find a cause. 1 hour ago, alphaprior said: I'm not a programmer so my understanding the issues are limited. But I have a good experience or perhaps bad... with mods in various games. At least in KSP it keeps working instead of entirely ruining the game. I can alwas reload and continue even with errors. I feel your pain. There're some developers that believe they don't have any kind of responsibility on what they give you to run on your machine. Of course, there're no legal responsibility (no argument on it) - but if what you deliver consistently breaks the user's savegames, users will just stop using the toys you make - and so, why bother making them at first place? In a way or another, keeping things working between multiple releases is hard for multiple reasons (being the technical ones the lesser ones). But, as once said Kennedy, "We choose to go to the Moon in this decade and do the other things, not because they are easy, but because they are hard; because that goal will serve to organize and measure the best of our energies and skills". 1 hour ago, alphaprior said: To remove TweakScale or some other mods it's not possible because they remove their dependecies then I won't be able to load my savegame. Exactly my point! 2 hours ago, AccidentalDisassembly said: Here is the (sadly, also huge) MM cache - I notice on OPTdropTank that there *are* two B9PartSwitch modules, but only one appears in game... very strange: Way interesting. You may had diagnosed the problem (perhaps), I will try to confirm it. I will get back to you soon. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.