ValveSoftware / ValveSoftware/Proton

Plans to enable a native wayland driver

Open
#4,638 112 comments 296 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Feature Request
Dominant language
C++
Stars
32.8k
Forks
1.6k
PR merge metrics
PR metrics pending

Description

Feature Request

I confirm:

  • that I haven't found another request for this feature.
  • that I have checked whether there are updates for my system available that
    contain this feature already.

Description

This issue is mainly to ping, so we can prepare for the future.

As some of you may know, there is a wayland display driver that is the work in wine. There's a recent report in the mailing lists that show the advancements made.

Proton should prepare for eventual compatibility with wayland.

XWayland is not a perfect solution. HDR won't be supported in X and won't benefit from the synchronisation features wayland exposes for low latency and reliability.

Justification

This is being introduced in wine. As far as I remember, Proton has its own display driver and will need to catch up feature-wise on wayland support to not lag behind once it hits stable releases.

Risks

The experimental driver being worked on could be flawed for games (even though super tux cart was showcased). This could impact proton as it needs to support gaming needs such as pointer capture, variable refresh rate (Freesync, GSync), raw input and more.

References

Video showcase of the recent progress of the wayland driver for wine

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no repository files, tests, or entry points. Start by reviewing the referenced Wine Wayland driver work and Proton’s existing display-driver architecture; the request highlights pointer capture, variable refresh rate, raw input, HDR, and synchronization. The issue does not specify what completion looks like.

Written by the indexing model from the issue text.

Assessment

Domain
desktop-dev, operating-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.