• 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.
I can report that I no longer have freezes, but the freezes have changed to sudden crash to desktop, even after just few minutes of play.
its even MORE unplayable than 1.08. :confused:
1.09b ASAP please!
 
Same as the others: at around 5 minutes, the game simply CTDs. This is arguably an improvement, as before I had to force shut down the computer whenever the game froze. However, this makes the game unplayable for practical purposes.
 
I'm able to reproduce the freeze, but not the crash (at least I do think it's the correct freeze). I will look into it further, but can you please post what version of the Mac OS X you're running.
 
osx 10.6.8 is what I'm running. I'm currently playing with the shield packs, rome and the republic on. Right now I'm running it with the republic activated, since at least when it CTD's I'm able to restart. Without the republic it completely freezes at random and I'm stuck having to shut down my computer completely. At this point I'm playing with monthly autosaves to save myself the work of having to retrace my steps, it's a pain in the ass saving every month but it's better then restarting and replaying the same five months over and over again.
 
I'm running 10.8.2 on a 2012 iMac with NVIDIA 680MX video. I can play for 1-2 hours, and then the game freezes, but doesn't CTD. I can't click on anything, but I can see the screen. Also, sometimes the music starts looping (playing the same 3-5 seconds of whatever song was playing over and over again). I'm running 1.08, since 1.09 has required a hotfix for Macs, and I haven't purchased the Republics DLC.
 
I decided to play a few StarCraft 2 games since CK2 freezes on my system as well. Turns out after about two hours the same thing happened to SC2. I was able to move my cursor and the music was still playing. Console told me this: 23.01.13 00:29:55,000 kernel[0]: **** Debug info for *possible* hang in MAIN graphics engine ****, followed by more details. It's pretty much what it tells me about CK2 freezes, too. Google told me a bit more about that and it turns out that other users are experiencing this issue while using apps like Chrome.

Are any of the other users here having problems with other apps as well? I really don't hope this is part of a much larger problem. :(

This is what the console says about one of my CK2 freezes:

Code:
22.01.13 02:13:23,000 kernel[0]: stampWait: Overflowed checking for stamp 0x1ad1037 on MAIN ring: called from 
22.01.13 02:13:23,000 kernel[0]: timestamp = 0x1ad1035
22.01.13 02:13:23,000 kernel[0]: ****  Debug info for *possible* hang in MAIN graphics engine  ****
22.01.13 02:13:23,000 kernel[0]: ring head    = 0x286042e4, wrap count = 323
22.01.13 02:13:23,000 kernel[0]: ring tail    = 0x00004418
22.01.13 02:13:23,000 kernel[0]: ring control = 0x0000f001   enabled, auto report disabled, not waiting, semaphore not waiting, length = 0x010 4KB pages
22.01.13 02:13:23,000 kernel[0]: timestamps = 0x1ad1035
22.01.13 02:13:23,000 kernel[0]: Semaphore register values:
22.01.13 02:13:23,000 kernel[0]: VRSYNC: (0x12044) = 0x1ad1035
22.01.13 02:13:23,000 kernel[0]: BRSYNC: (0x22040) = 0x0
22.01.13 02:13:23,000 kernel[0]: RVSYNC: (0x 2040) = 0x0
22.01.13 02:13:23,000 kernel[0]: BVSYNC: (0x22044) = 0x0
22.01.13 02:13:23,000 kernel[0]: RBSYNC: (0x 2044) = 0x0
22.01.13 02:13:23,000 kernel[0]: VBSYNC: (0x12040) = 0x0
22.01.13 02:13:28,000 kernel[0]: stampWait: Overflowed checking for stamp 0x1ad1039 on MAIN ring: called from 
22.01.13 02:13:28,000 kernel[0]: timestamp = 0x1ad1035
22.01.13 02:13:28,000 kernel[0]: ****  Debug info for *possible* hang in MAIN graphics engine  ****
22.01.13 02:13:28,000 kernel[0]: ring head    = 0x286042e4, wrap count = 323
22.01.13 02:13:28,000 kernel[0]: ring tail    = 0x00004658
22.01.13 02:13:28,000 kernel[0]: ring control = 0x0000f001   enabled, auto report disabled, not waiting, semaphore not waiting, length = 0x010 4KB pages
22.01.13 02:13:28,000 kernel[0]: timestamps = 0x1ad1035
22.01.13 02:13:28,000 kernel[0]: Semaphore register values:
22.01.13 02:13:28,000 kernel[0]: VRSYNC: (0x12044) = 0x1ad1035
22.01.13 02:13:28,000 kernel[0]: BRSYNC: (0x22040) = 0x0
22.01.13 02:13:28,000 kernel[0]: RVSYNC: (0x 2040) = 0x0
22.01.13 02:13:28,000 kernel[0]: BVSYNC: (0x22044) = 0x0
22.01.13 02:13:28,000 kernel[0]: RBSYNC: (0x 2044) = 0x0
22.01.13 02:13:28,000 kernel[0]: VBSYNC: (0x12040) = 0x0
22.01.13 02:13:33,000 kernel[0]: stampWait: Overflowed checking for stamp 0x1ad1042 on MAIN ring: called from 
22.01.13 02:13:33,000 kernel[0]: timestamp = 0x1ad1035
22.01.13 02:13:33,000 kernel[0]: ****  Debug info for *possible* hang in MAIN graphics engine  ****
22.01.13 02:13:33,000 kernel[0]: ring head    = 0x286042e4, wrap count = 323
22.01.13 02:13:33,000 kernel[0]: ring tail    = 0x000047e0
22.01.13 02:13:33,000 kernel[0]: ring control = 0x0000f001   enabled, auto report disabled, not waiting, semaphore not waiting, length = 0x010 4KB pages
22.01.13 02:13:33,000 kernel[0]: timestamps = 0x1ad1035
22.01.13 02:13:33,000 kernel[0]: Semaphore register values:
22.01.13 02:13:33,000 kernel[0]: VRSYNC: (0x12044) = 0x1ad1035
22.01.13 02:13:33,000 kernel[0]: BRSYNC: (0x22040) = 0x0
22.01.13 02:13:33,000 kernel[0]: RVSYNC: (0x 2040) = 0x0
22.01.13 02:13:33,000 kernel[0]: BVSYNC: (0x22044) = 0x0
22.01.13 02:13:33,000 kernel[0]: RBSYNC: (0x 2044) = 0x0
22.01.13 02:13:33,000 kernel[0]: VBSYNC: (0x12040) = 0x0
22.01.13 02:13:38,000 kernel[0]: stampWait: Overflowed checking for stamp 0x1ad1043 on MAIN ring: called from 
22.01.13 02:13:38,000 kernel[0]: timestamp = 0x1ad1035
22.01.13 02:13:38,000 kernel[0]: ****  Debug info for *possible* hang in MAIN graphics engine  ****
22.01.13 02:13:38,000 kernel[0]: ring head    = 0x286042e4, wrap count = 323
22.01.13 02:13:38,000 kernel[0]: ring tail    = 0x00004850
22.01.13 02:13:38,000 kernel[0]: ring control = 0x0000f001   enabled, auto report disabled, not waiting, semaphore not waiting, length = 0x010 4KB pages
22.01.13 02:13:38,000 kernel[0]: timestamps = 0x1ad1035
22.01.13 02:13:38,000 kernel[0]: Semaphore register values:
22.01.13 02:13:38,000 kernel[0]: VRSYNC: (0x12044) = 0x1ad1035
22.01.13 02:13:38,000 kernel[0]: BRSYNC: (0x22040) = 0x0
22.01.13 02:13:38,000 kernel[0]: RVSYNC: (0x 2040) = 0x0
22.01.13 02:13:38,000 kernel[0]: BVSYNC: (0x22044) = 0x0
22.01.13 02:13:38,000 kernel[0]: RBSYNC: (0x 2044) = 0x0
22.01.13 02:13:38,000 kernel[0]: VBSYNC: (0x12040) = 0x0
22.01.13 02:13:43,000 kernel[0]: stampWait: Overflowed checking for stamp 0x1ad103e on MAIN ring: called from 
22.01.13 02:13:43,000 kernel[0]: timestamp = 0x1ad1035
22.01.13 02:13:43,000 kernel[0]: ****  Debug info for *possible* hang in MAIN graphics engine  ****
22.01.13 02:13:43,000 kernel[0]: ring head    = 0x286042e4, wrap count = 323
22.01.13 02:13:43,000 kernel[0]: ring tail    = 0x00004918
22.01.13 02:13:43,000 kernel[0]: ring control = 0x0000f001   enabled, auto report disabled, not waiting, semaphore not waiting, length = 0x010 4KB pages
22.01.13 02:13:43,000 kernel[0]: timestamps = 0x1ad1035
22.01.13 02:13:43,000 kernel[0]: Semaphore register values:
22.01.13 02:13:43,000 kernel[0]: VRSYNC: (0x12044) = 0x1ad1035
22.01.13 02:13:43,000 kernel[0]: BRSYNC: (0x22040) = 0x0
22.01.13 02:13:43,000 kernel[0]: RVSYNC: (0x 2040) = 0x0
22.01.13 02:13:43,000 kernel[0]: BVSYNC: (0x22044) = 0x0
22.01.13 02:13:43,000 kernel[0]: RBSYNC: (0x 2044) = 0x0
22.01.13 02:13:43,000 kernel[0]: VBSYNC: (0x12040) = 0x0

Does this help the devs in any way? My system is a Mac mini 2011, 4GB, HD 3000, OS X 10.8.2. CK2 is patched and the hotfix has been applied.
 
I would suggest you to update to the latest version and after you have updated to the upcoming, not yet released, patch please see if you are able to reproduce this again. Also, try and prevent the computer from entering sleep mode or power saving mode as that seem to cause a freeze almost every time for me.

I'll be checking back and see how it goes, please follow this up as it would be much appreciated as we want to have this issue tracked down and solved and knowing if it's something with the game or if it's due to the Mac itself.
 
I would suggest you to update to the latest version and after you have updated to the upcoming, not yet released, patch please see if you are able to reproduce this again. Also, try and prevent the computer from entering sleep mode or power saving mode as that seem to cause a freeze almost every time for me.

I'll be checking back and see how it goes, please follow this up as it would be much appreciated as we want to have this issue tracked down and solved and knowing if it's something with the game or if it's due to the Mac itself.

....wait, there's another patch coming?
 
1.091 is still freezing my Macbook Air 4,2 (Intel Core i5, Intel HD Graphics 3000, OS X Version 10.7.5).
Same console messages as posted by Kalean here.
 
Last edited:
At first the new patch seemed to work like magic. But now its the same as 1.08. The game play Okay for a while and then suddenly freezes the whole computer. This frequency increases dramatically after the first 100 years of play.

Macbook air late 2011 model.
 
I'm able to reproduce the freeze, but not the crash (at least I do think it's the correct freeze). I will look into it further, but can you please post what version of the Mac OS X you're running.

So... as the freeze bug is acknowledged by QA and they can reproduce it, can we expect a fix in a not-so-distant future?
 
So... as the freeze bug is acknowledged by QA and they can reproduce it, can we expect a fix in a not-so-distant future?
That post was before the current patch 1.091, so clearly expecting it to fix the remaining problems, which it mostly has. If you are still having issues like this after 1.091 (with the right checksum) then post details, hopefully K-vald is still monitoring this thread.
 
That post was before the current patch 1.091, so clearly expecting it to fix the remaining problems, which it mostly has. If you are still having issues like this after 1.091 (with the right checksum) then post details, hopefully K-vald is still monitoring this thread.

Other than:
1.091 is still freezing my Macbook Air 4,2 (Intel Core i5, Intel HD Graphics 3000, OS X Version 10.7.5).
Same console messages as posted by Kalean here.
I don't know which details you expect me to post... checksum is correct (YZBE) btw.
 
I'm running 10.8.2 on a 2012 iMac with NVIDIA 680MX video. I can play for 1-2 hours, and then the game freezes, but doesn't CTD. I can't click on anything, but I can see the screen. Also, sometimes the music starts looping (playing the same 3-5 seconds of whatever song was playing over and over again). I'm running 1.08, since 1.09 has required a hotfix for Macs, and I haven't purchased the Republics DLC.

The exact same thing is happening to me.
 
I'm running version 1.091 on a Macbook and am still getting the freeze. The game runs beautifully for an apparently random number of minutes, after which it simply "freezes" the entire system. The music still plays and the cursor still moves around the screen but I'm not able to interact with my computer at all. I cannot command + tab to another application, nor, if I'm running in windowed mode, can I click on other windows, other apps, or force quit the game. I have absolutely no choice but to cringe while force powering down the system in order to use my computer any further.

Being a huge fan of both Crusader Kings I and the Europa Universalis series, I waited patiently for this game's initial release. And then I waited patiently for the game to be released for Mac. And then I waited patiently for it to work with my Intel HD 3000 video card, which I had not realized was fixed until just this past week or so. Now I am waiting for the game to stop freezing my computer up in a fashion that could seriously harm my system. I say none of this as an expression of impatience (as I know that debugging is a major pain in the a** and I don't blame you guys in the first place), and I'm willing to do whatever it takes to help get this awesome game running perfectly; all I ask is that the development team will not let all this waiting be in vain -- please keep working on this! :)
 
I'm running version 1.091 on a Macbook and am still getting the freeze. The game runs beautifully for an apparently random number of minutes, after which it simply "freezes" the entire system. The music still plays and the cursor still moves around the screen but I'm not able to interact with my computer at all. I cannot command + tab to another application, nor, if I'm running in windowed mode, can I click on other windows, other apps, or force quit the game. I have absolutely no choice but to cringe while force powering down the system in order to use my computer any further.

After half a year non playing (I was unable to play on MBA) I started yesterday again and... now these freezes! Have the same issue as poster above: I just can't click on anything while music is playing for some time. I have to hard restart my MBA to stop it. Jeez why MBA gives us so much trouble?