Screen flickers while streaming

[FMLM87]

I use Steam In-Home streaming like almost a few months to play a lot of games of my library without any problem, but after the last update everything go to hell, the screen in my client computer flickers like 1 per second, and it´s imposible to play with that!!!

This is what happen https://www.youtube.com/watch?v=AZsN9F26YaY

My specifications are:

Host:
Intel core i5 3.40 ghz
AMD Radeon R7 200 series
8G of Ram
Windows 10

Client:
Intel Core i3
Intel HD Graphics 3000
8G of Ram
Windows 10

I don´t know what to do, the last week everything works fine!!

[loud_colour]

引用自 henryg：

We'll try to get this fixed ASAP.

Thats the newest news we have. ASAP is like 50 years.

[b0ff3n]

引用自 ĆAĆA SE VRAĆA：

Any news about fix?

You're funny! 😂

[Tsukiko]

引用自 ĆAĆA SE VRAĆA：

Any news about fix?

aah, this made me laugh XD though it really shouldn't, i should be crying instead with my amd hardware ;_;

[Brites de Almeida]

引用自 Tsukiko：

引用自 ĆAĆA SE VRAĆA：

Any news about fix?

aah, this made me laugh XD though it really shouldn't, i should be crying instead with my amd hardware ;_;

Valve's lack of support is the thing you should be crying about. Counting all our money takes them all their available time.

[Car]

Using software encoding is no solution, the hardwareencoding/decoding has to work. So far I know, hardwareencoding is working if you use an AMD GPU into the host and an Steamlink adapter as client. So why it isn't working with an AMD/Nvidia or Intel as an hardwaredecoder client? The only reason I see there is to force the AMD GPU Users (Host) to buy an Steamlinkadapter, so Valve can make cash with it!

[acrylamidetic]

引用自 Car：

Using software encoding is no solution, the hardwareencoding/decoding has to work. So far I know, hardwareencoding is working if you use an AMD GPU into the host and an Steamlink adapter as client. So why it isn't working with an AMD/Nvidia or Intel as an hardwaredecoder client? The only reason I see there is to force the AMD GPU Users (Host) to buy an Steamlinkadapter, so Valve can make cash with it!

Is this confirmed that the blinking issue does not occur with steamlink when using hardware encoding on an amd gpu and hardware decoding on the steamlink? I've held off on trying the steamlink again because of this issue but I've seen this mentioned before and wanted to double check before purchasing another one (returned the first one due to other issues I know they've since fixed.)

[Car]

Please double check if it work, i do not own the steamlink, I only read abaut that anywere so I am not sure about that. May be some one in the forum can confirm or disconfirm.

[ShadowNate]

Is Steam Link running some Linux OS/ SteamOS or Windows?

[Panthau]

wow... didnt expect that. i just got myself a laptop for in home streaming just to find out, that it doesnt work anymore. well, it was a good idea from valve... hopefully others pick it up in the future.

[Griz]

There is a workaround. Enable hardware encoding on host, but disable hardware decoding on client. Flickering stopped.

[MasterMind]

引用自 ĆAĆA SE VRAĆA：

There is a workaround. Enable hardware encoding on host, but disable hardware decoding on client. Flickering stopped.

yah its a workaround but regardless people will see better performance on there clients by using hardware decoding, which is what you want because thats where your gonna game from...and I also heard that this problem has been solved on the steam link...

[Atreides]

引用自 ĆAĆA SE VRAĆA：

There is a workaround. Enable hardware encoding on host, but disable hardware decoding on client. Flickering stopped.

It depends on your setup. I have an 8 core AMD FX 8320 @ 4.4GHZ as my host, and a wimpy old Intel Core 2 Duo 3GHZ on my client. If either one of these is doing SOFTWARE decoding (which relies completely on CPU power) it has to be my host. I can set it to use 4 cores for the video encoding and it works pretty well for most games. Not sure how Witcher 3 or GTA 5 would do on Very High.

I'm not saying im happy with this workaround but it's better than the flickerfest that I can barely even look at without getting a headache.

This also seems to be OS independent. I have tried the following with my client computers:

Windows 7 64 bit - flickers
Linux Mint - flickers
Ubuntu - flickers
xubuntu - flickers
SteamOS - flickers

Steam/Valve, if this is something you are waiting on AMD for, please throw them under the bus and let us know. Has there been any progress on this? New AMD cards are coming out very soon, will they have the same issue?

The biggest thing that bothers me about this is the lack of communication!

I remember the first time I reported this issue it was a week before my GF's birthday. We were having a party and I wanted to do some pc party games (sonic racing, magicka, rocket league etc). I figured it would be fixed in a week, right on time for the party.

THAT WAS NOVEMBER!!!!! 6 Months with no communication. Please give us an update, even if it is "We're still working to resolve this". Cause right now I feel we are being ignored and that's a great way to lose customers. I was a steam early adopter. I own I believe every Valve game. I'm a little bit of a fan boy. I have a 5 digit steam id. And right now I am disgusted with Valve.

Post an update!!!!

[loud_colour]

引用自 ĆAĆA SE VRAĆA：

There is a workaround. Enable hardware encoding on host, but disable hardware decoding on client. Flickering stopped.

Thats not a good workaround, because it will not work for a lot of users.

I have a low-budget, low-power HTPC that has a weak cpu (E-450) that i want to stream to. Software decoding is not an option, but there is more than enough power to decode a 1080p/60Hz stream with hardware decoding (GT-710).

Because, you know, i feel like this IS the idea of streaming: Get the performance of my powerful desktop PC and stream it to my cheap, not very powerful client connected to a TV. Why would i stream to an i5 or something (that could do software decoding brilliantly)? I'd rather install the game on the client directly in that case.

Steam wants us to buy a Steamlink I guess, but at least they could say so here so that this discussion can finally end. I definitely will NOT buy a steamlink, because if I'd have troubles with it (like screen flickering), I guess nobody from steam would help me with my troubles or would respond in the forums.

[The Spekz0r]

引用自 Coopolon：

引用自 Car：

Using software encoding is no solution, the hardwareencoding/decoding has to work. So far I know, hardwareencoding is working if you use an AMD GPU into the host and an Steamlink adapter as client. So why it isn't working with an AMD/Nvidia or Intel as an hardwaredecoder client? The only reason I see there is to force the AMD GPU Users (Host) to buy an Steamlinkadapter, so Valve can make cash with it!

Is this confirmed that the blinking issue does not occur with steamlink when using hardware encoding on an amd gpu and hardware decoding on the steamlink? I've held off on trying the steamlink again because of this issue but I've seen this mentioned before and wanted to double check before purchasing another one (returned the first one due to other issues I know they've since fixed.)

引用自 Car：

Please double check if it work, i do not own the steamlink, I only read abaut that anywere so I am not sure about that. May be some one in the forum can confirm or disconfirm.

Yes, as owner of a steam link I can verify that the Steam link is working perfectly with AMD AMF hardware encoding on the host and hardware decoding on the steam Link.

引用自 ShadowNate：

Is Steam Link running some Linux OS/ SteamOS or Windows?

The steam link has an ARM based device (like mobile phones) which differs form computer cpu's (which are x86-x64). Though the link runs a ARM based version of linux.

My guess is that since valve has more control over the software and drivers of the steam link they were able to create a work around for this issue while for Windows Valve depends on microsofts DXVA API for decoding as well as properly supported drivers from nVidia, AMD and Intel.

I also have another Linux client and while there are also issues with hardware decoding in Linux they differ a bit from the issues in Windows. With a Linux client there is no flickering, just extremely low FPS.

It's a real shame that this issue is still not resolved... However a post in the steam link forum states that the issues for the link were resolved by an updated driver from AMD for the host, so that suggests that there were indeed issues at the AMD side of the driver. But what I don't get is why that driver solved the issues for the link and not every other device...

But like I mentioned before here in this forum is that I get the strong feeling that Valve is devoting all their resources in the Controller, Link and VR and just forgot the rest of us...

If you take a look at the update logs from the steam client you'll see that there's almost solely fixes/features for either the Controller, Link and VR. Having said that it took them MONTHS to port host encoding options from Big Picture mode to the regular client...
Why? The only reason I can think of is that you can change your host options with the link as the host streams the Big Picture mode directly to the link. As a result you can alter host options with the link and since the link only uses the BP mode from the host, why bother porting those options to the regular client?

[SmellyCat]

Still checking this thread sometimes to see if I can finally use in-home streaming...