Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable To Find Controller #15

Open
kayliekay opened this issue Jan 17, 2018 · 6 comments
Open

Unable To Find Controller #15

kayliekay opened this issue Jan 17, 2018 · 6 comments

Comments

@kayliekay
Copy link

ProconXInput was working perfectly fine, when out of nowhere after about two weeks of using it reliably, it crashed. I tried reopening it, and all it will say is:
"initializing hidcerberus
Unable to find controller"

I have tried numerous times to replug my controller, reinstall ProconXInput, and tried countless times trying to restart my computer. It just will not work anymore for seemingly no reason

@Jdbaii
Copy link

Jdbaii commented Feb 17, 2018

I had the same issue, but then I looked at the switch-pro-x driver linked to in the readme that is part of the base for this one.
This part is of importance:
"ViGEm. You will need both the bus driver from the 1.8.1.0 release (1.10.0.0 is buggy) and the HidGuardian Driver + HidCerberus.Srv. Currently requires devcon.exe from the Windows SDK to install."
I noticed that this version didn't include the bus driver. Once I right-clicked the inf for the bus driver linked to there and installed it, this driver is able to detect my pro controller just fine.
Which is weird, since it claims to not require HidGuardian/HidCerberus, and I originally didn't have them installed, and it still couldn't detect my pro controller.

@Jdbaii
Copy link

Jdbaii commented Feb 17, 2018

This is the repo for switch-pro-x: https://github.com/ToadKing/switch-pro-x
And the link for ViGEm is further down on the page. Download the version mentioned, extract it, go into the drivers folder (x86/x64 depending on what architecture your Windows is running on), right-click ViGEmBus.inf and click install.
After doing that, and running ProconXinput (which now recognizes my controller), my Switch Pro Controller is now recognized as a 360 controller in wired mode and works as expected.
Let me know if it works for you as it did for me.
Of course you still need SCPVBus. I already had it due to using XOutput in the past, but ran the install script that came with this anyway which did not help at all. Anyway, if you didn't already run the install script, even if you already have SCPVBus and the other things, do that first, since it'll install the specific versions that are confirmed to work with this program.

@Jdbaii
Copy link

Jdbaii commented Feb 17, 2018

That being said, this doesn't really offer any benefits over wireless BT mode, except not needing BT support. I'll be trying switch-pro-x instead since it seems to support rumble.
Aaaand.... switch-pro-x seemed to work after going through all the hurdles to compile it but once connected and detected by the program my Pro Controller was flashing the charging LED and input didn't work, nor did the LEDs at the front light up.

@jonapatig
Copy link

None of this helped the issue or I have done something wrong. Is it possible that somebody restates the necessary steps in order to solve this issue in a simpler manner? After downloading the switch pro x, I could not find the ViGEmBus.inf file.

@Panossa
Copy link

Panossa commented May 26, 2020

Same here but it didn't work, ever.
I don't even get a sound when I plug in the controller after installing the drivers through the .bat

@f0rtdev
Copy link

f0rtdev commented Apr 24, 2021

Same issue after an entire year.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants