NVIDIAGameWorks
[Runtime Bug]: V-Sync enables itself every launch
Describe the bug
It appears that "Save Settings" button in the Alt+X menu does not take V-Sync option into consideration. It's always enabled on launch by default and not related to FrameGen/Reflex settings.
How do you reproduce the bug?
Launch the game Disable V-Sync in the Alt+X menu Hit "Save Settings" Relaunch the game See that it's enabled
What is the expected behavior?
V-Sync user setting should be saved and behave on launch as configured
Version
bridge-remix-6edc666-129-release dxvk-remix-b5fce9f-752-release
Logs
bridge64.log bridge32.log remix-dxvk.log
Crash dumps
No response
Media
This is intentional as we flag it as NoSave in rtx_options.h. I am not entirely sure about the reason why that was done originally, but if I had to guess it is likely to avoid issues with developers accidentally saving this option and forcing specific VSync settings on everyone using their mod.
If you want to set it persistently, one can manually add rtx.enableVsync=1 (or 0 to disable it) to either dxvk.conf or rtx.conf. Additionally, it's worth noting the default is not "On" per se, rather it is set to the value of 2 (WaitingForImplicitSwapchain) which essentially pulls the VSync flag from the underlying application. With that being the default you should be able to just enable/disable VSync in the underlying game if that's an option without needing to do this and it should be reflected properly, but that just depends on the game.
That said, it is a bit confusing I suppose that this option is exposed in the user graphics menu where it seems like you should be able to save all the values when clicking that save button. It's not really clear which ones are save-able and which ones aren't, so perhaps having a better way to indicate that would be useful rather than allowing this setting to be saved, as that may cause issues as mentioned previously.
@anon-apple
Thank you for your response, setting rtx.enableVsync=0 in rtx.conf does disable Vsync on launch. However, there's a catch. Whenever you click the "Save settings" button (even if you changed nothing), it deletes that string from the rtx.conf. Setting it in dxvk.conf works fine, though.
In agreement with your last paragraph, there is definitely something that needs to be fixed. This thing can be very confusing, frustrating even.
Hey @PseudoPolish - it is on our roadmap currently to clarify which settings are saved and which aren't in the runtime. We'll update you here when that's implemented and make sure it works as expected for you. Thanks for reaching out!
