-
Notifications
You must be signed in to change notification settings - Fork 852
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MESA_VK_WSI_PRESENT_MODE no longer has effect on VSync #4096
Comments
This is most likely because DXVK now uses VK_EXT_swapchain_maintenance1, which allows the application to change the present mode dynamically without recreating the swapchain, and Mesa probably only applies whatever you set in MESA_VK_WSI_PRESENT_MODE on swapchain creattion. Not a DXVK bug (nor could some driver specific env var ever be a DXVK bug...). |
In that case I'll stay on DXVK 2.2.0 for the time being and see how it goes. Thanks anyway |
Why would you stay on DXVK 2.2 because of that? Most games allow you to just change the present mode between at least fifo and immediate in the display settings directly, and for all other cases dxvk.conf can do everything the driver env var can. |
There's a single unity game which doesn't have an option for that. Had to force it through driver. Also I didn't know about dxvk.conf. Gonna look into that as well. |
For example for d3d11 games:
and those don't suffer from the problem of being overwritten with VK_EXT_swapchain_maintenance1 dynamic present mode switching. |
Running games with DXVK no longer sets present mode to the preferred present mode specified in MESA_VK_WSI_PRESENT_MODE environment variable.
Damavand (wine's builtin vulkan renderer) does not have such issue and the present mode is correctly set according to the environment variable.
Software information
Arch Linux
Kernel 6.9.7
GNOME desktop environment (X11)
Mesa 24.1.2
Tested on some DX9 and DX11 games.
System information
Apitrace file(s)
Is this necessary?
Log files
Games don't have any useful logs in stdout. Unless you need output with WINEDEBUG?
The text was updated successfully, but these errors were encountered: