Remote Play seems to be a constant problem for Valve to fix up on Steam / Steam Deck, as there's always something broken with it and the latest Steam Client Beta fixes it up again.
It was only back at the end of February that Valve patched the infinite loading screen specifically on Steam Deck, which they pushed out broken after the recent stable update and here we are again. For both Desktop and Steam Deck there's another new Beta available that has these fixes:
Remote Play
- Fixed missing audio while streaming.
- Fixed continually being prompted for the PIN when pairing a device.
For such an incredibly useful feature, it sure is broken a lot isn't it. Every time I go to use it there's always something that causes an issue.
Have you been having issues with Remote Play lately?
Article taken from GamingOnLinux.com.
Some you may have missed, popular articles from the last month:
fenglengshun Mar 14
Quoting: TheSHEEEPWait, so the 5th or so "year of the Wayland" is not actually it? ....For what it's worth, RustDesk is currently working on remote desktop portal compatibility so that they can do Remote Desktop Host even from flatpak on wayland. TeamViewer have support Wayland host for a while now, though it still has issues.
I am shook!
As far as I can see, 2024 is looking like the year where most of the Wayland stuff is done. Wine on Wayland is progressing decently, Google seems to be looking at Wayland too so browsers (and CEF & electron apps) should be getting better, new input module is being tested, display colors, drawing tablet, so many things have basic implementation that should be wrapping up this year or the next.
For this issue specifically, once the full pipe from DE/WM/Compositor to Steam to the Steam game (Linux Native or Wine) is fully Wayland, it should help with the latency and stability. It's really is just Steam that we don't have a timeline for when they may go full Wayland native - but even then we've seen the moves they've made to pay their tech debts and modernize.
2024 I think will be the year where Wayland is mostly done, and 2025 is mostly testing through early birds like Fedora before the likes of RHEL, Ubuntu LTS, and Debian drops x11 as a default fallback.
3 Likes, Who?
pleasereadthemanual Mar 14
Quoting: fenglengshunAs far as I can see, 2024 is looking like the year where most of the Wayland stuff is done. Wine on Wayland is progressing decently, Google seems to be looking at Wayland too so browsers (and CEF & electron apps) should be getting better, new input module is being tested, display colors, drawing tablet, so many things have basic implementation that should be wrapping up this year or the next.Not incidentally, Google has been sponsoring some of this work for the Wine Wayland driver.
Quoting: fenglengshunIt's really is just Steam that we don't have a timeline for when they may go full Wayland native - but even then we've seen the moves they've made to pay their tech debts and modernize.Well, you can sort of run Steam in Wayland as of two weeks ago, though a lot of things are broken: https://github.com/ValveSoftware/steam-for-linux/issues/4924#issuecomment-1975248612
Last edited by pleasereadthemanual on 14 March 2024 at 6:32 am UTC
1 Likes, Who?
The SteamOS integrated Steam Link has consistently been so broken for me that I have moved to using the Flatpak as a non-Steam app for streaming from my Desktop.
This results in both the Desktop and Deck's client's input layout being applied, neither having the option to be turned off and the latter being buried in Steam settings and staying active when in the Deck's settings.
Which is annoying as I use my Steam Deck as my primary controller now, thankfully the above can be worked around by creating an empty layout in one of the two settings.
On the Desktop side hardware acceleration is disabled too, I'm not sure if this is still necessary, but it was needed some time back to avoid system crashes.
But once it works it just works and works well, it's just very silly having to apply such a workaround on an integrated system with a dedicated shortcut and library synchronisation for streaming in the same way.
I'm not using the internet aspect of remote play (yet) and am sticking to X11 for various problems which I've tried solving but didn't quickly find working solutions for.
This results in both the Desktop and Deck's client's input layout being applied, neither having the option to be turned off and the latter being buried in Steam settings and staying active when in the Deck's settings.
Which is annoying as I use my Steam Deck as my primary controller now, thankfully the above can be worked around by creating an empty layout in one of the two settings.
On the Desktop side hardware acceleration is disabled too, I'm not sure if this is still necessary, but it was needed some time back to avoid system crashes.
But once it works it just works and works well, it's just very silly having to apply such a workaround on an integrated system with a dedicated shortcut and library synchronisation for streaming in the same way.
I'm not using the internet aspect of remote play (yet) and am sticking to X11 for various problems which I've tried solving but didn't quickly find working solutions for.
0 Likes
NeoMorpheus Mar 14
Hello.
I did a quick test from ChimeraOS to Shield TV, both over wifi and it worked ok, just with massive lag, but that’s because both devices were on wifi.
I wonder if all the people are that are reporting issues have a Nvidia gpu?
I did a quick test from ChimeraOS to Shield TV, both over wifi and it worked ok, just with massive lag, but that’s because both devices were on wifi.
I wonder if all the people are that are reporting issues have a Nvidia gpu?
0 Likes
Patreon
PayPal
See more from me