HomeUser Control Panel (unavailable in archive)ForumsTutorialsArt GalleryResourcesMaps

Disabling Replays

08-22-2002, 04:30 AM#1
Guest
I posted a question on this a while back about disabling replays. Ill repost it 'cause its still an issue.

Does anyone know of a way to disable the replays in WC3?

Setting Campaigns simply disables the ability to save the replay, but internally WC3 is still caching the replays. It's not really a problem with smaller maps, but in maps that take a few hours and literally tens-of-thousands of monsters are killed, the replay cache gets to be a very big issue. The game will start to lag horribly, and forget saving the game, as it will crash your game.

I know whats coming next... "its your triggers, dude" believe me, ive thought the same thing. You can see what i mean, just make a simple map that generates peons or whatever at the rate of about 2 per second.... make 20 or so mortarteams simply to waste the peons as fast as they come out... let it run this overnight... my bet, is the game will be frozen solid in the morning when you check it.

If there was a way of disabling the replay cache in WC3... all of this could be prevented. I've looked and researched and no luck. No response from Blizzard either. They could atleast give us an option to disable the replay internally.

Having enormous amounts of system ram, does help, but doesnt solve the problem.

Any help here would be appriciated.
08-22-2002, 05:06 AM#2
Guest
I get a chance to reply to my own post, not to bump, but to update, woot!

This replay cache thing is also the source of the game crashing after a long game on Bnet. Most of you who play on Bnet know what i mean.

This is a copy of the email i sent blizzard:

>The game replay is a very cool idea; however, it causes a major >problem. On large maps or games that take a long time, it can >cause an excruciating amount of lag, not to mention crashing >the game when a user attempts to leave. It’s not a big deal on >systems with 1 gig of ram, but on the average 256-512m ram it >can be a very big issue. Give us the ability to “disable the >replay” in F10 options, so that it disables replay caching >internally, not just the ability to save the replay (through set >campaign).
>
>Do a simple test… in the editor, make a power circle spawn a >peon like twice a second, and have 20-30 mortar teams >standing close to waste em as they come out… let it run for a >few hours and take a look at how big the lastreplay (and >replaytemp) files are. Let it run for 8-10 hours and see if the >game is even still running. This is a major issue; many people >cannot exit the game after a good game on battle net without >their game crashing because of extreme replay caching.
>
>Please don’t use the “we don’t support the editor” line… this >bug is not in the editor or specific to any custom maps… its >internal to WC3… it’s the replay cache… allow us to disable it, >please.
>
>Thanks


If enough of us send "bugreports" complaing about the replay lag (game crash) issues... maybe they will give us an option to disable the replays and actually fix it. Blizzard is a good company, but sometimes it takes a flood of "bugreports" to get them to make a priority out of a specific issue.