Retested with the Dec 15 2017 release. Still occurs. Thank you again for in home streaming, it's awesome.
I'm having a similar issue which is probably related to the same change that caused this. When streaming from a 1080p host to a 2160p client (both Linux), the streaming window used to be full screen and 1080p. Since a recent update, the streaming info still says its capturing at 1920x1080 but the streaming window is zoomed in to the top left quarter of the screen. Changing the client resolution to 1080p or disabling hardware decoding works fine
Reporting the same issue, also with intel VAAPI decoding. No issues when using software decoding.
Workaround is changing the desktop resolution wiht xrandr after starting the game (and again when exiting), but this is far from convenient.
If you're familiar with compiling C code, I knocked up an app to detect the streaming window getting focus and auto-switching the resolution, then back again on loss of focus:
https://gist.github.com/tombriden/e634d44847f65a769d785cb8e98446c5
gcc resolution-switcher.cpp -lX11 -lXrandr -oresolution-switcher
Change line 95 if you're switching to something other than 1920x1080
It's not perfect but does the job well enough. You can also run as a daemon with -d option.
So, moderator closed my issue, then I'll ask here.
The problem identified in mid-December 2017. Four months after, problem still exists. Any chance it will be solved? Or it will be continuously ignored by developers?
Finally I found what I was looking for and I have to report the same bug/problem.
In example I'm using the Wargaming-Launcher called "Game Center" and it also appears offset and additionally the mouse is offset too. If I resize the Window on my client via "Alt+Enter" only the launcher gets displayed, has the correct size and the mouse doesn't have some offset anymore. But then I have the next problem with starting the game in fullscreen. If I try to switch back with "Alt+Enter", the stream sometimes still uses the previous (lower) resolution. This is a serious problem, since I need to use software like anydesk/teamviewer (Remotedesktop would kill the game, since it is using its own graphic driver) to switch between gamelauncher and the game itself on the host-machine. Sometimes I need to start the game several times to get it to work in fullscreen. This is very frustrating and it worked like a charm before this update.
My configuration:
Host - Windows 10 Beta-Client (iGPU)
Client - Arch Linux (Cinnamon) Beta-Client HW-Decoding (iGPU) VAAPI
I have a dedicated GPU on my Host-machine, but Intel Quicksync seems to work much better and lagfree for me. (patch your network-manager if you're using WiFi ;)
This issue should be fixed in the latest steam client beta.
Closing per the last comment.
This is most definitely still not fixed. I switched over to the Steam Client beta just to test. Steam Link is still presenting this issue. I'm running a 21:9 host and a 16:9 client.
Hello @karasuhebi, looking this issue report over, the issue tracked here was specifically about hardware accelerated decode on Intel hardware. Please open a new issue report so that your issue can be tracked properly.
Nothing extracted yet.
Your system information
Please describe your issue in as much detail as possible:
Visual Aid: https://imgur.com/a/gsTUE
Only since the Dec 12 2017 update (was working just the night before this update) that in-home streaming with hardware decoding enabled results in the mouse and video offset inside of the steam full screen X window.
In the screenshots you can see that VAAPI decoding is properly working and no updates to the libraries were detected via apt.
Client: 2160x1080@144hz
Host: [email protected]
Client machine appropriately adds black bars and centers the steam client window even with though the game is rendered off center. I believe it might be an artifact of aspect ratio's not be accounted for when applying the offsets
Workaround
Changing the client's resolution to match the host's resolution w/hardware decoding enabled does not produce the offset issue. This workaround isn't ideal as it requires extra steps to play a game.
Steps for reproducing this issue: