• xan1242@lemmy.mlEnglish
    301·
    1 year ago

    While I understand that Wayland is broken for the purpose of PCSX2, I am unfortunately biased against the developers here due to the horrible experiences I had with them.

    If anyone will take up the task of fixing this, be warned that they absolutely do not cooperate with you on the PRs that they receive.

    • Bruno Finger@lemm.eeEnglish
      16·
      1 year ago

      PCSX and PCSX2 are ancient. I wish DuckStation supported PS2 too because it’s an excellent modern emulator.

      • xan1242@lemmy.mlEnglish
        15·
        1 year ago

        Well, stenzek is the developer of DuckStation and the person behind the new Qt UI and many new fixes on the backend of PCSX2.

        But, I will agree that we do need a new emulator. The emulator called “Play!” is a really good candidate and looks promising. Seeing how it runs on ARM beautifully, I can’t wait to see how far it goes.

        PCSX2 runs fine for most people today, but the foundation is a bit too old for its own good. This is why you don’t see too many ports of PCSX2 to other plaforms. They have improved massively by ditching the entire plugin system a few years ago, but that alone isn’t enough to make it more portable and easy to run.

        • merthyr1831@lemmy.worldEnglish
          2·
          1 year ago

          PCSX2 is great, but i still feel like the performance for gran turismo 4 is still pretty bad for years (and has multiple game breaking bugs that haven’t been addressed!) in certain tracks and if anyone could fix that I’d be VERY happy.

      • bgtlover@linuxrocks.online
        12·
        1 year ago

        @brunofin @xan1242 Idk, I use them all the time. And furthermore, emulation needs to be precise and fast, not written in some modern technology, if the need doesn’t outway the efforts put into it. Or, maybe I’m mistaken, I may have misunderstood what you mean. So, perhaps you can clarify?

        • xan1242@lemmy.mlEnglish
          1·
          1 year ago

          It needs to be accurate and fast, indeed. The code being old isn’t a problem unto itself, but rather the side effects of it.

          It is fine for all intents and purposes today. But, there is some inherent difficulty associated with decisions brought years ago when some of the code was originally written, making portability quite a challenge.

          I wasn’t making a comment on its age, mind you. I don’t necessarily think it’s that big of a problem and probably can be fixed easily. If anything, it has gotten way better thanks to the departure from the plugin system and various other optimizations over the years.

        • Bruno Finger@lemm.eeEnglish
          1·
          1 year ago

          In my case it was due to need. I didn’t get any PS1 emulators to run well on my laptop at the time (a Windows 10 Microsoft Surface Book 2) and if I recall was due to old OpenGL libraries used in all emulators, but DuckStation implements DX11 and Vulkan, and performance was simply brilliant, so by modern that’s what I meant.

  • Quack Doc@lemmy.worldEnglish
    21·
    1 year ago

    This is understandable, and honestly xwayland is great, even with fractional scaling now, at the very least on KDE. I think simply relying on xwayland is a very viable solution now for a lot of apps. and it helps work around a lot of issues so that’s always a major plus

      • Quack Doc@lemmy.worldEnglish
        3·
        1 year ago

        It’s not really hacky as far as I know, it’s just the old status quo. On X applications could scale themselves if they have high DPI support, and that’s what KDE is allowing. And it works great. The vast majority of apps I use support high DPI on X, and they work perfectly fine on xwayland.

        It is legitimately a great experience using xwayland like this. A lot of apps I use, they look perfectly fine, they perform perfectly fine, and they’re not broken, which is a massive plus.

        Of course, this probably does break one or two apps out there. I’m not saying it’s a perfect solution. It’s far from it. But honestly, I think it’s a really good solution. It allows developers the ease and flexibility of developing for X11 if you don’t need Wayland’s features.

        Of course, you are still losing out. Having proper touch support is such an amazing feature with Wheland. Don’t get me wrong. I love a lot about Wheland. It’s just a pain in the ass to develop for. It is nowhere near as flexible as X11.

        • AProfessional@lemmy.worldEnglish
          1·
          1 year ago

          Setting the DPI is only a partial solution and plenty of assets and rendering will be incorrect. It is more crisp, especially for text, than the approach others take of upscaling though. It’s probably the approach I’d prefer personally.

          • Quack Doc@lemmy.worldEnglish
            1·
            1 year ago

            Yep, I would say it’s the best we got. I have a 4K monitor at a 20% scale and it works great.

      • KeriKitty (They(/It))@pawb.socialEnglish
        3·
        1 year ago

        Everything I’ve tried works better under Wayland than it did under X :3 Battlefield V, for example (why I play that… who knows :-\ ) has always taken a bunch of struggling with Wine/Proton versions and settings to get it to run at all, and even then it was a crashy glitchy mess. I decided to try it under Wayland just for the hell of it and somehow it’s absolutely flawless now (okay fine, there’s some kinda mouse focus bug I’ve been working around but still). Sooo now I just use Sway all’ the time. It’s great. I made a whole thread just to gush about it. Wayland and xwayland both seem to be doing great! Woo! Cheerness! \ö/ 🥳 et cetera!

      • Mixel@feddit.deEnglish
        2·
        1 year ago

        Think so, I actually had a different perspective Games that I run under native x11 stutter to the point where I don’t enjoy playing it anymore (rocket league in my example) but under xwayland the game runs without any issues/stutters

      • Quack Doc@lemmy.worldEnglish
        2·
        1 year ago

        I haven’t had any stuttering issues myself, so I cant comment on that outside of “works for me”

  • Vilian@lemmy.caEnglish
    72·
    1 year ago

    what i could understand from there is , Qt has bugs that pissed the dev, bugs that occur in wayland, gnome pissed the devs don’t doing sane things and following what everyone is doing, nvidia pissed the dev, tobe fair is nvidia always doing shit, and also wayland bugs, well, it happen, software etc what i don’t understand why he want the global coordinate on the app?, where it could help?

    edit: the emulator want to save the local of the window and re-open it again, i give them the credit, there is merge requests being worked tho.

    i don’t think they are being unreasonable, they are getting complains that aren’t their fault(aka gnome) i could be pissed of too, and disabling for now until nvidia, qt, etc fix the bugs isn’t a bad thing too, also the code isn’t removed, you can enable wayland with the flag on flatpak

  • YamiYuki@lemmy.kde.socialEnglish
    1·
    11 months ago

    I figured that GNOME’s insistence on CSD few years back will bite them in the rear.

    https://github.com/PCSX2/pcsx2/pull/10179#issuecomment-1779298467

    And I don’t wanna be that guy that’s wants something to fail just because it’s not to my taste, but I’m glad to hear that the dev thinks KDE’s Wayland is in much better shape than GNOME’s, especially since GNOME’s pushing it really hard.

    For me, personally, I won’t switch away until Plasma 6 comes out, if it’s in much better shape than Plasma 5’s Wayland, and games running through Proton work well enough in Wayland competitively.