Controller suddenly stopped working. Tried all the logical things, no movement. #2293
Comments
|
To do some tinkering, I removed sunshine and VGiEmBus entirely, no configs, and issue still persists. Then I found out in the device manager that as soon as I connect with Moonlight to Sunshine that a Xbox 360 controller is created, so that part works. However the controller shows a exclamation mark, and I cannot resolve that. Even with driver installer suites. Tried everything there. So Sunshine connects with VGiEmBus but after that no response from controller. Steam Link still work as expected. |
|
Try reinstalling vigembus (it may require a few attempts), following each one by a restart. If that doesn't work, try downgrading vigembus. |
|
Thanks for replying. I tried 3 versions, installed it multiple times, including fully reinstall everything, but I keep only seeing the controller appear in the devices panel from windows, but with an exclamation mark. On the newest version of vigembus the controller doesn’t show up there at all. So it does something. |
|
Same, tried with multiple versions of vigembus and sunshine, with no luck. I wanted to stream to moonlight on steam deck, the controller wouldn't show up in device manager or in steam controller settings at all. But sunshine didn't even complain anything about this in the log. Thanks for your dedication anyway, I can still steam with keyboard and mouse without issues. |
|
Had a similar problem on moonlight embedded. In my case a firmware update to my Xbox Wireless Controller seems to have changed the hardware id code from 050000005e040000200b000013050000 to 050000005e040000130b000020050000. Adding this code to the controller database has worked for me. By the look of the two codes, two identifier numbers seems to have been swapped around. Perhaps a Microsoft oopsie? Might be the case for series x as well. Have you updated the firmware recently? |
I have the same issue, can you elaborate how I can add the code to the controller database? Thanks! |
Wonder it too for my notes. Eventually I reinstalled Windows, and everything is working fine now. So I wonder what caused it eventually. |
Usually removing some entries in the registry could get the issue solved... But the real issue is, even experts in Windows may not know which entry to remove..... |
|
It seems this issue hasn't had any activity in the past 90 days. If it's still something you'd like addressed, please let us know by leaving a comment. Otherwise, to help keep our backlog tidy, we'll be closing this issue in 10 days. Thanks! |
|
This issue was closed because it has been stalled for 10 days with no activity. |
Is there an existing issue for this?
Is your issue described in the documentation?
Is your issue present in the nightly release?
Describe the Bug
Controller not working anymore since a few weeks out of the blue
I’m using Sunshine + Moonlight for as long as Sunshine exists and Moonlight back on Nvidia Game Steam. Recently I wanted to resume a game, but noticed that the controller doesn’t work anymore.
I’m using Moonlight on the Apple TV, I can use the controller to navigate to moonlight, select for example ‘Desktop’ on Moonlight. As soon as the desktop appears, it doesn’t do anything anymore. What I’ve tried on moonlight:
Non works. What I’ve tried furthermore:
Steam Link does work however, I find the quality and latency of link slightly inferior to Moonlight + Sunshine. So I want to fix it. Took my time today to spend many hours over it, normally I give advice in this sub, but now I’m the one who’s stuck.
Here is my Sunshine log after a fresh reboot, connectd with Moonlight, pressed a few buttons on my Xbox Series X controller, and closed it (again, no response in Windows on the controller)
Expected Behavior
The controller to work. Which it did for a long time.
Additional Context
No response
Host Operating System
Windows
Operating System Version
11
Architecture
64 bit
Sunshine commit or version
Latest
Package
Windows - installer
GPU Type
AMD
GPU Model
RX 6800
GPU Driver/Mesa Version
Latest
Capture Method (Linux Only)
No response
Config
.Apps
No response
Relevant log output
The text was updated successfully, but these errors were encountered: