Open memphisobrien opened 8 years ago
You don't?
passthrough is for common class game controllers.
Have the same problem with 2 Xbox 360 controllers. Is there any possibility that the triggers on both controllers work correctly? I know they are both xinput, anyway I need this program for ASTER. PLEASE HELP US!! Edit: Durazno/KrossX wouldn't help me
Use passtrough, if you want only to reconfigure buttons for XBOX controller x360ce is NOT for you use KrossX Durazno: https://github.com/KrossX/Durazno
yeah I tried that, but it only works for the first controller like memphisobrien said:
Now I found the solution to just mark pass through in the options. Sadly it only works with 1 controller (here aim and shoot works now). But the second controller with pass trough just converts with pass trough just in a copy of a first (a button on the first ps4 controller shows in controller 1 with pass trough and the second controller with pass trogh (but I mapped both to different numbers)).
Passtrough works for any controller, select proper "Pass Trough ID" for each controller.
Sorry but I also tried that. When I change the pass through ID for each controller it makes no difference. First controller works, second controller doesn't (it uses the first controller instead). I don't know... Have you got another solution or should I give up?
Selecting "Any" for both also not fix problem ?
nope Edit: only to give more information: When I disable pass through, the second controller works but only with the trigger problem... When I enable Pass through the first controller reacts instead of the second.
Damn I didn't mean to make this blow up :/
Try "Xinput Plus" it works perfect for me and has a heap of cool options. I was able to offset the center and increase the deadzones to fix my thumbstick drift.
Pleaaase isn't there a possibility in !!x360ce!! to enable pass through for both xinput-controllers that both will work? I'm despairing....
I think last change in passtrough code was done long ago by @jbienz and nobody found any bugs then ...
Err... actually, this was raised on the forum some time ago.
https://github.com/x360ce/x360ce/blob/master/x360ce/x360ce/Config.cpp#L330 :expressionless: Setting is ignored in full passtrough, so always index 0 is used ...
Edit: try this DLL (x86 only): http://www68.zippyshare.com/v/y4RzMTvY/file.html
Pushed small fix to master that add possibility to set PassThroughIndex
to -1
then is used default user index.
Thank you for your effort, but this also didn't work for me. I "fixed" it by disabling pass through on the second controller and changed the places of LB and LT. Then I re-changed the controls ingame --> the gamepad works without the trigger-issue :) I think it's not the perfect solution but it works...
@Squall-Leonhart Can you check ?
unfortunately can't. i only have the one controller and i don't even use the xusb driver for it.
I just wanted to bump this to say that I have the same problem (although its for MK X for me), any progress ?
Hi, I use DS4 for my 2 ps4 controllers to use it as 360 controllers with 360ce.
Sadly 2 LT + RT together earse eachother (cant aim and shoot at the same time)
Now I found the solution to just mark pass through in the options. Sadly it only works with 1 controller (here aim and shoot works now). But the second controller with pass trough just converts with pass trough just in a copy of a first (a button on the first ps4 controller shows in controller 1 with pass trough and the second controller with pass trogh (but I mapped both to different numbers)).
How to use 2 ps4 controllers in 360ce with pass trough?
Thank you a lot