Lag building up over time
Posted: June 20th, 2011, 10:19 am
Hey all,
So I just discovered the Eschalon series and am loving them. I played through Book I and am starting Book II now but am having some technical trouble with it.
I'm a few hours into the game and here's what is happening:
I'll load my game and it will run well for about 10 minutes (performance = 10). Then it will start to get progressively laggier. The performance will jump to around 40, then in a few minutes it will jump to around 70. A few minute later I'm looking at over 100.
I've tried closing the game and restarting. Sometimes this works, sometimes it doesn't. When I restart my computer entirely the lag always disappears but builds up again.
This happens regardless of the zone I'm in. It happens in towns, underground, in forests, etc.
I'm running the game on a Dell Latitude E6400 laptop, Intel Core2 Duo 2.66GHz with 4 gigs of ram. I assume this should be plenty to run the game smoothly.
I've also updated all of my drivers to see if that would fix the problem; it didn't.
Does anyone have suggestions on what to do?
Thanks,
~Luke
So I just discovered the Eschalon series and am loving them. I played through Book I and am starting Book II now but am having some technical trouble with it.
I'm a few hours into the game and here's what is happening:
I'll load my game and it will run well for about 10 minutes (performance = 10). Then it will start to get progressively laggier. The performance will jump to around 40, then in a few minutes it will jump to around 70. A few minute later I'm looking at over 100.
I've tried closing the game and restarting. Sometimes this works, sometimes it doesn't. When I restart my computer entirely the lag always disappears but builds up again.
This happens regardless of the zone I'm in. It happens in towns, underground, in forests, etc.
I'm running the game on a Dell Latitude E6400 laptop, Intel Core2 Duo 2.66GHz with 4 gigs of ram. I assume this should be plenty to run the game smoothly.
I've also updated all of my drivers to see if that would fix the problem; it didn't.
Does anyone have suggestions on what to do?
Thanks,
~Luke