KSP1 Won't Load?!?

[TwoCalories]

So, after a series of the game crashing when I tried to use Kerbal Konstruct's "Spawn New Group" tool, KSP just simply won't load.

It goes through the loading screens and stuff, and then just sits on a blank black screen, except for the grey "Loading" animation with the planets and stuff.

The full modlist is here:

Spoiler

And if possible, I do want to be able to figure out that Kerbal Konstructs crashing issue, as well.

[Kerb24]

This might be a stupid question, but have you tried uninstalling and reinstalling Kerbal Konstructs (And the mods that depend on it)?

[TwoCalories]

57 minutes ago, Kerb24 said:

This might be a stupid question, but have you tried uninstalling and reinstalling Kerbal Konstructs (And the mods that depend on it)?

I did, but I have a custom KSC that I'm worried will all be deleted if I uninstall KK. It took an extremely long time to set up, so I'm considering this a last resort option. Thanks, though.

***

52 minutes ago, Hotel26 said:

You could try the following.

1. rename your saves/<world>/persistent.sfs to saves/<world>/persistent.sfs.231225 (now you have a backup)
2. copy your save/<world>/quicksave.sfs to saves/<world>/persistent.sfs  (Now you've regressed to happier times)
3. do not panic!  (I should have mentioned that eariler)
4. now try the startup...
5. if it works, there's something wrong with the most persistent.  Check its size and compare it with the quicksave: maybe it's significantly shorter?  If so, it's toast: move on without it.
6. if it doesn't work, you can copy your persistent.sfs.231225 back over persistent.sfs (but keep the Xmas (231225) version).  Further diagnosis required.

Let us know how these steps work out for you.  Also, don't panic!  But don't fork it up...

(Pay particular attention to everything above that is underlined.)

20 minutes ago, swjr-swis said:

Adding to @Hotel26's instruction: make a copy of the <savename>\backup folder and save it someplace else. KSP1 keeps a backup there of the last 5 (default, could be more if you changed it) persistent files.  That way you can test them, starting with the most recent, and see if you can get back to a working situation without losing too much progress.

Just copying this here for reference.

***

20 minutes ago, Hotel26 said:

Check what is in  GameData/KerbalKonstructs/NewInstances

and delete it if it looks totally new (check dates).  Roll it back.  Then try the load.

As usual, "Don't fork it up!"

  

Edited December 24, 2023 by TwoCalories

[Bej Kerman]

2 hours ago, TwoCalories said:

I did, but I have a custom KSC that I'm worried will all be deleted if I uninstall KK. It took an extremely long time to set up, so I'm considering this a last resort option. Thanks, though.

What if you copied its save data elsewhere?

[TwoCalories]

19 minutes ago, Bej Kerman said:

What if you copied its save data elsewhere?

I'm pretty sure the issue had something to do with KK and those crashes though, so copying its save data might save the problem, too. I don't know, I'm not a very computer-y person. Thanks for the help, though. I really appreciate it.

[TwoCalories]

Well, I've tried all these methods and none have worked. Is there anything else I can do?

[HebaruSan]

No logs?

[TwoCalories]

13 minutes ago, HebaruSan said:

No logs?

What do you mean?

[HebaruSan]

36 minutes ago, TwoCalories said:

What do you mean?

[TwoCalories]

UPDATE: My KSP is working again. It turned out to be an issue with Exported Instances. Removing those turned out to fix it. However, I don't really know what caused the crashes that led to this issue in the first place. I really want to be able to make custom KK bases, so help would be appreciated.

Log will be coming soon.

[TwoCalories]

Still working on figuring out how to upload the log, but I know how to reproduce the issue, I think:

1. Launch a vessel (I launched a single probe core part, only so that I could access the KK building menu)
2. Open the building menu (CRTL + K) and go to "Edit Groups".
3. Click "Spawn New Group".

I'm not sure if it'll happen to other people, or if these steps will work. I'm a little nervous about trying to provoke this glitch on purpose after just fixing my game.

[Royalswissarmyknife]

The Sky is Not the Limit but Computer issues are.

[TwoCalories]

So, I tried to reproduce the issue, and checked the log. The last thing that was in the log was this, spammed tens, possibly hundreds, of times:

KK: [LaunchSiteManager] GetLaunchSiteByName: found LS: The Outpost Rover Parking Lot 
(Filename: C:\buildslave\unity\build\Runtime/Export/Debug/Debug.bindings.h Line: 35)

Does this have something to do with it?

[Schniw]

Did you find an answer to this in the end? I have the same issue with KK and note I first got the error once I started setting roles to the buildings (Hangar, Merchant, Business. Research Set Launchsite etc). Will play around and workout whether this was the cause.

RIP Beck AFB - A central port to the Joolian Deuterium harvest industry

[TwoCalories]

1 hour ago, Schniw said:

Did you find an answer to this in the end?

No. Three hours of work on a custom KSC down the drain.

[Schniw]

On 7/9/2024 at 11:20 PM, TwoCalories said:

No. Three hours of work on a custom KSC down the drain.

Oh no! gutted! If you still have the instances in a separate folder you can try copy them across.

I did some further testing and found I could copy all of my instances across to the new KK install crash-free, except the "KK_2500m_runway-instances" which for some reason then caused the issue to occur.

I created another KK Group to test whether the runway static would cause this issue and found no issues with making this a launch site; and playing around with orientation/scaling. So overall the tests worked fine.

So Beck AFB is back excluding the runway which I can spawn in again. If the issue crops up again I will update the thread.

[TwoCalories]

5 hours ago, Schniw said:

Oh no! gutted! If you still have the instances in a separate folder you can try copy them across.

I did some further testing and found I could copy all of my instances across to the new KK install crash-free, except the "KK_2500m_runway-instances" which for some reason then caused the issue to occur.

I created another KK Group to test whether the runway static would cause this issue and found no issues with making this a launch site; and playing around with orientation/scaling. So overall the tests worked fine.

So Beck AFB is back excluding the runway which I can spawn in again. If the issue crops up again I will update the thread.

No, I already removed KK to fix my install when this happened a few months back. Also, the crashes would happen for me whenever I made a new Group.