Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Big Picture works slowly with the latest version of the Steam client (1726604483) #1350

Open
cold-distance opened this issue Sep 20, 2024 · 4 comments

Comments

@cold-distance
Copy link

cold-distance commented Sep 20, 2024

Hi, I recently updated the Steam client and I see that Big Picture works slowly. I'm using Aeon Desktop on a ASUS TUF GAMING B660-PLUS WIFI D4 motherboard with an Intel Core i5-12600K CPU and a standard Radeon RX 7600 dGPU. The iGPU is disabled, I use the Wayland session on GNOME and the Steam version is 1726604483 obtained from the Flatpak launcher.

The opening and the closing work smoothly, but after the interface works slowly with the keyboard and a controller.

I don't know if someone has the same issue.

@JamesMcMahon
Copy link

Same issue. On Radeon as well. Interface works but is extremely slow.

@Blumoop
Copy link

Blumoop commented Oct 18, 2024

Does this issue happen on native Steam as well? Big Picture Mode is also laggy for me until I launch a game, with Flatpak on Vanilla OS/Debian Sid and the native Fedora and Solus packages on Bazzite and Solus respectively since the update mentioned. I'm running a i5-14500 and a A770 Arc card.

@JamesMcMahon
Copy link

JamesMcMahon commented Oct 18, 2024

Happens for me both in Flatpak and native Steam (package from OpenSUSE Tumbleweed).

From my side it actually doesn't look like a Flatpak issue but a downstream one.

@Blumoop
Copy link

Blumoop commented Oct 18, 2024

From my side it actually doesn't look like a Flatpak issue but a downstream one.

That appears to be the case since I saw that other people were having the same issue on various distros when I was trying to find a solution, hopefully it can be fixed by Valve soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants