Ce sujet a été verrouillé
Enable Force Feedback for Xbox One Controllers (Windows 7/8/8.1 x64 ONLY)
***UPDATE 4/17/2016***

Going forward "Updates" will no longer be posted here at the top. To view updates (including TODAY's) and compatible controllers follow the OneDrive link and view the changelog.
______________________________________________________________________


For those interested in having force feedback, vibration, rumble or whatever one decides to call it, I have modified the existing Japanese force feedback driver for the 360 controller (and other xinput devices) by Masahiko Morii. If you are seeking support for official wired and wireless Xbox 360 controllers go here:

Force Feedback Driver for Xbox 360


1. Download the file.

Updated Force Feedback Driver for Xinput Controller[onedrive.live.com]

2. Run and click Next. (If prompted beforehand, click more info or I understand and run anyway)


3. If previous version is installed, click Remove.


4. Run again and click Complete, then choose install. (if prompted again, choose yes to complete installation)


NOTE: THIS IS SAFE...

This does not overwrite the official Xbox One Controller driver. It simply redirects the force feedback call from DInput to XInput. I have tested this on two of my home computers and it worked on all Directinput reliant games.


TROUBLESHOOTING:

1. DOUBLE CHECK that "Force Feedback Driver for Xinput" is removed in Add or Remove Programs, restart PC, then try again.

2. If you intend to use 360 controllers alongside an Xbox One controller you may have to have said 360 controller(s) turned on during installation.

3. x360ce may conflict with the force feedback of controllers (remove from game directory if this is the case) and try again.

4. From my understanding of this driver, Xbox 360 racing wheels DO NOT WORK. That is to say they will not vibrate or rumble.
Dernière modification de NUK3 TH3 WHAL35; 17 avr. 2016 à 10h05
< >
Affichage des commentaires 91 à 105 sur 152
EVII 14 déc. 2015 à 11h27 
Brass a écrit :
evitec (GER) a écrit :

?
???


Wheres the post in this thread containing this info? We didn't know about this. So whats your point with "late to the party"
evitec (GER) a écrit :
Brass a écrit :
???


Wheres the post in this thread containing this info? We didn't know about this. So whats your point with "late to the party"
My bad, it's actually in the other thread about this issue.

http://steamcommunity.com/discussions/forum/1/490123938430246727/
I bought a Wireless Adapter and one of the new 3.5mm-equipped controllers. No Rumble/FF in DirectInput with the posted driver. Interestingly, it puts each trigger on its own Axis and unlocks the Xbox Guide button, something it doesn't do when connected by the cable. I've tried a couple XInput games, they work fine.

If this is still maintained, could you give adding VID_045E PID_02FF a go?
i have a 360 controller and it works fine for me
jdenm8 a écrit :
I bought a Wireless Adapter and one of the new 3.5mm-equipped controllers. No Rumble/FF in DirectInput with the posted driver. Interestingly, it puts each trigger on its own Axis and unlocks the Xbox Guide button, something it doesn't do when connected by the cable. I've tried a couple XInput games, they work fine.

If this is still maintained, could you give adding VID_045E PID_02FF a go?

Wow! That's interesting. I noticed a while back that the Xbox One official driver has separated the triggers, but not that they've added the Home button as usable button (although I foresee Steam conflicts like unwantingly opening it), but try this link below.

{Link Re-directed To Top of Page}
Dernière modification de NUK3 TH3 WHAL35; 18 janv. 2016 à 14h54
jdenm8 17 déc. 2015 à 18h39 
No luck, that's a bit annoying. I'll keep at it.
EDIT: Just had Big Picture listen to it. Hasn't responded to it the last several times I've tried.
Dernière modification de jdenm8; 17 déc. 2015 à 18h41
Thanks
jdenm8 a écrit :
No luck, that's a bit annoying. I'll keep at it.
EDIT: Just had Big Picture listen to it. Hasn't responded to it the last several times I've tried.

That's strange. I double checked the driver and it "should" be working for you. I was "hoping" that when I added support for the wireless adapter itself it would prioritize itself above a specific Xbox One controller's specific Hardware ID.

I can only suggest that you double check you're getting the right Hardware ID's for the controller. The only places the controller shows up when using it wirelessly is under Human Interface Devices as an XINPUT compatible HID device and under network devices as Xbox Wireless Adapter for Windows. Other than that, uninstall the driver I've provided and double check it's been removed from Apps and Features or Add or Remove Programs. It's listed as Force Feedback Driver for Xinput (or something along those lines). Restart after removal and once your back on the desktop run the driver installation software again and choose COMPLETE install.

If you STILL don't get Rumble then try seeing what the Hardware ID's are by removing (physically, not as in uninstalling) the wireless adapter and plugging the controller into a USB port.
Dernière modification de NUK3 TH3 WHAL35; 18 déc. 2015 à 9h24
Just wondering, do you already have these HWID's in your package:

Wireless USB Connector:

USB\VID_045E&PID_02E6&REV_0100
USB\VID_045E&PID_02E6

Wireless Controller, without 3.5mm Its named as XINPUT compatible HID device:

HID\VID_045E&PID_02FF&IG_00
HID_DEVICE_SYSTEM_GAME
HID_DEVICE_UP:0001_U:0005
HID_DEVICE

Just curious
jdenm8 18 déc. 2015 à 20h23 
I don't know what's happening either. I'll give reinstalling another go.

As for the Hardware information, it matches what Xadro has listed. I've tried the controller when it's plugged in and DirectInput rumble works fine with the driver. Playing an XInput game when connected wirelessly also has rumble, tested with Just Cause 2 and Saints Row 2.
Dernière modification de jdenm8; 18 déc. 2015 à 20h25
NUK3 TH3 WHAL35 a écrit :
***UPDATE 12/6/2015***

As a means to clear the clutter up top here, I've decided to package alongside the download a change log of the newly compatible controllers instead of listing each update up here. The latest one being the XBOX 360 Afterglow AX.1 controller.
______________________________________________________________________


For those interested in having force feedback, vibration, rumble or whatever one decides to call it, I have modified the existing Japanese force feedback driver for the 360 controller (and other xinput devices) by Masahiko Morii. I have replaced the HORI STEERING CONTROLLER EX option with that of an Xbox One Controller.


1. Download the file.

Updated Force Feedback Driver for Xinput Controller[onedrive.live.com]

2. Run and click Next. (If prompted beforehand, click more info or I understand and run anyway)


3. If previous version is installed, click Remove.


4. Run again and click Complete, then choose install. (if prompted again, choose yes to complete installation) (Or to pick and choose controllers, click Custom instead of Complete)


NOTE: THIS IS SAFE...

This does not overwrite the official Xbox One Controller driver. It simply redirects the force feedback call from DInput to XInput. I have tested this on two of my home computers and it worked on all Directinput reliant games. I̶ ̶C̶A̶N̶N̶O̶T̶ ̶c̶o̶n̶f̶i̶r̶m̶ ̶i̶f̶ ̶t̶h̶i̶s̶ ̶w̶o̶r̶k̶s̶ ̶o̶n̶ ̶"̶w̶i̶r̶e̶d̶"̶ ̶3̶6̶0̶ ̶c̶o̶n̶t̶r̶o̶l̶l̶e̶r̶s̶ ̶a̶s̶ ̶I̶ ̶d̶o̶ ̶n̶o̶t̶ ̶h̶a̶v̶e̶ ̶o̶n̶e̶ ̶(̶j̶u̶s̶t̶ ̶w̶i̶r̶e̶l̶e̶s̶s̶)̶.̶ ̶I̶ ̶h̶a̶v̶e̶ ̶s̶e̶e̶n̶ ̶d̶i̶f̶f̶e̶r̶e̶n̶t̶ ̶f̶o̶r̶u̶m̶s̶ ̶f̶o̶r̶ ̶d̶i̶f̶f̶e̶r̶e̶n̶t̶ ̶g̶a̶m̶e̶s̶ ̶h̶e̶r̶e̶ ̶o̶n̶ ̶t̶h̶i̶s̶ ̶t̶o̶p̶i̶c̶ ̶a̶s̶k̶i̶n̶g̶ ̶f̶o̶r̶ ̶t̶h̶i̶s̶ ̶s̶o̶ ̶h̶e̶r̶e̶ ̶i̶t̶ ̶i̶s̶.̶


REMEMBER:

Though this Guide is intended primarily for Xbox One controllers, this still works and gives force feedback to Xbox 360 controllers as well.


TROUBLESHOOTING:

1. DOUBLE CHECK that "Force Feedback Driver for Xinput" is removed in Add or Remove Programs, restart PC, then try again.

2. If you intend to use 360 controllers alongside an Xbox One controller you may have to have said 360 controller(s) turned on during installation.

3. x360ce may conflict with the force feedback of controllers (remove from game directory if this is the case) and try again.

4. From my understanding of this driver, Xbox 360 racing wheels DO NOT WORK. That is to say they will not vibrate or rumble.


I had to sign in just to let you know, you are ♥♥♥♥♥♥♥ amazing, I can now have rumble on epsxe :D thank you so much.
Xadro a écrit :
Just wondering, do you already have these HWID's in your package:

Wireless USB Connector:

USB\VID_045E&PID_02E6&REV_0100
USB\VID_045E&PID_02E6

Wireless Controller, without 3.5mm Its named as XINPUT compatible HID device:

HID\VID_045E&PID_02FF&IG_00
HID_DEVICE_SYSTEM_GAME
HID_DEVICE_UP:0001_U:0005
HID_DEVICE

Just curious


jdenm8 a écrit :
I don't know what's happening either. I'll give reinstalling another go.

As for the Hardware information, it matches what Xadro has listed. I've tried the controller when it's plugged in and DirectInput rumble works fine with the driver. Playing an XInput game when connected wirelessly also has rumble, tested with Just Cause 2 and Saints Row 2.



Okay BIG apologies on MY end. I really couldn't understand why the RUMBLE wasn't working. So I again went through the driver and everything checked out. THEN I went and actually grabbed my driver from the link at the top of the page. I checked THAT driver and realized... I had uploaded the WRONG one. It was a previous update's driver. SO... hopefully NOW with THIS link all should be in order.

{Link Re-directed To Top of Page}]

(I'm just hoping neither of you haven't gone on any rapid uninstalls of other programs to get it working)
Dernière modification de NUK3 TH3 WHAL35; 18 janv. 2016 à 14h55
Thanks
jdenm8 19 déc. 2015 à 10h05 
Working a treat now, rumbles like it does on the cable.

I hadn't tried uninstalling anything else at that point. The only software I could possibly conceive of interfering was the Scarletsoft DS4 stack used for Wii U Pro Controller interfacing. Glad to know it was just a mix-up. Thanks for updating this excellent driver!

EDIT: I think I may have a theory about why sending the signal to the Adapter's PID didn't work. The Adapter (supposedly) supports up to four simultaneously connected wireless controllers. If it receives the Rumble directly, it likely discards it as erroneous rather than forwarding it to any connected controllers.
Dernière modification de jdenm8; 19 déc. 2015 à 10h07
< >
Affichage des commentaires 91 à 105 sur 152
Par page : 1530 50

Posté le 23 janv. 2015 à 15h59
Messages : 152