Out of Sync from LivingCharacters_AI mismatch

[DaScrooge]

Information​

I have verifed my game files (Steam only)​

Yes

I have disabled all mods​

Yes

I am running the latest game update​

Yes

Required​

Summary​

Out of Sync from LivingCharacters_AI mismatch

Description​

Multiplayer game, just 2 players, keeps desynchronizing with the same error.
Message mentions "LivingCharacters_AI mismatch", apparently both are not up-to-date for the second player.
A quick look into the OOS files hints at some character not being able to be equipping an artifact, or involved in a scheme, I could not find this one though.
I will be providing 2 save games, to compare with some time passed ingame. and the OOS reports.
I know this issue has been reported before, I just want to provide more information to research the issue, bonne chance for your team!

Steps to reproduce​

Loading the affected save game in either singleplayer or directly hosting for multiplayer, both allow the second player to join, but about of 2 ingame days later desynchronize. Game has to drop the joined player. Second player IS using the MS Store version.

Game Version​

Steam + MS Store

Platform​

Windows

Additional Information​

Affected Feature​

• Crashes
• Multiplayer

Save Game​

View attachment Emperor_Rodrigo_of_Francia_1026_05_12-02.ck3View attachment Emperor_Rodrigo_of_Francia_1026_04_26-02.ck3

Other Attachments​

View attachment 0ef9db4fe2b5321e_14_43.rarView attachment 1c6af1814990c5eb_44.rar

 

[Aloha Akbar]

My friend and I have the same problem since 1.15.
Both of us are using steam.
Now its going OOS after a few ingame days. It seems to be "LivingCharacters_AI mismatch" aswell.

I attached the files, maybe data from a different save with same issues helps

 

[Derion]

We just started experiencing this (LivingCharacters_AI dsync) as well. 5 players (all on Steam; 2 Macs, 3 Windows), but always the same player getting the error.

 

[Partixx]

Same issue with two different play saves.
One a two player session and with with a three player session.
Beside of LivingCharacters and AI also with Faction.

 

[Partixx]

Hello @DaScrooge @Aloha Akbar @Derion

I’m tagging you so that you might receive a notification about this potentially applicable solution.

As already mentioned in my post from Saturday, we also encountered this issue with the OOS.
After a lot of troubleshooting, we found a solution—at least for the two-player session. The three-player session will be tested next Friday.

Search for a "Population Control" mod in the Steam Workshop. We used "Better Population Control" by the author "Saltfish"—yes, the one with the anime girl pictures.
After subscribing to this mod, you can select it in the Crusader Kings 3 Paradox Launcher and start the game.
The host (the player with the savegame) should start the game in single-player mode and check if "Death is Coming" appears in the Decisions tab.
First, click on the second option, where you can configure the "HUMAN PURGE PROJECT" to your specific needs. Then, close the settings window, click on "Death is Coming" again, and select the first option to let it run.

We let Ms. Death run for about one in-game year. My friend in the two-player session also subscribed to the mod, launched CK3 with it, and joined my session after the one-year purge. Ms. Death remained active during the session, and we have now played 50 in-game years without any issues.

During the purge, I checked the save states with "PDX Unlimiter" and saw that the living character count dropped from 33k to around 29k. This was enough to get the session running again without any OOS errors.

Hopefully, this small guide will help you.

Regarding the settings, I’m not sure which ones are perfect for this use case, but discuss it with your friends, and you’ll surely find the best configuration for your game state.

I wish you the best of luck! Hopefully, this will save your precious save states and allow you to enjoy your multiplayer sessions again!

 

[DaScrooge]

Thank you for your suggestions, I'll try it out,

One janky workaround, we use now is:
1) Ignore the Popup, do not close the window when it auto-pauses
2) Push the windows of the screen
3) Unpause and you can continue, usually the other player does not have to drop

Not perfect, and certainly has the error showing up again, but after a few sessions also fixed and got less frequent.

 

[Malachi]

I have the same problem, in a game from March. This keeps on being a problem with multiplayer, almost every time there has been a patch, old saves start to bug. This does not work for a multiplayer, that we constantly have to start new games because Paradox is unable to keep save file integrity! This is a serious and multiplayer-gamebreaking issue that has lasted for several years!

 

[bumtouch]

Thank you for your suggestions, I'll try it out,

One janky workaround, we use now is:
1) Ignore the Popup, do not close the window when it auto-pauses
2) Push the windows of the screen
3) Unpause and you can continue, usually the other player does not have to drop

Not perfect, and certainly has the error showing up again, but after a few sessions also fixed and got less frequent.

this works

 

[Benismann]

Thank you for your suggestions, I'll try it out,

One janky workaround, we use now is:
1) Ignore the Popup, do not close the window when it auto-pauses
2) Push the windows of the screen
3) Unpause and you can continue, usually the other player does not have to drop

Not perfect, and certainly has the error showing up again, but after a few sessions also fixed and got less frequent.

There's no way this works, what? Bring me sweet memories of nasty eu4 events that you just push into the corner and forget about them