I think this is just downloading the (new) shader sets see Github issue.
I’m using an AMD GPU and never had any issues with disabling the shader cache in Steam. Note that in some games it might be a bit stuttery in the very beginning then due to the shader compiler (ACO if using Mesa drivers with AMD) running in the background.
I think that’s what Tauri is trying to do
Overall a fair assessment! 🤝
Very much pro-Wayland in my case.
Just saying that certain CEF/Electron apps (especially those running on older Chromium version) are what is causing certain Wayland specific issues, hence my issue is on the application side (Steam, Spotify etc.), not on Wayland’s side… My bad for the badly worded post which made it seem like the classical “Wayland bad!” posts.
I haven’t touched X11/Xorg in years, nor am I planning on reverting back to it anytime.
Yeah, maybe it was just badly worded by me…
most (if not all) Wayland issues I currently have are related to Chromium, and especially CEF/Electron applications that are based on older Chromium versions. Weren’t trying to say that this is an inherent Wayland issue, considering most of the applications works as expected.
Why have a consistent Wayland experience when each application can run it’s own Electron version with varying degrees of enforced Wayland flags, and/or such an outdated Chromium version Wayland is just jank.
Any particular reason you’re not on/tested the v590-branch? Of course it might be borked compared to 570, but might be worth a shot?
For reference/others:
The setting is:
Settings -> Downloads -> Enable Shader Pre-caching