Hi all!

I’ve recently come across an issue with launching games from steam. For now I’ve seen it happen on two games (or rather demos): Crow Country and Sophonce. They launch fine but have some flickering black blocks on the screen that make them unplayable. Here are some images:

https://pasteboard.co/qXH4H5gm7sIS.jpg

https://pasteboard.co/7k9XM394Zlsi.jpg

https://pasteboard.co/6vPC8GYxhHu8.jpg

This only happens when they go full-screen and on wayland, on X11 works fine. I’ve tried many versions of proton including eggroll variants.

The games work fine when launched with wine without steam in the middle if i do wine <game.exe> . If i do it this way the games detect that I’m running on an ultra-wide screen and play as such but through steam they stay on 16:9 instead.

My system:

Os: Nobara 40
Kernel: 6.8.12-200.fsync.fc40.x86_64
DE: Gnome 46.2
CPU: AMD Ryzen 7 7800X3D (16) @ 5,05 GHz
GPU 1: AMD Radeon RX 7900 XTX
RAM: 32GB

Any help is appreciated,

Thanks!

  • exu@feditown.comEnglish
    0·
    5 months ago

    Does your wine support Wayland natively maybe? Proton doesn’t yet, and I found some games have issues with that.

    I usually use ganescope for such games. Maybe try that

    • khi@lemmy.worldOP
      0·
      5 months ago

      I think you are correct assuming it’s an issue with proton not supporting wayland as if i try to use lutris proton still doesn’t work but wine does and so does with gamescope.

      I’m trying to use gamescope now as you and the other comment have mentioned but I’m having the issue with this command, if you could help me:

      gamescope -w 3440 -h 1440 -W 3440 -H 1440 %command%

      It creates a window of the appropriate size but the game is still in 16:9 (Without the black blocks issue, which is already a win, but i’d prefer it to be ultrawide too).

      Thanks for the help!!

      EDIT: Just tried it with Lutris but it seems to also not work even with their setup on proton. So it might be a them thing. For now I’ll just use lutris to play on wine directly.

      • prole@sh.itjust.worksEnglish
        0·
        5 months ago

        For some reason I’ve been having issues too, but I started adding this to my launch options in the game properties in Steam and it seems to work for several games. Dunno if this is the same issue as you though, but maybe worth a shot:

        PROTON_USE_WINED3D11=1 %command%

        Also use Wayland.

        • khi@lemmy.worldOP
          1·
          5 months ago

          Thanks for the input! I tried it but no luck, the black blocks are still there and it still renders on 16:9. Thanks though!!

          • prole@sh.itjust.worksEnglish
            1·
            5 months ago

            Ah, bummer… Can’t you just log in using X11 instead of Wayland for the session when you want to play? Assuming it’s a Wayland issue…

  • azvasKvklenko@sh.itjust.worksEnglish
    0·
    5 months ago

    I know this issue. It’s reproducible when

    • Using AMD on Wayland
    • Only on certain screens or only on HDMI (I never reproduced that when using DP)
    • The game is running in non-native resolution, meaning the compositor is doing upscaling
    • The game window is full screen and focused - the black blocks go away if you show some desktop menu or focus other window on top - so basically looks like only happens when the direct scanout protocol is doing its thing
    • not only in Steam games, in most games in general

    The problem has long been reported in Mesa project, but nothing was done to help. My bet is that the bug sits in amdgpu kernel driver and not user space.

    https://gitlab.freedesktop.org/mesa/mesa/-/issues/8705

    EDIT: maybe it’s worth to report in kernel bugzilla or wherever amdgpu kernel driver bugs would go. I don’t reproduce this on my end anymore, because I changed my screen and it uses DP

    EDIT2: I could only reproduce it on RDNA2 and yours is RDNA3. I had Polaris (RX 570) for quite some time and it was running on Wayland. Maybe it only happens on newer cards, maybe it’s regression added along the way

    • khi@lemmy.worldOP
      0·
      5 months ago

      Bingo, yes this is the same issue for what they say. I am connected through DisplayPort though on all my screens. Shame that it is not being worked on but from my testing I assume that when steam moves proton to support wayland natively it will be fixed. Thanks for the info, very interesting!!

      • azvasKvklenko@sh.itjust.worksEnglish
        1·
        5 months ago

        The HDMI/DP was my wild guess. For now the problem should also go away if you just change in-game resolution for whatever is your screen. Maybe the problem isn’t being addressed because it was reported to Mesa user-space driver, but maybe the problem is in kernel module. It’s also not 100% always reproducible.