There is a problem with GTX 1xxx cards (1660Ti in my case) running Proton 8+ for quite some time due to Nvidia driver, they’re unusable. Because of this even Experimental and GE branches are useless for me.

To be fair, Proton 7 is mostly enough. However, I cannot play one of my games after its update and it’s working fine with Proton 8 according to other people.

So, is there a workaround for this or I should wait for Nvidia’s Vulkan updates?

  • dinckel@lemmy.world
    link
    fedilink
    English
    arrow-up
    11
    ·
    7 months ago

    We’ll need more information from you.

    What is the problem? Which nvidia driver revision are you running? Which one of the games? What desktop environment, or window manager?

    • muhyb@programming.devOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      7 months ago

      Thank you for the reply!

      The problem is, when I try to run anything with Proton 8+, it immediately bottlenecks the GPU and everything kinda freezes because of it. Trying to change workspace and closing the game takes time, but at least it’s not impossible.

      By the way, Proton 8 was fine until driver version 535 (or 530, memories getting fuzzy).

      It’s independent from distro, DE or WM, and happens with every game. However, I’m on EndeavourOS, using bspwm, the game I currently try is 100% Orange Juice (it works fine, it just cannot connect to Steam after some update and apparently it works fine with Proton 8), and my driver revision is 550.67 but it’s been like this for some time.

      Also tried LMDE with Cinnamon so it’s definitely Nvidia. Someone said NVK doesn’t have problems like that but I don’t want go that route yet because I can play almost everything with Proton 7.

  • SSUPII@sopuli.xyz
    link
    fedilink
    English
    arrow-up
    6
    ·
    7 months ago

    I have no issues with Proton 8 on Nvidia GTX 1050 Mobile. Please be more specific with your info

    • muhyb@programming.devOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      7 months ago

      Thank you for the reply!

      I just wrote the details here: https://programming.dev/comment/9284416

      What is your driver version, you might be the first person I met who doesn’t have problems. If your driver is older than 535, that’s normal though.

      I have 1660Ti and same things happens with 1060 on a different PC. Doesn’t happen with 470 series driver for example.

      • Atemu@lemmy.ml
        link
        fedilink
        English
        arrow-up
        2
        ·
        7 months ago

        Note that 1660 ti and 1060 are from an entirely different generation of product; one is Turing the other Pascal.

        • muhyb@programming.devOP
          link
          fedilink
          English
          arrow-up
          1
          ·
          edit-2
          7 months ago

          I know but I read somewhere that it could be related to Nvidia’s Vulkan 1.3 implementation in their driver. It was fine when the version was 1.2. Generally cards without ray-tracing but somehow some of the older cards are fine apparently.