Skip to content
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

wayland_vk: use FIFO if commit-timing and fifo protocols are available #15056

Draft
wants to merge 2 commits into
base: master
Choose a base branch
from

Commits on Oct 15, 2024

  1. options: replace --wayland-disable-vsync with --wayland-internal-vsync

    With the upcoming fixes to FIFO in wayland, it should be preferable to
    use FIFO instead of our own hacky heuristic. This means
    --wayland-disable-vsync should become a tristate option with an "auto"
    behavior (not implemented in this commit). The semantics have to
    slightly change so introduce --wayland-internal-vsync and deprecate
    --wayland-disable-vsync.
    Dudemanguy committed Oct 15, 2024
    Configuration menu
    Copy the full SHA
    aba5b14 View commit details
    Browse the repository at this point in the history

Commits on Oct 21, 2024

  1. wayland_vk: use FIFO if commit-timing and fifo protocols are available

    A very long time annoyance with wayland was compositors indefinitely
    blocking our vo thread if the surface gets occluded in some way. We've
    worked around this by using mailbox and our own custom vsync function.
    Thankfully it looks like people are finally solving this and with these
    two protocols it should be possible to guarantee forward progress on
    vulkan which means all the workarounds we do shouldn't be needed. So we
    can just request fifo in this case as a default since all we want is
    standard vsync blocking.
    Dudemanguy committed Oct 21, 2024
    Configuration menu
    Copy the full SHA
    62f6cda View commit details
    Browse the repository at this point in the history