#Error 10053 and 10054 when trying to stream

13 messages · Page 1 of 1 (latest)

weary knoll
#

Hello all. yesterday, I was trying out ALVR when Air Link for the Quest 2 didn't work for me. Everything went smoothly and I was able to play VRChat with little to no issues at all.

Cue today, I was trying the exact same, opened ALVR on my Quest 2 and started SteamVR on my PC. And I get met with a bunch of error messages.

Now, my setup, which worked flawlessly yesterday, is to host a wifi hotspot with 5Ghz band on my PC and connect my quest to it. This worked perfectly fine yesterday and just fails, today.

When it does work every so often, it boots to SteamVR, lags out and gets a lot of fragments in the screen, as well as black borders when looking around, then crashes back to the client trying to connect.

Windows
Quest 2
Installed the server via the windows exe installer.
GPU is an RTX 3050 Laptop GPU
CPU is an AMD ryzen 7 5800H
16GB RAM

#

I should mention, I did see the topic mentioning OS error 11, since I was getting that one and I tried to connect once again, but with microphone disabled in the dashboard settings. This did not change anything at all.

weary knoll
#

Another attempt further and for some reason it works just fine? Tried ALVR over USB, didn't work. I reset the discovery and set UDP back to TCP under connection. Removed the wrong client and now it just works after I added it again?

weary knoll
#

I can see error 10053 is well documented already, but error 10053 still persists

wild plover
#

If so, I would recommend having a look at this and trying this fix: #1193074269505204376 message

weary knoll
#

Ah, yes, these issues were on 20.5.0. The 10053 audio error was at least resolved by disabling the mic a 100 percent. It's not ideal, of course, but it is what it is. But I also got error 10053, which wasn't fixed, the last time I tried I'll check the new version and let you know if it works, later today!

wild plover
#

Alright, sounds like you have a plan! I'll consider this resolved (seeing as there is a known solution). Any other issues, ya know what to do!

weary knoll
#

The streamer was updated to 20.6.0. I sideloaded the quest app again, as well. I can't verify if it updated, I guess it did. But either way, the stream works after one/two retries or less, every time now.
At least this solves the issue. So all is well.

wild plover