First of all, I know xWayland already does this when in a Wayland session but RPCS3 (PS3 emulator) runs disgustingly bad inside Wayland on my PC, and during an Xorg session the same emulator runs perfectly, and it’s not a FPS issue or framerate, it is a problem that any game is simply unplayable because it suddenly gives stutters that do not exist in Xorg.

KDE Plasma honestly feels extremely buggy and slow on Xorg and so I don’t want to use Xorg, I would like to use Wayland and not have to log into an Xorg session every time I want to use RPCS3.

Now, I am using KDE Plasma 5.27 with Wayland and using Nvidia proprietary drivers (515).

(If Linux4Noobs existed on Lemmy I would have posted this there)

  • Nuuskis@sopuli.xyz
    2·
    1 year ago

    PS3 emulator is so niche app that I recommend you to ask its community or more ratherly devs.

  • Aman Das@rammy.site
    2·
    1 year ago

    Which distro?

    I would suggest filling a bug report to RPCS3 with all the system details you can

  • ReveredOxygen
    1·
    1 year ago

    You might be able to rdp into your own computer or something? But I’m sure that would be even less performant that xwayland.

    Xwayland really shouldn’t generate lag anyways, so I’m not sure what’s up with that

  • themoonisacheese
    1·
    1 year ago

    At some point no matter what you do, whatever was rendered in xorg will have to be converted to a Wayland surface to show it on screen. Xwayland just does that with internal x components instead of converting a whole canvas, so if anything it should be faster. I don’t think there is a way for you to decide this to happen, but I think there is a bug to raise with both the xwayland team (because it’s not working properly and they should be able to tell quite easily why) and the prcs3 team (because they can migrate to Wayland in not that much time, it’s not one-click but it should be quite easy for talented devs like this)

    • Xirup@lemmy.oneOP
      1·
      1 year ago

      In fact checking their Github it seems that it is an open issue from January 2022 that has not received any attention.

      • themoonisacheese
        2·
        1 year ago

        That is unfortunate. During the Wayland transition period, sadly this is bound to happen though I have to admit xwayland is otherwise really powerful and has not caused me many issues.

        I’d just put a comment on this issue asking for status. Debian 12 recently released and it uses Wayland by default now so the issue is bound to happen more and more.

        • Xirup@lemmy.oneOP
          1·
          1 year ago

          Wow, Debian 12 using Wayland by default? I didn’t know, it’s about time!

          And thanks for asking the status of the issue, I’ll check back later for an answer.

  • boerbiet@feddit.nl
    1·
    1 year ago

    Maybe you can try running the application with QT_QPA_PLATFORM=xcb. I have to do so for Webex for my work, since it won’t run properly on Wayland. You can edit the application’s shortcut in KDE and set environment variables in the Application tab.

    • Xirup@lemmy.oneOP
      0·
      1 year ago

      In fact you are right, although unfortunately it didn’t help, and I have a doubt, how can you find so quickly the information of commands or specific variables that solve something?

      I mean, of course, before asking in a community I try to investigate on my own but many times I don’t find anything useful and that’s why I have to ask.

      • Communist@beehaw.org
        1·
        1 year ago

        I have had to force xwayland a number of times, so, I was familiar with it beforehand, it took me forever to find the first time!

        In this case, you’re going to want to post a bug report to the rpcs3 issue tracker, this sounds like something they need to resolve on their end.