So Linux is nothing like Windows–like at all, in any way that you are used to.
There is no control panel for AMD GPUs because AMD stopped making their own driver. What you have is Mesa, which is a multi-vendor graphics stack that is used by Intel, AMD, and various GPUs that are integrated into ARM / RISCV SoCs. Valve, AMD, and various other folks help develop the RADV (Vulkan) and RadeonSI (OpenGL) drivers within Mesa for AMD GPUs.
There are some environment variables that you can use to enable certain features with RADV and RadeonSI that the Windows AMD driver had as options like anisotropic filtering. Then you have the graphics API wrappers like DXVK and VKD3D-Proton that have their own config files and environment variables that can be used to enable certain features that the AMD control panel would have also let you configure. An example would be anti-aliasing.
#Force anisotropic filtering with RadeonSI for OpenGL apps / games
AMD_TEX_ANISO=16
#Force anisotropic filtering with RADV for Vulkan apps / games
RADV_TEX_ANISO=16
#If AMDVLK is installed along side mesa's RADV, you can manually select which Vulkan driver to use with the following env var:
AMD_VULKAN_ICD=<RADV|AMDVLK>
Wine and Proton also have their own environment variables to configure things for Windows apps/games.
Basically, since the Linux userspace is not developed by a single entity, rather a host of different parties, configuration is scattered into different projects that work together.
I’d personally suggest reading up on the environment variables provided by Mesa here:
And do the same for DXVK and VKD3D-Proton.
As for “FSR4 upgrade” with Proton, all Proton does is download the 4.0.2 amdxcffx64.dll from AMD’s website and places it in the system32 directory. Yes, that is all that envvar does. What actually matters is VKD3D-Proton loading the amdxc64.dll that is included with Proton which in-turn loads the amdxcffx64.dll. This mimics AMD’s Windows driver and performs the “upgrade”. Turns out that RNDA2+ can just use the int8 DLL, and for RDNA3 get roughly 12% better performance over the fp8 DLL, but you need to rename the upscaler DLL or make a symbolic link to it named amdxcffx64.dll and you can use either the int8 4.0.2 or fp8 4.0.3 “Redstone” FSR4 algorithm. It’s laughably simple once you understand what to do. But was a head scratcher for me at first.
You can see my demystification of this and how you can use the FSR4 upgrade with normal Wine too here:
https://discuss.cachyos.org/t/fsr-4-0-3-with-vanilla-wine-on-rdna3-yes-it-actually-works