Howdy folks. I've been playing on 2.8 for a very long time, and have never had any issues. These problems have only arisen in the past week, since I bought Holy Fury and updated to the latest version of the game.
Frequently, I'm getting CTDs now. Sometimes, the game just exits, out of nowhere, no error message at all. Sometimes, the game hangs up a moment, then exits. Rarely, the game hangs up until it gives me the Windows "CK2 has stopped working" message. This seems to happen at random, with the only reproducible part being that it *always* does this if I attempt to use the Shattered or Random World options.
Now, I admit, I haven't played vanilla with this update (actually, I haven't played vanilla CK2 since... 2016?). However, I have tried several completely different mods, and they all do it, so I'm fairly sure it isn't a mod problem, unless it's somehow a problem with mods in general. I've played HIP, After the End FF, and Middle Earth campaigns, and have had the problem in all three. Thus far, I've had it:
Randomly while waiting as Holy Roman Emperor, HIP
Randomly as Duke of Freiden, ATE
Randomly as Black Numenorian Emperor, ME
Randomly as King of Frisia, HIP
Randomly as Duke of Latium, HIP
Again randomly as Duke of Latium, HIP
Multiple times trying to use random/shattered world, experimenting with options, HIP
While clicking around the new crusade screen as Duke of Latium, HIP
So, I'm not quite sure what to do about this. I don't have any logs handy, and the only thing that's reproducible is the random/shattered world bit, which isn't even sure to be the same issue. But, given that the issue has only happened since this update, and two of the instances have been while doing things added by this update, I have a feeling it's related. Any suggestions on things I can do? Tests I could make? I don't have internet access at home, and I'm planning on going to the library tomorrow where I could do something like reinstall the game or upload logs, so hopefully you guys have some suggestions for stuff I can do tomorrow. If not, I'll probably just reinstall the game, I'm pretty sure this is the same install I've had since 2015. Hopefully that fixes it.
Frequently, I'm getting CTDs now. Sometimes, the game just exits, out of nowhere, no error message at all. Sometimes, the game hangs up a moment, then exits. Rarely, the game hangs up until it gives me the Windows "CK2 has stopped working" message. This seems to happen at random, with the only reproducible part being that it *always* does this if I attempt to use the Shattered or Random World options.
Now, I admit, I haven't played vanilla with this update (actually, I haven't played vanilla CK2 since... 2016?). However, I have tried several completely different mods, and they all do it, so I'm fairly sure it isn't a mod problem, unless it's somehow a problem with mods in general. I've played HIP, After the End FF, and Middle Earth campaigns, and have had the problem in all three. Thus far, I've had it:
Randomly while waiting as Holy Roman Emperor, HIP
Randomly as Duke of Freiden, ATE
Randomly as Black Numenorian Emperor, ME
Randomly as King of Frisia, HIP
Randomly as Duke of Latium, HIP
Again randomly as Duke of Latium, HIP
Multiple times trying to use random/shattered world, experimenting with options, HIP
While clicking around the new crusade screen as Duke of Latium, HIP
So, I'm not quite sure what to do about this. I don't have any logs handy, and the only thing that's reproducible is the random/shattered world bit, which isn't even sure to be the same issue. But, given that the issue has only happened since this update, and two of the instances have been while doing things added by this update, I have a feeling it's related. Any suggestions on things I can do? Tests I could make? I don't have internet access at home, and I'm planning on going to the library tomorrow where I could do something like reinstall the game or upload logs, so hopefully you guys have some suggestions for stuff I can do tomorrow. If not, I'll probably just reinstall the game, I'm pretty sure this is the same install I've had since 2015. Hopefully that fixes it.