Cossus

After deleting MMPatch in C:\GOG Games\KSP_Test\PluginData\ModuleManager, nothing has changed, and new 400 MB KSP log was recorded along with new 300 MB MMPatch, when I succesfully launched the game, loaded the save and then exit.

Not yours, in fact. I kept in mind that KSPe is one of a few mods requiring from user some actions beyond GameData during installation, but I just wanted to keep as many folders as possible in a stock form. Now I have a fresh KSP log... and it is still huge. Despite the strings on the loading screen differ at this time, they were without ":FOR" (there is also no string from the quote above in the log). After launching the game, I also loaded the save and ensure that there is no FPS glitch while mounting certain engines in the VAB.

Here it is.

Lisias, Thanks a lot for trying to solve my mods assembly problem! After some simple actions it has just vanished for me as well... I really apologize I took up so much of your time, but I think it's really unexpected for everybody who is playing KSP that the cause of the crash (which is still enigmatic for me) is somewhere out of GameData folder. What exactly I made: 0. Updated all the mods from my previous message, with no result (crash). 1. Installed a fresh vanilla game from setup files (not via simple copying, true installation) and succesfully ran it. 2. Copied the whole GameData folder (also Music and Playlists folders...) from the "crashing" copy of the game to the fresh one. 3. Succesfully launched it, changed the settings to make them like previous, exit the game, copied the folder with JNSQ save in the saves folder. 4. Succesfully launched the game again, loaded the save, checked whether two my rovers on Mun and Minmus working allright, and whether their surrounding is eyecandy. Than switched into VAB, opened a craft with the engines (there are lots of such engines, of course...) caused initial FPS glitch, removed them and mounted again, with no FPS drops. Launched the rocket to ensure that I have beautiful Waterfall engine plumes. 5. Reloaded the game again two or three times to be sure that the crash is no more happens. I don't know whether you want to know the root causes of this problem at all costs, but if yes, I'll keep the "crashing" copy of the game intact for some time, I may also upload any folders and/or files in it if you're interested in. I can also upload KSP log and Player log from the last succesfull launch of the game, they are unexpectedly huge, about 500 MB...

Probably a noob question, but if you're using only my partial assembly, maybe it includes Kerbalism and SystemHeat, but not zKerbalismSystemHeat? Can this cause problems with loading thread (a problem which I still havent's seen on my PC)? UPD: I've also checked manually which of mods from my assembly have updated past few days, but without re-intstalling them, here they are: - Cryogenic engines with all its lots of GameData folders... - JNSQ volumetrics - Kerbal Joint Reinforcement - Near Future Launch Vehicles - Near Future Spacecraft - Rational Resources

OK, thanks a lot! So now I'll just wait and see which problem(s) and/or solution(s) you will find!

I've found that my trash bin is totally full and removed everything. After that and reload, it becomes 152 GB of free space on the disk. But I still have the same crash, here it is a fragment of the error log like above, but with actual numbers:

It worth noting that when I temporarily removed some mods from GameData, the number of last lines in KSP log might vary a bit, as well as its size, from 160 to 165 kb. One time the line about Universal storage was last but one, so I think you're right and the reason of the crash is somewhere else but in the last lines of the log... Fetched player and error logs from the fresh crash. I've just in case checked free space on SDD (70+ GB), size of the swap file (55 GB) and examined whether anything will change after temporal removing of the one of the largest mod folder (BDB) in GameData, the answer is no.

Thank you for a quick reply, I've edited my first post to include logs on Google.Drive, but anyway, just in case, here are the two fresh logs obtained just now: the first, from my over-modded JNSQ mod assembly, with quick crash and the second, from the succesfully loaded almost vanilla minimally modded game. But I saw orange warnings about "...19x" at the upper right corner of loading screen at the start before any pictures are emerging. Here it is the mod list from the second assembly, but I suspect that files in some other folder (because I've simply copied the first game assembly without GameData*) or in AppData folder may cause these warnings: 000_Harmony; 999_KSP-Recall; 000_KSPe; ModuleManager; ModuleManagerWatchDog; Squad; SquadExpansion; TweakScale; TweakScale Companion; 000_KSPe.dll; 001_KSPe.dll; 666_ModuleManagerWatchDog.dll; 999_Scale_Redist.dll; ModuleManager.dll *also emptied "saves", "Logs" and "PluginData" folders, with subsequent copying in the latter of ModuleManagerWatchDog.cfg as it recommended in installation instructions --------------------- UPD: Yes, I'm launching KSP from SSD and it's the only hard drive on my notebook (which is from Asus Zenbook series).

Yes, it was a bit laggy... Done!

Hello everybody and the author, today I've spoiled my JNSQ KSP mods assembly, luckily I'm on the very start. After updating of actual mods and fine-tuning the game, mostly in graphical part, I've noticed massive fps drops in the VAB after adding some engines to the craft. I've found that some problems with Waterfall/TweakScale may cause this drop, so I've replaced "Frameworks" folder in Tweak Scale with the freshest one, which caused crash less than in 1 minute after I've started KSPx64.exe. Reverting this doesn't help! An old "Frameworks" folder now has reproduced the same crash. I've then updated the whole TweakScale Companion (including Frameworks), and just in case re-installed TweakScale, KspE with all dependencies and so on... nothing changes. It seems that my problem is close to this one... I've also tried to find whether any error in log became fatal despite it wasn't during previous succesful load and removed (separately) KAX, Contract Configurator and its dependent mods, UmbraSpaceTechnologoies folder, but the crash has persisted. So I now may only asc for help on this forum, with GameData folder screenshot and KSP log attached. I've also made like-a-new copy of KSP via copying of every folder from the old one but GameData (except Squad, SquadExpansion) and a pair of others which the game doesn't need. Then I've installed all the mods but the least two from the link (Crash to desktop with version 2023.03.28.3 #6) above, and despite the game started succesfully, I've seen a bit warning sings on the loading screen. Caution, the log is very large.