- #Sixaxis pair tool windows 8 error for mac
- #Sixaxis pair tool windows 8 error drivers
- #Sixaxis pair tool windows 8 error driver
- #Sixaxis pair tool windows 8 error code
The third thing I noticed, (and maybe this is more important?), the bytes for Source Channel Identifier that the controller is sending back is different on the working vs non working. The ones that aren't working are setting value in position 20 and 21 while the ones that are working fine seem to have 0 in these positions on L2CAP Config response. The second thing I noticed is that MTU was showing as 672 yet on every other working example (and even the Slickblue) it looks like MTU is 0. So I dug a little more to see if I could find what is happening.įirst off I noticed that the position 12 never changes over from 0x11 to 0x13 on the 2nd pass. They are able to come all the way to where name response is given but then it immediately executes an HCI_Disconnection_Complete_EV.
The Fivestar and GAME-O seem to be doing the same thing as in this post, though. this leads to connect.CanStartService set to true and ScpServer continues by establishing the connection with the controller. after name request and "Trying workarounds." I sends a L2CAP connect request as HID_Command (0x11 in position 12 of RawBytes buffer) and then another HID_Command on the L2CAP config request, then it sends a connect request as HID_Interrupt (0x13 in position 12) followed by L2CAP config request also as HID_Interrupt.
#Sixaxis pair tool windows 8 error driver
The first thing I noticed was that the Slickblue (the one working) seemed to work exactly as the driver was expecting.
#Sixaxis pair tool windows 8 error code
So I pulled down the source code for the latest release and decided to do a little debugging to see if I could either do a quick-fix to get it working or find more out about the problem. However when connecting via bluetooth, the response to the HCI name request seems exactly the same for all of them: PLAYSTATION(R)3Conteroller-PANHAI
#Sixaxis pair tool windows 8 error for mac
for MAC I don't remember because it is already in the box to return :)
Slickblue: PLAYSTATION(R)3 Controller (MAC 8A:5D:66)įivestar: PS(R) Ga`epad just like above. The output in ScpServer and logs is identical to what LOSSLOSS posted above.Īll three of these gamepads I linked here come up as VID_054C&PID_0268 (with REV0100) but the name when you plug in via USB is a little different for each of them. Wired they work perfectly, but I cannot get them to work wireless over bluetooth with the same issue mentioned here as well as many times in both PCSX2 forum threads (the original Scarlet Crush as well as yours). The physical properties of the pad and sensors on both of them are great. So I wanted to try others to see.įor these pads, they both had great button clicking and tapping - the sensors worked immediately and every time no matter how or which angle I pressed the buttons. It doesn't sound like a big deal but it is actually VERY distracting and impossible for me to get used to after growing up playing console games (Nintendo, Sega Genesis, etc :) ). You can push and tap the buttons over and over and the only way they will register a button click is if you press exactly in the center very firmly. The only problem is, the buttons on this gamepad are TERRIBLE.
#Sixaxis pair tool windows 8 error drivers
This one works perfectly with the drivers with both wired and bluetooth. I know that you said you have it on the table but my curiosity always gets the best of me so I tried to take a little look :)įirst I have tried 3 different kind of gamepads with varying degrees of success.
Not sure if you have had a chance to look into this PANHAI issue as of late or if you have very specific things already in mind that would fix this problem.
0 kommentar(er)
