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

Filters not working as intended #1725

Open
3 of 6 tasks
sfjuocekr opened this issue Jan 27, 2025 · 0 comments
Open
3 of 6 tasks

Filters not working as intended #1725

sfjuocekr opened this issue Jan 27, 2025 · 0 comments

Comments

@sfjuocekr
Copy link

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

When I use the "linear" filter everything works fine.

When I use nearest (neighbor) or pixel filters it looks like there is some memory corruption going on!

Steps To Reproduce

Launch gamescope with:

gamescope -S integer -F pixel

I do not like linear smearing or any other upscaling beyond integer scaling with a pixel filter :(

Hardware information

- Distro: Arch
- CPU: 5800X3D
- GPU: RTX 3080
- Driver Version: 565.77

Software information

- Desktop environment: KDE 6.2.5 (6.10.0 / 6.8.1)
- Session type: Wayland
- Gamescope version: 3.16.1
- Gamescope launch command(s): -S integer -S pixel

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

It seems to happen with screen redraws/updates for windows that are not a perfect 1:1 fit, for example when I move the mouse in launchers (Battle.net/RSI/etc).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant