ShieldControllerWinDriver icon indicating copy to clipboard operation
ShieldControllerWinDriver copied to clipboard

Shield Controller 2017 support

Open bezza191 opened this issue 7 years ago • 12 comments

It states in Read Me that 2017 model support is coming, but that was from several months ago. Is this still planned to happen? Or is there someone else who may be able to do the work?

I ask because the 2017 model is barely supported by Windows, and gas major problems with the trigger and analogue stick inputs

bezza191 avatar Mar 30 '18 13:03 bezza191

IIs this project still underway or has the work been abandoned completely going forward?

bezza191 avatar May 10 '18 04:05 bezza191

Sorry, I got really busy around the time I intended to "blindly" add support for the 2017 controller and later my motivation faded in favor of other projects. I can't tell if I completely abandoned it yet, just not right now.

What issues do you have with the generic Microsoft driver? More specifically what doesn't work in x360ce?

Since I don't have the controller physically knowing in advance exactly what needs fixing will greatly help me get it right quickly instead of shooting in the dark.

Syniurge avatar Jun 25 '18 15:06 Syniurge

No worries, these things happen!

Controller had multiple issues running on a PC without GeForce Experience, things such as mapping the triggers and analogues to the same axis and the like. This also meant x360ce couldn't distinguish between them when running the generic windows driver

A few weeks back there was another firmware update for the controller though, and it now works flawlessly on both my main Win 10 rig (with GFE) and on my laptop (No GFE as Intel graphics)

Thanks for stopping by to reply though, and for your honesty.

Good luck with the other projects

bezza191 avatar Jun 25 '18 17:06 bezza191

Nice move from Nvidia! Does even rumble work without GFE?

Syniurge avatar Jun 25 '18 21:06 Syniurge

To be honest, I'm not sure if it did before this update. Couldn't get enough working to make a game worth playing

I've not not tested for it specifically, but given how well the rest of the controller works now, I don't see why rumble wouldn't work too

bezza191 avatar Jun 25 '18 21:06 bezza191

Rumble is kinda special, it's harder for the firmware coders to implement it "the DirectInput way".

Syniurge avatar Jun 25 '18 23:06 Syniurge

Oh ok. Well I'll give it a test and let you know. Likely be tomorrow sometime

bezza191 avatar Jun 25 '18 23:06 bezza191

Done some testing today, and you were right, the rumble doesn't appear to work without GFE

bezza191 avatar Jun 26 '18 16:06 bezza191

If you provide me the HID descriptor of the latest firmware by following https://github.com/Syniurge/ShieldControllerWinDriver/issues/6#issuecomment-299656835 , I could probably add rumble support for Intel and AMD users with very few changes to my driver and it should work on the first attempt.

Syniurge avatar Jun 27 '18 15:06 Syniurge

Hi, any plans to add 2017 controller support? What do you need? to implement it? Is it at all possible for me to learn how to add it?

Mikestriken avatar Nov 01 '19 11:11 Mikestriken

Id love to have 2017 controller support, since im having issues with both stick y axis not working. I found this: https://github.com/Sonic853/NvidiaShieldController_2017/blob/master/BusDog_Data.md

idk if youve ever thought about updating this driver, so this is more or less of a bump

givowo avatar Sep 08 '21 18:09 givowo

If you provide me the HID descriptor of the latest firmware by following #6 (comment) , I could probably add rumble support for Intel and AMD users with very few changes to my driver and it should work on the first attempt.

Hello, Did you add rumble to your driver? I can't find anything on the web.

purhunter avatar Jul 16 '24 21:07 purhunter