XInput Wrapper for DS3 and Play.com USB Dual DS2 Controller
(01-25-2014, 06:50 AM)Scarlet.Crush Wrote: @x_berzerker: can you zip up your ScpService.log and post as an attachment after restarting the service.

Adjust the threshold sliders to around 3/4 to the right. Go in to Game Controller Settings and view properties of one of your controllers - you should be able to see a huge deadzone while moving the Left and Right sticks.

threshold problem was solved removing xinput1_3.dll from game folder. thanks btw!

about the service problem, sorry but i couldn`t reproduce the problem. if it happpens again i'll let you know!

but now i discovered that restarting service via services.msc the controllers reconnect, but via scpserver they don't, with nothing on the log. not a trouble though, but maybe you wanna check.

Sponsored links

@x_berzerker: the XInput1_3.dll that is provided in the Win32 directory is primarily for PCSX2 use. It provides pressure sensitive button functionality which is streamed from the Native Feed provided by the ScpService. The provided Lilypad and Pokopom can make use of these extensions. The dll is not required for normal gaming use and you can disable Native Feed via configuration.

ScpService.exe is a Windows Service wrapper for ScpControl.dll, ScpServer.exe is a Windows GUI wrapper for ScpControl.dll. You should use one or the other, not both.
Since scarlet crush don't give a f*** about us users of generic controllers (ds3-conteroller) here's the one I use.
The only problems is with charging, but at least it works with bluetooth.

anonfiles.com/file/b88d045c33753b640d9004fbd97e5ada
When I installed the driver, I had one controller plugged in. Everything worked fine, bluetooth and all.

However, when I plugged in a new, second controller (after the driver was installed), it was recognized by SCP monitor and would function via usb, but neither controller would work via bluetooth after that.

I tried uninstalling the driver then reinstalling with both controllers plugged in at the same time and now everything works.

Is this by design, or is it a bug? In other words, if you want to connect 4 controllers via bluetooth, you need to have all 4 controllers connected via usb when you first install the driver?
(01-25-2014, 07:53 PM)Thigz Wrote: Since scarlet crush don't give a f*** about us users of generic controllers (ds3-conteroller) here's the one I use.
The only problems is with charging, but at least it works with bluetooth.

anonfiles.com/file/b88d045c33753b640d9004fbd97e5ada

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
(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

@Nashi
Thanks Nashi for the work you are doing to allow us to use aftermarket PS3 controllers (conterollers?). It's obvious that SC has no interest in providing support for these, so we all appreciate you stepping in to add this option. There is a large variety of these controllers that are unique, and they deserve recognition. Keep up the effort, we thank you!
The Dohitchy is there so you can attach the Whatchamacallit to the Thingamabob.
i was using four ds3 controllers that were working fine.
after turning notebook off then on again, and plugging one of the controllers to one of the usb ports, probably not the same than before, the controller not worked. checking windows usb controllers screen, there were still the four, but none of those responded to the actual connected. then i restarted service via net stop/start, and everything went ok. this shouls be considered as a bug? i am using win8.1

also, my scpmonitor window suddenly appeared outside my screen (i can see its edge around the corner), and i cant use it or bring it to a visible area either. this probably happened because of when i first ran it i was using external monitor, and now i am on notebook display. anyone know how to reset window position?
This is pretty nice.

BUT.

It makes the controller appear as an xbox360 controller to directx, and there's a serious problem.

you cannot press both triggers, because directx maps xbox360 as a single axis.

Only native xinput recognizes both triggers!

Is there a solution for this?
(01-26-2014, 07:56 PM)zaphod77 Wrote: This is pretty nice.

BUT.

It makes the controller appear as an xbox360 controller to directx, and there's a serious problem.

you cannot press both triggers, because directx maps xbox360 as a single axis.

Only native xinput recognizes both triggers!

Is there a solution for this?

There is a settings toggle that enable some button remapping that means the triggers are the same button as R3 or L3. look in ScpMonitor.exe for the setting.

In my opinion motionjoy handles this issue much better by having a toggle between xinput (with merged dinput triggers) or dinput only mode (with no xinput limitations, so can have triggers as buttons without any need for remapping).

I would prefer it if Scarlet.Crush had mimicked Motionjoys method instead of the remap hack we have now.
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.




Users browsing this thread: 22 Guest(s)