Shinlucifeh
New member
The problem of why different controls, for example, Xbox 1 + Xbox 360 or X1+ps3 or X360 or Ps3 on versions at least above 4107 is because until 4107 the keys binding where correct. I don't know if it doesn't occurs on some newer builds but you can't play Turtles and Bt, Justice League United, any newer game with 2 different joysticks, 4432 definitely is bugged. What I noticed what is wrong are the key bindings, here is a list of what is wrong with xbox 360 and ps3:
---------------
Xbox 360
X= 13
A= 11
B= 12
Y= AXIS 1-
HAT UP= 1
HAT DOWN= 2
HAT LEFT= 3
HAT RIGHT= 4
LB= 9
LT= HAT UP
RB= 10
RT= HAT DOWN
LAXIS= L AXIS OF PS3…
L3= 7
R3= 8
START= 5
SELECT= 6
PS3
SQUARE= 1
X= 2
CIRCLE= 3
TRIANGLE= 4
L1= 5
L2= 7
R1= 6
R2= 8
START= 10
SELECT= 9
L AXIS= L XBOX AXIS...
HAT UP= UNKNOWN 1
HAT DOWN= UNKNOWN 2
HAT LEFT= UNKNOWN 3
HAT RIGHT= UNKNOWN 4
-----------------------------
Ok but so what? This is what you are thinking right? Ok, the problem is that whoever made the key binding on the newer versions of Openbor REVERSED the bindings on the menu! So if you want to configure P1 with the PS3 you have to use the XBOX 360 controller and vice-versa! So, as you can see it is impossible to properly configure the Xbox controller on this situation since whoever made the key binding made the hats of PS3 an UNKNOWN value and the crucial buttons a value higher of what we get on PS3 joystick... To fix this I believe is pretty easy, though I never messed around with Openbor but you just have to switch the bindings of P1 and P2 (or better yet, just overwrite the script on 4432 related to button mapping with the 4107 version and voila! Fixed
With the X1 and Xbox 360 is a little easy, since the values are the same you just have to switch the bindings from P1 and P2 but the fix is exactly the same as above.
Also this is the reason you don't discover this bug playing alone, because since you can play anyway, doesn't matter if you are on P2 or P1 configured because openbor will still function properly.
Ps: If you noticed that the traffic on the forum slowed down, you could try to take out the image captcha based on java that does not work neither on Firefox 64 nor Chrome… having to listen the terrible machine just to post…Guys… this is horrible…
---------------
Xbox 360
X= 13
A= 11
B= 12
Y= AXIS 1-
HAT UP= 1
HAT DOWN= 2
HAT LEFT= 3
HAT RIGHT= 4
LB= 9
LT= HAT UP
RB= 10
RT= HAT DOWN
LAXIS= L AXIS OF PS3…
L3= 7
R3= 8
START= 5
SELECT= 6
PS3
SQUARE= 1
X= 2
CIRCLE= 3
TRIANGLE= 4
L1= 5
L2= 7
R1= 6
R2= 8
START= 10
SELECT= 9
L AXIS= L XBOX AXIS...
HAT UP= UNKNOWN 1
HAT DOWN= UNKNOWN 2
HAT LEFT= UNKNOWN 3
HAT RIGHT= UNKNOWN 4
-----------------------------
Ok but so what? This is what you are thinking right? Ok, the problem is that whoever made the key binding on the newer versions of Openbor REVERSED the bindings on the menu! So if you want to configure P1 with the PS3 you have to use the XBOX 360 controller and vice-versa! So, as you can see it is impossible to properly configure the Xbox controller on this situation since whoever made the key binding made the hats of PS3 an UNKNOWN value and the crucial buttons a value higher of what we get on PS3 joystick... To fix this I believe is pretty easy, though I never messed around with Openbor but you just have to switch the bindings of P1 and P2 (or better yet, just overwrite the script on 4432 related to button mapping with the 4107 version and voila! Fixed
With the X1 and Xbox 360 is a little easy, since the values are the same you just have to switch the bindings from P1 and P2 but the fix is exactly the same as above.
Also this is the reason you don't discover this bug playing alone, because since you can play anyway, doesn't matter if you are on P2 or P1 configured because openbor will still function properly.
Ps: If you noticed that the traffic on the forum slowed down, you could try to take out the image captcha based on java that does not work neither on Firefox 64 nor Chrome… having to listen the terrible machine just to post…Guys… this is horrible…
