There's already the option to use a global config file with per-app overrides (DXVK_CONFIG_FILE=/path/to/dxvk.conf, documentation on the wiki: https://github.com/doitsujin/dxvk/wiki/Configuration), as well as the DXVK_CONFIG env var itself. No reason to add another env var that does something that can already be accomplished by two or three other means.
There's already the option to use a global config file with per-app overrides (
DXVK_CONFIG_FILE=/path/to/dxvk.conf, documentation on the wiki: https://github.com/doitsujin/dxvk/wiki/Configuration), as well as theDXVK_CONFIGenv var itself. No reason to add another env var that does something that can already be accomplished by two or three other means.
This makes sense, but the actual act of adding the exe to a master config file is actually pretty tedious ,user unfriendly compared to just a simple command and in some cases actually doesn't seem to work properly at all. The game war of rights. I can't figure out how to fix by putting its exes in the config file. It just doesn't work
In regards to War of Rights then that seems to be because you have to match against a all lower case exe even though the filename itself is mixed case [warofrights.exe].
Note that filtering can also work with the config env var. E.g. DXVK_CONFIG="[KillingFloor.exe]; d3d9.maxFrameRate = 5; [SR2_pc.exe]; d3d9.maxFrameRate = 1"
Gonna close this since the available options have been mentioned and there isn't appetite for a new env var.
DXVK_CONFIG="[KillingFloor.exe]; d3d9.maxFrameRate = 5; [SR2_pc.exe]; d3d9.maxFrameRate = 1"x1 2026-02DXVK_CONFIGx2 2025-12DXVK_CONFIG_FILE=/path/to/dxvk.conf`,x2 2025-12DXVK_ANISOTOPY=16x1 2025-12
If we could have one that short cuts to using a selected value like DXVK_ANISOTOPY=16 or -1 to disable
This way we can set aniso to 16x globally and more easily disable it for problem applications.