So what you are saying is that you are not getting an auto-cap with NULL in Fortnite and Battlefield (Battlefield 5?), correct?1000WATT wrote:I do not have overwatch. but there is fortnite, battlefield.
nvcp v-sync off + g-sync on = fps no limit.
nvcp v-sync off + g-sync on + ingame v-sync on/off = fps no limit.
nvcp v-sync auto + g-sync on + ingame v-sync on = standart v-sync but no auto-cap
nvcp v-sync on + g-sync on = auto-cap
this behavior on my system.
If this graph does not lie, then something is wrong with my system.
I haven't tested those games myself with NULL, but I'm guessing if a game doesn't support external manipulation of the pre-rendered frames queue, NULL's auto-cap won't work either.
As a side note, DX12 and Vulkan do not currently support NULL.