After the latest stable update it just got stuck on the connecting screen and now I get "Failed to start streaming" on Deck to Windows, not sure if its the same issue as you're facing.

tyl0413님이 먼저 게시:

After the latest stable update it just got stuck on the connecting screen and now I get "Failed to start streaming" on Deck to Windows, not sure if its the same issue as you're facing.

I got that before it asked me to enter the 4 digit pairing code. I was able to get past that by making sure both machines are on the same version of steam (in this case I made sure they were both on the stable client). Both machines being on the same version of the client gave me a popup with a pairing code.

Now I get no error whatsoever, it just crashes, and the steam client on my main pc resets.

It's good to know I'm not the only one experiencing the exact same thing. It was working two days ago

I just tested it again and issue still exists.

datagram40님이 먼저 게시:

I just tested it again and issue still exists.

Yup

yeah it's broken, like so many things and the app itself.

who here has had a useful, relatively bug free steam the last year? i doubt there's a single soul out there who can honestly say that now. ok maybe one, but they're a lucky minority.

a silly workaround you can try that actually performs well surprisingly often:

nomachine nx - the remote desktop solution. it's actually super fast and i've run games with it remotely when remote play didn't work (ie. half the time).

there are other nx-type remote desktops too, but i'm mentioning nomachine's solution since it usually 'just works' no matter what os or system you're on (even has a good android client).

Seems fixed now

Latest Beta seems to have broken the audio stream for me, it now only plays on the host.

I am having this exact same problem again with the latest stable and beta clients.

Please stop breaking it.

Something you can use instead:

https://moonlight-stream.org/

Will require setup, but at least it won't break regularly.

Yes, I CAN confirm this is happening. My set up is thus: main Linux server running Ubuntu 22.04. A Steam Link. And a Laptop that WAS running 22.04 until recently when Ubuntu BROKE the ability to suspend. So I updated it to the latest LTS. That's where the problems started. The laptop (and by the way, both server and laptop are running NVIDIA cards), now cannot stream from the server. Gets a blank screen. If you look at the server, the app is actually running.

But running my Steam Link from the same server works FINE. No issues. So the problem started after updating my laptop to the latest LTS from Ubuntu (never go with version 1.0 of anything, but I wanted suspend back). With Arch I can't help you but I can't help but feel that something changed library wise that broke things. This is very annoying. I wonder if it will ever be fixed. Until now I was using the Remote Play quite successfully, even over the internet from Linux-to-Linux. Now it's completely hosed.

Just a follow up because this was annoying me enough to start messing with settings.

I DID get things working again by disabling, on the client, hardware decoding. I had to go into Settings>Remote Play>Advanced Client Settings and explicitly turn it off for the laptop that just got updated to the new Ubuntu LTS that hosed everything (had other issues with this stupid LTS release, such as rebooting into a black screen, but that's another story). After that, the Remote Play appears to work.

Give that a try, maybe it will help. I don't know how it will affect game performance though as I haven't tried it yet.

)+(Chickenhead님이 먼저 게시:

Just a follow up because this was annoying me enough to start messing with settings.

I DID get things working again by disabling, on the client, hardware decoding. I had to go into Settings>Remote Play>Advanced Client Settings and explicitly turn it off for the laptop that just got updated to the new Ubuntu LTS that hosed everything (had other issues with this stupid LTS release, such as rebooting into a black screen, but that's another story). After that, the Remote Play appears to work.

Give that a try, maybe it will help. I don't know how it will affect game performance though as I haven't tried it yet.

I just tried disabling advanced host and advanced client settings on both the host and client. In all configurations of on and off.

Unfortunately this work around did not work for me.

GustavGlaven님이 먼저 게시:

I just tried disabling advanced host and advanced client settings on both the host and client. In all configurations of on and off.

Unfortunately this work around did not work for me.

I also have NVFBC enabled in the "Advanced Host Settings." Although that setting didn't do anything for me until I turned off hardware decoding on the client laptop.

The Link had no such problems. The problems only started after updating to the latest LTS release with the latest Steam client.

)+(Chickenhead님이 먼저 게시:

GustavGlaven님이 먼저 게시:

I just tried disabling advanced host and advanced client settings on both the host and client. In all configurations of on and off.

Unfortunately this work around did not work for me.

I also have NVFBC enabled in the "Advanced Host Settings." Although that setting didn't do anything for me until I turned off hardware decoding on the client laptop.

The Link had no such problems. The problems only started after updating to the latest LTS release with the latest Steam client.

That's been on, and disabling hardware decoding on the client didn't get me going, I am on a rolling release distro, and have had this happen in the past, when I opened this thread. Thanks for trying to help out.

Idk when this bug got back into the beta client, but it just popped back up for me on the latest stable Steam client.