STEAM GROUP
Steam Remote Play homestream
STEAM GROUP
Steam Remote Play homestream
5,650
IN-GAME
44,000
ONLINE
Founded
November 7, 2013
WIRED xbox one controller not working with steam link.
Is anyone having an issue with a wired controller not being recognized outside big picture? I have narrowed it down to a steam link issue. Basically, My controller worked fine in the desktop and big picture with the steam link when I first got it, but now there are these new controller options called base options. It seems to only be built for the steam controller and I have a feeling that **** is breaking my xbone controller.
Last edited by Hobelar Espanol?; Jul 10, 2017 @ 8:49pm
< >
Showing 1-15 of 15 comments
wicked_one.at Jul 11, 2017 @ 1:27pm 
Same to me here, since today, after a few minutes in game, my input just becomes unresponsive and my character is just heading the direction the last input came.

ALso using a xbox one controller for windows, which works perfectly fine when playing on the gaming rig itself, so it´s only affected when using in-home streaming

Very annoying, hope they fix it asap.
G3na5ide Jul 11, 2017 @ 4:24pm 
Phew. Not just me then. :)

I'm seeing this streaming to an Ubuntu Linux 14.04 box with both wired and wireless X-Box 360 controllers. I've tried the steam beta, changing the version of the xpad driver I'm using, just about everything, even using Windows (fine streaming to a Windows box.)

If you turn on the on screen streaming diagnostics and look at the outgoing bitrate you can see where the controller input gets queued for a while but then suddenly "bursts" when the control comes back to life again. Interestingly, when the game is unresponsive, you can still use the controller shortcut (Start + Y on a 360 controller) to turn on the full diagnostics info on the screen, so it's definitely steam itself!
jb33 Jul 12, 2017 @ 2:16am 
Is it similar to what I'm experiencing here?

http://steamcommunity.com/discussions/forum/11/1457328846184422104/
ripper81 Jul 12, 2017 @ 7:46am 
Same here. Host and Client are on Linux (Kubuntu 17.10).
FallenAege Jul 12, 2017 @ 9:55pm 
Been having similar PITA issues here. Host is a Windows 10 PC and guest is a Ubuntu 16.04.2 PC.

Guest system fried a wireless Logitech F710 Gamepad dongle after repeatedly connecting and
disconnecting following inputs being frozen despite controller working fine. Tried using the Logitech utility to reprogram the dongle, but my Windows 10 PC can't even detect it anymore.

Got a replacement wired Logitech F310 Gamepad but the guest Ubuntu PC has the same problem.

My solution was to plug the Logitech F310 Gamepad on the Windows 10 host PC, stream to the Ubuntu 16.04 guest PC, and use the gamepad once the stream is connected (since the computers are nearby, but on different TVs).

Anyone know where I can file a complaint? A new Logitech F710 Gamepad dongle is 15 USD + shipping from Logitech.
TDA003 Jul 22, 2017 @ 11:17am 
I do not think it is the controller, but rather your steam client. I'm having similar issues when streaming between win10 pcs using an xbox360 controller. This was not a problem 2 weeks ago.
EAPidgeon Jul 22, 2017 @ 10:46pm 
Suffering the same issue using an Xbox One Controller. Steam seems to be detecting the controller when using streaming in the steam controller mouse and keyboard config, not as an xinput device. This issue persists whether using the pubic or beta clients.

*Edit:
This was meant for a different but similar thread of which all of these are currently the most active topics. Regardless all of the recent xinput issues seem to be related. Just consider it another affirmation that there's a problem with steam's client in relation to xinput devices while streaming at the moment.
Last edited by EAPidgeon; Jul 22, 2017 @ 10:49pm
Viscerus Jul 24, 2017 @ 10:19am 
Yes Sir Tainly, I have this issue as well. It has essentially rendered my Steam Link unplayable for the whole month of July:

http://steamcommunity.com/groups/homestream/discussions/1/540731691173043692/?tscn=1500426010

Maybe if you could also post the bug there we can get a fix!
Viscerus Jul 28, 2017 @ 7:31am 
BTW, I fixed my broken controller configs by enabling the Steam Overlay - something that previously could be disabled with no effect on controllers.

"Steam Overlay" is a very misleading name. Based on this support page, there is no reason to believe it would screw up your controller configs:

https://support.steampowered.com/kb_article.php?ref=9394-yofv-0014

Either the overlay breaking controller configs is a bug or its usage is really poorly documented.
TDA003 Jul 30, 2017 @ 5:16pm 
It is not just wired XBOX360 controllers; it is wireless as well.

Could someone with VALVE Cusomter Support pleas comment on one of these posts about a pending resolution to this issue. Clearly based on this thread and several others:

1. XBOX360 Wired and Wireless Controllers no longer work with Steam Link
2. XBOX 360 Wired and Wireless Controllers no longer work with Windows 10 streaming
3. XBOX 360 Wired and Wireless Controllers no longer work with Linux Client streaming

I've seen where VALVE employees have helped DS4 controller users resolve their issues. Could you please provide XBOX 360 controller users the same courtesy?
Viscerus Jul 30, 2017 @ 5:21pm 
Originally posted by TDA003:
It is not just wired XBOX360 controllers; it is wireless as well.

Could someone with VALVE Cusomter Support pleas comment on one of these posts about a pending resolution to this issue. Clearly based on this thread and several others:

1. XBOX360 Wired and Wireless Controllers no longer work with Steam Link
2. XBOX 360 Wired and Wireless Controllers no longer work with Windows 10 streaming
3. XBOX 360 Wired and Wireless Controllers no longer work with Linux Client streaming

I've seen where VALVE employees have helped DS4 controller users resolve their issues. Could you please provide XBOX 360 controller users the same courtesy?

Valve responded to my report on this bug in the bug thread- they claim its fixed in latest Steam Client beta. You might want to participate in the beta to see if it works for you:

Originally posted by SDalton:
Originally posted by Viscerus:
ISSUE:
When using Xbox One S controller in Steam games over Steam Link, some or all of the inputs aren't registered in the game. NOTE: This also happens with a wired Xbox 360 controller connected to the Steam Link.

This should be fixed in the latest Steam Client Beta
Last edited by Viscerus; Jul 30, 2017 @ 5:22pm
TDA003 Jul 30, 2017 @ 5:37pm 
I've installed the latest client beta on both my windows pc's to try to fix this issue. XBOX 360 controller does not workt wint streaming between Win 10 or to Steam Link unfortnately.

Additionally, updating to latest beta client required user developped solution to resolve broken audio driver issue.

Viscerus, thank you for trying to help.

Valve Customer Support, please update on pending resolution.

Viscerus Jul 30, 2017 @ 8:45pm 
Sorry to hear that! I should have mentioned my issue was happening while running Win 7.
TDA003 Jul 31, 2017 @ 4:48pm 
Hat tip to Viscerus and ReBoot for leading me down the right path.

After digging up every thread on broken XBOX360 controller IHS issue, I found a solution that works for me. Caveats: My IHS host is Win10.

1. Do fresh instal of latest Win 10 beta client.

2. Uncheck every box in controller config panel (no XBOX controller configs, etc.)

3. Enable steam overlay on host.

4. Disable MS game bar or whatever the XBOX thing is on Windows 10 Creators Update

5. Restart computer.

This has fixed the issue for both steam link and win 10 to win 10 IHS for me.

For Win 10 to Win 10 IHS, see above for host and streaming client settings.

I hope this helps everyone experiencing the same issue. I tested this on: (1) RetroArch, (2) Lego Star Wars: The Force Awakens, (3) Galak-Z which was not affected by the issue, but I just wanted to check to confirm I didn't break anything else, (4) Metal Gear Solid V: The Phantom Pain.

VALVE Customer Support: Same request as before, please acknowledge this issue and post a response outlining an official solution or pending update. This was a community developed response for what appears to be a long-standing Win 10 Client issue.
TimoV Aug 5, 2017 @ 4:44am 
Just a friendly reminder that I'm trying to document this issue as detailed as possible. With every new Steam Client beta, I'm recreating my issue, with no success so far.

I will continue to document the issue in my thread: http://steamcommunity.com/groups/homestream/discussions/1/1470840994955648024/ until I hopefully get a response.
< >
Showing 1-15 of 15 comments
Per page: 1530 50

Date Posted: Jul 10, 2017 @ 8:45pm
Posts: 15