• Bruno Finger@lemm.ee
    link
    fedilink
    English
    arrow-up
    14
    ·
    11 months ago

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

    • xan1242@lemmy.ml
      link
      fedilink
      English
      arrow-up
      13
      ·
      11 months 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.

    • bgtlover@linuxrocks.online
      link
      fedilink
      arrow-up
      1
      arrow-down
      2
      ·
      11 months 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?

      • Bruno Finger@lemm.ee
        link
        fedilink
        English
        arrow-up
        3
        ·
        11 months 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.

      • xan1242@lemmy.ml
        link
        fedilink
        English
        arrow-up
        2
        ·
        11 months 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.