(05-31-2015, 07:35 PM)xenphor Wrote: [ -> ]Is there a way to somehow configure the driver to handle L2 and R2 as buttons and not analogs? If not could this be added or is development stopped at this point? It would be useful for Dualshock 3s that have funky triggers that don't exactly replicate the 360 trigger action.
(05-31-2015, 07:35 PM)xenphor Wrote: [ -> ]Is there a way to somehow configure the driver to handle L2 and R2 as buttons and not analogs? If not could this be added or is development stopped at this point? It would be useful for Dualshock 3s that have funky triggers that don't exactly replicate the 360 trigger action.
Not sure if that's possible in terms of keeping the xbox controller emulation going. Lots of programs let you change the deadzone tho and in many games you can, effectively, configure them as buttons. Depends on the support.
First of all I like to give a big thanks to all programmers in this thread !! After having a series of issues with Motionin(not so much)Joy ;-) I decided to look for alternatives and eventually found this thread so I gave it a try.
I have no programming background what so ever besides some html childsplay but, with some guidance and information I've allways been able to help myself around when have to edit files.
I'm owning a Sony PlayStation3/PS3 DualShock3 controller which has allways been connected to the PC via USB-cable using MotioninJoy DS3 Tool. Up untill recently it has allways worked without a hitch.
Recently it started to be bugged without any clear reason.
It keeps getting disconnected when I'm in-game. Resulting in the game going to pause menu untill I manually enabled it again in MotioninJoy!
IMPORTANT TO KNOW IS:
I'm only playing the game "MaxPayne3" 's online multiplayer mode.
So I have no clue about this problem only being isolated to "MaxPayne3" or not.
MY TROUBLE SHOOTING UP TO THIS POINT WAS:
- Connected USB-cable to all other USB-ports
- Paired it to a Bluetooth Dongle and used it wireless instead
- Updated \ Rolled back \ Uninstalled \ Reinstalled all drivers
- Resetted the controller via the tiny reset option on the device backside
None of the above things had any effect and the problem still remained there. This was the moment I decided to go for a alernative to MotioninJoy. Found this and followed the instructions, resulting in a perfect working controller again. (I haven't tried it via Bleutooth tho)
So thanks again for sharing all this that helped me resolving my problem!
Only one question for me remains, which is:
How can I disable the left thumbstick button, or for that matter any of the buttons? I hate to say this but, in MotioninJoy this was easily done in the programs GUI. (probably the onlything that was good about it). Anyway, I tried doing this via xpadder but it seems xpadder gets ignored by MaxPayne3 completely.
Maybe the awnser to my question is already given somewhere earlier in the thread but I think asking for it is much easier than reading 440 pages and in the end risking to have possibly missed it.
I am using the latest version, everything works including the bluetooth, but it drops after 3 minutes and I have to press the controller to pair again. Can someone help me to resolve this?
The problem I'm having for the fake PLAYSTATION®3Conteroller-PANHAI is that the fake DS3 cannot remember the mac address of the Scp Bth dongle when disconnected from USB. I've tried everything; RayfenWindspear's modified .dll, pairing via ScpPair, installing & re-installing (on win 7 & 8.1 64 systems), tried internal Bluetooth on and off, also used a Bth dongle, all to no avail. Official DS3's work every time on Bluetooth, so I know it's the particular version of the "PANHAI" controller that I have. Specifically one that Scp recognizes as
[USB\VID_054C&PID_0268\5&6032F3F&0&2] Local [00:46:F9:BC:63:25] Remote [00:00:00:00:00:00]
when attempting to connect via Bth. (Notice Remote [00:00:00:00:00:00])
I have no experience in coding or building from source other than my recent attempts at understanding what is wrong, or in this instance what is not written in the code, that would make these "PANHAI" controllers work via Bluetooth. In a recent post, and in many past posts concerning the PLAYSTATION®3Conteroller-ghic (notice the "ghic" and the misspelling of "conteroller"), a solution is made by adding the proper code in the Bth configuration files contained in the source for Scp. Can anyone write the proper code and build a modified .dll that will accept the "PANHAI" controllers? Here is an excerpt from my last ScpServer log to show how these controllers are communicating with Scp.
(06-02-2015, 10:15 PM)compri Wrote: [ -> ]i get redirected from google to this forum multiple times in regards to making motioninjoy work with a BT400 ASUS dongle.
i can't really find a concrete answer and this forum is quite long. can someone tell me if a solution has been found.
just making the bt400 work wireless with my ps3 controller is enough, doesn't have to be motioninjoy.
thanks to anyone using their time to help.
you are bascily shooting yourself in the foot , uninstall motionjoy then read the instructions at the start of this thread
(06-02-2015, 01:13 AM)OfAnthony Wrote: [ -> ]The problem I'm having for the fake PLAYSTATION®3Conteroller-PANHAI is that the fake DS3 cannot remember the mac address of the Scp Bth dongle when disconnected from USB. I've tried everything; RayfenWindspear's modified .dll, pairing via ScpPair, installing & re-installing (on win 7 & 8.1 64 systems), tried internal Bluetooth on and off, also used a Bth dongle, all to no avail. Official DS3's work every time on Bluetooth, so I know it's the particular version of the "PANHAI" controller that I have. Specifically one that Scp recognizes as
[USB\VID_054C&PID_0268\5&6032F3F&0&2] Local [00:46:F9:BC:63:25] Remote [00:00:00:00:00:00]
when attempting to connect via Bth. (Notice Remote [00:00:00:00:00:00])
I have no experience in coding or building from source other than my recent attempts at understanding what is wrong, or in this instance what is not written in the code, that would make these "PANHAI" controllers work via Bluetooth. In a recent post, and in many past posts concerning the PLAYSTATION®3Conteroller-ghic (notice the "ghic" and the misspelling of "conteroller"), a solution is made by adding the proper code in the Bth configuration files contained in the source for Scp. Can anyone write the proper code and build a modified .dll that will accept the "PANHAI" controllers? Here is an excerpt from my last ScpServer log to show how these controllers are communicating with Scp.
I'm having the exact same problem as OfAnthony here. I have a bootleg DS3 that I got for about $21 (better deal than a Logitech F310, imo). Works great, for the most part, except the wireless.
I'm not sure about whether or not the controller has a problem remembering the BT address but it does try to contact it. After I disconnect it, it just powers off but when I turn it on again by pressing the PS button (without connecting it back via USB), the display on SCP does say that the controller is ringing it.
This is awesome it works really well. Although i have a problem.
Sometimes when i use these drivers my controller stops working for some reason. It's still connected but it just doesn't work. I have to plug the USB cable Out and back In again for it to work again. It's not a big deal just a small problem that can be annoying sometimes (especially when it starts my PS3 when i plug out the USB cable)
Does anyone know if this'll work with off brand controllers? I've been looking into buying these, but I'd like to make sure that I can use a Xinput wrapper before I buy them.
