..:: PCSX2 Forums ::..

This program seems to work great for two of my controllers, but for one it simply reads "00:00:00:00:00:00 Reverved" as pictured below (they are all official controllers)

I was using better DS3 for a while and motioninjoy before that, so my completely uninformed pipe theory is that prolonged use of my one controller in that system has nuked it or something, though I should note it still works on ps3 and all that. I uninstalled all of the ps3 controller drivers and they were promtly reapplied when I plugged the controllers back in, and for a bit my one controller was working. The "reserved" was replaced with USB and charging, though the "00:00:00:00:00:00" was still there. When I plugged it back in after testing the others, it returned the original state, much to my frustration.

So I guess my question is: is there any chance that my controller is just screwed or is there any way to get it to work with SCP? Has anyone else had this problem with one controller but not others?

(06-28-2015, 09:56 PM)Hyori Wrote: [ -> ]Eureka! I got mine working!

Unfortunately the name fix was not enough. Appearently a fake controller will not respond to the standard "Set Feature Report", so it has to be changed slightly to account for this.
I followed the steps made by Report Fix and got it woking!
My approach for the device name problem was to change the name verification to use the "StartsWith" method instead of a comparison.

Code:

for (int i = 0; i < 6; i++) BD_Addr[i] = Buffer[i + 3];
if (Name.StartsWith("PLAYSTATION(R)3 Controller") || Name.StartsWith("PLAYSTATION(R)3Controller") || Name.StartsWith("PLAYSTATION(R)3 Conteroller") || Name.StartsWith("PLAYSTATION(R)3Conteroller") ||
Name == "Navigation Controller" ||
Name == "Wireless Controller")
{
        NameList.Add(bd, nm.ToString());
        Transfered = HCI_Accept_Connection_Request(BD_Addr, 0x00);
}
...

I have uploaded the modified source code and compiled version:
Fake Controller Fix

so i was hoping that this fix would work for me however it didnt but i belive its the closest ive come to getting the bluetooth to work on my controller. it keeps spitting back this over and over.



any help would be gretly apreciated. ive also tried the 2 most recently posted PANHAI .dll files to try and use but those dont seem to change anything.

Hey, so I have another question. How do I get vibration working over USB for my DualShock3? It's been working, but I haven't been using the wrapper. ...Everything else is working great!


Unrelated:

(06-29-2015, 04:35 PM)Khevarash Wrote: [ -> ]You mean for the unblock or the UAC issue? UAC tends to be a bit of a nag when it comes to Program Files. Regular admins on the account are listed after the 'true admin' account. Another way of seeing if UAC was the issue is to recreate the folder in Program Files, Right click > properties > security tab and giving your user full access with file inherited permissions. Windows does a terrible job of handling permissions sometimes.

Both 'unblock' and I didn't unzip the archive files in the C:\Temp directory.
Nah, it wasn't UAC, that's disabled, and I am the only admin user.

EDIT: I tried reinstalling again, including the update, now I'm able to select the gamepad in the ScpServer.exe and use vibration!

Hey guys,

I am going through this whole thread, plus whole internet for my issue but I still couldn't figure out.

Everything is working perfectly, from installing to executing scp server programs, even my DS3 is able to connect to my bluetooth.

The problem is, my left analog or d-pad are just randomly pressing downward. You might doubt that my DS3 itself is having issues or broken. But it is not. And if I test in the hardware's setting, I can see and test all buttons working fine.

Because I still have my old laptop which is running with Motioninjoy, DS3 tool and it is perfectly running with that. But I cannot just do it right for SCP server. I followed all the instructions. Please help me!

Same story with the PANHAI, I tried with all the ScpControl.dll available in this thread.

HCI = 6.1203
LMP = 6.220E

ScpServer.exe 1.2.2.175
ScpControl.dll 1.2.2.175

Bluethoot seems to be in the valid list.

USB\VID_0A5C&PID_21E8

it always stop at:
L2CAP_Configuration_Response [05]


any ideas?

2015-07-09 17:29:57.750 -- Remote Name : 004:53:6C:63:25 - PLAYSTATION®3Conteroller-PANHAI
2015-07-09 17:29:57.765 << HCI_Accept_Connection_Request [0409]
2015-07-09 17:29:57.797 >> HCI_Command_Status_EV [0F] [00] [HCI_Accept_Connection_Request]
2015-07-09 17:29:57.921 >> HCI_Role_Change_EV [12]
2015-07-09 17:29:57.937 >> HCI_Connection_Complete_EV [03]
2015-07-09 17:29:57.953 >> HCI_Max_Slots_Change_EV [1B]
2015-07-09 17:29:57.984 >> L2CAP_Connection_Request [02] PSM [11]
2015-07-09 17:29:57.984 << L2CAP_Connection_Response [03]
2015-07-09 17:29:57.999 << L2CAP_Configuration_Request [04]
2015-07-09 17:29:58.015 >> L2CAP_Configuration_Request [04]
2015-07-09 17:29:58.046 << L2CAP_Configuration_Response [05]
2015-07-09 17:29:58.046 >> L2CAP_Configuration_Response [05]

I hope this one is really simple for someone to solve. It's probably something obvious but I just don't understand enough of this to spot it.

My PS3 gamepad works fine over cable, not over BT. I have dug though thousands of messages on this thread looking for a solution. I have not found anything that works for me, though with 4K+ messages and limited understanding, I could have missed it. I know a bit about computers but I'm a novice on drivers. Here are some details:
- Using version 1.2.2.175
- My gamepad is a Sony DS3 controller.
- My laptop has a built in BT 4.0 controller, but when I could not get that to work I plugged in a BT 3.0 dongal, reinstalled, used Zadig to install the BT driver. The BT3.0 dongal shows up as a USB device. The BT4.0 integrated controller show up as a BT device, not working (yellow triangle).
- Note the difference in my Dev Manager pic: BT3.0 dongal shows as *USB* device, not BT device. BT4.0 Integrated shows as broken *BT* device.
- My BT dongal is on the supported list, USB\VID_0A5C&PID_2198
- I am not (currently) trying to use the BT4.0 so it probably does not matter, but it is not on the supported list, USB\VID_8087&PID_07DC.
- When I first start up and go into ScpServer none of the pads are active, whether the DS3 is connected or not (but the DS3 works via cable anyway). If I disconnect/connect it shows up on pad1 with an address and Charged.
- Host Address always shows Disconnected.
- After I select pad1 the Pair button in ScpServer stays greyed out. Both, Left, Right, and Off all work fine.
- If I disconnect the DS3 it shows the removal but no host address, no BT.

- I tried the uninstall, turn on force install, install trick. No joy.
- As mentioned earlier, I did use Zadig to make sure the BT driver was installed.

Attached are my service and driver logs. Is there anything else that would help spot the problem? Thanks for your help.

can someone please tell me how to uninstall this and its drivers so I can install better ds3 tired of this program making my pads disconnect and slowly become unresponsive

nvm I seemed to have installed ds3 even with scpserver still installed pad sttill has the same problems so I guess its just faulty just gonna buy a wired gamepad for this instead

(07-11-2015, 12:47 AM)Contratempo Wrote: [ -> ]I hope this one is really simple for someone to solve. It's probably something obvious but I just don't understand enough of this to spot it.

My PS3 gamepad works fine over cable, not over BT. I have dug though thousands of messages on this thread looking for a solution. I have not found anything that works for me, though with 4K+ messages and limited understanding, I could have missed it. I know a bit about computers but I'm a novice on drivers. Here are some details:
- Using version 1.2.2.175
- My gamepad is a Sony DS3 controller.
- My laptop has a built in BT 4.0 controller, but when I could not get that to work I plugged in a BT 3.0 dongal, reinstalled, used Zadig to install the BT driver. The BT3.0 dongal shows up as a USB device. The BT4.0 integrated controller show up as a BT device, not working (yellow triangle).
- Note the difference in my Dev Manager pic: BT3.0 dongal shows as *USB* device, not BT device. BT4.0 Integrated shows as broken *BT* device.
- My BT dongal is on the supported list, USB\VID_0A5C&PID_2198
- I am not (currently) trying to use the BT4.0 so it probably does not matter, but it is not on the supported list, USB\VID_8087&PID_07DC.
- When I first start up and go into ScpServer none of the pads are active, whether the DS3 is connected or not (but the DS3 works via cable anyway). If I disconnect/connect it shows up on pad1 with an address and Charged.
- Host Address always shows Disconnected.
- After I select pad1 the Pair button in ScpServer stays greyed out. Both, Left, Right, and Off all work fine.
- If I disconnect the DS3 it shows the removal but no host address, no BT.

- I tried the uninstall, turn on force install, install trick. No joy.
- As mentioned earlier, I did use Zadig to make sure the BT driver was installed.

Attached are my service and driver logs. Is there anything else that would help spot the problem? Thanks for your help.

I don't know if this will help but I couldn't get my DS3 to work over bluetooth, while it was working fine over USB.
I followed these steps and now it works fine :

- Uninstall the service and the drivers. For this, use the ScpDriver.exe program and hit the Uninstall button.
- Go to Device Manager, and delete everything related to DS3. For me, it was under Xbox 360 Peripherals. You may have to show hidden devices under the View menu to be able to see it.
- As a safety measure, reboot the computer.
- Plug the DS3 and the bluetooth dongle and install the program again using ScpDriver.exe, then close it.
- Apply the 1.2.2.175 update.
- Open ScpServer.exe, connect your DS3, you should not see anything connected. It's because the SCP DS3 Service is running. So go to Services on your computer and stop the SCP DS3 Service.
- Back to SCP Server, you should now see the gamepad connected over USB. If not, unplug it and plug it back. You may have to click the Pair button, although I'm not sure what it does since mine is already grayed out.
- Back to Services, start the SCP DS3 Service.
- Head back to SCP Server and now disconnect the USB cable. The program will try to pair up the DS3 over bluetooth. If nothing happens, press the PS button on your DS3 so that it tries to pair up.

Voila. It worked for me, and I don't even know if my gamepad is a genuine one or not. The overall look is the same, and the material quality is similar to genuine DS3s I touched before but on Android it is detected as a fake one.
It works perfectly but I wondered if the hard time I had to pair it up was not due to the fact it may be a fake...

I'm here with the PANHAI Conteroller problems too.

I used the fix from http://forums.pcsx2.net/Thread-XInput-Wr...#pid466628

It's almost working. At least it's detected as fake now. Maybe it's just a few settings I can't figure out.

I have an issue. Everything works fine (The bluetooth and USB works just fine) but only after a force install. And I have to uninstall and reinstall the Driver every time I restart my computer or else the bluetooth pairing with the DS3 wont work, only the USB works. I'm on windows 8.1. Any fix for this?

EDIT: Made the question more clear.