controller does not work after going from test mode back to regular mode back to test mode #6
Comments
|
So i turned off secure boot in UEFI/BIOS. How would I add a test
certificate?
…On Thu, May 4, 2017 at 9:03 AM, mirh ***@***.***> wrote:
Most likely you have to add test certificate to driver
OR you have secure boot enabled and windows is kindly telling you to fuck
off
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#6 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AKZR2G2OUu3XmxEmLFI7Z72HkK3YVFyLks5r2fbIgaJpZM4NQr0Y>
.
|
|
Tried that hehe. Thank you for your assistance. I want to help your
project. If i paypal'd you the 260 dollars to make your driver
windows-legit would this make it easier for you to get this out to the
masses?
…On Fri, May 5, 2017 at 4:44 AM, mirh ***@***.***> wrote:
Ok, seems <http://www.osronline.com/showThread.CFM?link=278845> like
<https://communities.intel.com/thread/110632#451088> code 10 has nothing
to do with signing.
Given a reboot triggered it, I wouldn't say it's a hardware problem.. More
likely your windows (let me guess, 10?) going stupid.
Try to full <https://arduino.stackexchange.com/a/8643> reboot, uninstall
and reinstall the driver.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#6 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AKZR2Ir64GZJl6WQDrQwpe1OHfaz3Gxcks5r2wuNgaJpZM4NQr0Y>
.
|
|
|
|
Because I know you and HID minidrivers are like bread and nutella. 😅 |
|
You know me too damn well by now; I've already forked the repo 🤣 |
|
lols @goldenfett feel free to donate to https://www.patreon.com/nefarius ^^ |
|
Oh I definitely will so we can get this driver recognized because windows creator edition is kicking my azz hehe
Sent from my iPhone
… On May 5, 2017, at 12:25 PM, mirh ***@***.***> wrote:
lol
@goldenfett feel free to donate to https://www.patreon.com/nefarius ^^
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
What's even happening here? 😉 Hi, I'm still around, but most of my Github activity is on a fork which why it doesn't show up. Thanks for your offer @goldenfett, it would certainly help some users to not have to bother with switching testsigning on. But @nefarius seems to have quite a lot of drivers going too, and I'd be perfectly okay with "Nefarius Software Solutions" signing my driver if this can avoid having to buy two code signing certificates. Besides the Shield controller is much more niche than DualShocks. Anyway I don't think your error is related to signing, I couldn't replicate it. Could you post screenshots of the device manager showing the Shield controller, with "Display -> Device by connection" on? (showing the device hierarchy and the error code) |
|
Here is a screenshot of my device manager. And the error code |
|
I saw the code 10 error too while switching drivers, so try the following, it may help:
|
Well, unless you also want to wire the controller mic, jack and touchpad (which wouldn't be bad though 😆), just replacing HID isn't all that complex/different/rocket science. In other news, did you see the effort to make it work over wifi? https://github.com/devmapal/nvidia-shield-controller-driver |
|
Trying it right now hmmm and I get the same error. What do you mean by switch to the driver. Do I install it right before because I already installed the inf.
…Sent from my iPhone
On May 5, 2017, at 2:04 PM, Elie Morisse ***@***.***> wrote:
I saw the code 10 error too while switching drivers, so this may help, try the following:
Switch back to the generic "USB Input device" driver (right click on the Shield controller device, Update Driver Software.. -> Browse my computer for driver software -> Let me pick from a list of device drivers on my computer)
Unplug then replug the controller
Switch to the "NVIDIA SHIELD Controller" driver
Unplug then replug the controller again
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Same way you selected the generic driver (right click on the Shield controller device, Update Driver Software.. -> Browse my computer for driver software -> Let me pick from a list of device drivers on my computer), but in the list choose "NVIDIA SHIELD Controller" instead of "USB Input device". If this didn't work, could you paste your |
|
@Syniurge I want to say thank you for your help and great service to humanity good sir. i couldn't post the entire thing on pastebin so i went through that file to find things relating to my nvidia shield controller.
hopefully i copy and pasted the right stuff |
|
Here you go. @mirh hopefully this was fast enough 😉 Beware it's untested since I don't own the hardware. |
|
wow awesome the driver is signed now. I still have the same error message
:(. I have no idea what the issue could be
…On Sat, May 6, 2017 at 8:53 AM, Benjamin Höglinger ***@***.*** > wrote:
Here you go.
<https://github.com/nefarius/ShieldControllerWinDriver/releases/tag/v1.0.0.0>
@mirh <https://github.com/mirh> hopefully this was fast enough 😉 Beware
it's untested since I don't own the hardware.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#6 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AKZR2NreY79Lhxta-KThWKCJyTf0jAa4ks5r3JeWgaJpZM4NQr0Y>
.
|
|
Just attach the setupapi.dev.log file here instead of pasting, it ruins the formatting and is impossible to read. |
|
@goldenfett so the issue is that your controller is the new Shield controller (different Product ID). I had no idea if the driver would still be compatible, it would have if the HID reports remained the same but your error confirms that this isn't the case. If you want to help get the new controllers supported, you need to provide me its HID report descriptor, extracted for example with BusDog:
The HID Report Descriptor is the longest Hex value (should be around 268 bytes) that should show up at the top of the "Trace" tab:
Then paste the descriptor and the previous line here, you should have something like: |
|
@nefarius NICE! I will direct new users towards your release in the README if you're okay with that (with of course a warning that I cannot vouch for your trustworthiness but that you seem like a decent guy :D). Thanks for doing this! |
Too bad I haven't the hardware 😂 |
|
@Syniurge I respect your trust in me. It's my way of giving back to the community and if it helps yet another developer I'm happy 😄 I made a few adjustments already; should I create a pull request or would you like to keep things "separate"? Also note that I also included my name in the version information so users can see that it's a build by a third-party (me) so you're not responsible for my fuck-ups (if any). Hope that's ok with you. |
|
@mirh good idea, I had no idea about this feature. |
|
Tell me if I did it wrong @Syniurge. Ur a godsend dood 27 In (USB URB Function: 8) 0.000000 18 12 01 00 02 e0 01 01 40 55 09 14 72 25 05 01 02 00 01 .......@U..r%..... |
|
Here it is in image form the hex version: http://imgur.com/C2FibbF and ascii expanded http://imgur.com/nFlBDmC @Syniurge tell me if you need any more information. thanks again |
|
A pastebin or a simple text file perhaps? ._. |
|
@mirh https://pastebin.com/Rn2s2i68. sorry im a github noob lol |
|
@goldenfett it's perfect thanks. So the new controller model is pretty different HID-wise, however there's nothing inside the HID report descriptor that prevents it from begin detected out-of-the-box as a gamepad by DirectInput (i.e it doesn't suffer from the original issue my driver was trying to fix), I just tried with @nefarius please make a PR, your changes would be nice to merge. |
|
@Syniurge I don't believe that the controller is being detected by x360ce. The driver when being installed still gives the error. It still is being detected as a gamepad. |
|
Sorry I forgot to specify: you need to uninstall the Shield controller driver first (right-click in the device manager -> Uninstall device, tick Uninstall the driver software for this device before accepting -> Unplug -> Replug the controller), so the generic Microsoft driver takes over. Don't use my driver at all. Here's my "virtual 2017 shield controller" being detected in x360ce: Your controller should be detected too, and the descriptor appears standard so x360ce should at least pick buttons and axis. |
|
So I downloaded that emulator. And all of the "HID gamepad properties" function. I just don't know why it wont work in any games or for anything. What should I do @Syniurge. Any more diagnostics I should send you? |
|
Good news then, the new Shield controller model doesn't seem to need a custom driver, most of its functionality already works with the default Microsoft driver (except rumble).
That's because you need x360ce. Today's world of PC game controllers can be a bit confusing, but nowadays for standard gamepads x360ce is a requirement, because most modern PC games rely on Xinput and have bad or no support for DirectInput. Learn to use x360ce, and your Shield controller should work. Basically:
You should hear a bip at the game startup indicating that x360ce has kicked in, and then your gamepad should come to life. I've googled a bit and indeed a few people report that the 2017 controller works with the generic Microsoft driver. So all I can offer is adding rumble support at some point. |
|
The issue that I have with x360ce is that it wont let me specfically bind the z and y axis (if i try and bind one it overwrites the other). Idk what to do sorry if im being annoying @Syniurge. I really appreciate your help |
|
One last question: Does NVIDIA have a windows 10 fix. Because now I have a GTX 1080 and i was wondering if I could get the driver through the companys means? |
Try to use half-axis |
Well this is where you should have checked first 😁 , because yes, NVIDIA does provide a Xinput driver bundled with Geforce Experience, that is usable only by owners of NVIDIA graphics cards. And that driver supports vibration, touchpad, etc. My driver is meant primarily for people with AMD or Intel graphics cards. Until I released it 9 months ago the gamepad was unusable for us (I had mine for 1 year, utterly useless until I took the time to investigate). For some history: https://forums.geforce.com/default/topic/775777/wired-pc-support-for-shield-controller/ With Geforce Experience you do not need x360ce since it already provides Xinput support.
Not at all, this cleared a lot of things for me. I was under the impression from reading the Shield tablet forum that the new controller needed Geforce Experience too to become usable, and some people were asking whether my driver supported the new model or not (the Product ID changed, and noone AFAIK tried to force the driver like you did). Now I have the answers, and I have the HID report descriptor so I can implement rumble support (and perhaps some other tweaks, for ex. my guess is that the triggers probably aren't being detected like on the old model) for AMD users. |
|
@Syniurge I'm glad to have helped. I have GeForce Experience but it seems that the controller is still unrecognized/or I haven't found the correct drivers. Thanks! |
|
I know I must sound stupid but I can't figure out how to get Nvidia's driver working/where to find it ugggggh. usually im not this bad lol |
|
So i uninstalled and reinstalled geforce experience and nada. idk whats wrong. could i be using a low bandwith micro usb cable or something along those lines? |
|
nevermind it started working all of the sudden???? hopefully I didn't annoy you too much lol |
|
All good then, closing the issue. |
I actually got the controller to work last night then i turned off test mode in windows and it didn't allow the driver to run. I changed test mode back to where it was originally (because the unsigned driver wouldn't work with test mode off in windows). And it gives me code 10. Anything that I can do. I entered these commands
bcdedit -set TESTSIGNING OFF
bcdedit -set NOINTEGRITYCHECKS OFF
i did the opposite and put on for both of those. and it still doesen't work :(. Any help would be greatly appreciated and I thank you for doing this work! Thanks
The text was updated successfully, but these errors were encountered: