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.
Alright, then you haven’t done anything I haven’t done. I’m sure this will get fixed at some point.
Apart from this nitpick the experience is really good.
Nice. And what exactly did you do to fix waking up after suspend? This is pretty much the only thing not working for me. On Sway. But I’ve Hyprland installed as well. I just use it less than Sway.
I think I’ve read somewhere that FSR3 has trouble when there is a too low base of “real” frames it has to work with. So don’t expect it to do miracles in every scenario.
I too hope we can use it on Linux soon. Take note of this comment on the Proton Github page refering to a hack this person wrote: https://github.com/ValveSoftware/Proton/issues/7361
Hopefully something like this can be included in a future version of Wine/Proton/Proton-GE. Proton-GE doesn’t have an issue page. I think one would have to reach out via Discord. I don’t use Discord though.
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.
Paru has this funtionality build in. I don’t remember whether it is enabled by default though.
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.
Tell me if I’m wrong or that’s not what you meant. But your Nvidia problem should go away as soon as you use nvidia-dkms (or nvidia-open-dkms) instead of the regular nvidia package (or nvidia-open). I haven’t had any problems (of that kind) in a long time.
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.