Sure, but the save was made on an installation with an invalid checksum. I simply can't log a bug under those conditions, sorry all. If it can at all be reproduced on a valid installation I'd be happy to add this to the other reports of problematic saves.
Also, I have the correct checksum, and it crashes on my computer as well.
The fact that Maginor's checksum was correct when he loaded your flawed save game is not relevant. That game was created and saved under your incorrect checksum and so is suspect in and of itself.
The checksum ensures that all game data files are as intended - neither corrupt nor edited. The main purpose is to allow MP players to ensure they have the identical version of the game, and are not cheating, but it's a handy indicator of general game installation health. The fact yours keeps changing is likely the cause of your problems and we need to fix that.
Not sure if you have the game from Steam or Gamersgate. I suggest you move any valued save games elsewhere and uninstall the game, and then manually delete both the game code directory, and the data directories under your MyDocuments folder. Then reinstall from scratch (if GG then install the 1.03b patch manually), and make sure you now get the right checksum consistently.
The game code directory is wherever the GamersGate installer, possibly altered by you, put it, I would assume the installer asks you where you'd like to install the game? There. It is where ck2.exe ends up, plus all the graphics and game data sit.
Yes, the data directories are where you mention. Actually data directories is an incorrect term, I should have said user file directories - it's where anything the game writes out goes (this is to get around the Vista/Win7 Virtual Store stuff that makes supporting EU3 so painful).
After the clean install you'll need to apply the 1.03b patch, and make 100% sure you point it to the place the game itself installed (so that the patch overwrites the older files in the GG download). Run the game up and check you have the right checksum now.
After the clean install you'll need to apply the 1.03b patch, and make 100% sure you point it to the place the game itself installed (so that the patch overwrites the older files in the GG download). Run the game up and check you have the right checksum now.
Awesome, right? Then, loaded up my save, and lo and behold, by the 16th of August 1299 (not even 3 weeks ingame was allowed to pass) the game crashed, just as it always did.
Would that be enough for it to be considered a bug?
I guess not
Meanwhile i really feel sorry for AndrewT i must say ...cause he explained it in detail but you simply don't want to understand.
Your savegame is from a different checksum or ? (then it can't be considered as a bug)
- or was it a totally fresh game you saved ? - then it could be a bug - but i must say 1299 does not look as if it was a fresh game)
PS: I do apologise if I've pissed anyone off with my short answers or remarks, no malice is intended. It's just rather buggering annoying, really...
Even if I had changed anything, why is it that horrendous crashes can't be considerd a bug if a file is altered? Isn't that the joy of this game, the modding? Because I alter one value in the opinion_modifier file, it starts crashing a century later?
It is normal that the checksum changes by one letter (say KUMH -> JUMH), when you resign from a game but do not exit the program. This is to force MP players to restart the whole game when they drop out, which aids stability. This is entirely unrelated to the random ones you were getting; if you are still getting anything except KUMH on game startup, you have a severe PC problem I believe.The original game was created from a normal checksum of KUMH, yes. However, it started altering wildly; even now, with my fresh install, the checksum keeps changing without me doing anything at all playing on a different save entirely.
It is always possible to crash a game by modding badly, Paradox cannot write a game that does not crash despite being fed bad data. Not that I'm saying this issue is certainly caused by your modding, but that does render your particular game unreportable. If your problem is actually the same as the others reporting such issues here on unmodded games such as this one, then the root cause will be fixed when that issue is dealt with. We cannot however guarantee that saves that are now broken will then be playable, it depends on the nature of the problem.Even if I had changed anything, why is it that horrendous crashes can't be considerd a bug if a file is altered? Isn't that the joy of this game, the modding? Because I alter one value in the opinion_modifier file, it starts crashing a century later?
It is normal that the checksum changes by one letter (say KUMH -> JUMH), when you resign from a game but do not exit the program. This is to force MP players to restart the whole game when they drop out, which aids stability. This is entirely unrelated to the random ones you were getting; if you are still getting anything except KUMH on game startup, you have a severe PC problem I believe.
It is always possible to crash a game by modding badly, Paradox cannot write a game that does not crash despite being fed bad data. Not that I'm saying this issue is certainly caused by your modding, but that does render your particular game unreportable. If your problem is actually the same as the others reporting such issues here on unmodded games such as this one, then the root cause will be fixed when that issue is dealt with. We cannot however guarantee that saves that are now broken will then be playable, it depends on the nature of the problem.
Well as I said, there does appear to be a bug or bugs that cause problems with saves crashing the game. Until the devs come up with a cause and a fix we can't be any more specific, sorry.