..:: PCSX2 Forums ::..

(04-15-2014, 10:17 PM)electrobrains Wrote: [ -> ]Can you figure out the EXACT first version of DS4Windows that incurs the problems?

It all started with DS4 Tool v1.3 Beta's. Everything after the first 1.3 beta does this to me.

(04-15-2014, 10:19 PM)DaRkL3AD3R Wrote: [ -> ]It all started with DS4 Tool v1.3 Beta's. Everything after the first 1.3 beta does this to me.

So every single version of DS4Windows, too, then? I am combing through the code trying to find a culprit, but it's going in blind without any of the debugging information that would be printed to the console.

(04-14-2014, 01:27 AM)electrobrains Wrote: [ -> ]I've spent a day working on cleaning up the mapping support, and so now I have some new capabilities in store for you in DS4Windows 1.0 Beta 5:

This is perfect . I'll be giving the latest a go tonight.

(04-15-2014, 10:44 PM)electrobrains Wrote: [ -> ]So every single version of DS4Windows, too, then? I am combing through the code trying to find a culprit, but it's going in blind without any of the debugging information that would be printed to the console.

Unfortunately yes it has been like this with every version of DS4Windows (since I assume it's based of DS4Tool v1.3 right?)

I will run the console and see if I can log what's happening for you.


I'm at a loss. DS4Windows crashes immediately after trying to connect to my controller, every time I run it with the custom Library.

(04-15-2014, 10:47 PM)DaRkL3AD3R Wrote: [ -> ]Unfortunately yes it has been like this with every version of DS4Windows (since I assume it's based of DS4Tool v1.3 right?)

I will run the console and see if I can log what's happening for you.


I'm at a loss. DS4Windows crashes immediately after trying to connect to my controller, every time I run it with the custom Library.

The DS4Windows 1.0 Beta 6 release has the debugging output already, so don't replace anything, just to run it from the console. Generally each version will have some incompatibilities between the various DLLs if you don't upgrade all of them.

You should see some of these messages when there is a disconnect:

If it were disconnected because of timeout or the PS+Options combination, you should see this one:

I'm still getting the "Connecting..." problem in beta 6. I'm headed to my girlfriend's now, and she has Windows 8.1, so I'll see if it works on her machine. I'm wondering if it's just a Windows 7 thing.

(04-16-2014, 12:22 AM)pedrovay2003 Wrote: [ -> ]I'm still getting the "Connecting..." problem in beta 6. I'm headed to my girlfriend's now, and she has Windows 8.1, so I'll see if it works on her machine. I'm wondering if it's just a Windows 7 thing.

Well, the output to the console must be different now? I think there must be an error you guys are getting that just doesn't happen with Win8's Bluetooth. But I need to know what that error is and where it occurs so I can filter it out appropriately. AFAIK it shouldn't be possible to disconnect a controller now without getting some kind of useful console debug output...

Alright here's the log.txt file. I started the controller prior to loading DS4Windows, and only the first disconnect worked properly. After that, it completely broke and requires I restart my PC to fix.

Just an FYI, this occurs on USB as well...

(04-16-2014, 12:36 AM)electrobrains Wrote: [ -> ]Well, the output to the console must be different now? I think there must be an error you guys are getting that just doesn't happen with Win8's Bluetooth. But I need to know what that error is and where it occurs so I can filter it out appropriately. AFAIK it shouldn't be possible to disconnect a controller now without getting some kind of useful console debug output...

I was stupid enough to forget my controller, so I'll have to try beta 6 on my Windows 7 machine again when I get home.

Thanks again for all the help, by the way. I really want this program to be amazing (well, moreso than it already is, I mean).

(04-16-2014, 01:16 AM)DaRkL3AD3R Wrote: [ -> ]Alright here's the log.txt file. I started the controller prior to loading DS4Windows, and only the first disconnect worked properly. After that, it completely broke and requires I restart my PC to fix.

Just an FYI, this occurs on USB as well...

Code:

A4:15:66:7D:F6:1C 2014-04-15T23:09:06.3500566Z> start
A4:15:66:7D:F6:1C 2014-04-15T23:09:06.3970593Z> power subsystem octet: 0x04
Trying to disonnect BT device
Disconnect successful: True
Close fs
Close sh
A4:15:66:7D:F6:1C 2014-04-15T23:09:22.0799563Z> start
A4:15:66:7D:F6:1C 2014-04-15T23:09:22.0799563Z> disconnect due to write failure: 995
A4:15:66:7D:F6:1C 2014-04-15T23:09:22.1779620Z> disconnect due to read failure: 1167
Close fs
Close sh
A4:15:66:7D:F6:1C 2014-04-15T23:09:35.9447494Z> start
A4:15:66:7D:F6:1C 2014-04-15T23:09:35.9577501Z> power subsystem octet: 0x04
Trying to disonnect BT device
Disconnect successful: True
Close fs
Close sh

So these are the two errors you are getting:
ERROR_OPERATION_ABORTED
995 (0x3E3)
The I/O operation has been aborted because of either a thread exit or an application request.

ERROR_DEVICE_NOT_CONNECTED
1167 (0x48F)
The device is not connected.

You're saying the exact same errors appear using USB? I'm wondering if Windows 7's HID drivers can't do simultaneous read and write operations.