
Can be caused by excessively long log commands with multiple references to global variables.Įnsure that your "positions.txt" is not misnamed and that it is empty.Ĭheck that interface. Check for unbalanced quotes, such as has_dlc = "Reapers. Check Province Map for any Antialiazing pixels. Check the format and color indexes of map files (terrain.bmp. Compare setup.log with the mod and with raw vanilla : next steps normally logged in vanilla are the likely cause of the crash. Instant CTD clicking Play in the launcherĬheck no new a entries are missing in the mod (or better use defines folder to override, and avoid duplication)
There is usually little to no information to identify the cause. Once this is done the lobby interface will be rendered.Ĭrashes or Crash To Desktop (CTD) are the despair of the players and nightmare of the modders.
Processing Flags - generates the flag sprites in gfx\flags from the individual. (Loading of vanilla history files occurs here (even if is replace_path), though it'll still show as "Loading Sounds") - very slow step !. When launching the game the following steps occur: In case of crash, you may get a stacktrace, with the last method called (ex: CLandedTitle::GetShortName) Only logged if -fullhistoricalsetuplog is enabled.Īsserts on events that fire for courtiers Įxtra errors linked to title/character history. The following lines are OK if no elements is listed: Errors can be logged without also logging asserts by enabling -scriptlog. More asserts will be logged when enabling -debugscripts. Game data loading logs (gui, modifiers, traits. Since patch 2.4.1 only logged if -debugscripts is enabled.
In game notifications and output of log commands. debug -debugscripts -scriptlog -fullhistoricalsetuplog File
More logging can be activated by using command line arguments (via Steam game properties / define launch options): These are overwritten every time the game starts. The game stores various log files in your CK2 user folder ( ~\Documents\Paradox Interactive\Crusader Kings II\logs\).