Interesting, I was actually going to suggest an "advanced" option to allow the old function with FPS Limit to work, but the way you say it, I guess it's a no go...Oh well.Even though the old rules worked perfectly fine for your setup we had to pick the lesser evil here. Too many people did not have the correct hardware combination to make such a vsync setup work. Basically, you need a working adaptive sync setup with a monitor and driver that doesn't fuck it up. We can't ask all our users to use the "Prefer Layered on DXGI swapchain" solution as we'd have to educate users about this again and again. We don't have the resources to code our own vulkan->d3d12/dxgi interop, so that's why we ended up doing what we did. Why NVIDIA doesn't always use the DXGI swapchain I don't know, although I'd love to know the technical answer from NVIDIA on that one.
So you enable VSync through Nvidia Control Panel and set the limit in RAZE?It works if you turn on Vsync for the game in your driver config while leaving it off in-game. That way, the driver will enforce Vsync while the game can be set to any fps you want.
I use 60 fps in-game at 120 Hz set in NVidia Control Panel on maps that cannot be played at 120 fps at all times.
Any reason you don't do it in reverse? Enable VSync in Raze and use the framelimit in Nvidia.
Anyway, I use the same method as you and it's going fine as is. I guess that's how I'll do with GZDoom and RAZE from now on.
Statistics: Posted by Blackgrowl — Mon Jul 01, 2024 6:26 am