SteamLink for Raspberry Pi Released

[hhromic]

Hi all, I just stumbled into this: https://steamcommunity.com/app/353380/discussions/0/1743353164093954254/

The Steam Link app is now available in beta on the Raspberry Pi 3 and 3 B+ running Raspbian Stretch

I just quickly tried it and works pretty decently on my stock non-overclocked RPI3B+. Looks like moonlight has a competitor on the RPI devices!

Testers welcomed, this is not opensource (yet?) but maybe we can craft a scriptmodule if enough people is interested.

[MisterMints]

@hhromic If I install this using the script in the Steam Community link, would it show up as a system on the Emulation Station/RetroPie menu?

[hhromic]

@MisterMints no, but @psyke83 already sent a PR for a scriptmodule here https://github.com/RetroPie/RetroPie-Setup/pull/2550

Should be accepted soon, so stay tuned for that PR to be merged, then update your RetroPie-Setup script and should work from ES as a port.

[MisterMints]

@hhromic said in SteamLink for Raspberry Pi Released:

@MisterMints no, but @psyke83 already sent a PR for a scriptmodule here https://github.com/RetroPie/RetroPie-Setup/pull/2550

Should be accepted soon, so stay tuned for that PR to be merged, then update your RetroPie-Setup script and should work from ES as a port.

GREAT! :)

[hhromic]

Update

The PR from @psyke83 has been accepted in RetroPie now. Update your RetroPie-Setup script and Steam Link should be available in the Experimental section. After installing, Steam Link should be visible as a port in EmulationStation (after restarting).

Testers please let know of your experience!

[psyke83]

It seems that Valve modified their script to detect and block execution when overscan_scale is enabled (which it is in our RetroPie image), but provide a means to ignore it. Supposedly this setting can cause a black screen when streaming begins, but I haven't noticed any issues on my Pi 3B.

It won't work until this PR is also merged: https://github.com/RetroPie/RetroPie-Setup/pull/2552

[psyke83]

I also noticed this in the same script:

# Check to make sure the hardware is capable of streaming at 1080p60
# Model code information from:
# https://www.raspberrypi.org/documentation/hardware/raspberrypi/revision-codes/README.md
if [ ! -f "$TOP/.ignore_cpuinfo" ]; then
        revision=$(cat /proc/cpuinfo | fgrep "Revision" | sed 's/.*: //')
        revision=$((16#$revision))
        processor=$(($(($revision >> 12)) & 0xf)) # 0: BCM2835, 1: BCM2836, 2: BCM2837
        if [ $processor -lt 2 ]; then
                show_message --error "You need to run on a Raspberry Pi 3 or newer - aborting."
                exit 1
        fi
fi

I wonder if this can launch on a Pi Zero/2/1, albeit with reduced streaming quality?

It's possible to enforce a framerate limit by creating the file ~.local/share/Valve Software/Streaming Client/streaming_args.txt and adding this:

--framerate 30

Edit: no, it wouldn't be possible as the binary is definitely compiled for ARMv8:

readelf -A ~/.local/share/SteamLink/bin/streaming_client
Attribute Section: aeabi
File Attributes
  Tag_CPU_name: "8-A"
  Tag_CPU_arch: v8
  Tag_CPU_arch_profile: Application
  Tag_ARM_ISA_use: Yes
  Tag_THUMB_ISA_use: Thumb-2
  Tag_FP_arch: FP for ARMv8
  Tag_Advanced_SIMD_arch: NEON for ARMv8
  Tag_ABI_PCS_wchar_t: 4
  Tag_ABI_FP_rounding: Needed
  Tag_ABI_FP_denormal: Needed
  Tag_ABI_FP_exceptions: Needed
  Tag_ABI_FP_number_model: IEEE 754
  Tag_ABI_align_needed: 8-byte
  Tag_ABI_enum_size: int
  Tag_ABI_VFP_args: VFP registers
  Tag_CPU_unaligned_access: v6
  Tag_MPextension_use: Allowed
  Tag_Virtualization_use: TrustZone and Virtualization Extensions

Seems odd that they'd bother to implement a CPU override in the scripts; perhaps they might recompile for ARMv6 at a later time, but it's doubtful.

[LeSabotageur]

I've tested it on my Pi 3, yet I'm stuck when launching, the splash screen won't go away unless I kill it.

How can I show the output log, so I can see what's wrong ?

EDIT : no log in /dev/shm :(

[hhromic]

@psyke83 , the RPI 2 revision 1.2 have the same CPU as the RPI3, as described in https://www.raspberrypi.org/documentation/hardware/raspberrypi/revision-codes/README.md

a22042	2B (with BCM2837)	1.2	1 GB	Embest

the binary should work on these boards too, but definitively not on RPI 0/1.

Edit: funny enough, their script seems to actually check on the processor information itself, not the board nor revisions, which should pass on an RPI2 with a BCM2837 processor, so their error message is not fully true either.

[thezoof]

This is amazing. I have never played around with experimental additions for pi. Can someone provide the steps on how to achieve this from start to finish(tutorial)?

Thanks.

[mitu]

@thezoof You just install it as any other package - update your RetroPie-Setup script, then go into the experimental packages section, find steamlink and then install it - as @hhromic said in a previous post.

[psyke83]

@mitu said in SteamLink for Raspberry Pi Released:

@thezoof You just install it as any other package - update your RetroPie-Setup script, then go into the experimental packages section, find steamlink and then install it - as @hhromic said in a previous post.

As I mentioned earlier, it won't yet work until the second PR is merged. A temporary fix would be to manually create the override yourself:

mkdir -p "~/.local/share/SteamLink/"
touch "~/.local/share/SteamLink/.ignore_overscan"

@hhromic said in SteamLink for Raspberry Pi Released:

@psyke83 , the RPI 2 revision 1.2 have the same CPU as the RPI3, as described in https://www.raspberrypi.org/documentation/hardware/raspberrypi/revision-codes/README.md

a22042	2B (with BCM2837)	1.2	1 GB	Embest

the binary should work on these boards too, but definitively not on RPI 0/1.

Edit: funny enough, their script seems to actually check on the processor information itself, not the board nor revisions, which should pass on an RPI2 with a BCM2837 processor, so their error message is not fully true either.

That's interesting - I wasn't aware there was a Pi 2 with ARMv8 cores.

On my Pi3B (revision a02082), I'm having difficulty getting a smooth streaming experience with any of the preset bitrate/quality settings for 60fps at 1360x768. I keep getting a spike in the decoder (light blue and red lines in the streaming OSD statistics). It might be possible to get a better result via the advanced parameters that can be added to streaming_args.txt such as --burst or --hardwarebitratelimit, but I haven't had time to test properly.

[Mick2K]

Played for a few hours and it seems pretty stable for me but I think original steam link hardware has little bit less lag.
Performance monitor says ~20ms but I measured around 100ms (not scientifically accurate) for the video stream.
Can't say something about additional controler lag cause gamepad was connected directly to PC.

[Darksavior]

@Mick2K I think it's the app. I tried both pi3b+ and firestick 4k with the steamlink app on each one right next to the router. They performed rather poorly wirelessly with wifi AC. With my real steamlink I can stream with no noticeable lag across walls. Moonlight is a crude alternative and the bitrate quality was much less (I don't remember what it uses), but the input lag was decent enough. It also detected my pad. Steamlink app doesn't on my 3b+.

[hhromic]

@psyke83 said in SteamLink for Raspberry Pi Released:

That's interesting - I wasn't aware there was a Pi 2 with ARMv8 cores.

I only learned of it some months ago, the foundation doesn't seem to have announced it very loudly.

On my Pi3B (revision a02082), I'm having difficulty getting a smooth streaming experience with any of the preset bitrate/quality settings for 60fps at 1360x768. I keep getting a spike in the decoder (light blue and red lines in the streaming OSD statistics). It might be possible to get a better result via the advanced parameters that can be added to streaming_args.txt such as --burst or --hardwarebitratelimit, but I haven't had time to test properly.

On my Pi3B+ (plus), Steam Link seems to be running quite smoothly. I also have a 1360x768 TV but I output at 720p to take advantage of game mode (only works on CEA resolutions). Are you using ethernet or wifi to your gaming computer? The non-plus Pi3B has a very weak Wifi module and at 2.4ghz I don't think its suitable for game streaming. A realistic minimum is 5Ghz AC wireless IMHO. Moonlight also performs poorly with 2.4ghz Wifi.

Speaking of which, I do notice more random stutters using Steam Link compared to Moonlight, so I guess Steam Link still has some way to go to catch up. Also I don't like the packaging they chose for Steam Link. I understand is meant for novice users but their scripts are a bit cringy xD

[psyke83]

The required changes have been merged, so it should be safe to test the module as long as your RP script is updated. Just keep in mind that you may need to disable overscan_scale in /boot/config.txt if you experience a black screen on startup.

I've also exposed the streaming_args.txt configuration to configs/ports/steamlink so that advanced tweaks are a bit easier to test. I need to set --framerate 60 in this file or else I get heavy tearing in 2D games (not related to vsync, which the client seems to have enabled).

@hhromic said in SteamLink for Raspberry Pi Released:

On my Pi3B+ (plus), Steam Link seems to be running quite smoothly. I also have a 1360x768 TV but I output at 720p to take advantage of game mode (only works on CEA resolutions). Are you using ethernet or wifi to your gaming computer? The non-plus Pi3B has a very weak Wifi module and at 2.4ghz I don't think its suitable for game streaming. A realistic minimum is 5Ghz AC wireless IMHO. Moonlight also performs poorly with 2.4ghz Wifi.

Speaking of which, I do notice more random stutters using Steam Link compared to Moonlight, so I guess Steam Link still has some way to go to catch up. Also I don't like the packaging they chose for Steam Link. I understand is meant for novice users but their scripts are a bit cringy xD

My host PC and Pi are both connected via Ethernet; the streaming statistics showed 0 packet loss and low ping, so I think it was an issue with the decoder not keeping up due to excessive bitrate.

However, from some quick tests today I didn't notice those spikes (which were accompanied by audio underruns). Perhaps they improved something in the 1.03 -> 1.05 bump, but it's still not perfect, as I can notice stutter especially in a 2D game like Sonic Mania.

I also tested over wireless and yes, latency was terrible. I've only got a Pi3B, so it's limited to my 2.4Ghz wireless network (in a fairly congested area).

[LineOf7s]

So far it seems to work great, but using a standard wired Xbox 360 controller (userspace driver, apparently) the default mapping is... odd. Like, the left and right triggers are Select (aka Back) and Start respectively (among other things).

Remapping the controller in Steam Link seems to complete successfully, but Testing Controller immediately after shows that it doesn't "take".

Doing some research now to see if I can find a config file somewhere I need to tweak, but I thought I'd provide the data point in the meantime.

[LeSabotageur]

@psyke83 said in SteamLink for Raspberry Pi Released:

The required changes have been merged, so it should be safe to test the module as long as your RP script is updated. Just keep in mind that you may need to disable overscan_scale in /boot/config.txt if you experience a black screen on startup.

Thanks, I should've paid more attention earlier, that was my problem. Now the interface loads nicely !

EDIT : Bit of feedback : I'm using VirtualHere for my input, and while on moonlight everything goes quite smoothly, with the Steam Link the input lag is a bit more noticeable. However, Helldivers, which didn't work in Big Picture in moonlight, does work here, and I'm guessing that's the case for other games like those.
So all in all, I'll be sticking to moonlight for now but I'll keep an eye on the progress for this port.

[StarshipKnight]

I am also trying it but I am struggling because my ipega 9055 controller doesn't get detected. Any suggestions??

[thezoof]

Hey all. I was able to add steamlink as instructed via experimental package. I updated the overscan as instructed but I am still getting a black screen.

I notice that in the runcommand.log I am seeing this:

Executing: /usr/bin/steamlink
Steam needs to install these additional packages:
libgudev-1.0-0:armhf, libinput10:armhf, libmtdev1:armhf, libwacom2:armhf, libxcb-xkb1:armhf, libxkbcommon-x11-0:armhf
..Package libgudev-1.0-0:armhf needs to be installed
Package libinput10:armhf needs to be installed
Package libmtdev1:armhf needs to be installed
Package libwacom2:armhf needs to be installed
Package libxcb-xkb1:armhf needs to be installed
Package libxkbcommon-x11-0:armhf needs to be installed
This application failed to start because it could not find or load the Qt platform plugin "eglfs"
in "".

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb.

Reinstalling the application may fix this problem.

Any ideas how to proceed?