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
Discussions Rules and Guidelines
Report this post
Actually it does.
Can reproduce and see the issue you are describing.
There is a bug in stable client that stops shield controller being listed in Steam Input at all and is yet somehow applying configurations but controller is glitchy
Which steam beta client fixes.
There is possibly a bug in steam client beta that detects shield controller mouse emulation only when launching gamestream apps from Shield device (tablet and satv) which means Steam Input sees KB + M so never lists controller to apply configurations to. This could be Games Hub app on shield device or GFE on pc issue.
A possible workaround you can try is:
Make sure you have steam client beta installed.
On your local PC setup GeForce Experience to stream your desktop.
On satv launch the desktop from gamestream library.
Enable shield controllers native mouse emulation by pressing and holding android "play" button.
Exit steam
Launch Steam - When you launch steam again very quickly press "B" button on Shield Controller to disable its native mouse emulation and wait for steam to start up.
This should be enough for Steam Input to see shield controller as a controller and apply desktop bindings so your controller just starts working
Exit steam again and quit gamestream session.
Choose the steam app listed in gamestream library to launch big picture and choose which game you want to play from steam library .
I have changed to the most stable update for now. Thank you so much for the work around, but it would be annoying to do everytime.
http://steamcommunity.com/sharedfiles/filedetails/?id=1335561896
On shield tablet touchscreen or mouse helps out but find the touchpad on 2015 shield controller works really well
http://steamcommunity.com/sharedfiles/filedetails/?id=1335561891
Best chances of getting shield controller to work in steam is making sure it is listed in steam input and make sure you are running steam client beta.
As well as all the obvious stuff like latest GFE, gpu drivers, windows updates and your making sure windiws is virus free and healthy as well as your hardware running latest firmwares and healthy
How did he get the Shield Controller to be named as Nvidia Shield Controller. When I have multiple controllers connected, steam forces them to use the same name.
I'm not sure but the most Beta-version of Steam-update is not working so well with Geforce Experience. I think this is more of a GFE issue. I have to run remote desktop on Gamestream, and then open up shield in Big-Picture mode.
Never had too jump through those hoops to get Steam Input detecting shield controller properly for a long time but steam cloud still remembers my steam accounts name for that device
But yeah you are right. For everybody else they will only see device listed as "Xbox type controller" or the like which means Steam Input is detecting and configuring controller, which is good and is what they want.
If device shows up as "generic gamepad" there is more hoops to jump through to get Steam Input to detect controller properly so is not so good
I been describing similar to get steering wheels and pedals and other controllers working in steam and steam apps for a long time now as well
Steam Beta Client Updates Break Steam Input Detecting Controllers Properly.
What makes me notice Steam Input has stopped detecting Shield Controller properly is I can not use controller dpad to navigate Big Picture and controller configurations never get applied properly.
After steam client beta update today, all I had to do was use Big Picture to apply the update and then restart steam again. Then controller was properly detected by Steam Input and be used giving expected behaviours in games and can use dpad to navigate big picture. Desktop config is probably my biggest reason to keep all this working. 😁
Can anybody reproduce or make any sense of what I am describing or am trying to describe?. I see huge improvements in making sure Steam Input lists controllers (especially wheel base buttons for racing sims) and yet nobody seems to be able to reproduce!?
Just make sure to launch add desktop as gamestream app and access steam running in large mode on desktop. Launch big picture from there and just exit steam when you can see your shield controller listed as device, can use dpad to navigate steam (big picture overlay) and can use desktop config for controller in desktop.
Remember to use controller options for each steam library item before launching to personalise and prioritise device. You can completely switch off configurations being applied at all here to for each and every library item.
Do not use the gamestream app shortcuts for games. Use the steam app to launch steam games from steam library after you hàve used desktop app to get steam to get controller detected properly.
But basically if you can use dpad to navigate big picture and your right stick is behaving like expected in steam games then your shield controller is probably working like expected.
If you can not use dpad and or controller in games, restarting steam or rebooting windows PC helps to get steam input to detect controller properly.
If those don't work opt in (or out of) beta client to refresh/verify steam files and try again.
That is what I currently do, use remote desktop to open up steam and then big picture. I have still found that the best to get multiple controllers to work, is to make sure all controllers are on and connected before you turn on the shield. Then open up steam from moonlight and choose whatever game you want.
I too find there is something wrong with the shortcuts assigned to gamestream apps for steam games.
With steam running in large mode when streaming desktop steam seems to detect controllers and apply configurations better.
This issue is actually humungous as it relative to local PCs as well. Every single steam group discussions are all awash with input related issues.
What we are describing is what Valve NEED TO FIX pronto!
I grew to love steam discussions (especially Steam Universe) because Valve developers used to be active and were very good at clearing things up.
Where has all the great feedback, acknowledgements and great advice from Valve developers went?
I also think changes made to steam for windows beta client to better support cloud gaming solutions offering android support also need to be much more transparent. Adding a "Cloud Gaming" or "Steam Streaming" sub forum to Steam Universe would be cool.
I also think Steam Input deserves its own games hub/ discussion group as Steam Input has far out grown being relative to Steam Controller only.
There is simply do denying Valve developers can be doing an awful lot more to be helping this situation they all and all steam users now find themselves in.
The irony is that all these Steam Input issues we see on desktop is all because of the work being done to make Steam Input handle non steamvr tracked devices work better in steamvr.
I have even noticed not being affected by bugs until I get notifications for updates that contain the fixes!
Have noticed dpad on Thrustmaster steering wheel does work in game but does not work at all in steam overlays.
Shield Controller works flawlessly when paired to SATV and accessing steam apps from virtual windows in the cloud.
I do not have GFE installed too VM and skycomputer uses windows server 2016 and GRID M60 gpu. I.e. not using GeForce gpu
This helps show the problem is steam or windows. Not gamestream, games hub, GFE or GeForce drivers issue/s.
https://youtu.be/atzqcJCf47o
Have you tried using multiple controllers (local-co op games)? I know there is one-bug from gamestream and that is it registers one player to two occasionally. Have you have ever had that bug?
Do you know if the controller issues such as registered controller 1 as two, or buggy multi-player controller support is a gamestream issue or a steam issue ? I have read that steam link also has similar problems.
So I was playing around with controllers again this past weekend. It does seem to be more of a windows/steam issue. If I disable the "X-box" Configuration selection, then controllers seem to work fine using Moonlight's built-in Xbox drivers. So this shows, there, is some error in between Steam's native xbox-drivers and the Xbox controller.
It seems game-stream also has a bug where it disables multi-controller support for some games, when you access the game, even if it is enabled in the drop-down menu. So some bugs are native to stream and some bugs are native to game-stream.