GPU_DetectedFramesAhead=# wont go higher than 2

[-=seany=- 5]

I can't seem to set my GPU_DetectedFramesAhead=#; to go to more than 2 with the Arma2.cfg:

GPU_MaxFramesAhead=0; = GPU_DetectedFramesAhead=0;

GPU_MaxFramesAhead=1; = GPU_DetectedFramesAhead=1;

GPU_MaxFramesAhead=2; = GPU_DetectedFramesAhead=2;

GPU_MaxFramesAhead=3; = GPU_DetectedFramesAhead=2;

etc for any higher number

If I try to use Nvidia control panel to force it I get (using GPU_MaxFramesAhead=1000; which is whatever your driver sets iirc):

NV 0 = Locks up my PC When I launch the game

NV 1 = GPU_DetectedFramesAhead=0;

NV 2 = GPU_DetectedFramesAhead=2;

NV 3 = GPU_DetectedFramesAhead=2;

NV 4 = GPU_DetectedFramesAhead=2;

etc up to 8

I got GPU_Detected to go to 4 once with NV frames ahead set to 5, but then it went back to 2 the next time I launched. In fact, the Nvidia way seems fairly random as to what number it puts in, but I have never seen it go higher than GPU_DetectedFramesAhead=4;

Is any one else having this issue, does it look like there is some problem? what's the highest everyone else can get it to go?

[Bulldogs 10]

I'm not absolutely definite on it but I believe that GPU_DetectedFramesAhead is the reading it gets from your nVidia drivers.

So if you go into the nVidia drivers and set the MaxPrerenderedFrames to 6 then your GPU_DetectedFramesAhead should equal 6.

As for the GPU_MaxFramesAhead setting, I believe you can set this manually to whatever you like, but if you set it over the size of your GPU_DetectedFramesAhead setting then it will have no effect. If your DetectedFrames is at 8, and you set your MaxFrames at 4, then you should still have a setting of 8 under your nVidia control Panel but the game will only use 4 frames ahead as that's what you set as the maximum for ArmA 2 to use.

As for the best numbers to use. Never set it to 0 (causes problems as it tries to access a frame from the buffer that isn't there), setting it to 1 can cause issues too, but less likely. 3 is usually a good setting (and the nVidia default), but basically if you are suffering mouse lag then set it to a lower number (1 or 2), if you have no mouse lag but the game doesn't feel smooth (frames feel lower than they are) then set it to a higher number. That should smooth out gameplay but has the chance of introducing mouse lag.

[-=seany=- 5]

Thanks for the suggestion I hadn't realised that your Nvidia pre rendered frames setting affected the max that you could set "GPU_MaxFramesAhead=#" to.

well, I tried the following settings:

Nvidia Max Frames ahead =8 | Arma2.cfg GPU_MaxFramesAhead=8

gives me:

GPU_DetectedFramesAhead=4;

Something still wrong here. :confused: It wont go higher than 4.

[Avoidable 10]

Could it be something to do with the fact that the 295 runs SLI with the 2 GPUs?

Don't see why it should make a difference, but Arma did have some major issues with 295s earlier (due to SLI) and this may be a left over.

Just putting it out there.

Might try it out with my 285's and see what happens.

[-=seany=- 5]

I tested completely disabling SLI on both XP and Vista but my Max frames ahead will still not go higher than 4 on XP and 3 on Vista.

Any Other 295 users can test or left me know what your max GPU_DetectedFramesAhead=#; you can get?

[Bulldogs 10]

I only just noticed it myself but it seems that it's doing it to me now too (set it on 8 in nVidia and it's set to 4 in ArmA), not sure what the cause is.