InputMapper - Now supporting more devices and plugins.

[viestursm]

Hello,

I used DS4Windows to make my DS4 work on Windows via Bootcamp on a Mac. It worked fine but now it doesn't pair with Mac OS properly. When I connect it via USB, the orange light on the back of the controller pulses once and then goes off, the controller then seems to work on Steam (Big Picture mode). When I try pairing it via Bluetooth, the blue light blinks a couple of time and then goes off - I can see that it establishes a connection but loses it in less than a second. Normally, the orange light would stay on and I never had any issues with connecting via Bluetooth.

Could DS4Windows have caused this or is it something else? The reset button underneath the controller doesn't seem to help this.

Thanks.

[Halabec]

The big/small motors are swapped in DS4Windows so in some games there will be alot more rumble then there should be.

I'm talking about the "Rumble" slider setting in the DS4Windows controller profile, which I have set all the way to the left. When I first set up everything last weekend with that setting, rumble was disabled in games such as Ryse

Now, however, that setting seems to be ignored and rumble is active.

[jhebbel]

I'm talking about the "Rumble" slider setting in the DS4Windows controller profile, which I have set all the way to the left. When I first set up everything last weekend with that setting, rumble was disabled in games such as Ryse

Now, however, that setting seems to be ignored and rumble is active.

Will be fixed next version

[Star]

btw I found out how to reproduce this exception:

Code:

A first chance exception of type 'System.IO.IOException' occurred in mscorlib.dll

just changing the "fully charged mode" under lightbar settings around causes it a lot. I know this isn't the error causing the prior crashes though but thought I might point that out.

btw thanks for the crash fix with the new DS4Library.dll, the exception catch for the power octet being out of bounds definitely stops the crashing. haven't had too much time to test it while gaming to see if there's any other anomalies yet though.

[jhebbel]

btw I found out how to reproduce this exception:

Code:

A first chance exception of type 'System.IO.IOException' occurred in mscorlib.dll

just changing the "fully charged mode" under lightbar settings around causes it a lot. I know this isn't the error causing the prior crashes though but thought I might point that out.

btw thanks for the crash fix with the new DS4Library.dll, the exception catch for the power octet being out of bounds definitely stops the crashing. haven't had too much time to test it while gaming to see if there's any other anomalies yet though.

Thats the profile save / load retrying when the file is in use, should not be an issue due to the fact it retries the file up to 10 times and and I haven't seen it go that far before.

[NoGlue]

hi there

up till now i used the ScpServer form scarlet.crush ( http://forums.pcsx2.net/Thread-XInput-Wr...t=touchpad ) but then someone told me about this. Being able to use the Touchpad and still be able to use the bluetooth dongle for othere devices is great, but i have a problem.

Setting it up for the first time everything works great. Adding the device ( share +ps button , bluetooth settings -> add device ... ) ) works fine and i can use the Controller. But the next time i wanna play an press the PS-Button it connects and instantly looses the connection again. So i have to pair it everytime to use it. Did omeone experienc the same problem and does have a workaround ? ( windows 7 64 bit , Bluetooth Dongle : CSR8510 A10)

[jhebbel]

hi there

up till now i used the ScpServer form scarlet.crush ( http://forums.pcsx2.net/Thread-XInput-Wr...t=touchpad ) but then someone told me about this. Being able to use the Touchpad and still be able to use the bluetooth dongle for othere devices is great, but i have a problem.

Setting it up for the first time everything works great. Adding the device ( share +ps button , bluetooth settings -> add device ... ) ) works fine and i can use the Controller. But the next time i wanna play an press the PS-Button it connects and instantly looses the connection again. So i have to pair it everytime to use it. Did omeone experienc the same problem and does have a workaround ? ( windows 7 64 bit , Bluetooth Dongle : CSR8510 A10)

There were a couple good tutorials for this posted just a page or two ago, one was a video and the other is also linked in the OP under the help.

[TheManOfSteel]

yea 0x63 is not a valid power octet either, that has to be the cause of the issues are the bad reports

I replaced the library.dll and left the controller running overnight at 100% charge idle, and it was successful for approx 7 hours with no problems. This appears to have fixed the problem. I will report back if issues arise again. Thank you for the help, much appreciated.

[vlcsf]

I recently switched to Windows 8 and started running to issues with DS4Windows. It was working fine when I was on Windows 7. The issue is the controller is connected to bluetooth but DS4Windows won't recognize it. If I unpair and pair it, DS4Windows will then recognize it. However, if I disconnect the controller DS4Windows won't recognize the controller. Using microUSB works, but when I remove the usb cable DS4Windows has the same issue.


10/20/2014 8:27:04 AM> TRACE: Active application changed to C:\Windows\explorer.exe
10/20/2014 8:27:07 AM> TRACE: Active application changed to C:\Windows\explorer.exe
10/20/2014 8:27:07 AM> TRACE: Active application changed to C:\Windows\explorer.exe
10/20/2014 8:27:07 AM> TRACE: Active application changed to C:\Windows\explorer.exe
10/20/2014 8:27:08 AM> TRACE: Active application changed to C:\Windows\explorer.exe
10/20/2014 8:27:08 AM> TRACE: Active application changed to C:\Program Files (x86)\DSDCS\DS4Windows\DS4Windows.exe
10/20/2014 8:27:08 AM> INFO: Starting...
10/20/2014 8:27:08 AM> INFO: Searching for controllers....
10/20/2014 8:27:08 AM> INFO: Using Exclusive Mode
10/20/2014 8:27:13 AM> TRACE: Active application changed to C:\Windows\ImmersiveControlPanel\SystemSettings.exe
10/20/2014 8:27:13 AM> TRACE: Active application changed to C:\Windows\explorer.exe
10/20/2014 8:27:30 AM> TRACE: Active application changed to C:\Windows\explorer.exe
10/20/2014 8:27:30 AM> TRACE: Active application changed to C:\Windows\explorer.exe
10/20/2014 8:27:30 AM> TRACE: Active application changed to C:\Windows\explorer.exe
10/20/2014 8:27:36 AM> TRACE: Device connected 525816|32768|13622272
10/20/2014 8:27:37 AM> TRACE: 84:17:66:88:52:87 device start
10/20/2014 8:27:38 AM> WARNING: 84:17:66:88:52:87 encountered synchronous write failure attempt (1/5): 170
10/20/2014 8:27:39 AM> WARNING: 84:17:66:88:52:87 encountered synchronous write failure attempt (2/5): 170
10/20/2014 8:27:40 AM> WARNING: 84:17:66:88:52:87 encountered synchronous write failure attempt (3/5): 170
10/20/2014 8:27:41 AM> WARNING: 84:17:66:88:52:87 encountered synchronous write failure attempt (4/5): 170
10/20/2014 8:27:42 AM> WARNING: 84:17:66:88:52:87 encountered synchronous write failure attempt (5/5): 170
10/20/2014 8:27:43 AM> WARNING: 84:17:66:88:52:87 encountered synchronous write failure attempt (6/5): 170
10/20/2014 8:27:44 AM> TRACE: StopOutputUpdate called, requesting gracefull disconnect.
10/20/2014 8:27:44 AM> TRACE: Close device filestream
10/20/2014 8:27:44 AM> TRACE: Close device handle
10/20/2014 8:27:44 AM> TRACE: IO closed
10/20/2014 8:27:44 AM> TRACE: Active application changed to C:\Program Files\ASUS\Bluetooth Software\BTTray.exe
10/20/2014 8:27:49 AM> TRACE: Active application changed to C:\Windows\explorer.exe
10/20/2014 8:27:51 AM> TRACE: Active application changed to C:\Windows\explorer.exe
10/20/2014 8:27:57 AM> TRACE: Active application changed to C:\Windows\explorer.exe
10/20/2014 8:28:00 AM> TRACE: Active application changed to C:\Program Files (x86)\DSDCS\DS4Windows\DS4Windows.exe
10/20/2014 8:28:00 AM> TRACE: Active application changed to C:\Windows\explorer.exe
10/20/2014 8:28:07 AM> TRACE: Active application changed to C:\Windows\explorer.exe
10/20/2014 8:28:14 AM> TRACE: Active application changed to C:\Windows\explorer.exe
10/20/2014 8:28:14 AM> TRACE: Active application changed to C:\Windows\explorer.exe
10/20/2014 8:28:29 AM> TRACE: Active application changed to C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
10/20/2014 8:29:41 AM> TRACE: Device connected 525816|32768|13622368
10/20/2014 8:29:42 AM> TRACE: 84:17:66:88:52:87 device start
10/20/2014 8:29:43 AM> WARNING: 84:17:66:88:52:87 encountered synchronous write failure attempt (1/5): 170
10/20/2014 8:29:44 AM> WARNING: 84:17:66:88:52:87 encountered synchronous write failure attempt (2/5): 170
10/20/2014 8:29:45 AM> WARNING: 84:17:66:88:52:87 encountered synchronous write failure attempt (3/5): 170
10/20/2014 8:29:46 AM> WARNING: 84:17:66:88:52:87 encountered synchronous write failure attempt (4/5): 170
10/20/2014 8:29:47 AM> WARNING: 84:17:66:88:52:87 encountered synchronous write failure attempt (5/5): 170
10/20/2014 8:29:48 AM> WARNING: 84:17:66:88:52:87 encountered synchronous write failure attempt (6/5): 170
10/20/2014 8:29:49 AM> TRACE: StopOutputUpdate called, requesting gracefull disconnect.
10/20/2014 8:29:49 AM> TRACE: Close device filestream
10/20/2014 8:29:49 AM> TRACE: Close device handle
10/20/2014 8:29:49 AM> TRACE: IO closed
10/20/2014 8:29:49 AM> TRACE: 84:17:66:88:52:87 device start
10/20/2014 8:29:50 AM> INFO: Found Controller: 84:17:66:88:52:87 (USB)
10/20/2014 8:29:50 AM> INFO: Controller 1 is using Profile "Profile 1"
10/20/2014 8:29:50 AM> TRACE: Device connected 525816|32768|13622352
10/20/2014 8:29:50 AM> TRACE: 84:17:66:88:52:87 power subsystem octet: 0x1b
10/20/2014 8:29:53 AM> WARNING: 84:17:66:88:52:87 encountered read failure attempt (1/5): 1167
10/20/2014 8:29:53 AM> TRACE: Device removed 525816|32772|13622368
10/20/2014 8:29:54 AM> WARNING: 84:17:66:88:52:87 encountered read failure attempt (2/5): 1167
10/20/2014 8:29:55 AM> WARNING: 84:17:66:88:52:87 encountered read failure attempt (3/5): 1167
10/20/2014 8:29:56 AM> WARNING: 84:17:66:88:52:87 encountered read failure attempt (4/5): 1167
10/20/2014 8:29:57 AM> WARNING: 84:17:66:88:52:87 encountered read failure attempt (5/5): 1167
10/20/2014 8:29:58 AM> ERROR: 84:17:66:88:52:87 disconnect due to read failure: 1167
10/20/2014 8:29:58 AM> TRACE: StopOutputUpdate called, requesting gracefull disconnect.
10/20/2014 8:29:58 AM> TRACE: Close device filestream
10/20/2014 8:29:58 AM> TRACE: Close device handle
10/20/2014 8:29:58 AM> TRACE: IO closed
10/20/2014 8:29:58 AM> INFO: Controller 84:17:66:88:52:87 was removed or lost connection
10/20/2014 8:29:58 AM> TRACE: Device removed 525816|32772|13622352
10/20/2014 8:30:06 AM> TRACE: Device connected 525816|32768|13622368
10/20/2014 8:30:07 AM> TRACE: 84:17:66:88:52:87 device start
10/20/2014 8:30:08 AM> INFO: Found Controller: 84:17:66:88:52:87 (USB)
10/20/2014 8:30:08 AM> INFO: Controller 1 is using Profile "Profile 1"
10/20/2014 8:30:08 AM> TRACE: 84:17:66:88:52:87 power subsystem octet: 0x1b
10/20/2014 8:30:08 AM> TRACE: Device connected 525816|32768|13622352
10/20/2014 8:30:22 AM> TRACE: Active application changed to C:\Program Files (x86)\DSDCS\DS4Windows\DS4Windows.exe
10/20/2014 8:30:30 AM> WARNING: 84:17:66:88:52:87 encountered read failure attempt (1/5): 1167
10/20/2014 8:30:30 AM> TRACE: Device removed 525816|32772|13622368
10/20/2014 8:30:31 AM> WARNING: 84:17:66:88:52:87 encountered read failure attempt (2/5): 1167
10/20/2014 8:30:32 AM> WARNING: 84:17:66:88:52:87 encountered read failure attempt (3/5): 1167
10/20/2014 8:30:33 AM> WARNING: 84:17:66:88:52:87 encountered read failure attempt (4/5): 1167
10/20/2014 8:30:34 AM> WARNING: 84:17:66:88:52:87 encountered read failure attempt (5/5): 1167
10/20/2014 8:30:35 AM> TRACE: Active application changed to C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
10/20/2014 8:30:35 AM> ERROR: 84:17:66:88:52:87 disconnect due to read failure: 1167
10/20/2014 8:30:35 AM> TRACE: StopOutputUpdate called, requesting gracefull disconnect.
10/20/2014 8:30:35 AM> TRACE: Close device filestream
10/20/2014 8:30:35 AM> TRACE: Close device handle
10/20/2014 8:30:35 AM> TRACE: IO closed
10/20/2014 8:30:35 AM> INFO: Controller 84:17:66:88:52:87 was removed or lost connection
10/20/2014 8:30:35 AM> TRACE: Device removed 525816|32772|13622352
10/20/2014 8:30:36 AM> TRACE: Active application changed to C:\Program Files (x86)\DSDCS\DS4Windows\DS4Windows.exe
10/20/2014 8:30:38 AM> TRACE: Active application changed to C:\Windows\ImmersiveControlPanel\SystemSettings.exe
10/20/2014 8:30:43 AM> TRACE: Active application changed to C:\Windows\explorer.exe
10/20/2014 8:30:43 AM> TRACE: Active application changed to C:\Windows\explorer.exe
10/20/2014 8:30:43 AM> TRACE: Active application changed to C:\Program Files (x86)\DSDCS\DS4Windows\DS4Windows.exe
10/20/2014 8:30:49 AM> TRACE: Active application changed to C:\Windows\SysWOW64\rundll32.exe
10/20/2014 8:30:51 AM> TRACE: Active application changed to C:\Windows\SysWOW64\rundll32.exe
10/20/2014 8:30:51 AM> TRACE: Active application changed to C:\Program Files (x86)\DSDCS\DS4Windows\DS4Windows.exe
10/20/2014 8:30:56 AM> TRACE: Saving
10/20/2014 8:30:57 AM> TRACE: Saving
10/20/2014 8:31:01 AM> TRACE: Active application changed to C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
10/20/2014 8:31:09 AM> TRACE: Active application changed to C:\Program Files (x86)\DSDCS\DS4Windows\DS4Windows.exe
10/20/2014 8:31:15 AM> TRACE: Active application changed to C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
10/20/2014 8:34:45 AM> TRACE: Active application changed to C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
10/20/2014 8:34:45 AM> TRACE: Active application changed to C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
10/20/2014 8:35:50 AM> TRACE: Active application changed to C:\Program Files (x86)\DSDCS\DS4Windows\DS4Windows.exe
10/20/2014 8:35:52 AM> TRACE: Active application changed to C:\Program Files (x86)\DSDCS\DS4Windows\DS4Windows.exe
10/20/2014 8:36:02 AM> TRACE: Active application changed to C:\Program Files (x86)\DSDCS\DS4Windows\DS4Windows.exe
10/20/2014 8:36:04 AM> TRACE: Active application changed to C:\Program Files (x86)\DSDCS\DS4Windows\DS4Windows.exe

[jhebbel]

I recently switched to Windows 8 and started running to issues with DS4Windows. It was working fine when I was on Windows 7. The issue is the controller is connected to bluetooth but DS4Windows won't recognize it. If I unpair and pair it, DS4Windows will then recognize it. However, if I disconnect the controller DS4Windows won't recognize the controller. Using microUSB works, but when I remove the usb cable DS4Windows has the same issue.

What BT dongle are you using?