Greetings all,
(I thought I'd make a new post about this for all the 128M card users.)
I have a 128M card (6600GT.)
I use FRAPS to check my FPS.
Usually, on BF2 I run at low-medium settings (individually tweaked) and get 40 FPS or so - quite OK for me.
But,
using EF I see periods of 20 seconds or so when I get only 6-7 FPS (unplayable) - typically this occurs when I move towards where the action is (i.e. more textures are loaded.)
So,
I used RivaTuner to check my texture VRAM usage - I see my local texture VRAM (TRAM) top out at 109M (the actual amount of local TRAM on a 128M card) with non-local TRAM (i.e. AGP aperture in my system RAM) about 40-50M or so.
When this 6FPS slow-down occurs, RivaTuner shows me that the TRAM usage is "shuffled" between local TRAM (on card) and non-local TRAM (system RAM).
I see the local TRAM usage figure drop a little and vary quickly up and down slightly while the non-local TRAM usage figure rises a little and also varies rapidly.
In short, what appears to be happening is that the card texture memory fills up, so the game has to off-load some texture into system RAM texture memory.
But this process takes 20 seconds or so - which seems very long, so this may be a bug - let's hope Dice fixes it.
The easy answer is - get a 256M card.
Kapyong
(I thought I'd make a new post about this for all the 128M card users.)
I have a 128M card (6600GT.)
I use FRAPS to check my FPS.
Usually, on BF2 I run at low-medium settings (individually tweaked) and get 40 FPS or so - quite OK for me.
But,
using EF I see periods of 20 seconds or so when I get only 6-7 FPS (unplayable) - typically this occurs when I move towards where the action is (i.e. more textures are loaded.)
So,
I used RivaTuner to check my texture VRAM usage - I see my local texture VRAM (TRAM) top out at 109M (the actual amount of local TRAM on a 128M card) with non-local TRAM (i.e. AGP aperture in my system RAM) about 40-50M or so.
When this 6FPS slow-down occurs, RivaTuner shows me that the TRAM usage is "shuffled" between local TRAM (on card) and non-local TRAM (system RAM).
I see the local TRAM usage figure drop a little and vary quickly up and down slightly while the non-local TRAM usage figure rises a little and also varies rapidly.
In short, what appears to be happening is that the card texture memory fills up, so the game has to off-load some texture into system RAM texture memory.
But this process takes 20 seconds or so - which seems very long, so this may be a bug - let's hope Dice fixes it.
The easy answer is - get a 256M card.
Kapyong
Comment