Installer Steam
connexion
|
langue
简体中文 (chinois simplifié)
繁體中文 (chinois traditionnel)
日本語 (japonais)
한국어 (coréen)
ไทย (thaï)
Български (bulgare)
Čeština (tchèque)
Dansk (danois)
Deutsch (allemand)
English (anglais)
Español - España (espagnol castillan)
Español - Latinoamérica (espagnol d'Amérique latine)
Ελληνικά (grec)
Italiano (italien)
Bahasa Indonesia (indonésien)
Magyar (hongrois)
Nederlands (néerlandais)
Norsk (norvégien)
Polski (polonais)
Português (portugais du Portugal)
Português - Brasil (portugais du Brésil)
Română (roumain)
Русский (russe)
Suomi (finnois)
Svenska (suédois)
Türkçe (turc)
Tiếng Việt (vietnamien)
Українська (ukrainien)
Signaler un problème de traduction
Wheres the post in this thread containing this info? We didn't know about this. So whats your point with "late to the party"
http://steamcommunity.com/discussions/forum/1/490123938430246727/
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}
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.
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
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.
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.
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)
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.