the Sim Settlements forums!

Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

Solved Cannot load previous save without CTD?

Nychthemeron

New Member
Messages
8
Sorry for bringing this back up, but everytime I load a save that just activated the city holotape, the game CTDs. Fast travelling and saving is perfectly fine. But when I load a previous game, then it CTDs. I was noted that the mods Endless Warfare, Conquest, and StartMeUp may facilitate in the crash. And so I have recently started a new game without those mods but the problem still persists. I tried to reload a previous save that just activated the holotape and it CTDs. However, I have noticed saying that it may take several minutes to finish the performance options. Was it because that I reloaded a save when the performance options may or may not (I don't know how to tell when the rendering is finished) have finished which was why it ended up CTD'ing?

You can see the mods I use (excluding the ones I mentioned here ofc) in this previous thread:
https://simsettlements.com/site/ind...ements-activated-by-using-the-holotape.10869/
 
Don't use any old save files.

My previous recommendation from the previous thread is still relevant.

I know it is frustrating. As an example: “I once had a bridge mod that caused my game to CTD when I drew a weapon after level 10-12.

I recommend that you:

Start a “new game.” Only activate Sim Settlement mods in the plugs tab. “Absolutely, nothing else.”

Get to the point just before your CTD.

Make a hard save

Test.

IF no CTD start activating your mods 5 at a time always replaying from your hard save.

I think you still have a mod conflict or some other corruption.

It is a process of elimination now. I see no quick fix to your problem other than repeated testing.


upload_2019-9-24_10-44-47.png
 
Thank you so much! After much trial and testing, it appears that it is the HUD Framework that is causing the issue, not Conquest, Endless Warfare, or StartMeUp!
 
Last edited:
Thank you so much! After much trial and testing, it appears that it is the Immersive HUD that is causing the issue, not Conquest, Endless Warfare, or StartMeUp!

Wow, that is an odd one. :scratchhead

edit, I miss read that the first time.

I am having a hard time getting my head around that one. :umnik2

As - is, I am glad you got it working. :good
 
Last edited:
Top