Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Also, that alert wasn't able for interaction until I got up and went out to the desktop, so I've no clue what happened last night.
Now, to figure out how to set the Steam Controller input as trusted..,
So, somewhere in Windows the Steam Controller via Steam Link app appears to be blocked. Any ideas on how to fix this are appreciated...
Dug around in settings and system alerts, can't find anything that stands out. Also reinstalled Steam, just to be sure, and no luck there either.
Also tried Sunshine (PC) and Moonlight (tablet). Still BT connect to tablet, table wifi to PC. Connect to Steam, no inputs recognized. Opened the Destroy All Humans demo through GoG Galaxy, and got right-pad mouse movement, right trigger select/fire, but nothing else. (Didn't do anything to make the SC work properly - the DLL renames/deletes; might try thst later.)
https://steamcommunity.com/app/353380/discussions/4/
each controller (on each device) can have its own mappings for desktop/chord/bpm and each game
after you start streaming, config the controller, or browse configs and pick defaults
Steam can see there's a Steam Controller connected, but cannot see *any* inputs from it when connected wirelessly to either the Steam Link hardware or the app, for a remote session.
Other Bluetooth controllers function through the app.
The SC functions via USB or BT directly connected to the PC, or via USB to the Link hardware; it will not be seen by Steam on the PC if it's connected wirelessly to the Link hardware.
The SC did function with wireless remote connections when I first used it with the Link hardware, and during the first test run using the Link app.
I've tried five different games, with different controller configs, and consistently have had no function of the Steam Controller, except for the first test run; this is also when I stopped being able to navigate Steam using the controller.
I did get a non-Steam popup on the PC when I first tried the Steelseries controller (and had to go clear it on the PC), regarding "trusting remote inputs" or the like, but only that time.
This smells like Windows "protecting" me from potentially harmful remote inputs, specifically anything from the Steam Controller, but I just don't know where Windows hides the digital jimmy that I need to kick to un-protect my computer, so I can get back to rotting my mind with vidyagamez.
Thank you for being the first to respond, however.
If I connect directly to the PC with the spare controller at the same time, it'll see two Steam Controllers, but will only take input from the local one. Both will work connected to the PC, both will connect to the tablet and be seen by Steam via the Link app, and both will not have inputs recognized/accepted via that remote connect.
choices are to use a k/m at the client, or go to the host and bind the remote controllers controls using the hosts k/m
And Steam is still seeing there's a Steam Controller connected remotely. Just no inputs. And if Steam can't see the imputs, it can't pass them to whatever game I'm trying to play.