Posts: 1.733
Threads: 2
Joined: May 2014
Reputation:
26
Location: Florida, USA
(08-24-2014, 05:06 AM)Xaero Wrote: Interesting, I did some investigating - my motherboard's Bluetooth module is exactly 2.1+ EDR. Unfortunately it uses the Toshiba Bluetooth stack (which I hadn't installed, hence it reporting basic functionality) which isn't working with DS4Windows; Supposedly one user had a working DS4Tool for this module, so I'm going to ask him and see if we can't figure out a way to add support for the Toshiba stack. In the meantime I've ordered a generic 4.0 BLE+EDR module for a fallback.
I can provide logs if you want to try and add support as well.
(08-24-2014, 05:16 AM)Xaero Wrote: Even more interesting!
The original DS4tool (attached as DS4tool.zip on the original DS4tool thread) DOES work with this adapter just fine. So some functionality added after the fact broke the support.
I had a stacktrace of the error (Index out of bounds of the array) from one of the various DS4tools out there, I'm trying to hunt down which one provided verbose output, yours simply reports an unsupported bluetooth stack (which given that the original application worked I'd wager thats a maybe)
In the mean time, I've reverted to the Microsoft stack, which is acceptable for most use aside from the occasional latency issues.
Ive yet to hear anybody getting the Toshiba stack to work for the simple fact that the Toshiba stack does not use MAC addresses for connected HID devices, something that is a MUST for us, and it is this exact lack of MAC that throws the Index out of bounds error, in our case we plain englished the error to read Unsupported BT stack or driver, but they mean the same exact thing. The only other thing I can think of is that you are getting high levels of interference causing the latency (BT operates on the same band as WiFi and many other wireless protocols). The other reason I tended to lean to it being the device being incompatible is that in the log you sent, one thing it includes is the PID of the BT dongle, upon referencing it this is what I found: http://www.modem-help.co.uk/Broadcom/chi...2-USB.html Could be a typo though
Sponsored links
Posts: 19
Threads: 0
Joined: Aug 2014
Reputation:
0
08-24-2014, 01:40 PM
(This post was last modified: 08-24-2014, 01:45 PM by sinlot.)
(08-23-2014, 11:05 PM)jhebbel Wrote: Looks like something is keeping the controllers drivers from installing. Does the controller show up in device manager when you turn it on?
The controller only shows yellow light device manager doesn't show up
Posts: 1.733
Threads: 2
Joined: May 2014
Reputation:
26
Location: Florida, USA
(08-24-2014, 01:40 PM)sinlot Wrote: The controller only shows yellow light device manager doesn't show up
Have you use any other tool or installed SCP Virtual bus drivers on your own at any point?
Posts: 19
Threads: 0
Joined: Aug 2014
Reputation:
0
(08-24-2014, 01:45 PM)jhebbel Wrote: Have you use any other tool or installed SCP Virtual bus drivers on your own at any point?
yes i tried previous ds4 tools before
Posts: 1.733
Threads: 2
Joined: May 2014
Reputation:
26
Location: Florida, USA
(08-24-2014, 01:50 PM)sinlot Wrote: yes i tried previous ds4 tools before
Could be some lingering remanence of them; i'm seeing 3 instances of SCP drivers for your 1 plugged in controller, could be an issue.
Code: Realtek Bluetooth 4.0 + High Speed Chip
Availability =
ClassGuid = {e0cbf06c-cd8b-4647-bb8a-263b43f0f974}
CompatibleID = System.String[]
ConfigManagerErrorCode = 0
ConfigManagerUserConfig = False
CreationClassName = Win32_PnPEntity
Description = Realtek Bluetooth 4.0 + High Speed Chip
DeviceID = USB\VID_0BDA&PID_B728\00E04C000001
ErrorCleared =
ErrorDescription =
HardwareID = System.String[]
InstallDate =
LastErrorCode =
Manufacturer = Realtek Semiconductor Corp.
Name = Realtek Bluetooth 4.0 + High Speed Chip
PNPDeviceID = USB\VID_0BDA&PID_B728\00E04C000001
PowerManagementCapabilities =
PowerManagementSupported =
Service = BTHUSB
Status = OK
StatusInfo =
SystemCreationClassName = Win32_ComputerSystem
SystemName = 7USSAIN-PC
Wireless Controller
Availability =
ClassGuid = {88bae032-5a81-49f0-bc3d-a4ff138216d6}
CompatibleID = System.String[]
ConfigManagerErrorCode = 0
ConfigManagerUserConfig = False
CreationClassName = Win32_PnPEntity
Description = Wireless Controller
DeviceID = USB\VID_054C&PID_05C4\6&1D7E6C28&0&1
ErrorCleared =
ErrorDescription =
HardwareID = System.String[]
InstallDate =
LastErrorCode =
Manufacturer = Sony Corp.
Name = Wireless Controller
PNPDeviceID = USB\VID_054C&PID_05C4\6&1D7E6C28&0&1
PowerManagementCapabilities =
PowerManagementSupported =
Service = WinUSB
Status = OK
StatusInfo =
SystemCreationClassName = Win32_ComputerSystem
SystemName = 7USSAIN-PC
Scp Virtual Bus Driver
Availability =
ClassGuid = {4d36e97d-e325-11ce-bfc1-08002be10318}
CompatibleID =
ConfigManagerErrorCode = 0
ConfigManagerUserConfig = False
CreationClassName = Win32_PnPEntity
Description = Scp Virtual Bus Driver
DeviceID = ROOT\SYSTEM\0002
ErrorCleared =
ErrorDescription =
HardwareID = System.String[]
InstallDate =
LastErrorCode =
Manufacturer = Scarlet.Crush Productions
Name = Scp Virtual Bus Driver
PNPDeviceID = ROOT\SYSTEM\0002
PowerManagementCapabilities =
PowerManagementSupported =
Service = ScpVBus
Status = OK
StatusInfo =
SystemCreationClassName = Win32_ComputerSystem
SystemName = 7USSAIN-PC
Scp Virtual Bus Driver
Availability =
ClassGuid = {4d36e97d-e325-11ce-bfc1-08002be10318}
CompatibleID =
ConfigManagerErrorCode = 0
ConfigManagerUserConfig = False
CreationClassName = Win32_PnPEntity
Description = Scp Virtual Bus Driver
DeviceID = ROOT\SYSTEM\0003
ErrorCleared =
ErrorDescription =
HardwareID = System.String[]
InstallDate =
LastErrorCode =
Manufacturer = Scarlet.Crush Productions
Name = Scp Virtual Bus Driver
PNPDeviceID = ROOT\SYSTEM\0003
PowerManagementCapabilities =
PowerManagementSupported =
Service = ScpVBus
Status = OK
StatusInfo =
SystemCreationClassName = Win32_ComputerSystem
SystemName = 7USSAIN-PC
Scp Virtual Bus Driver
Availability =
ClassGuid = {4d36e97d-e325-11ce-bfc1-08002be10318}
CompatibleID =
ConfigManagerErrorCode = 0
ConfigManagerUserConfig = False
CreationClassName = Win32_PnPEntity
Description = Scp Virtual Bus Driver
DeviceID = ROOT\SYSTEM\0004
ErrorCleared =
ErrorDescription =
HardwareID = System.String[]
InstallDate =
LastErrorCode =
Manufacturer = Scarlet.Crush Productions
Name = Scp Virtual Bus Driver
PNPDeviceID = ROOT\SYSTEM\0004
PowerManagementCapabilities =
PowerManagementSupported =
Service = ScpVBus
Status = OK
StatusInfo =
SystemCreationClassName = Win32_ComputerSystem
SystemName = 7USSAIN-PC
Posts: 19
Threads: 0
Joined: Aug 2014
Reputation:
0
(08-24-2014, 01:59 PM)jhebbel Wrote: Could be some lingering remanence of them; i'm seeing 3 instances of SCP drivers for your 1 plugged in controller, could be an issue.
Code: Realtek Bluetooth 4.0 + High Speed Chip
Availability =
ClassGuid = {e0cbf06c-cd8b-4647-bb8a-263b43f0f974}
CompatibleID = System.String[]
ConfigManagerErrorCode = 0
ConfigManagerUserConfig = False
CreationClassName = Win32_PnPEntity
Description = Realtek Bluetooth 4.0 + High Speed Chip
DeviceID = USB\VID_0BDA&PID_B728\00E04C000001
ErrorCleared =
ErrorDescription =
HardwareID = System.String[]
InstallDate =
LastErrorCode =
Manufacturer = Realtek Semiconductor Corp.
Name = Realtek Bluetooth 4.0 + High Speed Chip
PNPDeviceID = USB\VID_0BDA&PID_B728\00E04C000001
PowerManagementCapabilities =
PowerManagementSupported =
Service = BTHUSB
Status = OK
StatusInfo =
SystemCreationClassName = Win32_ComputerSystem
SystemName = 7USSAIN-PC
Wireless Controller
Availability =
ClassGuid = {88bae032-5a81-49f0-bc3d-a4ff138216d6}
CompatibleID = System.String[]
ConfigManagerErrorCode = 0
ConfigManagerUserConfig = False
CreationClassName = Win32_PnPEntity
Description = Wireless Controller
DeviceID = USB\VID_054C&PID_05C4\6&1D7E6C28&0&1
ErrorCleared =
ErrorDescription =
HardwareID = System.String[]
InstallDate =
LastErrorCode =
Manufacturer = Sony Corp.
Name = Wireless Controller
PNPDeviceID = USB\VID_054C&PID_05C4\6&1D7E6C28&0&1
PowerManagementCapabilities =
PowerManagementSupported =
Service = WinUSB
Status = OK
StatusInfo =
SystemCreationClassName = Win32_ComputerSystem
SystemName = 7USSAIN-PC
Scp Virtual Bus Driver
Availability =
ClassGuid = {4d36e97d-e325-11ce-bfc1-08002be10318}
CompatibleID =
ConfigManagerErrorCode = 0
ConfigManagerUserConfig = False
CreationClassName = Win32_PnPEntity
Description = Scp Virtual Bus Driver
DeviceID = ROOT\SYSTEM\0002
ErrorCleared =
ErrorDescription =
HardwareID = System.String[]
InstallDate =
LastErrorCode =
Manufacturer = Scarlet.Crush Productions
Name = Scp Virtual Bus Driver
PNPDeviceID = ROOT\SYSTEM\0002
PowerManagementCapabilities =
PowerManagementSupported =
Service = ScpVBus
Status = OK
StatusInfo =
SystemCreationClassName = Win32_ComputerSystem
SystemName = 7USSAIN-PC
Scp Virtual Bus Driver
Availability =
ClassGuid = {4d36e97d-e325-11ce-bfc1-08002be10318}
CompatibleID =
ConfigManagerErrorCode = 0
ConfigManagerUserConfig = False
CreationClassName = Win32_PnPEntity
Description = Scp Virtual Bus Driver
DeviceID = ROOT\SYSTEM\0003
ErrorCleared =
ErrorDescription =
HardwareID = System.String[]
InstallDate =
LastErrorCode =
Manufacturer = Scarlet.Crush Productions
Name = Scp Virtual Bus Driver
PNPDeviceID = ROOT\SYSTEM\0003
PowerManagementCapabilities =
PowerManagementSupported =
Service = ScpVBus
Status = OK
StatusInfo =
SystemCreationClassName = Win32_ComputerSystem
SystemName = 7USSAIN-PC
Scp Virtual Bus Driver
Availability =
ClassGuid = {4d36e97d-e325-11ce-bfc1-08002be10318}
CompatibleID =
ConfigManagerErrorCode = 0
ConfigManagerUserConfig = False
CreationClassName = Win32_PnPEntity
Description = Scp Virtual Bus Driver
DeviceID = ROOT\SYSTEM\0004
ErrorCleared =
ErrorDescription =
HardwareID = System.String[]
InstallDate =
LastErrorCode =
Manufacturer = Scarlet.Crush Productions
Name = Scp Virtual Bus Driver
PNPDeviceID = ROOT\SYSTEM\0004
PowerManagementCapabilities =
PowerManagementSupported =
Service = ScpVBus
Status = OK
StatusInfo =
SystemCreationClassName = Win32_ComputerSystem
SystemName = 7USSAIN-PC
how can get rid of them
Posts: 1.733
Threads: 2
Joined: May 2014
Reputation:
26
Location: Florida, USA
(08-24-2014, 02:14 PM)sinlot Wrote: how can get rid of them
If you have the original SCP installers for them you can try using that to remove, may have to be done manually though and that may be something that someone with a little more experience with SCPs stuff can answer better.
Posts: 19
Threads: 0
Joined: Aug 2014
Reputation:
0
(08-24-2014, 02:16 PM)jhebbel Wrote: If you have the original SCP installers for them you can try using that to remove, may have to be done manually though and that may be something that someone with a little more experience with SCPs stuff can answer better.
i reinstalled scp driver and the controller light is blue and scp driver says connected but how can i use the controller it doesnt show up in the tool
Posts: 1.733
Threads: 2
Joined: May 2014
Reputation:
26
Location: Florida, USA
08-24-2014, 02:52 PM
(This post was last modified: 08-24-2014, 02:54 PM by jhebbel.)
(08-24-2014, 02:50 PM)sinlot Wrote: i reinstalled scp driver and the controller light is blue and scp driver says connected but how can i use the controller it doesnt show up in the tool
What SCP driver says its connected? Dont reinstall, remove everything, you cannot use multiple people tools at the same time, you need to remove all remanence of anybody elses tools otherwise they conflict.
Posts: 19
Threads: 0
Joined: Aug 2014
Reputation:
0
(08-24-2014, 02:52 PM)jhebbel Wrote: What SCP driver says its connected?
the one that i tried to use before but didnt work
this one
http://forums.pcsx2.net/Thread-XInput-Wr...Controller
|
