Setting up Sunshine and Moonlight for high performance game streaming on Linux

  • FauxLiving@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    19 hours ago

    I have both strong opinions on things and suggestions.

    The Windows software stack is completely independent of the Linux software stack. This doesn’t tell you anything about the problem. Trying Windows tells you that the hardware has the capability, but you could have learned that from a spec sheet.

    If you want to solve the problem on Linux, make a post with the details of the problem and what you’ve tried so far as well as any logging that you can get out of Sunshine which would show you starting Sunshine and starting a stream.


    Without any other information:I read the fantastic manual.

    It looks like you’re likely running into a documented problem: Mesa has disabled VA-API for legal reasons

    Without vaapi support, sunshine falls to software encoding which means the encoding is running on your CPU and that is what is causing the stuttering, so to fix it you would need to install a version of mesa that’s been compiled with the correct flags (h264enc, 265enc).

    The instructions for doing this depends on our distro. On Arch, amdonly-gaming-mesa-git is listed as an optional package for the AUR version of sunshine, amdonly-gaming-mesa-git is compiled with video-codes=all which will enabled the h264, h265 support.

    • g0nz0li0@piefed.social
      link
      fedilink
      English
      arrow-up
      2
      ·
      edit-2
      17 hours ago

      I did exactly this but unfortunately it didn’t address the issue I was experiencing. I read the manual you linked and the support forum for Sunshine.

      I posted about it in support forums and also got helpful advice about network latency, matching res and refresh rates to host, running Wayland only session, running game scope, using Apollo, etc.It unfortunately didn’t help.

      I tried it on Bazzite (where it is preconfigured) and CachyOS and got the same result on both.

      It suspect it’s the encoder but I think it could be a Wayland issue. I didn’t test X11 as that didn’t really suit my purposes.

      I explored this issue pretty thoroughly and spent hours trying to solve it :(