Hello @softyoda, presenting your experience as AI slop doesn't inspire any confidence that your assessment is accurate. My understanding is that GPU accelerated web views is enabled by default on a clean install and it's more likely that you previously disabled it to troubleshoot something.
#8706 is a near-match for the performance behavior you've described.
I am sorry i haven't prompted enough my Claude to relive this ugly verbosity and overall bulletpointiness, but this echoborging i now see myself do more and more is because i'm completly removing myself from the windows ecosystem and the only way i found to make the life of everyone usefull is to go to the source and send comment or feature request on anything that doesn't work by default (and should) there are some many things outsider my knowledgable field i pefer to deleague to bots who have often more visibility on what part of the stack, of the ecosystem of the os to fix it, that's why i now have taken the reflex of opening an issue at the end of all Claude code talk i verbalise in natural language about something that doesn't work. Often it's a user problem (just me not aware of something) but most of the time i'll post something it's when i jusge it is worth it. I ackwledge 75% of the web now have became slopemerdia and my intention isn't at all to add to the pill of trash. I just simply don't reside in the crosspoint of either too human but rejected as "noobish and non conventional issue from what we usually awaight" and "too slope please use your own mouth to speak". I'm simply trying what i hope is reduction of enthropy, of friction that make linux still not an os usable by the everyone person.
See what happen when it's myself in command of the writing ? I digress and talk about things that seem completly irrelevant to the solve of my own issue. (Well the issue is locally fixed but i aim toward global solving, so i hope my digression isn't as out of topic as it could be).
I don't know how to prove you it wasn't enabled by default, i'll have to reinstall the os on another workstation, i could show / screen record my entire process from installing couchyos with plasma, installing steam from Shelly, using it in big picture, noticing it's at 1 to 2 FPS max, searshing on reddit, github and the wacky steam forums, trying some command to solve it, ask Claude code terminal, seeing multiple issues similar on this github, trying the checkbox for GPU acceleration on the interface as Claude cannot edit a compiled binary (steam), noticing it worked and nothing has go be overcomplicated one just had to know this checkbox in the settings existed and needed to be enabled, and finally trying to manifest a closure for not anymore souls shall be required to walk this path again.
@softyoda thanks for the report. There was a bug in the logic that was supposed to enable GPU acceleration by default on newer Nvidia driver versions.
A fix for this issue will ship in a future steam client.
Thanks
Nothing extracted yet.
Setup: RTX 3080, CachyOS (Arch-based), KDE Plasma, Wayland.
Problem: Big Picture runs at ~1fps, making it completely unusable.
Root cause: Steam → Settings → Interface → "Enable GPU accelerated rendering in web views" is OFF by default on this configuration. Confirmed via
webhelper_gpu.txt: GPU compositing disabled with statusk_EBrowserGPUStatus_DisabledCommandLine.Fix: Enabling the setting restores full performance immediately.
Request: This setting should default to ON for NVIDIA + Wayland. There is no indication in the UI that it is off, and the resulting 1fps makes Steam Big Picture appear completely broken out of the box.