diplo annex casues game crash

[King0fSalt]

returning to euIV after a long period. attempted to diplo annex my vassals and clicking the button casues the game to freeze and stop responding neccesitating a force close.

[grotaclas]

That sounds like a broken mod or broken installation. Try to disable all mods(if you think that you have no mods, look in the playset section of the launcher to make sure, because they might have been installed and activated without your knowledge) and if that doesn't help, you can try to verify the integrity of game files and if that doesn't help, you can try a clean reinstall as described in my guide on reddit about common startup problems with version 1.29

[King0fSalt]

i did a clean install and the problem persists

[grotaclas]

Have a look at the playsets section of your launcher. Does it show any active mods? If not, what is the checksum which is displayed next to the version number in the main menu of the game? (the checksum in the launcher doesn't count)

[King0fSalt]

1.33.3.0 France (5010)

[grotaclas]

That looks correct. Can you post your save game? Maybe I can find out what is happening

[King0fSalt]

how or where could I do that? theres no attachments on steam community?

[grotaclas]

You can use any file hosting service[en.wikipedia.org] like Dropbox or Google drive. Or you can send it to me per email. My address is my nickname at gmail dot com.

[King0fSalt]

sent on gmail

[grotaclas]

I tried your save and I had no problem starting the annexation of the vassals. I even tried all 4 languages and two resolutions. It is crashing immediately when you start the annexations and not when they finish, right?

Can you post the error.log and exception.txt from the crash? Maybe they contain a hint about the problem.

[King0fSalt]

when i click annex vassal from the influence menu the game freezes and then when i click it white outs and says game is not responding. close program or wait for it to respond. i've waited for 30 minutes and nothing. where can i find these error logs?

[bri]

documents/paradox interactive/europa universalis iv/logs

[King0fSalt]

all my error logs are blank

[grotaclas]

The error.log should not be blank, because there are a few lines which the current eu4 version always writes. Is game.log and system.log blank as well? Does the game create new files if you delete the blank logs?

Are you maybe looking at the wrong log folder? It should be in the same "Europa Universalis IV" folder which also contains the "save games" folder which contains your current save.

[grotaclas]

I noticed that eu4 writes the following message into the error.log when you start to annex a vassal:

[relation.cpp:151]: DELETING RELATION OUTSIDE OF PERMITTED CONTEXT!

But neither for me nor most others, it is causing a crash.
Maybe it is crashing because it can't write that message to the error.log in your case.
I can think of the following reasons:

• you have an antivirus or ransomware protection software that prevents blocks eu4. In that case you have to add eu4 to the exception list of your software
  
  • If you have Windows Defender(also called Microsoft Defender), add eu4 to the Ransomware "Apps Allowed Through" list(here[docs.microsoft.com] are instructions for that).
    
  • If you have bitdefender, add eu4 to the list of ransomware exceptions and "give it access" to "protected files".
    
  • If you have avast, you have to add eu4 to the allowed list in the ransomware shield
• your Documents folder or part of it is synced with a cloud storage service like Microsoft OneDrive, google docs or dropbox. A full cloud storage or connection problems could maybe cause such a problem
  
• the error.log files or the logs folder is read-only/write-protected
  
• there are some more advanced permissions set for the logs folder or one of its parent folders. I'm not very familiar with windows file permissions, but maybe there is something which allows eu4 to create new files in the logs folder, but prohibits it from writing to them. The other log files might not be affected by that, because might just open the existing file and not try to create a new one(it does that with the error.logs, because it moves the previous one to error_old.log