This thread is for anyone running the new April 1st patch using the DEBUG option. Instructions on how to do this are with the patch notes, but I'll repeat them here for convenience:
We have been diligently trying to track down the few remain bugs - and in particular the elusive VFC crash bug. We haven't suceeded in trapping yet - although I think you'll be happy with the reduction in overall issues - so we would like to solicit the assistance of anyone who is very patient and has some extra free hard drive space. Here's what you can do:
When reporting a crash, please give us the following info:
We have been diligently trying to track down the few remain bugs - and in particular the elusive VFC crash bug. We haven't suceeded in trapping yet - although I think you'll be happy with the reduction in overall issues - so we would like to solicit the assistance of anyone who is very patient and has some extra free hard drive space. Here's what you can do:
This week's exe has been enabled for a limited debug mode. To use this, install the beta patch as per normal. Create a shortcut on your desktop (if you don't have one already). Now make a copy of that shortcut. Right click on your copy and choose the "Properties" option from the menu. The target will probably be something like:
(the exact path will depend on where you've installed your game and what version you have, but it should look soething like that).Code:"C:\Program Files\Paradox Entertainment\Crusader Kings\Crusaders.exe"
Change that line to add the word DEBUG immediately after the existing path (there MUST be a space between the closing quotation mark and the word DEBUG) so the line will now read something like:
Click the "okay" button to save that change, and then rename the shortcut to remind you that this is the DEBUG version. Now double-click this to start the game.Code:"C:\Program Files\Paradox Entertainment\Crusader Kings\Crusaders.exe" DEBUG
- You will notice a performance hit - not a major one - when you run under debug, and you will need LOTS of hard drive space. When you start the game, a new file will be created in your CK root directory called "savedebug.txt" where all behind-the-scenes activity will be recorded. This file will get very big very fast! We recomend setting your autosave to yearly and then after every autosave or two, surrender, exit the game, go to your CK root directoory and delete the file. Then restart and load up the autosave and resume the game. This will keep the file size down to something reasonable if (or when) you need to later open it.
- IF you get a crash of any type immediately go to this file. Rename it to "debug_crash_yourname_whoyouwereplaying_yearifyounowit.txt" (example: debug_crash_MrT_King_of_France_1106.txt". This will avoid accidentally overwriting or deleting it. Now open the file with any text editor (Word/WordPerfect/Notepad/NotepadPlus/etc.) and when it finishes loading go to the end of the file (I use the ctrl+end keyboard shortcut). Copy the last 10-20 lines of the file and then post it in a thread that we will be creating on the forum for reporting purposes. ALSO please go to your ...\CK\sceanrios\save games\ directory and rename your most recent autosave using the same format (example: save_crash_MrT_King_of_France_1106.eug) just in case we need that save game. Now start up again (under debug) and load your save game and resume. If you have a reporducable crash from a save game then you've hit the jackpot and we'll want your save, but even a large sample of debug log crashes may suffice to track the few remaining bugs down and squish them.
- Reminder: this will hurt your CK game performance (it will run more slowly and may seem to respond sluggishly at times) and if you keep running for a long time without exiting and deleting the debug file then it will get immensely large (so large that many text editors will simply refuse to try opening it!).
- For those who feel up to the task, this extra effort will be greatly appreciated by everyone! For those who don't feel up to it, remember to thank those who do. It's an annoyingly time-consuming un-fun way to play.
When reporting a crash, please give us the following info:
- Anything at all that you think you were doing at the time that the crash occured or anything you think could be the cause.
- Confirm that you have saved a copy of the entire savedebug log in case Johan needs it.
- Confirm that you have a save game of some sort from not too long prior to the crash. Confirm whether you have gone back and retested the save game to see whether the crash is reproducable (it probably won't be but would be nice to know you've tried). DON'T forget to save your debug log under a different name before doing this test!
- Post the last 15 or so (10-20) lines of the savedebug log here, using the "CODE" vB tag. In case you haven't done that before, type:
<code>
then paste your log, then
</code>
except use the square braces [] instead of the <> so it looks like this:
Code:then paste your log, then
Last edited:
