Mjkh10 Posted November 8, 2024 Share Posted November 8, 2024 (edited) I've looked at the logs, and there seems to be more than one problem. I don't know how to fix it, though. KSP.log: https://www.dropbox.com/scl/fi/ppm7k0m9evgvhjlqn3p86/KSP.log?rlkey=h9dwx5gpbkat3fc8e2lrm3zzd&st=5nn70dtb&dl=0 Player.log: https://www.dropbox.com/scl/fi/anp8ezpbflvdvjcfqzf9f/Player.log?rlkey=tkh7dlo2djvztyjed6qg6v6cv&st=ly3122b0&dl=0 Modlist screenshot 1: https://www.dropbox.com/scl/fi/r1i6sk9lm1na08du9lh4e/Screenshot-99.png?rlkey=ihs40xwyb1nz1pgcba0sq4wiw&st=oo9az7a5&dl=0 Modlist screenshot 2: https://www.dropbox.com/scl/fi/m27fvc4f8sgtavfsnj7qu/Screenshot-100.png?rlkey=tsw6nrqccc1fl0ayict4ous6n&st=tlm7euik&dl=0 Edit: Forgot to mention this is my first time modding the game Edited November 8, 2024 by Mjkh10 Quote Link to comment Share on other sites More sharing options...
Gargamel Posted November 8, 2024 Share Posted November 8, 2024 Moved to tech support modded Quote Link to comment Share on other sites More sharing options...
Lisias Posted November 9, 2024 Share Posted November 9, 2024 4 hours ago, Mjkh10 said: I've looked at the logs, and there seems to be more than one problem. I don't know how to fix it, though. Hi, I had looked into the problem. KSP.log could not help, because this was a Process Crash, something beyound Unity's Mono - it was killed before being able to log something. You can ignore what you found on it, these ones are harmless or not a problem at all. Fortunately, you provided us with the Player.log - the C++ land have more robust Exception Handling, and logged the event: Crash!!! SymInit: Symbol-SearchPath: '.;D:\games\Kerbal.Space.Program.v1.12.3.3173.Incl.ALL.DLCs;D:\games\Kerbal.Space.Program.v1.12.3.3173.Incl.ALL.DLCs;C:\WINDOWS;C :\WINDOWS\system32;SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols;', symOptions: 534, UserName: 'xxxx' OS-Version: 10.0.0 D:\games\Kerbal.Space.Program.v1.12.3.3173.Incl.ALL.DLCs\KSP_x64.exe:KSP_x64.exe (00007FF60FA40000), size: 667648 (result: 0), SymType: '-deferred-', PDB: '', fileVersion: 2019.4.18.4260 <yada yada yada> 0x00007FFD18586193 (UnityPlayer) UnityMain ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 00007FFD18033F04) 0x00007FFD18033F04 (UnityPlayer) (function-name not available) ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 00007FFD180361E1) 0x00007FFD180361E1 (UnityPlayer) (function-name not available) ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 00007FFD18110791) 0x00007FFD18110791 (UnityPlayer) (function-name not available) 0x000001CC74B82F00 (Mono JIT Code) (wrapper managed-to-native) UnityEngine.AssetBundle:LoadFromMemory_Internal (byte[],uint) 0x000001CC74B82E4B (Mono JIT Code) UnityEngine.AssetBundle:LoadFromMemory (byte[]) <yada yada yada> 0x00007FFD184ED5BC (UnityPlayer) UnityMain ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 00007FFD182A272E) 0x00007FFD182A272E (UnityPlayer) (function-name not available) ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 00007FFD182A148A) 0x00007FFD182A148A (UnityPlayer) (function-name not available) ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 00007FFD182A553C) 0x00007FFD182A553C (UnityPlayer) (function-name not available) 0x00007FFD182A902B (UnityPlayer) UnityMain ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 00007FF60FA411F2) 0x00007FF60FA411F2 (KSP_x64) (function-name not available) 0x00007FFDA15D7374 (KERNEL32) BaseThreadInitThunk ERROR: SymGetSymFromAddr64, GetLastError: 'The specified module could not be found.' (Address: 00007FFDA339CC91) 0x00007FFDA339CC91 (ntdll) (function-name not available) What appears to had happened is a catastrophic failure due lack of memory. The interesting bit is "UnityEngine.AssetBundle:LoadFromMemory (byte[])", the crash happened while trying to load something, probably this: woomerang_launch_site.prefab (Filename: C:\buildslave\unity\build\Runtime/Export/Debug/Debug.bindings.h Line: 35) Scenes: (Filename: C:\buildslave\unity\build\Runtime/Export/Debug/Debug.bindings.h Line: 35) kspMissionEditor.unity (Filename: C:\buildslave\unity\build\Runtime/Export/Debug/Debug.bindings.h Line: 35) So, it's really probably lack of memory. You need to uninstall something. However, you can try something first before cutting out some fat from your GameData: If you don't use anything but the parts from Making History, you can convince KSP to ignore the Scene Editor from MH, as it eats some memory. Open Windows Explorer, go to the directory D:\games\Kerbal.Space.Program.v1.12.3.3173.Incl.ALL.DLCs\GameData\SquadExpansion\MakingHistory and rename the file makinghistory.kspexpansion to makinghistory.kspexpansion.bkp This will inhibit KSP from loading the Scene Editor saving you about 800MB to 1GB of CPU RAM. However, you still have a somewhat heavy installment for a 8G RAM machine. I suggest to upgrade the memory if possible. In the mean time, if this happens again, you will surely need to remove some memory intensive add'ons from your GameData, sorry! 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.