Lisias

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

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

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

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

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

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

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

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

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

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

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

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

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

About KSP2 Patch Two:

I'm away from my personal machine now, so I'm guessing - will inspect the logs later. But what you describes looks like GPU device driver crash. Perhaps due VRAM exhaust, perhaps due overheating, or Kraken knows what else. Install a temperature monitor and be sure to have it visible all the time. Stop gaming in the very instant it reaches the manufacturer's advised temperature limit. If the problem is overheating, it's time to do some preventive maintenance on the GPU card (cleaning up dust from the sinkers and replacing old fans - better hire a skilled technician for that). If temperature never reaches the "boiling" point on crash, then my next guess is VRAM exhaust together RAM exhaust. When you abuse the VRAM, the GPU device driver starts to borrow RAM from the CPU to use as a poor's man VRAM extension. This is troublesome because, besides pressuring an already under heavy pressure Virtual Memory Manager, the speed in which the GPU access CPU's RAM is some orders of magnitude slower than when accessing its VRAM. And this makes everything slower including to the CPU that is suffering from contention (i.e., it can't access its RAM when the GPU is doing it). Special code under Critical Sections that doesn't expect being halted on accessing its RAM may go bonkers and crash. Try to lower the Texture Quality on the KSP Settings page to see if things get better. Humm... An old AMD GPU driver is known to induce GPU overheating. If you are using AMD, check if your device driver version is prone to this problem. https://community.amd.com/t5/drivers-software/driver-causes-overheating/td-p/402596 — — — @Infinite_Maelstrom, I got the logs. Source Windows Summary Hardware error Date .17/.03/.2023 01:33 AM Status Not reported Description A problem with your hardware caused Windows to stop working correctly. Problem signature Problem Event Name: LiveKernelEvent Code: 1b8 Parameter 1: 1 Parameter 2: 0 Parameter 3: 0 Parameter 4: 0 OS version: 10_0_19045 Service Pack: 0_0 Product: 768_1 OS Version: 10.0.19045.2.0.0.768.101 Locale ID: 5129 Looks like an issue in the NVIDIA's device driver: https://linustechtips.com/topic/1404005-1a8-and-1b8-livekernelevents-crashing-the-gpu-drivers-please-help/ When did you updated the gpu device driver by the last time? In the link I posted, it's suggested that rolling back to version 473 fixed the issue for someone...

I did it myself a ton - on GTA IV . (loved my PS3). Boy, life imitates art. Things like this promotes games as a form of art.

This clip is so woderfully 80's… The Mission - The Serpent Kiss.

Sounds like the swapfile is getting without space for growing. Usually the swapfile is set to be on the boot drive, and it's nearly full in your case. @jimmymcgoochie's hunch appears to be right. You need to have at least the same amount of memory as free disk space on the drive where th4 swapfile is to be safe on heavy demand. Alternatively you move the swapfile itself to other disk. I like to create a dedicated volume on my fastest disk for the swapfile. Give this a try: https://www.windowscentral.com/how-move-virtual-memory-different-drive-windows-10

Hi. You are using a too old TweakScale version, the 2.4.6.2 is terribly outdated. Install the latest one. I also found MiniAVC V1.x In your GameData. This one was known to play havoc in the past. I suggest you remove all MiniAVC dlls from your game data. When this problem started to happen? — — POST EDIT — — I just fired the latest TweakScale, with the latest TweakScaleCompanion ÜberPaket, with the latest Waterfall (and so the DLLs that triggered the error on your log would be loaded, and they were). There's no problems on the latest releases of these add'ons. The problems appears to be, in fact, the MiniAVC v1 and the pretty old TweakScale version. Please update TweakScale, be sure to be using the latest TweakScaleCompanion_Frameworks (or just install the ÜberPaket and forget about dependencies) and get rid of all MiniAVC.dll instances from your GameData. Then publish a new KSP.log if anything else goes wrong. — — POST POST EDIT — — You also have more than one ModuleManager installed!!! [LOG 17:23:24.398] Load(Assembly): GameData/ModuleManager.4.1.4 [LOG 17:23:24.398] AssemblyLoader: Loading assembly at D:\Steam\steamapps\common\Kerbal Space Program\GameData\GameData\ModuleManager.4.1.4.dll [LOG 17:23:24.399] AssemblyLoader: KSPAssembly 'ModuleManager' V2.5.0 [LOG 17:23:24.399] Load(Assembly): GameData/ModuleManager.4.2.2 [LOG 17:23:24.399] AssemblyLoader: Loading assembly at D:\Steam\steamapps\common\Kerbal Space Program\GameData\GameData\ModuleManager.4.2.2.dll [LOG 17:23:24.400] AssemblyLoader: KSPAssembly 'ModuleManager' V2.5.0 It's not advisable to have multiple ModuleManager versions in your rig. Different KSP versions behave differently about having more than one Assembly on the system. It just doesn't worth the trouble. Remove GameData/ModuleManager.4.1.4.dll from your GameData.

Found it! You need to add a module to the project: https://github.com/Richi0D/Kerbalcontroller Out of curiosity, the missing define is on this file: https://github.com/Richi0D/Kerbalcontroller/blob/master/KerbalController.ino

Juno: New Origins! (ducking under the desk)

You need to add Serial support to your project. Check the documentation here: https://www.arduino.cc/reference/en/language/functions/communication/serial/ Follows a nice tutorial about how to handle serial communications with an Arduino. I think it will worth reading it! https://www.ladyada.net/learn/arduino/lesson4.html

Well, nothing wrong on the ConfigCache - I had seen some issues on some ModuleCaches lately with some nodes really screwed up. Really, really screwed up. But yours are not one of them, your ConfigCache is sound. So whatever is screwing your Crew, it may be related to that Exceptions I detected. You are very welcome, my friend. Drop a post here (or mention me using @Lisias when in another thread) anytime! Cheers! — — — — Yep, found it: [LOG 11:48:28.602] [TweakScale] WARNING: **FATAL** Found a showstopper problem on Knes.Structural.Guepiere (Guepiere Tri-Coupler). [LOG 11:48:28.602] [TweakScale] ERROR: **FATAL** Part Knes.Structural.Guepiere (Guepiere Tri-Coupler) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0 [LOG 11:48:28.602] [TweakScale] WARNING: **FATAL** Found a showstopper problem on Knes.Structural.Kylda (Payload Adapter K-250 "Kylda"). [LOG 11:48:28.602] [TweakScale] ERROR: **FATAL** Part Knes.Structural.Kylda (Payload Adapter K-250 "Kylda") has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0 [LOG 11:48:28.603] [TweakScale] WARNING: **FATAL** Found a showstopper problem on Knes.Aero.NoseCone.A (EAP Nose Cone for Ariane 5). [LOG 11:48:28.603] [TweakScale] ERROR: **FATAL** Part Knes.Aero.NoseCone.A (EAP Nose Cone for Ariane 5) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0 [LOG 11:48:28.604] [TweakScale] WARNING: **FATAL** Found a showstopper problem on Knes.Aero.NoseCone.B (Knes Nose Cone). [LOG 11:48:28.604] [TweakScale] ERROR: **FATAL** Part Knes.Aero.NoseCone.B (Knes Nose Cone) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0 [LOG 11:48:28.604] [TweakScale] WARNING: **FATAL** Found a showstopper problem on Knes.Booster.EAP (Ariane 5 "EAP" Solid Fuel Booster). [LOG 11:48:28.604] [TweakScale] ERROR: **FATAL** Part Knes.Booster.EAP (Ariane 5 "EAP" Solid Fuel Booster) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0 [LOG 11:48:28.604] [TweakScale] WARNING: **FATAL** Found a showstopper problem on Knes.Booster.P80 (P80 Solid Fuel Booster). [LOG 11:48:28.604] [TweakScale] ERROR: **FATAL** Part Knes.Booster.P80 (P80 Solid Fuel Booster) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0 [LOG 11:48:28.604] [TweakScale] WARNING: **FATAL** Found a showstopper problem on Knes.Booster.Pushotron (Pushotron). [LOG 11:48:28.604] [TweakScale] ERROR: **FATAL** Part Knes.Booster.Pushotron (Pushotron) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0 [LOG 11:48:28.604] [TweakScale] WARNING: **FATAL** Found a showstopper problem on Knes.Command.Cortex (Probe Core "Cortex" Avionics System). [LOG 11:48:28.604] [TweakScale] ERROR: **FATAL** Part Knes.Command.Cortex (Probe Core "Cortex" Avionics System) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0 [LOG 11:48:28.604] [TweakScale] WARNING: **FATAL** Found a showstopper problem on Knes.Engine.EPS (RS-72 "Aestus" Liquid Fuel Engine). [LOG 11:48:28.605] [TweakScale] ERROR: **FATAL** Part Knes.Engine.EPS (RS-72 "Aestus" Liquid Fuel Engine) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0 [LOG 11:48:28.605] [TweakScale] WARNING: **FATAL** Found a showstopper problem on Knes.Engine.Vulcain (Ariane 5 "Vulcain" Liquid Fuel Engine). [LOG 11:48:28.605] [TweakScale] ERROR: **FATAL** Part Knes.Engine.Vulcain (Ariane 5 "Vulcain" Liquid Fuel Engine) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0 [LOG 11:48:28.605] [TweakScale] WARNING: **FATAL** Found a showstopper problem on Knes.Fuel.Tanks.EPC (Ariane 5 EPC). [LOG 11:48:28.605] [TweakScale] ERROR: **FATAL** Part Knes.Fuel.Tanks.EPC (Ariane 5 EPC) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0 [LOG 11:48:28.605] [TweakScale] WARNING: **FATAL** Found a showstopper problem on Knes.Fuel.Tanks.Medium (Ariane "Behaviour" Medium Fuel Tank). [LOG 11:48:28.605] [TweakScale] ERROR: **FATAL** Part Knes.Fuel.Tanks.Medium (Ariane "Behaviour" Medium Fuel Tank) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0 [LOG 11:48:28.605] [TweakScale] WARNING: **FATAL** Found a showstopper problem on Knes.Fuel.Tanks.Small (Ariane "Slender" Small Fuel Tank). [LOG 11:48:28.605] [TweakScale] ERROR: **FATAL** Part Knes.Fuel.Tanks.Small (Ariane "Slender" Small Fuel Tank) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0 [LOG 11:48:28.608] [TweakScale] WARNING: **FATAL** Found a showstopper problem on Knes.Command.Minus (Probe Core "Minus" Avionics System). [LOG 11:48:28.609] [TweakScale] ERROR: **FATAL** Part Knes.Command.Minus (Probe Core "Minus" Avionics System) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0 [LOG 11:48:28.609] [TweakScale] WARNING: **FATAL** Found a showstopper problem on Knes.Fuel.Tanks.1875.H10 (H10 "Belenos" Fuel Tanks). [LOG 11:48:28.609] [TweakScale] ERROR: **FATAL** Part Knes.Fuel.Tanks.1875.H10 (H10 "Belenos" Fuel Tanks) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0 Problem: I had authored the KNES TweakScale patches, and I would had detected such major screw up on my last commit (I test things before shipping). Well, most of the time at least… I found that one of the screwed parts is being patched by two files from KNES: [LOG 11:39:37.335] Applying update Knes/Compatibility/Tweakscale/Knes_Tweakscale/@PART[Knes_Structural_Guepiere]:NEEDS[TweakScale] to Knes/Parts/Core/Adapters/_Knes_Structural_Guepiere.cfg/PART[Knes_Structural_Guepiere] [LOG 11:39:50.569] Applying update Knes/Compatibility/Tweakscale/Knes-Core_TweakScale/@PART[Knes_Structural_Guepiere]:NEEDS[TweakScale]:FOR[Knes] to Knes/Parts/Core/Adapters/_Knes_Structural_Guepiere.cfg/PART[Knes_Structural_Guepiere] Giving a peek on the job I had done https://github.com/AstroWell/Knes/tree/master/GameData/Knes/Compatibility/Tweakscale I detected that there's no file called "Knes_TweakScake.cfg". It's really some time since I had done that patches, but I think I may had revamped the whole thing at some point, and so this file was removed from the distribution. This means that you need to completely uninstall KNES and re-install it from scratch to get rid of any leftovers from the last version that were removed from the package. On a side note, it's usually a better idea to completely remove all old files before installing a new version. That would had prevented you from taking this hit - but, granted, I do it myself now and then too, it's the reason I wrote so many Sanity Checks, I do it all the time too!!! I also detected that you have two Module Managers installed, and this is terrible for a lot of reasons, being the most immediate one that you are using the oldest one (as the newest one is deactivated by the KSP's Assembly Loader/Resolver), and so you are not covered by bug fixes and new features from 4.2.2 (besides having it installed!): [LOG 11:39:14.791] Load(Assembly): /ModuleManager.4.2.1 [LOG 11:39:14.791] AssemblyLoader: Loading assembly at C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program\GameData\ModuleManager.4.2.1.dll [LOG 11:39:14.792] AssemblyLoader: KSPAssembly 'ModuleManager' V2.5.0 [LOG 11:39:14.792] Load(Assembly): /ModuleManager.4.2.2 [LOG 11:39:14.792] AssemblyLoader: Loading assembly at C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program\GameData\ModuleManager.4.2.2.dll [LOG 11:39:14.793] AssemblyLoader: KSPAssembly 'ModuleManager' V2.5.0 You need to delete GameData/ModuleManager.4.2.1.dll . I think you should install ModuleManagerWatchDog, it would had prevented this mishap for sure. Cheers!

No Kerbals again? I'm starting to think you have an incompatibility problem between two or more add'ons in your rig… Anyway. From the TweakScale point of view, you have Firespitter installed. There're some glitches on Firespitter that demands its Companion to be installed, otherwise things will not work too well on your gaming. Install this thing: https://github.com/net-lisias-ksp/TweakScaleCompanion_FS/releases Or just install the ÜberPaket and forget about it: https://github.com/net-lisias-ksp/TweakScaleCompanion/releases (this one have all Companions installed at once, on a convenient package). I'm also getting this exception about Burst: [ERR 14:30:32.204] [KSPBurst]: Burst compiler terminated with an exception [EXC 14:30:32.247] Win32Exception: ApplicationName='/Users/rhycecomley/Library/Application Support/Steam/steamapps/common/Kerbal Space Progr <yada yada yada> Native error= Cannot find the specified file System.Diagnostics.Process.StartWithCreateProcess (System.Diagnostics.ProcessStartInfo startInfo) (at <ef151b6abb5d474cb2c1cb8906a8b 5a4>:0) System.Diagnostics.Process.Start () (at <ef151b6abb5d474cb2c1cb8906a8b5a4>:0) (wrapper remoting-invoke-with-check) System.Diagnostics.Process.Start() KSPBurst.KSPBurst.RunBurstCompiler (System.String burstExecutable, System.Collections.Generic.IEnumerable`1[T] args, System.String workingDir, System.String logDir) (at <c8b5fe2baff6415cb73ea658bdb44b4c>:0) KSPBurst.KSPBurst.Generate () (at <c8b5fe2baff6415cb73ea658bdb44b4c>:0) System.Threading.Tasks.Task`1[TResult].InnerInvoke () (at <9577ac7a62ef43179789031239ba8798>:0) System.Threading.Tasks.Task.Execute () (at <9577ac7a62ef43179789031239ba8798>:0) Rethrow as AggregateException: One or more errors occurred. UnityEngine.DebugLogHandler:LogException(Exception, Object) ModuleManager.UnityLogHandle.InterceptLogHandler:LogException(Exception, Object) UnityEngine.Debug:LogException(Exception) KSPBurst.<BurstCompile>d__20:MoveNext() UnityEngine.SetupCoroutine:InvokeMoveNext(IEnumerator, IntPtr) This one you will need to reach the KSPBurst maintainers for help, I don't have the slightest idea about what's happening. it seems as there's something missing, but I'm at lost on this one. Perhaps KSPBurst doesn't works on MacOS? Interestingly, I'm find a lot of "Input String not in correct format" Exceptions on your log, like this one: [LOG 14:30:42.694] PartLoader: Compiling Part 'AtomicTech/radioactiveGreenhouse/Parts/PSAGreenhouse25/PSAGreenhouse25' [ERR 14:30:42.697] Module SoilRecycler threw during OnLoad: System.FormatException: Input string was not in a correct format. at System.Number.ParseSingle (System.String value, System.Globalization.NumberStyles options, System.Globalization.NumberFormatInfo numfmt ) [0x00083] in <9577ac7a62ef43179789031239ba8798>:0 at System.Single.Parse (System.String s, System.Globalization.NumberStyles style, System.Globalization.NumberFormatInfo info) [0x00000] in <9577ac7a62ef43179789031239ba8798>:0 at System.Single.Parse (System.String s) [0x0000b] in <9577ac7a62ef43179789031239ba8798>:0 at ResourceRatio.Load (ConfigNode node) [0x00041] in <46478292153440df94e04a2a2ddd1062>:0 at BaseConverter.OnLoad (ConfigNode node) [0x00101] in <46478292153440df94e04a2a2ddd1062>:0 at PartModule.Load (ConfigNode node) [0x001ab] in <46478292153440df94e04a2a2ddd1062>:0 And in more than one Add'On, including one that I had diagnosed recently and this problem didn't happened at that time! Please send me your ModuleManager.ConfigCache so I can give this a peek - there's something fishy on these Exceptions!

Reach the guys on their own thread, most Authors follow only their threads to save time. I only found your issue because a Fellow Kerbonaut hinted me in PVT! Cheers!