InputMapper - Now supporting more devices and plugins.

[Aniki]

well it does as any other BT dongle (3 of them) i had connected in the past it was reconized as Generic Bluetooth Radio.
This one was recognized as BCM20702A0...yet it doesn't find any drivers for it

I have a Bluetooth dongle with the same model no. (although its not the same brand). To get the drivers installed, the manufacturer recommended installing this Bluetooth software:
http://www.broadcom.com/support/bluetooth/update.php
After it was finished installing, I simply rebooted, then uninstalled the Widcomm Bluetooth software from my programs (because it overrides the Windows Bluetooth stack which messes with DS4Windows use), then rebooted again and boom, drivers installed and everything working. Also, try putting your dongle on a usb extension cord away from you computer and other electronics and it should help with latency issues.

[jhebbel]

Hi guys,
Today I noticed that process 'steam.exe' at Task Manager permanently loads one CPU core, but Steam is not running. I checked path of executable of this process and it was 'C:\Users\<my_username>\AppData\Roaming\DS4Windows\Reversed\steam.exe'.
Fast inspection of folder contents showed it was a bitcoin miner.
Virustotal confirmed this: https://www.virustotal.com/en/file/16724.../analysis/


Please check your AppData\Roaming\DS4Windows\Reversed folder for steam.exe and delete or rename it.
Kaspersky Antivirus (which i'm using on my machine) Lab confirmed it is a malware, it signature will be added to the next signature update.

UPD: I lurked for similiar cases, perhaps it's a some virus which uses random folder to place miner in it and mine was folder of DS4Windows appdata.

Yea, there is no steam.exe as part of this program, probably tried to hide it in other programs folders so it wouldn't be detectable, the name itself is probably random as well. Lucky i'm clean, but if you happen to find the root source let us know.

[::::::]

Hi,
So I used to connect the controller with bluetooth fine. But now the laptop cannot detect my controller anymore. The controller is in pairing mode and I've tried both Microsoft driver and Qualcomm driver but none of them worked. Is it a hardware problem? What should I do?

[apoklyps3]

so i have used a different usb port (i think it's USB3.0, can't really see in the back of my pc) using a usb prolongator (i think it has 3meters, but i only extended it about 1,5m from the computer) and i no longer get latency. now I see something else in the log:

Code:

12/17/2014 6:10:43 AM> INFO: Starting...
12/17/2014 6:10:43 AM> INFO: Searching for controllers....
12/17/2014 6:10:43 AM> INFO: Using Exclusive Mode
12/17/2014 6:10:43 AM> TRACE: 84:17:66:F2:E9:A3 device start
12/17/2014 6:10:44 AM> WARNING: 84:17:66:F2:E9:A3 encountered synchronous write failure attempt (1/5): 995
12/17/2014 6:10:45 AM> WARNING: 84:17:66:F2:E9:A3 encountered synchronous write failure attempt (2/5): 1167
12/17/2014 6:10:46 AM> WARNING: 84:17:66:F2:E9:A3 encountered synchronous write failure attempt (3/5): 1167
12/17/2014 6:10:47 AM> WARNING: 84:17:66:F2:E9:A3 encountered synchronous write failure attempt (4/5): 1167
12/17/2014 6:10:48 AM> WARNING: 84:17:66:F2:E9:A3 encountered synchronous write failure attempt (5/5): 1167
12/17/2014 6:10:49 AM> WARNING: 84:17:66:F2:E9:A3 encountered synchronous write failure attempt (6/5): 1167
12/17/2014 6:10:50 AM> TRACE: StopOutputUpdate called, requesting gracefull disconnect.
12/17/2014 6:10:50 AM> TRACE: Close device filestream
12/17/2014 6:10:50 AM> TRACE: Close device handle
12/17/2014 6:10:50 AM> TRACE: IO closed
12/17/2014 6:10:51 AM> TRACE: 84:17:66:F2:E9:A3 device start
12/17/2014 6:10:52 AM> INFO: Found Controller: 84:17:66:F2:E9:A3 (BT)
12/17/2014 6:10:52 AM> INFO: Controller 1 is using Profile "pes" in exclusive mode.
12/17/2014 6:10:52 AM> TRACE: Device removed 66764|32772|1952624
12/17/2014 6:10:52 AM> TRACE: 84:17:66:F2:E9:A3 power subsystem octet: 0x08
12/17/2014 6:10:52 AM> TRACE: Device connected 66764|32768|1952624
12/17/2014 6:10:53 AM> TRACE: Device connected 66764|32768|1956528
12/17/2014 6:10:54 AM> TRACE: Active application changed to C:\Program Files (x86)\DSDCS\DS4Windows\DS4Windows.exe
12/17/2014 6:10:54 AM> TRACE: Active application changed to C:\Windows\explorer.exe
12/17/2014 6:10:56 AM> TRACE: Active application changed to C:\Program Files (x86)\DSDCS\DS4Windows\DS4Windows.exe
12/17/2014 6:10:58 AM> TRACE: Active application changed to C:\Windows\explorer.exe
12/17/2014 6:11:00 AM> TRACE: Active application changed to C:\Windows\explorer.exe
12/17/2014 6:11:03 AM> TRACE: Active application changed to C:\Windows\explorer.exe
12/17/2014 6:11:03 AM> TRACE: Active application changed to C:\Users\Vali\AppData\Roaming\uTorrent\uTorrent.exe
12/17/2014 6:11:03 AM> TRACE: Active application changed to C:\Windows\explorer.exe
12/17/2014 6:11:05 AM> TRACE: Active application changed to C:\Windows\explorer.exe
12/17/2014 6:11:07 AM> TRACE: Active application changed to C:\Games\Steam\Steam.exe
12/17/2014 6:11:08 AM> TRACE: Active application changed to C:\Windows\explorer.exe
12/17/2014 6:11:11 AM> TRACE: Active application changed to C:\Games\Steam\Steam.exe
12/17/2014 6:11:11 AM> TRACE: Active application changed to C:\Games\Steam\Steam.exe
12/17/2014 6:11:12 AM> TRACE: Active application changed to C:\Games\Steam\Steam.exe
12/17/2014 6:11:14 AM> TRACE: Active application changed to C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
12/17/2014 6:11:15 AM> TRACE: Active application changed to C:\Games\Steam\SteamApps\common\Pro Evolution Soccer 2015\PES2015.exe
12/17/2014 6:12:29 AM> TRACE: 84:17:66:F2:E9:A3 power subsystem octet: 0x07
12/17/2014 7:00:21 AM> TRACE: Active application changed to C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
12/17/2014 7:00:24 AM> TRACE: Active application changed to C:\Games\Steam\Steam.exe
12/17/2014 7:00:24 AM> TRACE: Active application changed to C:\Games\Steam\Steam.exe
12/17/2014 7:00:24 AM> TRACE: User disconnect requested.
12/17/2014 7:00:24 AM> TRACE: Trying to disconnect BT device 84:17:66:F2:E9:A3
12/17/2014 7:00:24 AM> TRACE: Close device filestream
12/17/2014 7:00:24 AM> TRACE: Close device handle
12/17/2014 7:00:24 AM> TRACE: IO closed
12/17/2014 7:00:24 AM> TRACE: Device closed
12/17/2014 7:00:24 AM> TRACE: Devices closed
12/17/2014 7:00:24 AM> INFO: Disconnect successful: True
12/17/2014 7:00:24 AM> TRACE: StopOutputUpdate called, requesting gracefull disconnect.
12/17/2014 7:00:24 AM> INFO: Controller 84:17:66:F2:E9:A3 was removed or lost connection

[abroadb1]

Having issues assigning the right analog stick to mouse movement. Specifically trying to allow the right stick control point of view movement as you would with the mouse. It continuously slides in random directions, associated with my last movement of the analog stick. I have tried two controllers and they have the same issue, all associated with the assignment of the analog stick to mouse movement. Any tips? Something I need to reassign?

[jhebbel]

Hi,
So I used to connect the controller with bluetooth fine. But now the laptop cannot detect my controller anymore. The controller is in pairing mode and I've tried both Microsoft driver and Qualcomm driver but none of them worked. Is it a hardware problem? What should I do?

I've seen this before and the easiest solution has been to uninstall the controller drivers, bt drivers and reset the controller (reset pin), and do it fresh. I haven't the slightest idea what causes these BT issues

so i have used a different usb port (i think it's USB3.0, can't really see in the back of my pc) using a usb prolongator (i think it has 3meters, but i only extended it about 1,5m from the computer) and i no longer get latency. now I see something else in the log:

Code:

12/17/2014 6:10:43 AM> INFO: Starting...
12/17/2014 6:10:43 AM> INFO: Searching for controllers....
12/17/2014 6:10:43 AM> INFO: Using Exclusive Mode
12/17/2014 6:10:43 AM> TRACE: 84:17:66:F2:E9:A3 device start
12/17/2014 6:10:44 AM> WARNING: 84:17:66:F2:E9:A3 encountered synchronous write failure attempt (1/5): 995
12/17/2014 6:10:45 AM> WARNING: 84:17:66:F2:E9:A3 encountered synchronous write failure attempt (2/5): 1167
12/17/2014 6:10:46 AM> WARNING: 84:17:66:F2:E9:A3 encountered synchronous write failure attempt (3/5): 1167
12/17/2014 6:10:47 AM> WARNING: 84:17:66:F2:E9:A3 encountered synchronous write failure attempt (4/5): 1167
12/17/2014 6:10:48 AM> WARNING: 84:17:66:F2:E9:A3 encountered synchronous write failure attempt (5/5): 1167
12/17/2014 6:10:49 AM> WARNING: 84:17:66:F2:E9:A3 encountered synchronous write failure attempt (6/5): 1167
12/17/2014 6:10:50 AM> TRACE: StopOutputUpdate called, requesting gracefull disconnect.
12/17/2014 6:10:50 AM> TRACE: Close device filestream
12/17/2014 6:10:50 AM> TRACE: Close device handle
12/17/2014 6:10:50 AM> TRACE: IO closed
12/17/2014 6:10:51 AM> TRACE: 84:17:66:F2:E9:A3 device start
12/17/2014 6:10:52 AM> INFO: Found Controller: 84:17:66:F2:E9:A3 (BT)
12/17/2014 6:10:52 AM> INFO: Controller 1 is using Profile "pes" in exclusive mode.
12/17/2014 6:10:52 AM> TRACE: Device removed 66764|32772|1952624
12/17/2014 6:10:52 AM> TRACE: 84:17:66:F2:E9:A3 power subsystem octet: 0x08
12/17/2014 6:10:52 AM> TRACE: Device connected 66764|32768|1952624
12/17/2014 6:10:53 AM> TRACE: Device connected 66764|32768|1956528
12/17/2014 6:10:54 AM> TRACE: Active application changed to C:\Program Files (x86)\DSDCS\DS4Windows\DS4Windows.exe
12/17/2014 6:10:54 AM> TRACE: Active application changed to C:\Windows\explorer.exe
12/17/2014 6:10:56 AM> TRACE: Active application changed to C:\Program Files (x86)\DSDCS\DS4Windows\DS4Windows.exe
12/17/2014 6:10:58 AM> TRACE: Active application changed to C:\Windows\explorer.exe
12/17/2014 6:11:00 AM> TRACE: Active application changed to C:\Windows\explorer.exe
12/17/2014 6:11:03 AM> TRACE: Active application changed to C:\Windows\explorer.exe
12/17/2014 6:11:03 AM> TRACE: Active application changed to C:\Users\Vali\AppData\Roaming\uTorrent\uTorrent.exe
12/17/2014 6:11:03 AM> TRACE: Active application changed to C:\Windows\explorer.exe
12/17/2014 6:11:05 AM> TRACE: Active application changed to C:\Windows\explorer.exe
12/17/2014 6:11:07 AM> TRACE: Active application changed to C:\Games\Steam\Steam.exe
12/17/2014 6:11:08 AM> TRACE: Active application changed to C:\Windows\explorer.exe
12/17/2014 6:11:11 AM> TRACE: Active application changed to C:\Games\Steam\Steam.exe
12/17/2014 6:11:11 AM> TRACE: Active application changed to C:\Games\Steam\Steam.exe
12/17/2014 6:11:12 AM> TRACE: Active application changed to C:\Games\Steam\Steam.exe
12/17/2014 6:11:14 AM> TRACE: Active application changed to C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
12/17/2014 6:11:15 AM> TRACE: Active application changed to C:\Games\Steam\SteamApps\common\Pro Evolution Soccer 2015\PES2015.exe
12/17/2014 6:12:29 AM> TRACE: 84:17:66:F2:E9:A3 power subsystem octet: 0x07
12/17/2014 7:00:21 AM> TRACE: Active application changed to C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
12/17/2014 7:00:24 AM> TRACE: Active application changed to C:\Games\Steam\Steam.exe
12/17/2014 7:00:24 AM> TRACE: Active application changed to C:\Games\Steam\Steam.exe
12/17/2014 7:00:24 AM> TRACE: User disconnect requested.
12/17/2014 7:00:24 AM> TRACE: Trying to disconnect BT device 84:17:66:F2:E9:A3
12/17/2014 7:00:24 AM> TRACE: Close device filestream
12/17/2014 7:00:24 AM> TRACE: Close device handle
12/17/2014 7:00:24 AM> TRACE: IO closed
12/17/2014 7:00:24 AM> TRACE: Device closed
12/17/2014 7:00:24 AM> TRACE: Devices closed
12/17/2014 7:00:24 AM> INFO: Disconnect successful: True
12/17/2014 7:00:24 AM> TRACE: StopOutputUpdate called, requesting gracefull disconnect.
12/17/2014 7:00:24 AM> INFO: Controller 84:17:66:F2:E9:A3 was removed or lost connection

If your talking about the errors at the beginning it just looks like its trying to recover from a previous connection, looks like the controller worked after that, is this true?

Having issues assigning the right analog stick to mouse movement. Specifically trying to allow the right stick control point of view movement as you would with the mouse. It continuously slides in random directions, associated with my last movement of the analog stick. I have tried two controllers and they have the same issue, all associated with the assignment of the analog stick to mouse movement. Any tips? Something I need to reassign?

Add a tad of deadzone to the stick, the DS4s sticks do not mechanically center very well.

[apoklyps3]

yeah, i'm talking about "encountered synchronous write failure attempt".
what does it mean? recovery from a previus connection? It seems to apear in the log when i first power on the controller. will check to be sure.
yeah. it works. will do some more tests when I get the chance (direct USB connection).
maybe there is something wrong with shielding of the case after all , will see.
never noticed problems before with DS3.
I know this is not the thread to ask, but I'm wondering if DS4 & DS3 coexistence on system is likely (same BT dongle if possible, if not it's still good)

[jhebbel]

yeah, i'm talking about "encountered synchronous write failure attempt".
what does it mean? recovery from a previus connection? It seems to apear in the log when i first power on the controller. will check to be sure.
yeah. it works. will do some more tests when I get the chance (direct USB connection).
maybe there is something wrong with shielding of the case after all , will see.
never noticed problems before with DS3.
I know this is not the thread to ask, but I'm wondering if DS4 & DS3 coexistence on system is likely (same BT dongle if possible, if not it's still good)

Thats what im talking about too, its just trying to reestablish connection with controller that was disconnected on previous execution, its fine. DS3 wouldent have these issues because the bandwith requirements of the device are much much lower. Right now there is no way to have both ds3 and ds4 wireless as current ds3 tools replace the BT drivers

[apoklyps3]

ohhh...so it replaces them from all dongles connected?
wouldn't be a way , for example, to have one BT dongle for DS4 with generic drivers and another BT dongle for DS4 with replaced drivers?

[jhebbel]

ohhh...so it replaces them from all dongles connected?
wouldn't be a way , for example, to have one BT dongle for DS4 with generic drivers and another BT dongle for DS4 with replaced drivers?

I do believe it does a blanked replacement of the generic drivers making it useless to DS4s or any other device for that matter, but even if you could get 2 working The crosstalk and interference wouldn't make it a very viable solution,