Navi 10: RX 5700, 5600
Navi 14: RX 5500, 5300

  • noodlejetski@lemm.ee
    link
    fedilink
    English
    arrow-up
    5
    ·
    12 days ago

    The NGG culling override can be forced on existing Mesa releases if desired using the “RADV_PERFTEST=nggc” environment variable override.

    so I assume it’s worth trying it out on Navi 14?

    • mox@lemmy.sdf.orgOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      12 days ago

      I would definitely try it. If it doesn’t help any game, or if it causes glitches/crashes, an environment variable is easy to revert.

        • hellofriend@lemmy.world
          link
          fedilink
          English
          arrow-up
          4
          ·
          edit-2
          12 days ago
          YOUR_VARIABLE=1 %command%
          

          In Steam launch options for a specific game.

          So, in this case:

          RADV_PERFTEST=nggc %command%
          
          • A_Random_Idiot@lemmy.world
            link
            fedilink
            English
            arrow-up
            2
            ·
            12 days ago

            ah, my bad… I didnt realize it meant just putting it in the games launch options. I thought it had to be set in some file or something. Thank you for the clarification.

            • mox@lemmy.sdf.orgOP
              link
              fedilink
              English
              arrow-up
              2
              ·
              11 days ago

              It doesn’t necessarily mean putting it in a game’s launch options. Environment variables can be set in a startup script, or a flatpak config, or a command line, for example. But the Steam launch options approach is convenient when you’re just testing something for one specific game.