Skip to content

Merge forceRepaint fix into stable/3.7.x #1985

@wheaney

Description

@wheaney

Is there an existing issue for this?

  • I have searched the existing issues

Are you using any gamescope patches or a forked version of gamescope?

  • The issue occurs on upstream gamescope without any modifications

Current Behavior

My PR to fix a forceRepaint regression got merged a couple months back. So I assume it will go out with the next major release, but in the meantime anyone using my app on 3.7 still has a poor experience. The fix is one-line and was present in 3.6 until it was accidentally reverted in 3.7. Can it be merged into the next patch release of 3.7?

Steps To Reproduce

No response

Hardware information

- Distro: 
- CPU: 
- GPU: 
- Driver Version:

Software information

- Desktop environment: 
- Session type: 
- Gamescope version: 
- Gamescope launch command(s):

Which gamescope backends have the issue you are reporting?

  • Wayland (default for nested gamescope)
  • DRM (default for embedded gamescope, i.e. gamescope-session)
  • SDL
  • OpenVR

Logging, screenshots, or anything else

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions