- Aug 3, 2009
Please update the driver for your graphics card. This seems the fix the most common crash, so try that first, even if your driver is rather recent. The very latest can make a big difference.
The realm rejoices as Paradox Interactive announces the launch of Crusader Kings III, the latest entry in the publisher’s grand strategy role-playing game franchise. Advisors may now jockey for positions of influence and adversaries should save their schemes for another day, because on this day Crusader Kings III can be purchased on Steam, the Paradox Store, and other major online retailers.
While this is good general advice, Kallocain, and the stock answer of tech support anywhere, it isn't particularly relevant to the crashes we have reported since the majority of those who have posted in the crash thread and provided details are running GeForce cards that are already using the very latest released driver 258.96 (Driver file 8.17.0012.5896)Please update the driver for your graphics card. This seems the fix the most common crash, so try that first, even if your driver is rather recent. The very latest can make a big difference.
Not necessarily given the nature of the workaround. It is a mere 5 bytes changed in the header information having to do with memory usage IIRC. Shuffling around stuff may prevent a problem from arising for some people without being relevant to tracking down the problem. I'm not saying it isn't helpful in this case (I obviously don't know), it might be, but there's absolutely nothing that guarantees that it is helpful or key to fixing what is actually wrong.I have the latest driver for my GTX 470 and still experience crashes at the end of missions. The fact that a launcher workaround has worked for some should be the key to fixing it.
Entirely possible.I saw someone, say "she" when referring to Kallocain in another thread?
had the same problem, none of the solutions posted here worked for me. (Reducing resolution, testing different drivers, running in compatibility mode, ...)
Then I stumbled upon this:
- download "cff explorer 7"
- open the .exe-file for king arthur (I also did this with the steam.exe file, not sure if that's necessary though) with cff explorer
- Go to NT Headers / File Header, click on "click here" (lower right)
- check the box "app can handle >2GB - voilà!
(in hindsight, that might explain why it was more prone to crash when graphics settings were high. And why it was more prone to crash after two or three battles than after the first one: Some weird memory bug.)
... that did it for me - haven't had a crash since. Seems the memory managament of Windows Vista was at fault. (I also disabled "Superfetch", don't know if that had anything to do with it though.
Hope that helps some of you guys, cheers, Catullus
Already tested it back on Sunday (since I too played KA and knew of Neocore's crash record) and it didn't help me. Setting the flag is also part of eagleFMJ's edited launcher posted in the crash thread, which helps some and not others.I tried that for KA a while ago and it fixed my end-battle crash bug. I will try it with Lionheart as well and report back on success.