- cross-posted to:
- phoronix@lemmy.world
- cross-posted to:
- phoronix@lemmy.world
Navi 10: RX 5700, 5600
Navi 14: RX 5500, 5300
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?
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.
how does one add it as a variable?
YOUR_VARIABLE=1 %command%
In Steam launch options for a specific game.
So, in this case:
RADV_PERFTEST=nggc %command%
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.
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.