[1.1]Game crashes upon loading a game or starting a fresh colony (Solved)

[Minitialize]

This is my first post on this website so apologies if I get something wrong.

Before I start, I have seen a similar thread to this before, however, the source of the problem wasn't the same as mine and one of the circumstances that surrounded it was related to graphics. In my case, it just ceases to load and then CTDs. As far as I can tell in the error logs, there is some sort of "access violation" however I can't be too sure. I have already done a fresh re-installment of the game, but as I had expected, the problem continues to persist even in a vanilla state.

I run the game with mods (100+ on steam workshop), and for quite some time I hadn't encountered any issues/bugs in my time with rimworld. Just a day before an update landed on March 21, everything was completely fine until after I updated the game the following day (I don't think it was the update however, looking into the crash logs.). I can load into the menu perfectly, but I am unable to load into any of my save files, nor can I start a new colony (I can to an extent, particularly; choosing the storyteller, the setting, the colonists, and selecting where my colonists land in the world. When I start to load the local area though, that's when the crash happens).

I hope someone can help me work around this issue, I'm dying to continue playing the game especially during this lockdown that we're in right now.

[Canute]

Hi,
does i understand it right. You update your 1.0 safegame to 1.1 ?
Sorry but that was a bad idea.
If you got a 1.0 safe, you should revert Rimworld to 1.0, and use 1.0 mods and finish that colony.

And when your final update to 1.1, you should delete all 1.0 mods. Or better manualy delete the Mods folder, so you get right of all that old stuff.
And when you (re)activate the mods, take a look at the log window no red lines (errors) show up, better avoid these mods.

[Minitialize]

Hello, Thanks for the reply.

I started the game on 1.1 with mods for 1.1. I created a new save quite some time ago and played without any issues until recently.
The red lines shown on the log window didn't really create any issues for me, but I'll try and get rid of those that can be causing me problems. Will give an update ASAP.

[Canute]

Even when an error didn't got an impact at the first view.
Later you maybe will notice something, like you can't build something, some feature don't happen, pawn don't work or trader won't leave.
So you allways should get right of error's when Rimworld startup.
Later when you got some feeling about error's you can life with some, like when you read some sound.def arn't be loaded you can still play without that bullet sound.

But you still should get right of old mods at your mods folder, even when you don't activate them, rimworld browser throw them and increase the loading time.

[Minitialize]

Later when you got some feeling about error's you can life with some, like when you read some sound.def arn't be loaded you can still play without that bullet sound.

But you still should get right of old mods at your mods folder, even when you don't activate them, rimworld browser throw them and increase the loading time.

Alright, will do. I subscribed to some mods that are on 1.0 because I thought it might be a good way for me to keep in check any updates for the incompatible mod(s) in the future.

[Minitialize]

UPDATE: So I found out the source of the problem after inspecting the debug log for quite some time. A mod (of course, goddamnit). For some reason, the mod SRTS: Expanded bugged my game, causing me to have massive frame drops and consuming plenty of free memory. The presence of the mod alone (regardless of whether it was enabled/disabled) appears to have caused my game to crash since I created this post, and so I decided to remove the mod altogether instead of just having it disabled in which doing so allowed me to finally load my saves. Thanks Canute for the tips!

I hope this can be of help to anyone having the same issue. Although my case is pretty weird, basically, if you're having the same issue, look into your debug logs and locate any red lines (usually along the lines at the bottom of your debug log). They can help indicate the culprit behind any bugs you encounter.