It ranges from significant performance differences between the drivers with specific games to games having rendering issues with specific drivers. A lot of games don’t work at all with the proprietary driver.
My most recent issue was with the Indiana Jones game having horrible traversal stuttering making some areas basically unplayable on RADV, but AMDVLK had no stuttering and better framerate overall.
I’m not using an immutable distro and the issues with the Vulkan drivers have nothing to do with them.
AMD is just simpler because you don’t have to manage the drivers, but it’s really not a big deal. It’s very easily handled.
Honestly this isn’t as true as I was led to believe it was before I switched to AMD. Just like Nvidia has issues between the proprietary driver and nouveau; AMD has its own mix of issues with Vulkan between RADV (mesa), AMDVLK, and AMD’s proprietary driver on a per-game basis at times.
I tried fish before switching to zsh because it has much better compatibility with bash, and I think bash/zsh handles a lot of things like aliases way better. I’m also on CachyOS and the default zsh config with ohmyzsh and powerline10k it comes with is great.
I like the workflow of having a DNS record on my network for *.mydomain.com pointing to Nginx Proxy Manager, and just needing to plug in a subdomain, IP, and port whenever I spin up something new for super easy SSL. All you need is one let’s encrypt wildcard cert for your domain and you’re all set.
RADV has the least issues but I still tend to test AMDVLK (vulkan-headers makes switching drivers per-game easy) for any big performance differences, and it’s typically the first thing I try for crashes now. If you want to use ray tracing at all you should definitely use AMDVLK, it performs way better.