7 replies to this topic

[Rennn]

I reinstalled Windows a couple weeks ago, and I haven't done much gaming since then. As soon as I got everything reinstalled and updated (games, DirectX, drivers, etc) I realized that vsync wasn't working in any of my games.

 

I have all the most recent drivers for my hardware, an up to date BIOS, and basically everything should be up to date since I just installed it. I've also reinstalled DirectX, the .NET Framework, and my drivers just to make sure they weren't the problem. I've tried using in-game vsync, D3DOverride, and Nvidia driver vsync. None of it works, and this is the first time I've had a problem like this. Does anyone have any idea what might be going on?

 

Edit:

It appears that vsync just doesn't work as long as I have my framerate capped at 30 in Nvidia Inspector. I would like to keep my 30 fps caps, however. I used to be able to cap at 30 fps without losing vsync. Does anyone know a fix for this?

Edited by Rennn, 13 November 2013 - 02:48 AM.

[Werne]

It's a dumb question, but are you sure you don't have Adaptive VSync on? That thing will work at 60FPS but won't work at 30FPS.

[Rennn]

It's a dumb question, but are you sure you don't have Adaptive VSync on? That thing will work at 60FPS but won't work at 30FPS.

 

Yes, I'm sure. It's set to standard, not adaptive. :/

[Georgiegril]

Sometime way back, I recall there was a problem with 30 fps on Skyrim, though the problem was infinite loading screens.

I wonder, though, if the solution for that might also work for your case.

The solution was simply to alter the fps from 30 to something slightly higher or lower. I understand you want to keep the fps to 30, but maybe 32 or 38 would solve your problem?

[Rennn]

Sometime way back, I recall there was a problem with 30 fps on Skyrim, though the problem was infinite loading screens.

I wonder, though, if the solution for that might also work for your case.

The solution was simply to alter the fps from 30 to something slightly higher or lower. I understand you want to keep the fps to 30, but maybe 32 or 38 would solve your problem?

 

I've tried that, unfortunately.

The framerate limiter options are 29, 30, 35, 40, 45, 50, 55, and 60. 

29 and 35, the two closest options, have the same problem and also don't work with vsync.

 

I tried switching to an older driver (320.49 WHQL), and with the older driver it works. It seems like it just doesn't work with the newest drivers. For now I'm sticking with the older driver, but hopefully this gets fixed... Maybe this is just Nvidia's attempt to get people to switch to gsync or something. :/

Edited by Rennn, 16 November 2013 - 10:45 PM.

[Georgiegril]

Was it the 331 that caused the problem? I'm still on 327...I'd like to know so I won't go making problems for myself...

[Rennn]

Was it the 331 that caused the problem? I'm still on 327...I'd like to know so I won't go making problems for myself...

 

I'm on 320.49 right now. I haven't tested 326x or 327x, but the problem is definitely present in 331.58 and 331.65.

[Georgiegril]

Well, that is good to know! Thanks!