if theres any teleport triggers, those can be problems, and some triggers involving Gaia stuff can cause problems.

may just be coincidences,

desync at start usually means a bad connection of a player mixed with dozens (sometimes hundreds) of effects/triggers all at once goes bad.
^^^^^ its not fun, but a long while back ,scenarios of all kinds were crashing out at start, and so my scenario that ive built on repeatedly, has almost all triggers that would begin at start, be off, and groups of them turned on over the course of the first minute of the game.( of my attempt to remedy the problem, which it relly didnt.)


and desync later in game, can be unintended from a player crashing out, or of course on purpose..

since u said once it didnt desync all game, its probably just a little bad luck.

Thanks for replying Rhino.
I have played this scenario maybe 4 times without the triggers (i deleted them), and all went OSS sooner or later. But I suppose it could also be bad luck, and combination of PC lag.

My next step in debugging the scenario will be to remove all terrain and units in the map, and add it back again. If that wont help, then the file itself is damaged somehow.

I have some bad news for you :(
Everytime OOS has happened to me is because the file is corrupted somehow and cant be fixed

While editing you may corrupt the file with these actions (at least those are how I corrupted files in the past)

-Make some buggy triggers (to many triggers active at once, cicle/abuse of teleport or change camera triggers)
-Too many conditions/effects in triggers
-Copy/Paste gaia untis or terrains
-Bad save file while using AokTS
-Chaging a Forggoten Empire to African
-If you have really bad luck and your game crash while scenario editing testing it may corrupt your file even if you did nothing from above

While using triggers I recommend certain "debug" triggers for example deactivating the trigger you just use, even if it was not a cicle, or after finish a "trigger chain" t1 - > t2 -> t3 -> t4 ->final trigger -> Deactivate t1 t2 t3 t4 t5 and the deactivate trigger itself

Even if you fix the trigger cicles, the file will keep OOS like in your case and will remain like that even if it is just a blank map.
Well maybe for a blank map no, but for recreating your map from a ex bugged blank map is preferable to crate a new file avoiding everything I mentioned before.
Hopefully one day we might found a way to debug but for now all you can do is remaking your map in a new file trying to avoid those things

To avoid OSS saving the file constantly will help and then go back to certain point but dont load the desync file save it must be another
If there is a lot of Framerate lagg try pausing it with F2 until it is fixed.

Good luck with your map, you may not hear this often but as a creator you are adding value and gameplay time to this game, thanks for you effort, time and this gift to the community keep it coming!

Hi Alejandro. Thanks for sharing your ideas on how to avoid the problem with OSS. It is comforting to hear that I am not alone experiencing this kind of issues. About the OSS events you mentioned, did they happen immediately at start, or several minutes later in the game?

The copy and paste feature I rarely use, and never in this scenario, since I worry that it only hides the objects instead of removing it.
Trigger Studio have I used frequently in this scenario, and I know that TS can sometimes damage a scenario if you save a file more then once. To avoid this I always save the file as a new file for each new change. At the moment I have about 80 versions of the file on my computer.
I suppose I could test a couple of the older versions of the scenario, but I find debugging demanding, since the OOS only appear if I play it with several other players online.
I can't remember if the game have crashed when I edited the scenario, but I can't swear it hasn't either.
I have plenty of triggers that activate others, but I don't think the triggers are the problem.

I will consider to remake the scenario from scratch, with a new map. Pity we cant copy and paste triggers from one scenario to an another.

Some of the OOS issues I experimented had something in common, they all happened before 1 hour of gameplay my bugged scenario files couldn't reach 60:00 min, they always OOS sometimes at 1:00 min sometimes at 43:00.

But I also have an experience that when I reached certain area (it was an RPG) it always OOS,so to be able to pass this area with my friends we saved the file during the gameplay constantly and repeated the area like 2-3 times

One time I hear that a bugged scx file I made didn't OOS when someone else were testing it for me, it could be possible that this OOS is caused by your installation of HD try reinstalling HD but be careful since reinstalling DELETES all your scenarios, make a copy of them before.

Or maybe one of your testers may have a corrupted HD installation

Also we should remember that HD had really bad servers even for random maps since its launch 11

Lets hope that it debugs reinstalling your HD or returning to an old version

So i had a similiar problem and the root was a corrupted trigger id. in trigger studio try the button sync id to do under triggers and then use the scrawl option and paste the triggers as text into a file. now check the ids if they are normal and delete those that arent.