@hyperion
https://drive.google.com/file/d/15vGn4ddL1nNRbtZeXqI5sqKLhm7zyNAt/view?usp=sharing
This is another example. The game was originally hosted by @erictommy, and everything was going fine until several spectators joined at some point. One of them caused an OOS, but we continued the match for a few seconds until the simulation completely froze (the GUI was still responsive).
levai was one of the active players in the match — I don’t remember if he left on his own or was kicked, but once he was out, the simulation started working again. When he rejoined, the same thing happened: simulation frozen, GUI functional.
We decided to save and rehost the match, this time with me as the host. After everyone loaded in, the simulation was frozen again. Once levai left, it resumed.
So we saved and hosted again, but this time replaced levai with RangerK — who happened to be the player that, when kicked or banned, allowed the simulation to continue normally — as if there was a problem tied specifically to that slot or civilization.
What’s strange is that the simulation started failing when a spectator joined the game. Until then, everything worked fine and levai hadn’t shown any lag or other performance issues.
A preliminary hypothesis is that this bug occurs when a player or spectator finishes loading the game or map. Why do I think this? Because the only thing I can clearly identify in common between a match just starting and one already in progress when a spectator joins, is the act of loading the game/map.