..:: PCSX2 Forums ::..

(01-27-2014, 02:41 AM)zaphod77 Wrote: [ -> ]As i understand this, this driver activates the ps3 controller, and passes the inputs to MS's driver, which simply doesn't expose enough to directinput. hacking it so that the triggers go to l3 and r3 means you can't also use them. All 3rd party controllers i've seen when attached to PC expose the triggers as simple buttons.

To fix this, the xbox controller driver needs to be replaced and signed, so xinput can bet wrapped to directx differently.

Motioninjoy has to use the filter and driver method, which is impossible without signing it on windows 8 unless you introduce stability issues by disabling the singing check.

I'm pretty sure this software already uses signed drivers. but don't quote me on that.

On windows 8 the inf file needs to have a catalog and be signed.

Motioninjoy does NOT have that, last time i checked.

never mind, it sees they have signed it after all.

also you can use betterds3 to bypass their malware after you install the motioninjoy driver.

Plus you can actually get in separate analog triggers that way.

First of all thanks for the work Scarlet.Crush, I've been using your drivers for half a year now and they work flawlessly with my DS3 over bluetooth! I do have a bit of trouble to pair my DS4 as the DS4Pair application returns "Simple Pairing is not supported on this device." Now I suspect my dongle is too old as I bought it around 2009, it has the Hardware ID USB\VID_0A12&PID_0001&REV_3164

I do would like to buy a new one so I can use my DS3's and DS4's though could someone please suggest a model that's available in Europe? Alternatively the first post states that I need a Bluetooth 2.1 + EDR Dongle for the DS4, would it be written on the package if a dongle is 2.0 or 2.1?

Thanks in advance for any help!

EDIT: Would this one work? http://www.amazon.de/Hama-Nano-Bluetooth...th+2.1+EDR

It's listed as 2.1 and EDR.

(01-26-2014, 10:46 AM)Nashi Wrote: [ -> ]Could you describe changes you've made or is it all posted here http://forums.pcsx2.net/Thread-XInput-Wr...#pid332778 ?
Maybe I'll merge your changes and mine and release one big "non-genuine" fix for latest version [1.1.0.139]


PS. For all of you, trying to use my fix and having problems with finding old Scarlet.Crush release (.103) - here is the link: http://forums.pcsx2.net/attachment.php?aid=44084

I just took the compatible version of the driver to use with this fix and zipped.
If you could release an non-genuine fix for the latest version I'm sure a lot of people would be grateful, including me.

Hello this is my first post !!

I would like to ask for some help

Long story short I have Windows 8.1 Enterprise 64 bit , I've Installed the latest version of Scarlet Software + Latest Update and my dongle is this one which is on the supported list of page 1 :

Dongle Link

USB\VID_1131&PID_1004&REV_0373

Basically a generic chinese 3.0 dongle.

When I plug the Controller via USB works perfectly (red light on number one is lit) but as soon as I disconnect it from the USB port nothing happens, no light on the controller and It doesn't work at all.

I tried resetting the controller using a paperclip and also activating the Disable SSP option but no Luck.

Hope u guys can help me , Check the attachment for the required Logs.

Apart from this I would like to ask 2 more questions :

The number 241 under the SCP Monitor means that the controller is fully charged ?

What is the normal behaviour when u disconnect the Controller from the USB port the light under the number 1 remains lit or what ?

Thx in advance, Regards Zolcillonca !!

UPDATE: So I decided to uninstall everything and try an older version of Scarlet Software v1.0.0.103 instead of v1.1.0.136/139, what I noticed is that the HCI Version changed from 5.1311 to 5.4881 and LMP Version changed from 5.1311 to 5.4881 (this actually makes more sense because the default driver for my bluetooth used 5.4881 and not 5.1311).
Anyways still no luck with BT only USB is working properly but I found that with this older driver the gamepad works flawlessly on USB, on the latest version sometimes I heard the sound of disconnect/reconnect while playing during a rumble event, this doesnt happen on the older version.

Still need some help to try to make the BT Work

I can't get bluetooth to work!
I have a fake controller and i've used both nashi's fix and thigz' fix with no succes.

Service log

Driver log

(01-28-2014, 10:35 AM)geop0p3 Wrote: [ -> ]I can't get bluetooth to work!
I have a fake controller and i've used both nashi's fix and thigz' fix with no succes.

Service log

Code:

1/28/2014 12:25:31 AM.694 -- Remote Name : 00:26:37:08:3B:F4 - PLAYSTATION(R)3 Controller
1/28/2014 12:25:31 AM.696 << HCI_Accept_Connection_Request [0409]
1/28/2014 12:25:31 AM.698 >> HCI_Command_Status_EV [0F] [00]
1/28/2014 12:25:31 AM.700 >> HCI_Command_Status_EV [0F] [00]
1/28/2014 12:25:31 AM.851 >> HCI_Role_Change_EV [12]
1/28/2014 12:25:31 AM.868 -- Genuine Sony DualShock3 founded.

My fix is trying to recognize fake ds3 by MAC starting with 00:26:5C so it does nothing for your controller (00:26:37:xx:xx:xx). You can try to modify my code to work also with your MAC - maybe it will help.

Hello,

I'm new around here so first I want to thank for the awesome driver. At the begining I've been messing with motionjoy which was buggy. Constantly losing connetion with my bluetooth and even on the usb pretty much causes my ds3 to stop responding after some time in the middle of the game (I don't know why to be honest). But I immediatly switched to SCP as soon as I found them and they work flawlessly with my DS3 over usb ever since.

But, like some people here I struggled for couple of days with BT connetion. Driver installs without problem, but I got stuck with the 'Reserved' status in the SCP Monitor. I even borrow geniune ds3 (the older one with 300 mA, mine is probably aftermarket/fake'ish kind of ds3) and it also didn't work via bluetooth.

Today after scouring this thread I found working solution for above problem in Post: #1821 wrote by yetifrisstlama2. All I have done was replace the ScpControl.dll with the one from the attachment, uninstall the bluetooth driver with the SCP Driver and then install it once more (again tick the Bluetooth driver only). After that I just pluged the controller to the usb, start the SCP Monitor, unplugged usb cord and bluetooth started to work perfectly. Currently I'm sitting on the SCP 1.1.0.139 version.

Just remeber to stop the service before you replace the ScpControl file and reinstall the drivers, then start the service again.

Thanks yetifrisstlama2 for Your great big little fix

I also have one small question. Could anybody know how to switch controller to the player 2? I got wired xbox360 controller and the ds3. When I connect the ds3 via usb and the connect the xbox controller they 'sort out' which one is player 1 and 2 without problem. But when I switch the ds3 to BT both controllers appears to be player 1 (from the leds) and that could mess things in some games

Cheers!

(01-28-2014, 06:43 PM)Nashi Wrote: [ -> ]My fix is trying to recognize fake ds3 by MAC starting with 00:26:5C so it does nothing for your controller (00:26:37:xx:xx:xx). You can try to modify my code to work also with your MAC - maybe it will help.

It seems like I have a different fake... also in the log it says it's genuine... what?

Anyway how can I modify the code? i suppose i need to modify scpcontrol.dll right?
Thanks for the reply

Need info about 4 LED of my DS3, I don't understand, when I charge only LED "1" blink and when I play only LED "1" stay lighting.

No info about my battery state.