I think this issue might be related to the same problem I have for a 4k resolution device: when I press the Guide Button during gameplay the overlay take 5 seconds to load, but you can barely interact with it due to slowness. For 1080p it renders fine.

Specs:

• Steam build: Nov 17 2022
• O.S: ArchLinux
• Kernel: 6.0.8
• GPU: RX 6700 XT 12 GB (Mesa 22.2.3)
• CPU: Ryzen 7 5700G

With linux and Nvidia, new UI is slow and choppy.
I try it on Win 11, and it's fast here.

I'm having this issue too, furthermore when opted out of the beta big picture mode crashes after a minute or so with different error messages, so I am currently forced to use the beta big picture mode which is difficult to navigate due to this issue.

The fact that NBP is now out of beta, set to default and everything and this still isn't fixed is very disheartening. In what way was it ready for release when 1/2 major gpu vendors outright don't work well at all with it on linux?

Same right here. Hoped for it to get fixed before getting out of beta. I'm currently on a Ryzen 5 5600X and RTX 3060 sys with Arch Linux. It runs at about 15-20 fps on fullscreen, 1440p, but smoother on a ~720-1080p window.

Same right here. Hoped for it to get fixed before getting out of beta. I'm currently on a Ryzen 5 5600X and RTX 3060 sys with Arch Linux. It runs at about 15-20 fps on fullscreen, 1440p, but smoother on a ~720-1080p window.

Yeah, at 720p to 1080p its serviceable, but above that its objectively unusable. For awhile it seemed like they were working on it what with adding the force acceleration option (that doesn't work) but now I'm honestly not sure.

I'm having the same problem on Debian Testing at 4k. RTX 3080 and it is slooooooow.

Same Problem :(

Same problem with Steam up to date as of today.

• OS : Fedora 37
• Desktop environment: GNOME 43.1
• CPU: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz
• GPU: GeForce GTX 970
• Kernel version: 6.1.9

I went into BPM's Settings -> Display and enabled Disable GPU Blacklist to see if it'd improve performance on my Nvidia card and now all I see is a black screen. Is there a command line switch or a config file I can edit to change that back to off?

EDIT: Deleted ~/.steam/steam/config/config.vdf to reset my settings and it works again now, albeit with the slow software rendering.

So SteamOS Holo doesn't work with nvidia cards and BPM barely works with no updates concerning the issue from Valve. Fucking great.

Newest beta patch notes mentioned improved NV performance, but it seems to have improved nothing on Linux.

Can confirm; this "improved" Nvidia performance seems to be non-existent
Additionally but unrelated, this update also brought the desktop mode HiDPI scaling bug back :tada:

Still having the same problem on beta branch. RTX 3090

Could you all please stop with the "me too" posts that add nothing to the topic? Thank you.

@DanMan I'm sure that the volume of "me too" posts would reduce if we got any sort of acknowledgement of this issue from developers. Currently the new big picture mode is in the "stable" branch despite the fact that more than half of users are experiencing an issue that makes it totally unusable, and it has been unusable for months with no recourse.

Generally on GitHub if you are being annoyed by an issue discussion, it is considered your responsibility to unsubscribe.
This can be accomplished by clicking this little unsubscribe button in the upper right.

I hope this helps you understand what's happening, why people are frustrated, and how you can opt out of the conversation if you would like. I'll also point out that your telling people to shut up is not adding anything to the discussion either, and in fact goes against the GitHub Community Guidelines, and violates the request for polite and respectful discussion in the README of this repository.

Well, considering the amount of people having an issue with this and for how long it is a problem it should already be solved, but I guess that's how it goes in cases like this. Maybe soon the time will come for conspiracy theories that devs are not allowed to fix Nvidia issues.

Here to toss my hat in the ring. Been having the issues for months. Was shocked to see the official release without a fix.

OS: Nobara Linux 37 (Thirty Seven) x86_64
Kernel: 6.1.11-201.fsync.fc37.x86_64
Resolution: 2560x1440
DE: GNOME 43.2
WM: Mutter
CPU: Intel i5-6600K (4) @ 4.400GHz
GPU: NVIDIA GeForce RTX 3060 Ti
Memory: 32057MiB

Same issue, extremely laggy at about 2fps.

OS: Arch
Kernel: 6.1.12-arch1-1
CPU: AMD Ryzen 9 5950x
GPU: Nvidia RTX 4090
WM: XMonad
Memory: 64GB

Have tried stable and beta.

I have had the same issue for a while. The big picture mode is completely unusable.

OS: Fedora 37
Kernel: 6.1.11-200.fc37.x86_64
CPU: AMD Threadripper 2920X
GPU: Nvidia RTX 2080ti
DE: Gnome 43.3 running on Wayland
Memory: 48GiB

I'll join the "me too" train. (Sorry DanMan)

OS: Fedora 37
CPU: Ryzen 3600
GPU: Nvidia RTX 2060
DE: Gnome on Wayland

I don't know the exact kernel but it's the latest Fedora one (6.1.11 i think).

All you people achieve is that the ones who could actually do something about it will stop looking here, because they'll get increasingly annoyed by all the "are we there yet?". Not just in this issue, it can be seen in many of them.

If you actually added something new to the discussion, like some debugging logs or whatever… sure. But you don't. Because there isn't really anything you can do.

It runs slow on Nvidia. They know about it. All you can do is wait.

All you people achieve is that the ones who could actually do something about it will stop looking here, because they'll get increasingly annoyed by all the "are we there yet?". Not just in this issue, it can be seen in many of them.

If you actually added something new to the discussion, like some debugging logs or whatever… sure. But you don't. Because there isn't really anything you can do.

It runs slow on Nvidia. They know about it. All you can do is wait.

Your reasoning is blowing my mind. A single user reports a bug. Alerts devs that it is an issue, and not a one off thing? Yeah that's how bug reporting has always gone, sure.

The majority in this topic are not saying "are we there yet?". Scroll up, it's just people reporting.

No one is rushing Valve and the devs. More people reporting is a good thing.

Joining the "me too" train too. This bug is annoying, and I hope it gets fixed.
OS: Pop!_OS 22.04
Kernel: 6.2.0-76060200-generic
CPU: i7-12700H
GPU: Iris Xe + RTX 3060M (with the 525 proprietary drivers) 115W (optimus is set to NVIDIA)
DE: GNOME 42.5
RAM: 64GB

Me too. Very buggy, much annoying:

• OS : Ubuntu 22.04
• Desktop environment: GNOME 42.5 (X11)
• CPU: Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz
• GPU: GeForce GTX 1070 (nvidia 525 drivers)
• Kernel version: 6.1.0

Same issue here
Running Linux mint 21.1 xfce
Old i5
Radeon hd 6670
8 gigs of ram.
1080p

I used to have windows on the machine and the interface was buttery smooth. Switched to Linux to get rid of forced updates and bloat only to find the big picture interface running at 10fps.

Also experiencing this problem on Arco with an RTX 3060ti, 32GB RAM, Linux 6.2.7

Also got the same problem. Very annoying.

Distro: Linux Mint 21 Vanessa
DE: Cinnamon 5.4.12
Kernel: 5.15.0-67-generic
Drivers: Nvidia 525.85.05
CPU: AMD Ryzen 5 2600
GPU: Nvidia GeForce GTX 980 4GB
RAM: 8092MB
Resolution: 1920x1080@60Hz

same thing here.

OS: Arch
Kernel: 6.2.8-arch1-1
CPU: Intel i7-4790K
GPU: Nvidia GTX 1060
DE: KDE Plasma (wayland)
Memory: 16 GB

Newest beta kills support for running the old BPM.

Valve I dunno what you're doing, but I don't think you can delay this fix any longer.

How come it works fine on the deck (essentially, a linux pc) and not on regular PCs running linux?

The Deck uses an AMD GPU. This affects Nvidia GPUs.

On Tue, 28 Mar 2023, 12:37 pm emmandyar, @.***> wrote:

How come it works fine on the deck (essentially, a linux pc) and not on
regular PCs running linux?

—
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/steam-for-linux/issues/8918#issuecomment-1486705112,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AU3GRGIOD5D3LEQ4KQ2DEJDW6LEQZANCNFSM6AAAAAASCDUORM
.
You are receiving this because you commented.Message ID:
@.***>

@emmandyar It might not be essentially issue with new bpm itself. Considering that it doesn't lag at all when you lower the resolution a lot it would be safe to assume that it just uses CPU rendering. And that after all since it is a web desktop app there might be issue with the framework they're using not enabling GPU rendering on Nvidia or steam forgetting to implement some settings that would allow it. Though yeah, without any information we can just toss our specs and guesses just like me mine here here and wait for the actual maintainers who can see it fix it.

How come it works fine on the deck (essentially, a linux pc) and not on regular PCs running linux?

Lower resolution. Plus AMD over Nvidia.

There are a couple of reports of AMD GPUs having the same issue, one very old (HD6670) and one far more recent (RX 6700 XT), that's why I thougjt it was a more generalized issue and not nvidia-specific

Hm, interesting.

Clearly NBP should not be out of beta yet.

Edit: I should say I knew of the HD 6670 instance, but must've put it down in my head to the old radeon driver. I didn't know of the 6700 XT. It seems to primarily affect Nvidia GPUs, though.

On Tue, 28 Mar 2023, 12:51 pm emmandyar, @.***> wrote:

There are a couple of reports of AMD GPUs having the same issue, one
very old (HD6670) and one far more recent (RX 6700 XT), that's why I
thougjt it was a more generalized issue and not nvidia-specific

—
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/steam-for-linux/issues/8918#issuecomment-1486724244,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AU3GRGPSR6LQYG4AERRLKK3W6LGEZANCNFSM6AAAAAASCDUORM
.
You are receiving this because you commented.Message ID:
@.***>

As a daily user of Big Picture Mode, I am extremely frustrated with the removal of Old Big Picture Mode.
Regardless of which NVidia GPU I use, I am unable to use the New Big Picture Mode at all due to the performance issues.

I recently built a TV PC out of older hardware (my first comment here has the specs) and bought an older Nvidia card to save money. Big Picture is essential for that, and it's practically unusable. The Collections section of my library is the worst, with it basically being 1-2 FPS.

It is very irritating that NBP acts as if it's running on hardware from 2001 when in reality the CPU is from 2018 and the GPU is from 2015.

same here it looks like this on a 3080.

https://user-images.githubusercontent.com/5399780/228371194-bcef4a3a-4b07-49d8-9a69-f90823a433a2.mp4

Same here. Don't know why valve pushed the new gamepadui to stable if its still that buggy..

OS: Chimera 39 and Nobara 37
Kernel: 6.1.11 (Chimera), 6.1.14(Nobara)
Driver: Nvidia 525.89.02
CPU: Ryzen 9 3900X
GPU: RTX 3080
RAM: 32GB

Same here. Don't know why valve pushed the new gamepadui to stable if its still that buggy..

OS: Chimera 39 and Nobara 37 Kernel: 6.1.11 (Chimera), 6.1.14(Nobara) Driver: Nvidia 525.89.02 CPU: Ryzen 9 3900X GPU: RTX 3080 RAM: 32GB

I guess they are mainly focussed at the time on improving steam wide deck (it has a AMD GPU) support, and linux desktop gaming looks like a side effect to me.

At least the "gamepad ui" appears to be the same and evolve at the same rate on desktop and on steam deck from my perspective with my current stuff. I would like valve continue their epic game changing support for linux for the whole platform.

For me it will be fixed in a near future (from a small gamer perspective watching linux gaming improve dramatically each year). I guess they have limited time and ressources or at least the team busy with this maybe have to finish other things before going back on this topic. This is pure speculation and expectation though :D .

[edit] Side note appart, I think Nvidia and cloud stream platform in general would have (at least naïvely, because commercial people love to keep companies locked in with more or less usefull commercial licences) a lot of interest in investing in this change which can be a big deal. Today gaming support is on Windows, but what if nvidia could drop their hundred (but it is surely more thousands ?) microsoft windows server licences (but maybe this is already done in a way or another)?

If you hear me Valve, I love what you do ;)

If you hear me Valve, I love what you do ;)

Hear, hear!

Same issue here

OS: Manjaro Linux
Kernel: 6.1.19-1-MANJARO
Driver: Nvidia 525.89.02
CPU: Intel Core i7-6700K
GPU: Nvidia GeForce RTX 3060
RAM: 32 GB

Having the same issue on my machine, seeing as it's Nvidia specific

OS: Arch Linux
Kernel: 6.2.9-arch1-1
Driver: Nvidia 530.41.03
CPU: AMD Ryzen 7 3700X
GPU: Nvidia GeForce RTX 2080 Super
RAM: 32 GB

Me too :)

OS: Arch Linux
Kernel: 6.2.10-arch1-1
Driver: nvidia 530.41.03
CPU: Intel Core i7-4720HQ
GPU: NVIDIA GeForce GTX 860M
RAM: 16GB

Me too
OS: Nobara/Fedora 37 - Gnome 43
Kernel: 6.2.8-200.fsync.fc37
Driver: nvidia 525.105.17
CPU: Ryzen 7 5800X
GPU: RTX 3080
RAM: 32GB

OS: Nobara Linux 37 - GNOME (Xorg)
Kernel: 6.2.10-200.fsync.fc37.x86_64
Xorg: 1.20.14
Driver: NVIDIA 525.105.17
CPU: AMD Ryzen 9 7900X 12-Core Processor
GPU: GeForce RTX 4090 (NVIDIA) / Raphael (AMD)
RAM: 64GB DDR5

OS: Garuda Linux x86_64
Kernel: 6.2.11-zen1-1-zen
Resolution: 3840x2160
DE: GNOME 43.4
WM: Mutter
CPU: AMD Ryzen 5 3400G (8) @ 3.700GHz
GPU: NVIDIA GeForce RTX 3060 Ti Lite Hash Rate
Memory: 32GB

@kisak-valve

Apologies for the mention, but I am pulling my hair out. New, tangentially related, issues opened have been closed by Valve moderators/contributors with reference to #8918 but there has literally been no comment by Valve on the frequently referenced issue #8918 since it was opened in November. Worse, I cannot get -oldbigpicture to work, as it only opens the desktop client, seemingly ignoring the flag (kitty screenshot included). I love the new look and how easy it is to implement controller configs but it's unusably slow.

Some of the steps I have taken to troubleshoot:

• Trying multiple Arch installs, Fedora 36/37/38, and Pop OS (bare metal installations to test out other packages I am building)
• Toggling Steam's Hardware Acceleration (testing both with it off and back on again)
• Nuking the steam install folders, removing Steam, and then installing Steam
• Installing Steam via flatpak
• Run on numerous versions of NVIDIA Drivers from 510.85.02 to 530.41.03
• Toggling various power modes in nvidia-settings
• Patched and un-patched NVIDIA drivers (getting Sunshine to work with Moonlight)
• Continually trying both stable and beta steam update channels

I buy and play video games for fun on the couch, not to mess around with troubleshooting an issue that should have been patched months ago - an issue which Valve has pointedly ignored for 6 months. It's well understood NVIDIA sucks when it comes pretty much every aspect, especially Linux driver support^. I also understand Valve wants to focus their Linux efforts on projects and fixes which apply to the Steam Deck. However, I think it is safe to say that users would appreciate an official statement from Valve acknowledging the issue and stating a (relatively soon) timeline for a fix.

Specs

OS: Fedora 38 (current)
Kernel: 6.2.11-300.fc38.x86_64 (current)
WM: Plasma 5.27.4 (current)
CPU: Ryzen 9 5950x
GPU: EVGA 3080 Ti FTW3
Motherboard: ASRock X570 Taichi
Memory: 32GB G. SKILL FLAREX 3200 @CL14

^(my 3080 Ti purchase months before the 7900XTX release remains one of my biggest purchasing regrets, no matter how good of a deal the 3080 was)

(edit) Edited for small clarifying changes

Or at least valve should not remove the oldbigpicture from steam.

About -oldbigpicture it's working for me on non-beta. With beta i can enter on OldBigPicture pressing Alt + Enter (not clicking on bigpicture icon).

Is it stable? From what I know it wasn't removed yet, but often crashes and is very unstable without a clear reason for many users.

I have a steam deck, and it runs great. Because of my steam deck I tried to run linux as my daily driver on my gaming pc. And yeah, it makes it hard with steam running like this.

Same issue as everyone else. Slow and buggy.

@steam Devs. What are we doing here. You wanted to support linux gaming, support linux gaming

OS: Pop!_OS 22.04 LTS x86_64
Kernel: 6.2.6-76060206-generic
Shell: bash 5.1.16
Resolution: 2560x1440, 1920x1080
CPU: AMD Ryzen 5 5600X (12) @ 3.700GHz
GPU: NVIDIA GeForce RTX 3080 Lite Hash Rate
Memory: 32GB

Works here, it's about resolution (HW Acc), Old-BPM runs only in 1080p... New-BPM works well too in 1080p. It's like on browsers, if you don't activate Video Acc (VDPAU), you can play well 1080p but 2160p is laggy.

@Hideiuke New BPM is just a web view and we've had hardware accelerated web views on Nvidia and X11 just fine in basically every browser. This is just a bug that Valve needs to fix, not some Wayland requirement like you say it is. VDPAU has no relevance here as this is not about hardware video decoding or encoding.

come on steam, this is getting embarrassing.

does it work for anyone on the Steam Client Beta? Doesn't work for me even though they stated hardware acceleration would be enabled for Linux and Mac users.

Mac & Linux:
The technical work in this update also makes it possible to enable hardware acceleration for the Mac & Linux versions of Steam, bringing them up to par with Windows. You should see snappier animations, scrolling and more responsive UI. Linux users can try the new client out today! For Mac users, you will have to wait a couple weeks as we are hard at work getting the client ready for public testing.

Noooope

:(

I'm on the beta client with the Nvidia 530 driver on an RTX 3090. I am seeing ~10 FPS in big picture mode. I'd expect much higher performance. Something seems off.

Affected by this as well

Your system information

• Steam client version: Apr 29 2023 | 1682723851
• Distribution: Mint 21.1
• Opted into Steam client beta?: Yes (tried public too)
• Have you checked for system updates?: Yes
• GPU: NVIDIA RTX3060ti

Also having severe performance issues in new bpm.

Me Too 🫠

OS: Kubuntu 23.04 x86_64
Kernel: 6.2.0-20-generic
DE: Plasma 5.27.4
CPU: AMD Ryzen 7 3700X (16) @ 4.050GHz
GPU: NVIDIA GeForce GTX 1070
GPU: NVIDIA GeForce RTX 3070 Lite Hash Rate
Memory: 13552MiB / 31992MiB

same bug
Main Laptop: Dell G15 5510
Specs of the Laptop:
CPU: Intel(R) Core(TM) i7-10870H CPU @ 2.20GHz 2.21 GHz
GPU: Intel UHD
GPU 2: RTX 3060 Laptop GPU Moblie GPU
Ram: 16.0 GB (15.8 GB usable) SODIMM DDR4 2933 MHz
Storage: BC711 NVMe SK hynix 512GB, CT500P2SSD8 500GB
External Storage: WD My Passport 2627 USB Device 2TB
OS: Ubuntu 23.04 (512gb)

So I did some testing, with my laptop's integrated GPU on the i7-12800H processor, I get excellent framerate and responsiveness in the UI. When I switch to the Nvidia one, it runs like a slideshow. I think this is an Nvidia-specific issue where for whatever reason it's not using GPU acceleration on those cards.

New beta notes

Fixed hidpi scaling not working on Nvidia GPUs.
Fixed HW acceleration not being enabled on Nvidia GPUs.
Fixed Big Picture mode performance when using Nvidia GPUs. Known issue: some visual artifacts may appear. Use -disable-desktop-gl-fallback to restore previous behaviour if desired.

Artifacts are indeed present, and its not perfect perf wise, but BPM is actually usable now on NV Linux.

Looks like the beta resolves this slowdown for me but artifacts are definitely there. Very smooth for me.

Artifact example:

ESC key doesn't seem to back out anymore either, probably not an NV issue though.

Artifacts are indeed present, and its not perfect perf wise, but BPM is actually usable now on NV Linux.

It is noticeably MUCH better than before. Looks like they just have to fix a few visual glitches.

It freezes up a lot almost like a stutter when if you had hardware acceleration turned OFF these stutters wouldn't happen and it would load stuff faster

For me it just crashed the entire desktop enviroment. I'm on KDE Plasma X11 and opening big picture gave a black screen then booted me to the OS login screen.

For me it just crashed the entire desktop enviroment. I'm on KDE Plasma X11 and opening big picture gave a black screen then booted me to the OS login screen.

Same here. I had it opened in windowed mode, and once I entered fullscreen it crashed my Plasma session.

Please see if running with -disable-desktop-gl-fallback fixes this.

On Fedora 36, Gnome 42.9, X11, Nvidia 3060Ti (driver 530.41.03) BP works really well now. Haven't even noticed artifacts yet.

But if I open a link in a new window in desktop mode by clicking it with the middle mouse button and then close the window, it seems like Steam crashes and restarts itself. Might also just be the GUI restarting, dunno. Console prints:

GLib-CRITICAL **: 15:26:28.257: g_main_context_pop_thread_default: assertion 'g_queue_peek_head (stack) == context' failed
steamwebhelper.sh[19735]: Runtime for steamwebhelper: defaulting to /home/username/.local/share/Steam/ubuntu12_64/steam-runtime-heavy
steamwebhelper.sh[19735]: glibc >= 2.34, partially disabling sandbox until CEF supports clone3()

Not sure, if that's related, but it didn't happen before this beta version was released.

Please see if running with -disable-desktop-gl-fallback fixes this.

Using -disable-desktop-gl-fallback does indeed fix my "closing the new window" issue.

Using -disable-desktop-gl-fallback makes Steam not crash KDE Plasma, but it also makes Big Picture refuse to run in fullscreen.

Like others the big picture UI recently seemed to be GPU accelerated on the beta branch. However, with the beta update that auto-applied this morning I am back to the same choppy awful mess. Definitely a regression at least for me.

Kernel: Linux 6.3.2-arch1-1
Desktop Environment: KDE DE w/ X11
Drivers: Nvidia 530.41.03
Steam Version: 1684535786
Steam Client Build Date: Fri, May 19 6:00 PM UTC -08:00
Steam Web Build Date: Fri, May 19 6:13 PM UTC -08:00

AMD R9 5950X
EVGA 3080 Ti FTW3

Same for me. Performance was much better, but the update today got me back to a laggy UI.

Ryzen 7800X3D
GeForce 4080
Manjaro Linux
KDE

@kisak-valve when I enable this option and start big-picture mode my kde session crashes/restarts xD

Edit: it worked fine before the latest patch

Edit2: now it works like expected ... maybe just a hickup. Thanks for the hint with the parameter!

@antekmeco Have you tried the parameter "-enable-desktop-gl-fallback"?

hmmm for me big picture outright crashes without -enable-desktop-gl-fallback, wonder why

For me, the beta fixes the issue on Arch, but not Gentoo...

I have not yet tried the -enable-desktop-gl-fallback flag

Can confirm on NVidia RTX 3080 Ti, that the "-enable-desktop-gl-fallback" fixes this problem only in combination with the beta release of the Linux Steam Client on EndeavorOS (Arch-based distro).

For clarification, anyone who wants the full-speed BPM (at least on Arch), go to Settings -> Account -> Beta Participation and change that to "Steam Beta Update", and then launch Steam with the command line option "-enable-desktop-gl-fallback". Using only one of these two things does not fix the issue for me.

Hopefully this is fixed by default soon.

With the latest beta the lags are back. Even with the "-enable-desktop-gl-fallback" parameter -.- I don't get it, why it is so hard to get this UI running on NVIDIA Cards :(

With the latest beta the lags are back. Even with the "-enable-desktop-gl-fallback" parameter -.- I don't get it, why it is so hard to get this UI running on NVIDIA Cards :(

Cannot confirm. Still works much better than without it. New windows even don't seem to crash the desktop client anymore, or at least less often.

I'm using this one: https://store.steampowered.com/news/group/4397053/view/3731840159866842920

With the latest beta the lags are back. Even with the "-enable-desktop-gl-fallback" parameter -.- I don't get it, why it is so hard to get this UI running on NVIDIA Cards :(

Cannot confirm. Still works much better than without it. New windows even don't seem to crash the desktop client anymore, or at least less often.

I'm using this one: https://store.steampowered.com/news/group/4397053/view/3731840159866842920

Same, I am on the latest beta update, and I can still get a proper big picture UI with "-enable-desktop-gl-fallback".

On the latest beta without any flags, I am seeing horrible performance in BPM again.

On the latest beta without any flags, I am seeing horrible performance in BPM again.

Then you clearly haven't read the changelog or this thread, because both would have told you that's to be expected.

Working well with "Steam Beta Sneak Peak" and "-enable-desktop-gl-fallback"

As of the May 25th update on the beta channel, I'm getting no artifacting witht the nVidia driver and "-enable-desktop-gl-fallback"

As of the May 25th update on the beta channel, I'm getting no artifacting witht the nVidia driver and "-enable-desktop-gl-fallback"

Same beta, still present with the command option

works here, no artifacting

Working well with "Steam Beta Sneak Peak" and "-enable-desktop-gl-fallback"

Same for me

working okay, nowhere near the performance of windows, but at least its usable! on windows I get 165 fps and on this i get around 60 to 80. Still artifacts, not that bad. The stuttering happens in the places it would in windows, it just a little worse. Stutters a lot when scrolling on the home page. Stutters a little bit more with animated pictures cause it also loads the hero in the backdrop even though you can barely see it. But again, great job, still needs work. Thanks Valve!

Only happens with hardware acceleration, rare chance it shifts the whole ui over. I take back my previous statement, the stuttering can be completely random and can take up to 5 seconds especially with animated photos, which is odd because in windows animated photos dont change the performance I believe

Working well with "Steam Beta Sneak Peak" and "-enable-desktop-gl-fallback"

Same for me

how aplic this is changes ? @t4cmyk

Big Picture is smooth and without artifacts for me on Steam Client Beta Sneak Peek with "-enable-desktop-gl-fallback" argument. Without this argument big picture is laggy
My system: Arch Linux with Nvidia 1050ti and proprietary driver version 530.41.03. Steam version is 1685072487

For me it just crashed the entire desktop enviroment. I'm on KDE Plasma X11 and opening big picture gave a black screen then booted me to the OS login screen.

This now only happens when using -enable-desktop-gl-fallback for me, without that arg it's back to being super laggy but atleast not crashing my desktop.

With the new update today there is no artifacts! Great work valve, performance is still pretty bad, but at least it's usable!

I currently am observing that the Steam client purposely blocks GPU compositing/rendering on my system.

I got to see the full command line used to launch the steamwebhelper binary:

/home/alexis/.local/share/Steam/ubuntu12_64/steamwebhelper
--type=renderer
--disable-seccomp-filter-sandbox
--force-device-scale-factor=1.00
--log-file='/home/alexis/.local/share/Steam/logs/cef_log.txt'
--field-trial-handle=17280965424695382527,17308932074744730194,131072
--enable-features=CastMediaRouteProvider
--disable-features=SameSiteByDefaultCookies
--disable-gpu-compositing
--enable-blink-features=ResizeObserver,Worklet,AudioWorklet
--disable-blink-features=Badgin
--lang=fr
--log-file='/home/alexis/.local/share/Steam/logs/cef_log.txt'
--product-version='Valve Steam Client'
--force-device-scale-factor=1.00
--buildid=1685572056
--steamid=0
--num-raster-threads=4
--enable-main-frame-before-activation
--renderer-client-id=10
--shared-files=v8_snapshot_data:100

Even though there are a lot of flags, only two of them (from what I can think of) are responsible of forcing CEF to do software rendering:

I am trying to figure out if there is a way to alter the flags passed so that we can both:

• Suppress the aforementioned flags (--disable-gpu-compositing and --num-raster-threads=4)
• Add the necessary flags so that proper GPU compositing/rendering is done on Linux with Nvidia drivers & Wayland (I'm pretty sure this can also work with X11)

Here are the flags that I would specify to steamwebhelper:

Those flags are the same that I came up with when configuring Google Chrome on my machine so that it uses my GPU with Wayland -- so if you also happen to have a chrome-flags.conf that works for your setup, you should use the same flags for steamwebhelper as well.

I'll post an update if I ever find a way of accomplishing what I need to do in order to have a smoother BPM experience on Linux distributions.

This was a great tip thank you @alexis-belmonte!! I've found that "steam (runtime)" (notably not "steam (native)" for me) calls ~/.local/share/Steam/ubuntu12_64/steam-runtime-heavy/run.sh on my system in order to start steamwebhelper. I've added the following lines at the bottom replacing exec "$@":

# Not steamwebhelper so skip
if [[ "$1" != *steamwebhelper* ]]; then
  exec "$@"
  exit
fi

args=()

# Read blocklist from ~/.config/steam-flag-blocklist.conf
blocklisted_flags=()
while read flag; do
    blocklisted_flags+=("$flag")
done < "$XDG_CONFIG_HOME/steam-flags-blocklist.conf"

# Filter arguments using the blocklist
for arg in "$@"; do
  include_arg=true

  for blocklisted_flag in "${blocklisted_flags[@]}"; do
    if [[ "$arg" == "$blocklisted_flag" ]]; then
      include_arg=false
    fi
  done

  if $include_arg; then
    args+=("$arg")
  fi
done

# Add additional flags from ~/.config/steam-flags.conf
while read flag; do
    args+=("$flag")
done < "$XDG_CONFIG_HOME/steam-flags.conf"

# Execute
echo "${args[@]}" >> /tmp/steam-args
exec "${args[@]}"

And here are the flags that I personally send

~/.config/steam-flags-blocklist.conf

--disable-gpu
--disable-gpu-compositing
--use-angle=gl
--disable-smooth-scrolling

~/.config/steam-flags.conf

--ignore-gpu-blocklist
--disable-frame-rate-limit
--enable-gpu-rasterization
--enable-features=VaapiVideoDecoder
--use-gl=desktop
--enable-zero-copy

For debugging, tail -f /tmp/steam-args will contain the executed command. This should work for sending any flags to steamwebhelper!

@Saghen I had tried a similar solution, altering steamwebhelper.sh instead of steam-runtime-heavy/run.sh -- but since the files present at the root of ubuntu12_64 were overwritten each time the launcher found out that they had been modified, I had to chown root:root ... + chmod ga-r ....

Your solution seems more elegant, and it works great! The only thing that I had to do was to add a line at the start of your patch so that XDG_CONFIG_HOME is defined:

export XDG_CONFIG_HOME="$HOME/.config"

Here's a demo if you want to see the difference

I think we should make a script that automatically installs the "patch"/workaround so that more users can benefit from it.

@alexis-belmonte An installer would be great! I might look at doing this sometime this weekend. Fyi you can launch steam with -noverifyfiles to skip the verification that results in the file being overwritten

That solution works like a charm. Big picture is actually smooth and usable even at 3440x1440 without any graphical artifacts at all. The new desktop UI benefits from it too with smooth scrolling and no stuttering in the animations anymore. And best of all Steam isn't crashing my whole desktop environment anymore which is always a nice touch :D

The only issue I have is when using -forcedesktopscaling 1.25, the desktop UI is scaled slightly bigger then it's supposed to be after exiting Big Picture mode.

@Mar2ck There are known issues in general with fractional scaling on almost all desktop environments (except for Gnome IIRC) -- that'd be great if you could tell us what you're using!

I'm on KDE Plasma X11 so all of the scaling is being done on Steam's end, Plasma X11 doesn't have compositor-level scaling so I doubt it's that. Big Picture has it's own scaling slider which uses the same scaling mechanism as the Desktop so what I think is happening is that the scaling factor isn't being reset properly on exit like it is on Windows.

Edit: This actually ended up being an unrelated issue with steam's scaling handling where it accidentally uses two variables at once. Happens regardless of this unofficial fix.

@Mar2ck Since I also use Plasma, I tried replicating your problem but couldn't seem to reproduce it -- in any case, you should open a separate issue for that matter -- there are chances that you're not alone with this problem :+1:

I'm on KDE Plasma X11 so all of the scaling is being done on Steam's end, Plasma X11 doesn't have compositor-level scaling so I doubt it's that. Big Picture has it's own scaling slider which uses the same scaling mechanism as the Desktop so what I think is happening is that the scaling factor isn't being reset properly on exit like it is on Windows.

Edit: This actually ended up being an unrelated issue with steam's scaling handling where it accidentally uses two variables at once. Happens regardless of this unofficial fix.

Yeah, I reported on this issue yesterday at #9565 after also confirming this fix makes BP usable on Nvidia cards. At first I also thought was related to the fix, but seems to be something introduced with Steams recent general redesign. We can discuss it more in depth at the other issue to not furtherly spam this one.

Steam is now translucent!...

In other words, the official "fix" doesn't fix the problem... and even worsens the situation

Trying to apply the workaround again makes it EVEN WORSE, with only the steamwebhelper container showing... everything else has disappeared (or rather, because fully transparent)

The latest client update fixed it by default for me! Thanks Valve!

I am testing on Ubuntu 23.04. I'm using the latest graphics driver that they provide on a 3090. The frame rate is excellent in big picture mode now. It seems fairly stable too. Thanks, Valve! I am also experiencing the weird transparency issue, but that can be forgiven because this is totally usable now.

I found a workaround for https://github.com/ValveSoftware/steam-for-linux/issues/8918#issuecomment-1580743947 -- see https://github.com/ValveSoftware/steam-for-linux/issues/9422#issuecomment-1580770411

Now it works again! :]

June 6th beta looking good.

Mint 21.1
X/Cinnamon
GTX 3090
530.41.03

Getting some minor, intermediate, visual corruption on the "store, library, …" dropdown menu. Nothing critical thus far.

The new Stable update comes today. But, the new big picture is really bad on nvidia. I hope we can go back to old big picture at the moment.

The new Stable update comes today. But, the new big picture is really bad on nvidia. I hope we can go back to old big picture at the moment.

@dtantono Just tested the new stable update. It works great on my Nvidia card. Seems, at least from my end, that they have already rolled out the fixes from the beta into stable.

I try to connect to my Linux pc with Sunshine and moonlight on my phone and my Steam deck. But, this new big picture mode is really slow unlike the old one. Which tweaks you use?

I try to connect to my Linux pc with Sunshine and moonlight on my phone and my Steam deck. But, this new big picture mode is really slow unlike the old one. Which tweaks you use?

I enabled GPU Accelerated Rendering in the interface settings and now it runs fine.

if you mean these parameters. it is same. the old BPM is much smoother

That means its a regression and eventually will hit the stable as well if
not fixed

El lun., 3 de julio de 2023 20:15, antekmeco @.***>
escribió:

nevermind, i switched back from the beta to the stable release and it
works now

—
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/steam-for-linux/issues/8918#issuecomment-1619247239,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFP7B2LIEP75HL2WW5STJTLXONHC3ANCNFSM6AAAAAASCDUORM
.
You are receiving this because you were mentioned.Message ID:
@.***>

@antekmeco that command line flag doesn't do anything anymore.

To enable or disable hardware acceleration you can use the toggle in settings.

Just to update the thread, switching to the Steam beta has now fixed the issue.

I can now use "Enable GPU accelerated rendering in web views" without Steam crashing on launch, and as a bonus, Big Picture mode is nice and smooth again at 1440p.

Nvidia RTX 3060ti
Driver - 535.54.03
EndeavourOS

Why this is closed?

I am still facing same issue (NVidia).

I have tested 3 ou 5 times, only of them was smooth.

I have installed Pop_OS & Steam (flatpak) client today.

Yeah I still get it too, but only sometimes. Close and reopen, sometimes it comes good.

Confirm I have this issue.
CachyOS nvidia driver 555 with kde 6.1

Adaptive sync drops steam picture mode down to 3-30hz and input becomes extremely laggy. It seems be running at a low framerate and engaging adaptive sync/vrr causing horrible lag. My monitors OSD shows gsync kicking in and dropping the refresh rate to single digits.

Issue still persists in fedora KDE Nvidia 560.31.02

Hello,

I can confirm this issue still persists and is presenting itself more often than not when launching big picture. It is completely unusable both in and out of game.

I have tried using it in windowed mode.
I have tried using it with various mixes of "Enable GPU accelerated rendering in web views" and "Disable GPU blocklist".
For me on the "Steam Families Beta" branch, "Enable GPU accelerated rendering in web views" also has the side effect of completely blacking out every web page presented via steam. The only thing that is visible is the Library. Tracked here: https://steamcommunity.com/groups/SteamClientBeta/discussions/0/4514379280330442987/?tscn=1722190483

Steam Beta Branch:  Steam Families Beta
Steam client version: 1722380543
Distribution: Pop!_OS 22.04 LTS
Opted into Steam client beta?: Yes
Have you checked for system updates?: Yes
GPU: NVIDIA RTX 3090

Please make clean reports with full information. We don't follow up on closed issues, too much noise.

Please make clean reports with full information. We don't follow up on closed issues, too much noise.

To clarify are you telling us to open a new issue?

@thenicnet Most likely yes, but we need to figure out how to reproduce the darn bug first, or at least figure out which logs are relevant. So far, I've only been able to reproduce it sporadically, usually after the Steam client has been open for a long time. On a fresh start, it usually works fine.

EDIT: Just reproduced it by launching into Big Picture repeatedly.

I'm able to repro this on Fedora 40 using the rpmfusion version of steam, but the flatpak seems to work just fine.

Same issue here

Your system information

Steam Beta Branch:  Steam Beta Update
Steam Version:  1726683985
Steam Client Build Date:  Wed, Sep 18 20:13 UTC +03:00
Distribution: Debian 12
Opted into Steam client beta?: [Yes]
Have you checked for system updates?: [Yes]
NVIDIA GeForce GTX 1080
Linux 6.1.0-25-amd64