• We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.

unmerged(33030)

Recruit
Aug 10, 2004
3
0
I am not sure if this is a bug, but I have a lot of trouble with CK just exiting out while I am in the middle of playing. I have updated to 1.03, and my computer is pretty new. I don't think I noticed it exiting out as much before I downloaded the newest patch, either.

Is anyone else familiar with this happening?
 
Upvote 0
Grosshaus said:
Can you give any pattern about when it does that?

I haven't noticed any pattern. I will be playing and the game will just exit out. Sometimes it does it more often than other times. I have told one of my other friends about it, and he says he has had it happen to him too.

Could it be anything that is running in the computer's background?
 
It's a common problem in Paradox's games, and is called CTD(crash to desktop). It's much rarer in the latest patch(1.03b). If you don't have the b-version of 1.03, I recommend you to install it. I've not had any CTD's after I got 1.03b at least.:)
 
Augsburg said:
Could it be anything that is running in the computer's background?
My anti virus program or firewall sometimes causes problems, so I usually disable it before I start CK. As I am not connected to the internet while playing, I figure it's save.
 
Thanks much for your help, Nikolai and lenny. I will double-check that I have 1.03b instead of just 1.03.

It's frustrating when you're busy on Crusade and you haven't saved your game for a while and then *poof* your CK reality is shattered and you're staring at your desktop screen!
 
I've the same problem, too; at first I've suspected it could be an hardware problem, but I've started a new game and I see that CTD is now very less frequent (1 every 36 years of play, instead of 1 every 2 months of play of my previous play at 1300, totally unplayable).

It seems that my CK "collapsed" when the size of saved game grow (my previous saved play is 70 mb), and the frequency of CTD is direct proportional to size of saved game.

However, now I'm sure (a quite bit) that my pc is working normally (I've changed my old Geforce 4 with FX5200 and it works for sure).

I think, and is a drastic solution, to return to 1.0, that is (for my pc) more stable than 1.03b.... and I don't know why! :(
 
I should never have posted this...:p I just got my first CTD in 1.03b EVER...!:p
 
Byakhiam said:
Autosave is best medicine for CTDs.
Unless you CTD on autosave, of course. ;)

I usually use several save files for the same game, so that I can switch should one get corrupted. (Lucky me, I had only 3 corrupted saves so far!) Also, I save before important strategic decisions or every 2-3 years if I am in a quite time period.
 
lenny said:
Unless you CTD on autosave, of course. ;)

I usually use several save files for the same game, so that I can switch should one get corrupted. (Lucky me, I had only 3 corrupted saves so far!) Also, I save before important strategic decisions or every 2-3 years if I am in a quite time period.

This is something I strongly recommend. I use 3 save files for the save game + Autosave and this very much prevents the CTDs I get from ruining my day, as previously was the case.