KSP Crash and takes a lot of time to load

[PalowPower]

After i installed some Mods, KSP took so long to load. Stock KSP loads in like 10 - 20 Seconds. 

And there are only 59 Mods. Can someone help me please?

LOG: https://mega.nz/file/1GgmiaLQ#ooN9lAcaxOx49EfXIt0a1kBG_yenysMs58mQNqlvOG0

Also: KSP Takes very long to load it with mods on my new PC (it's like 2 or 3 Month old) but my PC is pretty good i guess.

[Guest]

Your computer is fine (more than fine). It’s an unfortunate consequence of running lots of mods especially part mods which you have a few. So you either have to get rid of some or just accept it. Some users have reported load times of up to 20 mins so you’re not alone.

The only thing I did notice is there are a few miniAVC checks going on. That’s supposed to be buggy now so I would delete all those from your mod folders or install the miniAVC disabling mod as those might be slowing loading down unnecessarily.

[Barar]

 

You are using the latest version of Kerbal Space Program - 1.11.2.3077

Logs show.

Environment Info
Win32NT 7FFFFFFFFFFFFFFF  Args: KSP_x64.exe -force-d3d9

Not sure why you have this in your arguments --> -force-d3d9

I thought DX9 was removed from unity a while back and affected 1.8 onward so it would not work. Not sure what happens when you put it in. 

 

Looking at your logs, it seems these three mods are generating most of your 1,484 errors on load.  Only giving a brief example below. Not sure if this is normal for these mods.

Spoiler

[ERR 17:31:06.827] Texture 'KerbinSideRemastered/Statics/ksc_exterior_terrain_grass_02-sharedassets10.assets-6' not found!

[ERR 17:31:06.828] Texture 'KerbinSideRemastered/Statics/ksp_runway_lights_diff-sharedassets9.assets-488' not found!

[ERR 17:31:06.828] Texture 'KerbinSideRemastered/Statics/ksp_runway_lights_em-sharedassets9.assets-612' not found!

[ERR 17:31:06.829] Texture 'KerbinSideRemastered/Statics/runway_light2' not found!

[ERR 17:31:06.829] Texture 'KerbinSideRemastered/Statics/ksc_exterior_terrain_asphalt-sharedassets9.assets-440' not found!

 

[ERR 17:32:01.147] Texture 'TundraSpaceCenter/Pads/TSC_Test/model_sph_interior_floor_01-sharedassets9.assets-381' not found!

[ERR 17:32:01.148] Texture 'TundraSpaceCenter/Pads/TSC_Test/model_vab_exterior_tile_00-sharedassets9.assets-466' not found!

[ERR 17:32:01.148] Texture 'TundraSpaceCenter/Pads/TSC_Test/model_vab_exterior_details_01-sharedassets9.assets-468' not found!

[ERR 17:32:01.148] Texture 'TundraSpaceCenter/Pads/TSC_Test/model_vab_exterior_details_01_emissive-sharedassets9.assets-412' not found!

[ERR 17:32:01.148] Texture 'TundraSpaceCenter/Pads/TSC_Test/model_vab_exterior_tile_04_roof-sharedassets9.assets-535' not found!

 

[ERR 17:31:28.114] Texture 'OSSNTR/Statics/TriangleSmall/WindTurbine/model_vab_exterior_details_01' not found!

[ERR 17:31:28.114] Texture 'OSSNTR/Statics/TriangleSmall/WindTurbine/model_vab_exterior_details_01_emissive' not found!

[ERR 17:31:28.115] Texture 'OSSNTR/Statics/TriangleSmall/WindTurbine/grass2' not found!

[ERR 17:31:28.115] Texture 'OSSNTR/Statics/TriangleSmall/WindTurbine/model_vab_exterior_tile_00' not found!

[ERR 17:31:28.117] Texture 'OSSNTR/Statics/TriangleSmall/WindTurbine/model_vab_exterior_tile_01' not found!

[ERR 17:31:28.118] Texture 'OSSNTR/Statics/TriangleSmall/WindTurbine/model_vab_exterior_lines_01' not found!

[ERR 17:31:28.119] Texture 'OSSNTR/Statics/TriangleSmall/WindTurbine/model_vab_exterior_props_01' not found!

Kerbin Side is at KSP 1.9, Tundra Space is KSP 1.81, Omega's Stockalike is for 1.61 KSP. All probably have differently levels of compatibility with current KSP. I wonder if the errors are increasing the load times. You could try removing them and see if it helps. Just copy your entire KSP game to your desktop or someplace and run from there. You can then delete the folders manually and not worry about messing up your current install.

As it was mentioned, more mods means longer load times. 

[Guest]

8 hours ago, Barar said:

Win32NT 7FFFFFFFFFFFFFFF  Args: KSP_x64.exe -force-d3d9

Not sure why you have this in your arguments --> -force-d3d9

I thought DX9 was removed from unity a while back and affected 1.8 onward so it would not work. Not sure what happens when you put it in. 

Well spotted! On older versions of Unity, running dx11 caused some games to crash so the workaround was to force it to use dx9. 

Im guessing “-force-d3d9” may have been added to the OP’s launch options on Steam from an older version  and they’ve forgotten (assuming they’re using steam or the shortcut on their desktop if not).

That said, I’m not sure it’s the cause of the OP’s issue but no point in keeping.