Depends of Maps ^^". If you do a slide and that you haven't removed leaks, then you already have 2 location leaks per player sliding per 0.01 seconds -> 200 location leaks per player sliding per second -> 2400 location leak per second if 12 players, that means 144000 leaks per minutes or 8640000 leaks per hour + 1 location leak per player per 0.05 seconds for checkpath (5 or more if it's not a simple one), or 864000 leaks per hour if 12 players (4320000 or more in case of complex one) + other things such as units patrolling.People overestimate leaks. Non-interactive and non-graphical objects like locations or groups are cheap and they only get noticeable in late game when massed.
ap0calypse said:leaks alone are probably not the cause.
@askin9: post the spell, we might be able to tell you how to reduce stress on Warcraft.
@Vladadamm: isn't that what WaterKnight said? (He did say they're noticeable "when massed").
You probably also know that nobody should use 0.01 seconds for movements. But yes, new people often do that.
Anyhow, WaterKnight is correct (as are you, Vladadamm): leaks are only a problem if they've been spammed enough. Usually this doesn't happen until mid-/lategame (I still remember the old WinterMaul Wars had some serious FPS issues after 20-30 minutes ).
Anyway, it certainly shouldn't be the case after casting a single spell.
So we've come to the conclusion that
Warcraft III's minimum requirements are 128MB RAM, 400MHz processor.
Recommended is 256MB RAM, 600MHz processor.
(Yes, it's a really old game ).
Still, even with those recommended requirements I think you can still experience some FPS drops whenever a heavy system gets activated.
And people who are new to triggering usually make every system pretty heavy (see WaterKnight's post).
if a spell causes lag first time its cast and that's the only spell you gotta buy some ram memory seriously
Too bad I have 6GB of memory, more than 2GBs more than the maximum process size WC3 can have as it is only 32 bit.if a spell causes lag first time its cast and that's the only spell you gotta buy some ram memory seriously
Actually it is mostly the CPU bottlenecking since WC3 consumes virtually nothing of the GPU. Exception is if you have huge billborded transparent surfaces as those seem to bottleneck GPU a lot.The problem there is connected to the video card.