^I'm afraid I don't think the devs have even figured out the problem yet. They desperately need more people testing games after they desync to see if after reloading an autosave the desync still occurs, and then testing it in the dev.exe so they can get some good data. Sadly that's probably out of the question for most ICO games. People just want to get on to the next game, not really do the monotonous testing for bugs.

My friends and I did some testing with it, however we didn't think to try it in the dev.exe at all.
We tried loading both an autosave and a manual save, and still continued to experience desyncs.

Stupid question:why isn't beta made to run in only dev.exe mode?

I've played games with friends and i can say with certainty the desyncs DO CARRY OVER from saved games.  If you load a savegame you will resume with the desynced status you left with, no matter which person saves the game.

Seems to desync in any and all modes of network setup if you use the online multiplayer system. At first I forwarded specific ports with alloy on and off, then did DMZ with alloy on and off. Desyncs every time.

Then we did direct connect with DMZ (as direct connect does not work with manual ports for some reason, only 6112). It was fine almost all the time. Then we had a third friend join in and after he finished download. After about a hour or two into the game ONLY HE desynced.

We saved game, had him delete Ironclad Games in My documents, then I zipped and gave him MY save. Loaded up fine and we finished the game with no desyncs.

Looks like desyncs arnt fixed when you reload game as you saved the desync itself. If the other players delete their save and grab the hosts or one other persons save thats desirable, it seems to work fine.