As you may be aware, Valve has released a new Steam client version not too long ago with many changes, including the release of the new Big Picture Mode that is inspired by the Steam Deck’s interface. It’s a great way to browse your games on a large screen, it looks way better than the aging old BPM, and is a welcome addition to the desktop client. However, there’s some problem with Nvidia GPUs on Linux: it seems like a lot of us are plagued with very poor performance in this mode (while the normal client is not affected).
On my machine, it’s something like 5 FPS or so, which is really bad. It’s been noticed by several Nvidia GPU users already on a specific issue on Github:
A few more observations:
- on Linux, AMD users are not affected by this problem
- on Windows, AMD and Nvidia seem to have no problem whatsoever running this new BPM with great performance.
Nils took a quick video of how the interface performed on his older MacBook with Intel HD5000 and you can see it’s working just fine there:
The strange thing is that the previous BPM had no such problem on the very same hardware, so there’s definitely something amiss in regard to the interface with the (proprietary?) drivers for this new BPM.
Let’s not forget that most gamers on Linux use Nvidia, so this is bound to impact quite a few of us. Will report back once a fix is found, or a new Steam update fixes the issue.
You might want to check out the following articles too!
BoilingSteam lets you access our content for free, but writing articles is a constant investment. We don't use ads or sponsporship, help us make our activities sustainable by donating via Patreon or LiberaPay if you prefer it anonymous. You can follow what we do via our newsletter, our RSS feed, our Mastodon profile or our Twitter feed. We also have Peertube, Youtube and LBRY channels. If you'd like to chat, you can also find us on #boilingsteam:matrix.org. (what is Matrix?)
Yes this has been the case for a year now on steamOS, it got me to switch to an AMD graphics card, even tho I loose out on HDMI 2.1 and raytracing. If they could do something about it, it would have already happend so I doubt there is an easy solution.
I have the same issue. I’ve noticed it since the new BPM UI was being worked on in beta. I’m shocked this wasn’t resolved before it was pushed to the stable client.
Are you sure?
Yes very sure. Numerous surveys and ProtonDB still indicates that.
Sorry, I forgot to tell you.
I am running Fedora 37 with Gnome on that MacBook Air 2013 test.