FlipQueueSize - Frametime Comparison CS:Go

[Toss3]

Thought this might of interest to some of you playing CS GO on AMD cards (would be great to see similar NVIDIA numbers):

Drivers: 16.9.1
Card: 290x
CPU: 4770k HT Off (@4.3Ghz)
RAM: 16Gb DDR3 2200Mhz

FlipQueueSize Auto (Min: 448, Max: 516, Avg: 485.7):

FlipQueueSize 3 (Min: 433, Max: 543, Avg: 498.7):

FlipQueueSize 2 (Min: 454, Max: 505, Avg: 482.2):

FlipQueueSize 1 (Deleted min value by accident, Max: 399, Avg: 341.358):

FlipQueueSize 0 (Min: 457, Max: 521, Avg: 490.9):

So what this tells us is that FlipQueuSize of 1 is best for input lag, while 2 is the smoothest. Also confirms that setting FlipQueueSize to 0 reverts to Auto, and that 3 isn't a great setting at all.

Numbers are from FRAPS (30s recording after 30s on the same map with bots).

For anyone who wants to try this out just do the following:

Win+R

Type in "Regedit"

Navigate to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class{4d36e968-e325-11ce-bfc1-08002be10318}\0000\UMD

add FlipQueueSize binary and set the value to "31 00"

Reboot

 

[Rroff]

I've always found the same with maximum pre-rendered frames with nVidia - 1 gives lowest input lag, 2 gives smoothest rendering, 3 or auto a bit mixed results.

 

[Toss3]

I've always found the same with maximum pre-rendered frames with nVidia - 1 gives lowest input lag, 2 gives smoothest rendering, 3 or auto a bit mixed results.

Seems to be the same for AMD cards. In games like CS:GO some people might want to set it to 1 though. Don't really get why AMD removed it as an option, as I would love to be able to set it on a per game basis.

 

[Rofflay]

Rroff with BF3 i will try BF4 soon but if you let it be application controlled like some do it would auto to 3 which on BF3 let you use the console command prerendering 0-3 and i could see 3 stutter with solid max fps so i go to 2 and then 1 and each time it improves but i always thought there was no difference between 0 and 1 but if you set it to 3 which apparantly 0 auto reverted to it was horrid so i dont know something is weird about the difference between 0 and 1. Which is funny all the developers say that means 3 but clearly not there was a hilarious row over this when Nvidia removed 0 for this reason people swore blind 0 was better and smoother and in some games i think from memory i agreed and this is downright crazy because im eagle eyed for that kind of stuff.


Ghosts in the machines but TLDR everyone should use 1 not 2 that 2 is supposed to be for two cards so you render two frames ahead. If you had smoothness trouble you would be best moving away from 60hz not swapping from 1 to 2.

 

[Toss3]

Rroff with BF3 i will try BF4 soon but if you let it be application controlled like some do it would auto to 3 which on BF3 let you use the console command prerendering 0-3 and i could see 3 stutter with solid max fps so i go to 2 and then 1 and each time it improves but i always thought there was no difference between 0 and 1 but if you set it to 3 which apparantly 0 auto reverted to it was horrid so i dont know something is weird about the difference between 0 and 1. Which is funny all the developers say that means 3 but clearly not there was a hilarious row over this when Nvidia removed 0 for this reason people swore blind 0 was better and smoother and in some games i think from memory i agreed and this is downright crazy because im eagle eyed for that kind of stuff.


Ghosts in the machines but TLDR everyone should use 1 not 2 that 2 is supposed to be for two cards so you render two frames ahead. If you had smoothness trouble you would be best moving away from 60hz not swapping from 1 to 2.

Think 0 is different, but only if you set it from within the game itself, as it requires developer support. If you set it in the registry it will reset to auto.

Something else that is interesting:

Disabled my Raid 0 setup and all of the stutters I was experiencing previously disappeared (so this is basically running off of a single SSD).

 

[Rofflay]

Hmm i did not know that 0 was really 0 with developer support so it was smoother then! It was so so small you could barely notice it but i did think it was so damm were all stuck with at least 1 pre-rendered frame. Also i dislike Raid Crossfire/SLI anything i build is for pre-rendered 0 or 1 and single cards and ssd's dont ask why but multiple things makes things less smooth. Heck i remember when we first moved to these Quads and Duals and people thought the same thing there was a drop in smoothness.


I would love to see a single core v multi core as well we already know two cards is worse, You say two drives is worse and i say more cores is worse because going into Source games and turning off thier multicore option helps a little. It is just a good job we have Low overhead API and 120hz and 144hz to offset all of this bullcrap.