As the title would suggest, I've been having some issues with actually running this game recently. I have about 960 hours of playtime in this game and have been rather enjoying the recent expansion and accompanying 1.3 update. However, the game just crashes on startup with the unity popup after I tweaked my modlist for my second playthrough with Ideology. It can run fine with no mods after I delete the ModConfigs.xml file, but the game just hangs on the Intializing... step and eventually crashes if I try to run it with all or most of my mods.
I have spent multiple days trying to resolve this issue and made little to no progress. I've tried all the fixes on the troubleshooting thread by Tynan and none of them have worked. I've tried basically everything else I could find to resolve this and gotten no results. I've tried looking for help elsewhere to no avail. I am absolutely at my wits end and coming here with this issue because I just don't know where else to go.
I can't even begin to imagine why I'm having all these issues. My hardware is fairly recent and well exceeds the minimum requirements. I have the latest drivers for my graphics card. I'm certainly not missing any Windows updates. All in all, I have little to no idea why this is happening. I took a look at player.log and it seems to be an out of memory issue, but I have 16 gigs of RAM and the game isn't even using half of it.
In conclusion, I really damn need some help here. My player.log file is attached to this post, but otherwise I can't really help any of you. I just want to play this game. Is that too much to ask?
Hi,
when you don't have problem without mods, all the fixes you tried are pointless.
You shouldn't activate all mod's at once, do it at small batches, then you might notice at which mod rimworld got problems.
It isn't a hardware problem, it is a software problem.
Just some mod's are bad by themself or they conflict with other mods.
The player.log don't show anything since you didn't even used mods from that log, so i can't say more.
Activate mod's at small batches (maybe you can use larger batches for popular mods) but that is prolly the only way to find the bad mod.
And once you found the mod, don't forget to blame the mod author about to waste your time as beta tester for his mod ! :-)
Well I hoped I could avoid having to go through my entire modlist with a fine-toothed comb to find the one that makes the game crash, but it seems like that's not an option.
I have 147 mods right now and going through all of that 1-5 mods at a time is going to be absolutely tedious.
Alright, I've gone through my modlist with a fine-toothed comb and managed to get the game to start up without crashing. For some reason, the game just refuses to run for me if I have 120 or more mods enabled. I've managed to pare my modlist down to 117 and it starts now.
I have however encountered another problem. The game somehow keeps running even after I quit out. I can quit to the desktop straight from the games main menu, but Steam insists that the game is still running. Steam doesn't respond when I try to manually stop it, and the game doesn't show up in task manager so I can kill it from there. The only way I know how to fix this now is to manually quit out of Steam and log back in, but I'd rather not have to do that. Any idea what might be causing this particular problem?
Sorry no expierence with Steam, i don't use that. Maybe you should ask that at a steam discussion.
Just out of curiousity, when you use hugslib too, just do a Share log upload and post the link ! :-)
Update on the game still running after quitting problem, I've uninstalled and reinstalled the game and the problem seems to have resolved itself. Had to do some jiggery-pokery to get the game to recognise my mods after the reinstall however: Exiting then restarting Steam managed to get it to download the workshop files. I now have things set up quite nicely.