..:: PCSX2 Forums ::..

@Bositman: oops ... fixed.

Thanks Scarlet! Didn't think you'd get back so fast with a fix. I just now had free time today to test out the new package you set up. Works perfect!

Hi, first I would like to thank Scarlet for the great program for DS3 pads. MotionJoy worked quite "well" for me except the fact that it very often BSODed my computer which made it unusable.

Well now when I tried this one I can say that it is very stable and reliable. However there are some concerns/problems that I would like to share and/or ask.

1. DS3 pads work perfect through USB but I have no bluetooth driver installed during installation, therefore bluetooth connection with pads doesnt work. I am assuming it is because my blutooth hardware isnt supported.

I have two bluetooths:
- built-in with Toshiba laptop with number: USB\VID_0930&PID_0214
- $1 USB dongle (Broadband chipset I think) with number: USB\VID_0A5C&PID_2154

Both support EDR2.0 for sure.

I was trying to add my BT numbers to "BthWinUsb.inf" but seems it takes more than this because it didnt work lol

Could you please add my numbers so that I could use one of my BT for wireless connection?

2. "SCPUser" doesnt seem to catch up connected DS3 pads (at least by USB). When I had two DS3 pads already connected (before opening "SCPUser") and opened "SCPUser", no pads were showing as connected. However, when I unplug pads and plug them again with SCPUser.exe opened, then pads started to be recognized by this program. To sum it up, "SCPUser" only catches up DS3 pads as connected when they are plugged with program opened. I dont think it is correct, it should be visible for the program without doing so.

Another concern with "SCPUser" is that when I disconnect pads, it doesnt detect them as disconnected. Program could be open or closed - it doesnt change anything. When I checked once, "SCPUser" was showing DS3 pads as connected even when they were disconnectted one hour ago. Disconnection time command of pads in this program seems to be random. That's not a big deal but I dont think it is correct behaviour so I am sharing what I experienced :-)

3. In ScpServer, "Host Address" always says "disconnected", same goes for "Pad 1", "Pad 2", etc., even though pads are connected and work pretty good. I dont know what "host address" exactly is and what it is supposed to do but is it normal?

4. "ScpMonitor" - same as with "ScpServer" - Host Address and Pads alwyas say disconnected. Second concern here is that there is "configuration" button when I right click it, however this option is grayed out and I cannot open it. I think it is were I could manage pad diodes etc., but seems I cant open it for some reason.

5. I am having problem with LilyPad-Scp-r5350.dll (from WIN32 folder). I copied it to PCSX2 plugins folder, set it up in config, plugin works correctly but there is no pressure sensitive buttons (only 0.00 and 1.00). I am guessing "XInput1_3.dll" is needed for native DS3 support but it doesnt work. I put it inside main PCSX2 folder and also plugins folder, but there are no pressure sensitive buttons. I tried to google, but couldnt find anything helpful. Maybe somebody could help me please how to deal with it.

@Kirkor: The components use UDP localhost connections to talk to each other, I think you have your Firewall configured to disallow these. Open UDP ports 26760 and 26761 for localhost/loopback connections, this should fix all your issues. [Only XInput/DInput functionality is available at present]

ScpService/ScpServer <-> ScpMonitor [Status & Configuration Requests]
ScpService/ScpServer <-> XInput Wrapper [Status & Rumble Requests, Pressure Reports]

Yes for PCSX2 - copy bin\Win32\XInput1_3.dll to your PCSX2 directory, and copy bin\win32\LilyPad-Scp-r5350.dll

In order to use ScpServer.exe you must first stop the Service (SCP DS3 Service) in Service Control Manager.

When you disconnect a controller from USB using L1+R1+PS it will no longer be recognised until you Unplug/Plugin again. The main use case for this is for people not using Bluetooth, who want to be able unplug their DS3 without turning on it's paired PS3.

When you disconnect a controller from BTH using L1+R1+PS it will no longer be recognised until you press the PS button again.

Controllers go into a Reserved state when Unplugged/Shutdown, this is to facilitate transparent switching from USB <-> BTH, and maintain their XInput pad id during switching.

Host Address is the Bluetooth MAC Address of your dongle when it is in use.

Which hardware id do you want added? or both?

(05-06-2013, 01:56 AM)Scarlet.Crush Wrote: [ -> ]Now that 1.0.0.103 has been released I'm considering what to implement for future versions.

Besides the non-Xinput modes which sound great, would it be possible to implement the ability to adjust(filter) rumble strength-signals under Xinput-applications for the DS3?
[I'm not sure, but does the Xinput-spec allow adjusting rumble strength in-game or not? On the few games I played I haven't seen it so far.]

In some instances the 360 controller rumbles just barely while the DS3 absolutely goes nuts which means increased battery drain too if you play via BT.

I'd imagine a slider per connected controller set default to 1.0 or 100%.
If a game's rumble comes off too strong on the DS3 you could try setting it to 0.9 or 90% and go lower until you reach the desired strength (comparable to a 360 controller).
This option probably shouldn't be able to effect a 360-controller also connected to the system, as Xinput games nowadays most likely get tested with one to check the intended effect, but if it's possible and not detrimental it would be a nice bonus.

Another option could be to increase rumble strength over 1.0 or 100%, however if a game uses a wide range of signals it probably wouldn't be ideal if you run into ceilings what the controller can do already on default.
Increasing it then would cause lower effects to be closer to that - resulting in a more compressed range of rumble signals strength-wise.

Best regards,
Toray

Hey, thanks scarlet for making this first of all. After not being able to get Motioninjoy working at all this is definitely the way to go. So, thanks again.

However, I seem to have one little problem and so maybe you can help me out.
The drivers look fine and so does everything in devices and printers. When plugged into USB, it connects and all the buttons work.
When I disconnect the DS3 from USB the lights suggest that it is connecting to the BT dongle and everything is perfect. However, the buttons don't seem to work on BT but do again when I plug it back in. The xbox 360 controller even shows up in device and printers but it just seems to not work.

The BT drivers appeared to have been installed correctly and my dongle is 'USB\VID_0A12&PID_0001'. I've also attached my logs.

Thanks a lot again

@Toray: It is partially doable, would be at the service level so wouldn't apply to real X360s.

In X360s both motors can be set from 0 - 255 [output seems to be linear].

In DS3s the low frequency motor can be set 0 - 255 [output seems to be non-linear, below ~100 gives no noticable rumble], the high frequency motor is on/off.

@Pyral: your dongle is not BTH 2.0+EDR capable ... it is BTH 1.2.


The numbering is a bit confusing, listed on the Bluetooth SIG here.

I see... well thanks for clarifying that. I guess i'll just buy another one, easy enough.
Thanks

time for a fresh thread i think Scarlet crush.

(05-08-2013, 06:12 AM)Scarlet.Crush Wrote: [ -> ]@Kirkor: The components use UDP localhost connections to talk to each other, I think you have your Firewall configured to disallow these. Open UDP ports 26760 and 26761 for localhost/loopback connections, this should fix all your issues. [Only XInput/DInput functionality is available at present]

Thanks for your explanation.

Yes, I opened those UDP ports in Firewall and certain message in ScpServer started to appear. ScpMonitor also started to communicate (configuration now working too) when ScpServer is running. It was Firewall fault, thanks.

(05-08-2013, 06:12 AM)Scarlet.Crush Wrote: [ -> ]Yes for PCSX2 - copy bin\Win32\XInput1_3.dll to your PCSX2 directory, and copy bin\win32\LilyPad-Scp-r5350.dll

I did it like this but there is no pressure sensitive buttons still. Also tested now when Firewall doesnt block any ports (I tried with firewall turned off too).

I have no idea what I am doing wrong. Files are copied where they should - XInput1_3.dll in main PCSX2 folder and LilyPad-Scp-r5350.dll to plugins and activated in program. I must be doing something wrong or missing something then

(05-08-2013, 06:12 AM)Scarlet.Crush Wrote: [ -> ]Which hardware id do you want added? or both?

Please add both BT hardware IDs if it is possible. Thank you!