OOS error if one player doesn't have Synthetic Dawn

[Ole122]

While trying to play a MP game with two friends we had the following situation:

Two of us, including the host, own Synthetic Dawn, one does not. When the third one picked a machine species, the game would go out of sync after a day or two of ingame time.

Him picking a normal species seems to have solved this, but it was my understanding that all features are available to all players if the host owns the DLC and it certainly worked like this for Leviathans, which we were able to play just fine. A clarification and/or fix regarding this issue would be most welcome.

 

[hlilje]

Thanks for the report!
Can you please ZIP and upload the OOS folder that was created for the host and the player which went out-of-sync?
On Windows the folders are typically located at: C:\Users\<username>\Documents\Paradox
Interactive\Stellaris\oos

Which galaxy size and operating system(s) are you playing with?
Are you using any mods?

 

[hlilje]

I haven't been able to reproduce this, I hosted a new game with three players, the host and one player had Synthetic Dawn and the third player didn't. Then I chose a pre-made machine empire for the player without the DLC and let the game tick for several months without any OOS.

Can you please be a bit more specific of how the game is setup, does it matter which machine empire you pick? Are you hosting a new game?
Does reinstalling the game fix the problem? (I read some other post which mentioned that fixing an OOS).

 

[GulMacet]

Hi, I am the third player mentioned before. Here is my OOS folder. You said you chose a pre-made machine empire - perhaps this is what caused the error? I made my own in the empire designer.

 

[Ole122]

We tried large and huge galaxies. I as host use Windows 10 Education 64bit, version 1703. The other player (the one with the problem) uses Windows 10

The problem occured when we tried to play together with three people (2 had SD, one did not) as well as when we tried it with 2 (again, host having SD, client did not) and chose non-pre-made machine empires. When we tried with two people who both had SD, and who both chjose a non-pre-made machine empire there was no problem.
Game setup consisted of individual, non-pre-made machine empires for the three/two of us. map size was large and huge, the problem occured both times.

Reinstalling wa snot attempted, we only tried to revalidate the files via Steam.

Hosting a game with two people where the host had SD and the client did not and both picked non-machine empires resulted in no problems.
Also a game with three people where two had SD and chose non-pre-made machine empires and the client without SD chose a non-pre-made "normal" empire resulted in no OOS. This was what we settled on and which makes us think that the bug is related to a non-SD owning client using a machine empires. this game which runs stable uses a huge ring galaxy (I can try and look the other specifics up if you need them).

I have attached my OOS folder with 4 subfolders in total, which should all relate to one of the instances of us trying to get it running.

We'd run another test with a pre-made empire in order to see how that goes, but unfortunately, we now all have SD as the last of us just bought it

 

[hlilje]

Thanks a lot for the information, you can disable the Synthetic Dawn DLC in the launcher which should have the same effect as not owning it.
It would be great if you could do the same test as you did but with pre-made machine empires just to leave out the possibility of it only happening for non-pre-made ones.

 

[hlilje]

This OOS has now been fixed internally and will eventually be released on the 1.8.1 beta branch.

 

[GulMacet]

Excellent! Thank you very much for your hard work! I will send my Rogue Servitors to pamper you as soon as possible.