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
According to dhewm/dhewm3#425 SDL2 (@Yamagi confirms that it also happens with latest SDL git), SDL2 defaults to using X11 via xwayland instead of native wayland - SDL_GetCurrentVideoDriver() returns "x11" instead of "wayland".
@obedlink, the original dhewm3 bug reporter, uses "KDE-Neon, Radeon driver, Mesa 21.3", @Yamagi uses Gnome 41.1 (also with a current Radeon Mesa driver).
I think SDL2 should default to native wayland if available - it probably will give better performance and apparently when it goes via xwayland 8x MSAA isn't supported (while it works when enforcing the wayland backend with SDL_VIDEODRIVER=wayland).
Tagging @flibitijibibo as he has done lots of SDL wayland work recently and @icculus because if you agree that it should default to native wayland on wayland, it would probably nice to fix this before 2.0.18
The text was updated successfully, but these errors were encountered:
Damn, sorry I didn't find the existing bug (and look at the existing PRs) first!
(I thought I searched for issues at least a few days ago, but maybe I included "videodriver" in the search)
According to dhewm/dhewm3#425 SDL2 (@Yamagi confirms that it also happens with latest SDL git), SDL2 defaults to using X11 via xwayland instead of native wayland -
SDL_GetCurrentVideoDriver()
returns "x11" instead of "wayland".@obedlink, the original dhewm3 bug reporter, uses "KDE-Neon, Radeon driver, Mesa 21.3", @Yamagi uses Gnome 41.1 (also with a current Radeon Mesa driver).
I think SDL2 should default to native wayland if available - it probably will give better performance and apparently when it goes via xwayland 8x MSAA isn't supported (while it works when enforcing the wayland backend with
SDL_VIDEODRIVER=wayland
).Tagging @flibitijibibo as he has done lots of SDL wayland work recently and @icculus because if you agree that it should default to native wayland on wayland, it would probably nice to fix this before 2.0.18
The text was updated successfully, but these errors were encountered: