Page 1 of 1

0059 Desyncs [SOLVED]

Posted: Mon Mar 02, 2009 9:44 am
by Hearst
I'm glad you enjoyed reading my babble, perhaps I'll bring you more soon.  Actualy here's a question.  When is the game going to get working ai's?

EDIT: I forgot to mention that when I was trying to play this on the shadowflare server with Omi, we were getting about 1.30 mins into the game and it would crash, it seemed to be a desync issue (omi pointed it out) so I was wondering what might casuing this/is it only us having this issue?

0059 Desyncs

Posted: Mon Mar 02, 2009 12:49 pm
by IskatuMesk
If the game actually crashes then it's not a desync. A desync is when players are dropped.

0059 Desyncs

Posted: Mon Mar 02, 2009 4:40 pm
by IskatuMesk
Omi wrote:
IskatuMesk wrote:If the game actually crashes then it's not a desync. A desync is when players are dropped.
Actually, come to think of it, I haven't seen the game crash even a single time, yet.
Right. Let's just not get the terminology confused. Easier for people like me to help you out debug.

I know some exe edits can cause desyncing but I'm not a programmer, so I can't say what would be causing it. I assume it would have something to do with how it updates stuff, but p_q would be the one to talk to about it.

0059 Desyncs

Posted: Tue Mar 03, 2009 12:47 am
by Hearst
Dread mentioned to me that he isn't having this desync issue, and I believe that he did a fresh install for STF, so perhaps a fresh install will fix this issue?

0059 Desyncs

Posted: Tue Mar 03, 2009 1:07 am
by Lavarinth
I didn't have an issue in the one game I have played, either. And it is definitely not a fresh install.

Did you install via CD or Blizzard Downloader?

Re: 0059 Desyncs

Posted: Thu Mar 05, 2009 7:27 pm
by Hercanic
Dear DarkHearst:
The desyncing issue has been happening with many people, and we're working hard to figure out the reason. The first big challenge is isolating the cause.

No ETA on any custom AIs.

Re: 0059 Desyncs

Posted: Fri Mar 06, 2009 1:46 am
by Hercanic
Desync issue isolated and solved! Hotfix available within the News subforum above.