You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Are you using any gamescope patches or a forked version of gamescope?
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:
I do not like linear smearing or any other upscaling beyond integer scaling with a pixel filter :(
Hardware information
Software information
Which gamescope backends have the issue you are reporting?
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).
The text was updated successfully, but these errors were encountered: