dannyhefc69 님이 먼저 게시:

Cthulhu 님이 먼저 게시:

I'm having a new issue with this. I'm not having any double input issues in the menu, but when I want to choose sides I see a
controller that shouldn't be there. Like, I have one controller connected to the steam link but for some reason 2 show up.

Anyone has a solution to this?

Opt out of steam beta on your host (pc

directional d pad. and set up down left right to wsad. [/quote]

It's not an issue of mapping, you can hit the Steam button on the controller and go to the mapping settings and see that everything is pre-mapped
. It's just that absolutely no inputs reach the game itself.

Also getting the same issue on Win 7 here.

Croat Maximus 님이 먼저 게시:

I have the PowerA Enhanced Wired Xbox One controller. It does work regarding all the input buttons, but it doesn't rumble. Rumble works fine when connected to
Steam Link app?

I have XBOX 360 and Logitech F310 both wired. Rumble works with PC but none of them rumbles with the app and tv. Maybe this is a bigger issue not just your specific controller.

I'm seriously at a loss with this one. I'll try to make my issue as clear as possible (sorry if this ends up being a book)

So I start my steam link via steam controller and connect to my PC
steam link via USB, press the PS3 button, and disconnect the cable, PS3 button. It shows to be player 1 and the steam controller now will NOT recognize any directional input. The only button that works is

Hello, I've been using my Steam Link + Steam Controller for over a year now with little issues. About a week or so ago there was an update to the Steam Client beta which stopped my Steam Controller
from working via the Steam Link: I could still turn the Steam Link on and connect to my PC, but once BP mode launched no controller inputs were recognised.
I switched back to the public steam build and

My controller doesn't work in steam link for Google tv. It pairs with my Hisense u6h and works in Google tv, and shows in steam link under controllers. But no input works in steam link app. It's a
series x controller.


Edit. Seems to be an issue with accessibility services in android. Turning off all services for accessibility and it works no problem. Was using button mapper to change my remotes

think?

Although the author of the blog says this fix is for non-original controllers, might work on original aswell? I don't know anything about XInput API or DirectInput though so this might be useless
I came across this link while googleing on the issue, did anyone try these steps? Might not even be related to the issue, but it might also be just what we need! Worth a shot maybe, what do you guys

MeganeDamashii 님이 먼저 게시:

Yes there hase been an update for the beta client that's supposed to fix controller issues (see pinned thread).

I tested one of my games that didn't accept
input from any of my controllers and it worked flawlessly so far.
(Just in case it might be relevant: My Link is also set to beta)

True, I also switched to beta too. Don't know it it matters but

as it has controller support, but nothing works at all. No mouse or controller input seems to go through until the game starts (I have a wireless mouse nearby that I use to click "launch").
Huh, here I was thinking not being able to move the cursor was a weird issue with The Witcher 2's launcher (only game I've played on the Link recently). Doubly strange with this particular launcher

some reason restarting my steam desktop that I'm streaming from fixes the issue.
- Disabling steam input does nothing. The setting doesn't seem to be working at all currently in the controller settings
Since the new big picture UI update I have had several issues that weren't happening before:
- The biggest (and most irritating) is half the time when exiting a game, especially a non-steam game, the