There have been a mass amount of problems with a few maps, and its inconstant it seems.

Following problems

Randomly will crash at start of game, sometimes it does sometimes it doesn't.
( Even with more than one player )

Randomly freezes the replay ( Units wont move etc. etc. )
( No speed up or down has happened either )

Any ideas? Thanks.

I've heard many complaints about replays recently. This is a theory, but I believe that Blizzard did as flawless a job with the replay-with-text feature as they did with the /r to reply feature. (Edit: Apparently, blacklight didn't catch what I was trying to say about the /r feature, or perhaps was just elaborating on my point.)

In short, Blizzard probably coded something poorly, and now the communities that value replays are suffering from it.

Wait for the next patch? There's no real known way of fixing a problem such as this.

Again, just my theory. I'd be more than happy to see a post following this saying I'm wrong.

Post has been edited 1 time(s), last time on Jan 21 2009, 5:32 am by Roy.

Replays are a bit screwy, one issue for you could be that these replays were created before the last patch, which could cause some glitches, as they did some work with replays, but also, there are lots of issues with replays, like the speed changing causes trigger problems, more than 3 upgrades causes problems, and really there's no way of fixing it.

A note. Replays which are causing new crashes also crash BWChart if you try to view the actions at that time.

Very strange, but I also think it's due to the new text-in-replays command.

A note to all is that with replays.. if the maps don't use Wait triggers, it doesn't freeze that often (especially trigger intensive units [units being used to trigger triggers]) ... for me.. it's mostly luck so i usually don't bother with replays...

Can anyone explain why TS replays work most of the time? .. I doubt anyone can...

I think hyper triggers make replays work again despite waits.
But without hyper triggers (mostly old maps) waits make trigger timing inaccurate for speeds above x1.