They’re talking about this Squad.
They’re talking about this Squad.
I haven’t gotten around to trying the stable release out, but there’s one ProtonDB report - presumably for 6.0 given the post date - so far that says it works flawlessly.
I’m guessing the situation is the same as pre-6.0, though. I participated in some of the playtests, where I got the same performance issues that I got before with the game slowing to a crawl after some time. The user on ProtonDB also has pretty beefy specs, so I couldn’t say if the performance issues were fixed, either. I’m not sure if you’re asking if it’s playable or has gotten better, so I will say that (at least for pre-6.0) it technically works regardless as long as your computer is beefy enough.
The Proton GitHub issue for Squad might be nice to bookmark to make or check up on every once in a while; usually any issues, fixes, and updates end up there.
It’s my pleasure :)
Just a note if you plan on installing Guix on top though, since I didn’t realize you might be running NixOS: according to this discussion, you’d need to take a different route to get Guix working.
I do!
For starters, you’re not required to install Guix System in order to use the Guix package manager itself; the manual provides instructions for installing it on top of your existing system here if you want to use it but not fully commit (you can do this with Nix too).
Guix allows for adding new sources to pull packages from using channels. The nonguix channel provides the Linux kernel - blobs and all - as well as other stuff that won’t be upstreamed, like Steam and NVIDIA drivers.
I recommend this helpful series by System Crafters, which includes a few guides on installing Guix and Guix System with the full Linux kernel.
You might find The Full-Source Bootstrap: Building from source all the way down by some of the GNU Guix maintainers of interest to read, which discusses how Guix is attempting to solve the “trusting trust” attack some have mentioned here.
Although I haven’t used it myself yet, Guix actually has a feature that lets you “challenge” the build servers to see if your builds match the pre-built binaries (the command being aptly named guix challenge
).
I have for the past half year. I don’t have numbers, but rolling with the NVK vulkan driver (context for the unaware [1]) on mesa’s main branch gets me somewhere around half the proprietary driver’s performance on average, and can be accompanied with stutters if it is a heavy bottleneck (turning down the resolution is an easy way out). Most games I’ve tried are runnable now.
It sounds like you’re looking for more performance with this post though, so you’re likely not going to see improvements taking this route. I would still suggest giving it a try for people that are able and can tolerate the sacrifice. It’s good enough for me (and better in the wayland case) that I rarely swap to the proprietary driver anymore.
Mesa has a tracker issue for games on NVK [2] [3] with reports about game statuses and issues from the past 5 months. It includes playable and unplayable games for those interested in gauging its usability.
Also, for the record, NVK is no longer considered experimental as of mesa 24.1 (May of this year) [4].
[1] https://www.collabora.com/news-and-blog/news-and-events/nvk-has-landed.html
[2] https://docs.google.com/spreadsheets/d/1RuHD3Z_nBKCp618HHC5I9hOu0lqCoFYwQ4FM69M-Ajg/edit?gid=469568508#gid=469568508
[3] https://gitlab.freedesktop.org/mesa/mesa/-/issues/11066
[4] https://www.collabora.com/news-and-blog/news-and-events/nvk-is-now-ready-for-prime-time.html