I’ve had a number of games mysteriously stop working on proton recently, like bopl battle, they severely lag the system on launch and sometimes need an REISUB reset to get my computer back.

This is new behaviour, these games have worked in the past.

Normally I’d go to protondb to see if there’s any information about how to fix it but when I go there, all I get is a pink square loading animation in the middle of the page and nothing loads. It’s been like this for the better part of a week for me at least.

Does anyone have any idea about what’s going on? Is it working for anyone else?

Edit:

Thanks for the replies everyone. It turns out that my noscript plugin was the problem. I enabled scripts for protondb.com but not for protondb.pages.dev which wasn’t showing up for me at first. I don’t know why I didn’t see it before.

  • undrwater@lemmy.world
    link
    fedilink
    English
    arrow-up
    8
    ·
    14 days ago

    Just FYI, when you ask these kinds of questions, provide your region, and ask for that if others.

    Here in southern California things are working as expected.

    • Excrubulent@slrpnk.netOP
      link
      fedilink
      English
      arrow-up
      4
      ·
      14 days ago

      I would have asked about that but I checked a few places through a VPN first.

      I turns out it was my noscript addon, I’ve put more details in an edit.

  • Wildmimic@anarchist.nexus
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    13 days ago

    Regarding your game issues: i had that the last 2 times my nobara (fedora) updated, where Proton games suddendly used my CPU for rendering out of the blue, lagging out my system so hard i had to reboot. Keep an eye on CPU load; if it’s this reinstalling Mesa Vulkan probably fixes it. I’m running an NVIDIA card.

    • Excrubulent@slrpnk.netOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      12 days ago

      Oooh, interesting, so you’re right that when I get the lag, there’s a lot of CPU usage. Also there was definitely a system update before it started happening - although I can’t say exactly when because I wasn’t gaming on this system for a few days.

      I’m on Mint 22.1 and I’ve tried uinstalling and reinstalling through the software manager GUI, and I’ve also tried:

      sudo apt purge mesa-vulkan-drivers
      sudo apt install mesa-vulkan-drivers
      

      None of that changed the problem. I also made sure I restarted the system.

      Am I doing that right? Are there any other steps that I’m missing?

      • Wildmimic@anarchist.nexus
        link
        fedilink
        English
        arrow-up
        2
        ·
        edit-2
        12 days ago

        I used the Nobara Driver Manager to do it, so i can’t really tell you how it works on Mint. It might be that youi have to reinstall your video drivers too, since those functions are closely related in my driver manager. FWIW, you might wanna look at the available renderer options for vulkan.

        This is where i can reinstall Mesa and my Drivers, maybe it helps:

        I explicitely chose Nobara because it’s well documented that Nvidia Cards tend to cause issues, and Nobara makes handling the situation easy.

        • Excrubulent@slrpnk.netOP
          link
          fedilink
          English
          arrow-up
          2
          ·
          12 days ago

          Okay, thanks, I’ll take a look at my options there.

          And I do also have an nvidia card. Thanks for the help!

        • Excrubulent@slrpnk.netOP
          link
          fedilink
          English
          arrow-up
          2
          ·
          8 days ago

          Hey, just letting you know I sorted the issue, the thread I opened about it on the mint forums is here if you’re interested in more details: https://forums.linuxmint.com/viewtopic.php?p=2691196#p2691196

          It turned out that the base mesa and mesa (extra) packages were duplicated on my system, so just uninstalling both of them and reinstalling only one copy fixed it. It wasn’t the mesa-vulkan-drivers though, but very similar to your problem. Your information did help me to the solution.

          Thanks for your help!