..:: PCSX2 Forums ::..

I just tried beta 7, and I'm still getting the same problem as beta 6. If I have the server running and in exclusive mode, and I turn the controller on, the controller shows up in the control panel, but no buttons register, and I still get the "Connecting..." message and the lightbar stays off.

I'm in the same boat as DaRkL3AD3R right now: Turning the controller on BEFORE the server works, but turning it on WHILE the server is already active messes it up.

(04-17-2014, 12:14 AM)pedrovay2003 Wrote: [ -> ]I just tried beta 7, and I'm still getting the same problem as beta 6. If I have the server running and in exclusive mode, and I turn the controller on, the controller shows up in the control panel, but no buttons register, and I still get the "Connecting..." message and the lightbar stays off.

I'm in the same boat as DaRkL3AD3R right now: Turning the controller on BEFORE the server works, but turning it on WHILE the server is already active messes it up.

I'm seeing the same issue. Also on beta7

(04-17-2014, 12:18 AM)knewknow Wrote: [ -> ]I'm seeing the same issue. Also on beta7

Any change with the patch I tried making for you guys in this post?
http://forums.pcsx2.net/Thread-DS4Window...#pid367564

It moves the 1/4 second sleep to before part of the device detachment, in an attempt to deal with the phantom reconnect. I wish I could make this problem happen locally, but I don't have Windows 7 installed.

---

(04-16-2014, 11:57 PM)knewknow Wrote: [ -> ]hmm... button mode doesn't seem to work for me. When I turn on button mode (it shows that this is the mode that it's in in the console), I can move the mouse cursor around using the touchpad.

edit: I'm using beta7 btw... also seems a bit strange that when I use the hotkey (pad+option) to change to the different modes, it skips over button mode. It'll flash on button mode quickly and then change to cursor mode.

Did you rebind the Options key key? I noticed you could make it wig out if you mess with a few specific bindings.

Beta 7 with the patch on previous page. Controller was on before starting DS4 Windows. Disconnected it after first hook with PS+Options, stopped server, turned controller on, started server, disconnected again with PS+Options and left server running, tried turning controller on again and same story. Phantom controller with connection state happens all on the same second in time and breaks the hooking.


Just a suggestion for ease of reading the log, might want to put the timestamp in the beginning of the command line hidden logged data so it matches up nicely with the DS4 Windows event log format. TIME - CONTROLLER ID - EVENT.

(04-17-2014, 01:56 AM)DaRkL3AD3R Wrote: [ -> ]Beta 7 with the patch on previous page. Controller was on before starting DS4 Windows. Disconnected it after first hook with PS+Options, stopped server, turned controller on, started server, disconnected again with PS+Options and left server running, tried turning controller on again and same story. Phantom controller with connection state happens all on the same second in time and breaks the hooking.

Code:

2014-04-16T23:52:57.9944931Z> Starting...
2014-04-16T23:52:58.0044931Z> Searching for controllers....
2014-04-16T23:52:58.0044931Z> Using Shared Mode
A4:15:66:7D:F6:1C 2014-04-16T23:52:58.0644932Z> start
2014-04-16T23:52:58.1044933Z> Found Controller: A4:15:66:7D:F6:1C (BT)
A4:15:66:7D:F6:1C 2014-04-16T23:52:58.1044933Z> power subsystem octet: 0x06
2014-04-16T23:52:58.1264934Z> Controller: A4:15:66:7D:F6:1C is ready to use
Trying to disonnect BT device
Disconnect successful: True
2014-04-16T23:53:11.1405130Z> Controller A4:15:66:7D:F6:1C was removed or lost connection
Close fs
Close sh
2014-04-16T23:53:14.8405187Z> Stopping X360 Controllers
2014-04-16T23:53:14.8405187Z> Stopping DS4 Controllers
2014-04-16T23:53:14.8405187Z> Stopped DS4 Tool
2014-04-16T23:53:29.4805392Z> Starting...
2014-04-16T23:53:29.4805392Z> Searching for controllers....
2014-04-16T23:53:29.4805392Z> Using Shared Mode
A4:15:66:7D:F6:1C 2014-04-16T23:53:29.4905392Z> start
2014-04-16T23:53:29.5105393Z> Found Controller: A4:15:66:7D:F6:1C (BT)
2014-04-16T23:53:29.5105393Z> Controller: A4:15:66:7D:F6:1C is ready to use
A4:15:66:7D:F6:1C 2014-04-16T23:53:29.5105393Z> power subsystem octet: 0x06
Trying to disonnect BT device
Disconnect successful: True
2014-04-16T23:53:40.9105558Z> Controller A4:15:66:7D:F6:1C was removed or lost connection
Close fs
Close sh
A4:15:66:7D:F6:1C 2014-04-16T23:53:54.6005755Z> start
A4:15:66:7D:F6:1C 2014-04-16T23:53:54.6005755Z> disconnect due to write failure: 995
2014-04-16T23:53:54.6005755Z> Found Controller: A4:15:66:7D:F6:1C (BT)
2014-04-16T23:53:54.6005755Z> Controller: A4:15:66:7D:F6:1C is ready to use
A4:15:66:7D:F6:1C 2014-04-16T23:53:54.6505756Z> disconnect due to read failure: 1167
2014-04-16T23:53:54.6505756Z> Controller A4:15:66:7D:F6:1C was removed or lost connection
Close fs
Close sh
A4:15:66:7D:F6:1C 2014-04-16T23:53:55.8005772Z> start
2014-04-16T23:53:55.8205772Z> Found Controller: A4:15:66:7D:F6:1C (BT)
2014-04-16T23:53:55.8305772Z> Controller: A4:15:66:7D:F6:1C is ready to use
A4:15:66:7D:F6:1C 2014-04-16T23:53:56.6005783Z> power subsystem octet: 0x06
Trying to disonnect BT device
Disconnect successful: True
2014-04-16T23:54:15.3006045Z> Controller A4:15:66:7D:F6:1C was removed or lost connection
Close fs
Close sh
2014-04-16T23:54:17.1206070Z> Stopping X360 Controllers
2014-04-16T23:54:17.1206070Z> Stopping DS4 Controllers
2014-04-16T23:54:17.1206070Z> Stopped DS4 Tool

Just a suggestion for ease of reading the log, might want to put the timestamp in the beginning of the command line hidden logged data so it matches up nicely with the DS4 Windows event log format. TIME - CONTROLLER ID - EVENT.

So when you try and force disconnect with PS+Options, is the controller actually getting disconnected and shut off, or is the Xinput device being removed but Wireless Controller (the HID device) still alive? It appears to show up as a phantom device 15 seconds later... What happens when you perform a traditional firmware-only controller shutdown by holding the PS button?

I'll try doing a native DS4 shutdown and see what happens.

But when I do the PS+Options disconnect, it totally removes the device from my PC and shuts the controller off. It's straight up gone and works lovely.

I have been noticing these errors in Event Viewer that occur every time I do a PS+Options disconnect, but I think it's just generic BT logging chatter for "hey what happened to your controller? I didn't tell it to turn off/go away."

Bluetooth HID device (a4:15:66:7d:f6:1c) either went out of range or became unresponsive.

(04-17-2014, 01:29 AM)electrobrains Wrote: [ -> ]Any change with the patch I tried making for you guys in this post?
http://forums.pcsx2.net/Thread-DS4Window...#pid367564

It moves the 1/4 second sleep to before part of the device detachment, in an attempt to deal with the phantom reconnect. I wish I could make this problem happen locally, but I don't have Windows 7 installed.

---

I had the same problem only once with the patch from previous page. I have tried to replicate, but can't seem to anymore.

(04-17-2014, 01:29 AM)electrobrains Wrote: [ -> ]Did you rebind the Options key key? I noticed you could make it wig out if you mess with a few specific bindings.

The only keys that I changed were the left touchpad button to "back" and right touchpad button to "start". I still have the same problem after changing both touchpad buttons to "start".

Alright, I just tried doing a native DS4 disconnect by holding the PS button for 10 seconds. Whacky behavior here. DS4 Windows doesn't even acknowledge that the controller disappeared. It just stays there, with the Wireless Controller and Xbox 360 Controller both showing as enabled and active in the controller panel for Windows. Turning the DS4 back on ends up with a White LED, but no acknowledgement and reconnection from DS4 Windows. I have to stop and start the server again for it to work, and all this really does is the equivalent of PS+Options, just much slower and much more awkward.

Honestly man, I'm just leaning towards it being a Windows 7 issue. People were getting perfect Bluetooth hotplugging on Windows 8 back in the DS4 Tools beta days. For all this trouble to be put into debugging this and STILL not have a clue what's causing it, I am really just starting to believe it's a Windows issue.

I'm okay to continue down this rabbit hole, but not sure if we'll be satisfied with what we find.

(04-16-2014, 11:57 PM)knewknow Wrote: [ -> ]hmm... button mode doesn't seem to work for me. When I turn on button mode (it shows that this is the mode that it's in in the console), I can move the mouse cursor around using the touchpad.

edit: I'm using beta7 btw... also seems a bit strange that when I use the hotkey (pad+option) to change to the different modes, it skips over button mode. It'll flash on button mode quickly and then change to cursor mode.

It was switching modes fine earlier when I tried it but now it isn't. Weird... I'm looking into this right now. Maybe I ought to just revoke Beta 7 from the main page.

Edit: Check to see if you don't have a bunch of instances of "Unbound" in your Button Mode mapping. You want everything to be "Fall-Through" if you don't want to use it, and for now you should not try and change Options or Share to anything else. I was able to provoke this problem and then after fixing the mapping to reset the Unbound ones to Fall-Through, so they disappeared from the mapping file, switching modes stopped being problematic. Here's a button mode mapping file I've tested and know works for me.

When the gamepad is not connected the tool tries to create the xinput controller, because it is paired? Is that happening?, because I see the tool reporting the gamepad that is not connected, but paired and the text connecting... Can that be related to the problem? This problem (not showing fake xinput controller, and also not receiving input in the directinput controller) has happened to me for a long time, but was being triggered randomly. Now it happens always both on my pc and laptop...