I just learned that PROTON_ENABLE_NVAPI=1 to enable DLSS got changed to PROTON_FORCE_NVAPI=1 in Proton 9.0 (including Proton Experimental). Just in case this helps someone in the future.
On another note: Feel free to let me know if you've got a good way to keep up with necessary/useful launch options. I've simply been having a look at what people use on ProtonDB. But I've come to the conclusion that a lot of the posts there use outdated or simply false launch options.
Didn't have any Problems playing (the one round that I did play). If one has played Tribes before one will feel right at home. Pretty sure they switched the default keybindings up a bit. Shift for sliding and Space for the jetpack.
Woooo!! Just played my first round. I have such fond memories of Tribes Ascent.
Here is hoping it stays this way and they keep allowing Linux players.
Just to be sure. Are the options "Enable Steam Play for supported titles" and "Enable Steam Play for all other titles" in Steam Settings >> Compatibility both set?
First and only thing that came to mind. Maybe somebody has more ideas.
Edit: Whoa, seems I was late to the party.
It might be that your distribution of choice has slightly different defaults in the files compared to regular Archlinux.
Either way you'll want to have a look at either Meld (graphical) or something like pacdiff (terminal). With these you can easily see the differences between your old file and the new .pacnew.
The new default is not always better. One example: Whenever Archlinux creates a new /etc/makepkg.conf.pacnew I don't simply overwrite the old file. The new default would comment out the line which defines how many CPU threads I want to use to build packages and reduce it to one thread (I assume).
You really don't have to understand every line in every file. Most often it's quite easy to determine whether you want the new changes or not. Just always have a quick look at what is different. You don't want to replace old files mindlessly.
Just to make sure. Are you aware of Tridactyl?
And apparently the plan is to have explicit sync ready for the next major driver version (v555).
From the discussions on Github and Gitlab it seems the work for that to happen is done. The changes in the necessary packages (Xwayland, Mesa?) just need to be merged and the the Nvidia driver 555 needs to be released. It hasn't been that long since the previous release 550. So I guess it is going to take a bit of waiting still.