peerqert.blogg.se

Ck2 checksum
Ck2 checksum










  1. Ck2 checksum how to#
  2. Ck2 checksum mod#
  3. Ck2 checksum Patch#
  4. Ck2 checksum windows#

  • Check loaded trade routes reference valid provinces.
  • Check that no character has a birth date later than death date.
  • Check that no character has a death date past the end date of the mod.
  • gfx files are properly merged with vanilla, if copied in the mod.ĬTD on applying history (initial load or selecting a bookmark)Ĭheck that all groups in technology history have an entry for earliest starting date of the mod.
  • 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.
  • Ck2 checksum mod#

    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)

    ck2 checksum

    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.

    Ck2 checksum Patch#

    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. I suspect it would fix a lot of issues beyond just a wonky checksum so it might be worth giving a shot for anyone who's desperate.The game stores various log files in your CK2 user folder ( ~\Documents\Paradox Interactive\Crusader Kings II\logs\). Start up the game and it will create a new settings folder where you can dump your saves back in if you backed some up.Īll in all this took me about five minutes to do (dependent on internet speed) and successfully fixed the issue. This is probably overkill but, as I said, I'm going for the nuclear option.

    ck2 checksum

    Ck2 checksum windows#

    I used an app ( Everything - Windows only) to do a search on my whole hard drive for anything related to CK2. Back up your saves first if you want to keep them. If it does, delete it manually.ĭelete settings folder for CK2 in your Documents (or wherever it saves them on Mac/Linux). Go into your 'common' Steam apps folder and make sure that CK2 is completely gone. I'm not sure that all these steps are completely necessary but they're what I followed and it resolved the issue without too much inconvenience. PROBLEM FIXED! Here's how! Disclaimer: This is basically a nuclear option that will ensure everything related to CK2 will be completely wiped out and installed fresh. Thanks in advance to anyone with any helpful ideas/suggestions.

    Ck2 checksum how to#

    I'm totally out of ideas on how to resolve this and thought I'd check in here since registering for a Paradox forum account is such a pain in the butt. I installed the game on another of my computers and did not have this issue at all so it seems to be tied specifically to this one computer, not my Steam account. I even rolled back to a previous version and it actually did the same thing (launcher shows correct checksum but totally different when game starts). I've tried verifying the game cache, reinstalling, deleting my settings, disabling DLC, etc.

    ck2 checksum

    What's even more strange to me is that the game launcher shows the correct version (BTOF) but when I start the game it's always XOFD. Every single time I start/restart the game, my checksum is XOFD (never different from XOFD) which doesn't match any previous version. I bought Way of Life the other day and tried to play it with a friend of mine but for some reason my checksum never matches the correct one for the current version.












    Ck2 checksum