Quite simply, replays for my map seem to cause SC2 to crash. No problems while actually playing the game. I noticed that fast forwarding at a higher speed makes it crash quicker. But, even normal speed eventually crashes it has been reported. What gives?
I'll lend the small amount of assistance that I can;
I personally used to have a problem where replays kept freezing for several seconds before continueing, which made it seriously annoying to watch back any game. I later found out that this was because of the way replays work - if you play them, the file seems to write the replay data to location X, and read Starcraft game data from wherever the game is located. By default, location X is on the same disc as where Starcraft 2 is installed, which means that replays cause the game to both read and write information to the same disc at the same time, which causes lags. To fix this, all you have to do is change the disc where temporary replay data is saved to a different one, and you should be set.
How this is done? Beats me - googling what I googled then gives me 0 good results and ALL threads I found on it those two months ago seem to have vanished into thin air. How it helps you? Beats me, as well - I suppose you could try this technique and see if it solves your crashes?
Rodrigo had discovered a problem where anything using banks would crash the replay. Blizzard supposedly fixed that.... Is the point that you are crashing at perhaps the point where banks are saved/loaded in the map?
Rollback Post to RevisionRollBack
Feel free to Send me a PM if you have any questions/concerns!
i use to crash my replays on star1 ;^) .. well not every time but on all triggered and maxed games, it would not re do all the actions (any trigger could be "forgotten" for one) from some "random" point and the "story" would then be screwed of course..(dropping players mostly)
if i may,
have you tried the replay function on a game played by yourself?
As i understand it, the replays are problematic in mods because of the way the game is build (starcraft2)
so when you change too many parameters that change the game, the engine is often incapable of re creating all of the simultaneous "other" players actions (replays are re creations not viewings per say) ...
this because of saving issues (as stated before, if your cp doesn't save all the proper information when playing how could it then work...?) but mostly, in the case of mods that stray too far from the mold, because of conflicting data.. conflicting with the normal use of the "engine"... things that are "acceptable" in game (since the saving issue does not come into play) but that the replay does not know how to deal with ...
sorry my post isn't really helpful..
if it is salvageable (and i wouldn't bet on it) i'd say your best bet is actors or behaviors... you must have gone quicker on some of your development (forgot to duplicate EVERY little thing) and a "wrongfully shared" actor or behavior is crashing your mod through the replay... or a certain trigger is not replicable on replays.. etc (again, it works when you play it, but the replay engine is incapable of dealing with it, whether generally or in case of multiplayer: conflicting simultaneous data)
in the other case,i feel sad to say it seems hopeless.. replays are nice, however blizz doesn't help for games (because of the quantity it would have to deal with), but they don't even seem to fully have "mastered" their own in the case of replays...
hope someone comes to your rescue and proves that replays are awesome in all situations :)
Quite simply, replays for my map seem to cause SC2 to crash. No problems while actually playing the game. I noticed that fast forwarding at a higher speed makes it crash quicker. But, even normal speed eventually crashes it has been reported. What gives?
I'll lend the small amount of assistance that I can;
I personally used to have a problem where replays kept freezing for several seconds before continueing, which made it seriously annoying to watch back any game. I later found out that this was because of the way replays work - if you play them, the file seems to write the replay data to location X, and read Starcraft game data from wherever the game is located. By default, location X is on the same disc as where Starcraft 2 is installed, which means that replays cause the game to both read and write information to the same disc at the same time, which causes lags. To fix this, all you have to do is change the disc where temporary replay data is saved to a different one, and you should be set.
How this is done? Beats me - googling what I googled then gives me 0 good results and ALL threads I found on it those two months ago seem to have vanished into thin air. How it helps you? Beats me, as well - I suppose you could try this technique and see if it solves your crashes?
@Mozared: Go
Not sure if that will help. This is for all players. Other maps don't suffer this problem.
-
View User Profile
-
View Posts
-
Send Message
Curse Premium@Karawasa: Go
Rodrigo had discovered a problem where anything using banks would crash the replay. Blizzard supposedly fixed that.... Is the point that you are crashing at perhaps the point where banks are saved/loaded in the map?
@zeldarules28: Go
The map doesn't use any banks, if I recall correctly.
@Chiquihuite: Go
Correct.
Here is a replay that crashes it and the log to go with it. I crash around 5 minutes in with 8x speed. But, any speed will eventually crash it.
Someone please help.
@Karawasa: Go Well, I have no idea.
Try posting/reporting it on the US B.Net tech/support forums?. If you haven`t already.
i use to crash my replays on star1 ;^) .. well not every time but on all triggered and maxed games, it would not re do all the actions (any trigger could be "forgotten" for one) from some "random" point and the "story" would then be screwed of course..(dropping players mostly)
if i may,
have you tried the replay function on a game played by yourself?
As i understand it, the replays are problematic in mods because of the way the game is build (starcraft2)
so when you change too many parameters that change the game, the engine is often incapable of re creating all of the simultaneous "other" players actions (replays are re creations not viewings per say) ...
this because of saving issues (as stated before, if your cp doesn't save all the proper information when playing how could it then work...?) but mostly, in the case of mods that stray too far from the mold, because of conflicting data.. conflicting with the normal use of the "engine"... things that are "acceptable" in game (since the saving issue does not come into play) but that the replay does not know how to deal with ...
sorry my post isn't really helpful..
if it is salvageable (and i wouldn't bet on it) i'd say your best bet is actors or behaviors... you must have gone quicker on some of your development (forgot to duplicate EVERY little thing) and a "wrongfully shared" actor or behavior is crashing your mod through the replay... or a certain trigger is not replicable on replays.. etc (again, it works when you play it, but the replay engine is incapable of dealing with it, whether generally or in case of multiplayer: conflicting simultaneous data)
in the other case,i feel sad to say it seems hopeless.. replays are nice, however blizz doesn't help for games (because of the quantity it would have to deal with), but they don't even seem to fully have "mastered" their own in the case of replays...
hope someone comes to your rescue and proves that replays are awesome in all situations :)
Can the cumulative effect of trigger errors cause this? I'd think it would also crash while playing but this doesn't happen.
Help!