495.44 results in flickering for xwayland windows

Since the release of the 495 driver with a GBM backend and the implementation of xwayland support in Use EGL_LINUX_DMA_BUF_EXT to create GBM bo EGLImages (f1572937) · Commits · xorg / xserver xwayland windows on all compositors show “flickering” when windows (games) are not using vsync. Personally i have experienced this on sway 1.6.1, gnome 41 and have seen reports of other users on both platforms VSync goes in and out of sync (#2013) · Issues · GNOME / mutter · GitLab and NVIDIA (495) on sway tutorial + questions (Arch-based distros) - #58 by cmprmsd More precisely this flicker appears to be due to multiple lines of the frame rendering as transparent or dark gray (presumably as its swapped without vsync), instead of the native X11 artifact of tearing. This issue does not occur on mesa drivers for AMD or Intel devices.

This may be related to a similar issues noticed on KDE (which doesnt support choosing the GBM backend yet) using the EGLStreams backend where similar xwayland windows rendering without vsync result in the display of what i can only assume is the wrong frame. If we assume a program is outputting frames 1,2,3,4,5,6,7,8,9,10 during this misrendering it appears as though frames are rendered 1,3,2,5,4,7,8,10,9. Anther way to describe this might be objects appear to jitter between their previous location and their current location.

1 Like

if this happens here too, i have tried gnome and sway

in some situations running the game in windowed mode runs without problems

Might be the issue @ekurzinger is on it, as stated here: Glitches with nvidia driver 470 (optimus render offload) on xwayland with vulkan games - #13 by ekurzinger

Would be cool if we could get a status update. This issue is very annoying.

This is on a single GPU device without any prime/optimus, so its unlikely to be precisely the same issue, but they could be related.

I’m also having this trouble on a single dedicated gpu with Sway and gbm on a desktop workstation.