VirtualHere for Steam Link stops remote play

Submitted by hansidm on #1

Hi,
I have Steam Link on my Raspberry Pi and I am trying to use my Logitech G430 headset through VirtualHere which I purchased the client through Steam. I set the headset to be "Shared" on the VirtualHere config on the Steam Link and as soon as I start the remote play, I can see the home screen of the Steam Big Picture mode with my games but it "freezes" just at this point (controllers stop responding).

If I go to my PC, I can see that the Big Picture mode (and remote play) are not running anymore ( back to the desktop), although VirtualHere is downloaded/started by Steam, but no hubs are showing on it.

I have tried uninstalling VirtualHere (through Steam) and reinstalling but with no success.

Please help.

Submitted by Michael on Fri, 2020/08/28 - 18:34

#2

Its almost sounds like the steam process on the pi crashed. Im not actually sure how to check that. Can you see the steam process using ps -ef

Submitted by hansidm on Sat, 2020/08/29 - 02:15

#3

Sure.
I've got two different, but similar, behaviors.

When VirtualHere is first started by Steam (like when I freshly boot my PC and start streaming via SteamLink), Steam Link freezes in the Steam Big Picture screen that shows my game library. When that happened, I ssh'ed into the Pi and here is the output of the steamlink process.

pi@retropie:~ $ ps -ef | grep steam
pi 622 621 0 11:51 tty1 00:00:00 bash /opt/retropie/supplementary/runcommand/runcommand.sh 0 _PORT_ steamlink
pi 1012 1006 0 11:52 tty1 00:00:00 /bin/bash /opt/retropie/ports/steamlink/steamlink_xinit.sh
pi 1015 1012 0 11:52 tty1 00:00:00 /bin/bash /home/pi/.local/share/SteamLink/steamlink.sh
pi 1040 1015 0 11:52 tty1 00:00:00 steamlink-cec
pi 1092 1015 15 11:52 tty1 00:00:22 streaming_client --settings /home/pi/.local/share/Valve Corporation/SteamLink/streaming_settings.bin --stats /home/pi/.local/share/Valve Corporation/SteamLink/streaming_stats.bin --sdr_config /home/pi/.local/share/Valve Corporation/SteamLink/sdr_config.txt --locale en_US --burst 90000 --captureres 1920x1080 --disable-touch-controller --transport k_EStreamTransportUDP --steamid [the steam ID] --server 192.168.1.143:27031 [some hash]
pi 1446 1355 0 11:55 pts/0 00:00:00 grep --color=auto steam

The second behavior is when VirtualHere is already running as started by Steam and I try to initiate streaming using SteamLink. SteamLink still freezes at the same point, but shortly after, the SteamLink app is killed and restarted, going back to the SteamLink home screen (the screen you can start streaming or configure SteamLink).

Submitted by hansidm on Sat, 2020/08/29 - 03:45

#4

I'm also adding the ps -ef output grepping with "Steam" instead of "steam"


pi@retropie:~ $ ps -ef | grep Steam
pi 620 595 0 11:51 tty1 00:00:00 sh -c bash /home/pi/RetroPie/roms/ports/Steam\ Link.sh
pi 621 620 0 11:51 tty1 00:00:00 bash /home/pi/RetroPie/roms/ports/Steam Link.sh
pi 1015 1012 0 11:52 tty1 00:00:00 /bin/bash /home/pi/.local/share/SteamLink/steamlink.sh
pi 1092 1015 3 11:52 tty1 00:03:31 streaming_client --settings /home/pi/.local/share/Valve Corporation/SteamLink/streaming_settings.bin --stats /home/pi/.local/share/Valve Corporation/SteamLink/streaming_stats.bin --sdr_config /home/pi/.local/share/Valve Corporation/SteamLink/sdr_config.txt --locale en_US --burst 90000 --captureres 1920x1080 --disable-touch-controller --transport k_EStreamTransportUDP --steamid [the steam ID] --server 192.168.1.143:27031 [some hash]
root 1143 1 0 11:52 ? 00:00:12 /home/pi/.local/share/SteamLink/bin/vhusbdarmslpi3 -b -c /home/pi/.local/share/SteamLink/.virtualhere/virtualhere.ini -r /home/pi/.local/share/SteamLink/.virtualhere/virtualhere.log
pi 1580 1355 0 13:42 pts/0 00:00:00 grep --color=auto Steam

Submitted by hansidm on Sat, 2020/08/29 - 03:48

#5

From the above ps I noticed there exists a virtualhere.log. Here are the contents of it for this last execution:
Fri Aug 28 11:52:55 2020 LOG_INFO >>> Starting VirtualHere USB Server v4.1.5 (Built: Apr 23 2020, 12:38:56)<<<
Fri Aug 28 11:52:55 2020 LOG_INFO Using configuration /home/pi/.local/share/SteamLink/.virtualhere/virtualhere.ini
Fri Aug 28 11:52:55 2020 LOG_INFO Server licensed to=[some_hash] max_devices=3
Fri Aug 28 11:52:55 2020 LOG_INFO Using large URB's
Fri Aug 28 11:52:55 2020 LOG_INFO Listening on all network interfaces at TCP port 7575
Fri Aug 28 11:52:55 2020 LOG_INFO Found Full speed device [046d:0a4d] "Logitech, Logitech G430 Gaming Headset" at address 113
Fri Aug 28 11:52:55 2020 LOG_DEBUG Warning, could not open device product file /sys/bus/usb/devices/1-1.1/product, error 2 (No such file or directory)
Fri Aug 28 11:52:55 2020 LOG_INFO Found High speed device [0424:ec00] "0x0424, 0xec00" at address 111
Fri Aug 28 11:52:55 2020 LOG_INFO Found Low speed device [413c:2111] "DELL, Dell USB Wired Entry Keyboard" at address 114
Fri Aug 28 11:52:57 2020 LOG_INFO 192.168.1.143 connected as connection 1
Fri Aug 28 11:52:58 2020 LOG_INFO Device 113 [046d:0a4d] BOUND to connection 1
Fri Aug 28 11:52:58 2020 LOG_INFO Device 111 [0424:ec00] BOUND to connection 1
Fri Aug 28 11:52:59 2020 LOG_INFO Device 114 [413c:2111] BOUND to connection 1
Fri Aug 28 11:53:07 2020 LOG_INFO Device 113 [046d:0a4d] UNBOUND from connection 1
Fri Aug 28 11:53:07 2020 LOG_INFO Device 111 [0424:ec00] UNBOUND from connection 1
Fri Aug 28 11:53:07 2020 LOG_INFO Device 114 [413c:2111] UNBOUND from connection 1
Fri Aug 28 11:53:08 2020 LOG_INFO Connection 1 successfully removed (reason:timeout)

Submitted by Michael on Sat, 2020/08/29 - 12:16

#6

Yes the steam process is crashing which is confusing things. I see the virtualhere seems ok (it would log a "segfault" in virtualhere log if it crashed)

Im not sure how to fix this as its not in virtualhere. Could you email valve and tell them your steam process is crashing and they will know how to get logs/debug that.