Anonymous edits have been disabled on the wiki. If you want to contribute please login or create an account.

Warning for game developers: PCGamingWiki staff members will only ever reach out to you using the official press@pcgamingwiki.com mail address.
Be aware of scammers claiming to be representatives or affiliates of PCGamingWiki who promise a PCGW page for a game key.

Topic on Store talk:Steam

This is a permanent link to the first version of this post. You can view later versions on the post history page.

Just some things may worth to be mentioned in the article:

  • Random lag spikes on wi-fi could be resolved by disabling Windows automatic network scan possibly no more valid
  • Streaming can just handle stereo sound [WIP][ADDED] [ADDED2] ["improved"]
  • Linux systems might have rumble issues

And then the biggest annoyance for me is not being able to use the host computer for something else whilst it's streaming (it's not just me that would like to play on a netbook).
I read several workarounds (like Virtual Machines and Multiseat desktop). Though these are still far from simplicity
some "benchmarks"

Albeit in-home streaming by itself isn't API limited, Steam Link only works with XInput (this indirectly means there's a 4 controllers hard limit)

Other trivia: DXVA2 is used for hardware decoding in Windows. This means basically any GPU since 2006-2007 (but some special cases) and ideally no XP support. There seems to be a specific W8+ decoder (ICodecAPI ?)

Linux side supports both VAAPI and VDAPU (again with exceptions)

Intriguingly Windows XP host support was a thing in the past.
And intriguingly, it seems Broadcasting doesn't share the same "platform"\API than this.

AMD&INTEL WINDOWS HARDWARE DECODING IS BROKEN.
The flickering problem gets more apparent when I use amd VCE encoding, but it's still slightly there regardless. Fixed.

I guess like "discovery" should go first, but we go by finding order here, so..

Example of edge case. Broadcast network address must be unfiltered (in both directions preferably, otherwise you need to force the "sending capable" machine to re-advertise itself by toggling repeatedly the checkbox in steam options), in addition to port 27036.

p.s. protocol has been partially documented