GivePass / x360ce_latest

Automatically exported from code.google.com/p/x360ce
0 stars 0 forks source link

Inverted (left-right) D-Pad! #361

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

D-Pad on my USB Controller is inverted! Left is right, and right is left! And 
x360ce don't see d-pad on my controller!

I am using: Genius Maxfire-G08XU without drivers

Windows 7 32-bit.

Ini file text:

[Options]
UseInitBeep=1
Log=0
Console=0
DebugMode=0
InternetDatabaseUrl=http://www.x360ce.com/webservices/x360ce.asmx
InternetFeatures=1
InternetAutoload=1
AllowOnlyOneCopy=1

[InputHook]
HookMode=1

[Mappings]
PAD1=IG_a335cc10e35611e18001444553540000
PAD2=IG_b8ae9260e14f11e18001444553540000
PAD3=
PAD4=

[PAD1]
[PAD2]
[PAD3]
[PAD4]
[IG_b8ae9260e14f11e18001444553540000]
ProductName=2-Axis,8-Button                                                     

ProductGuid=a0000583-0000-0000-0000-504944564944
InstanceGuid=b8ae9260-e14f-11e1-8001-444553540000
AxisToDPadDeadZone=256
AxisToDPad=1
AxisToDPadOffset=256
A=1
B=2
Back=
Start=
X=3
Y=4
D-pad POV=
D-pad Down=DOWN
D-pad Left=LEFT
D-pad Right=RIGHT
D-pad Up=5
UseForceFeedback=0
ForcePercent=100
SwapMotor=0
FFBType=0
ControllerType=0
LeftMotorPeriod=60
Left Shoulder=5
Left Analog X AntiDeadZone=0
Left Analog Y AntiDeadZone=0
Left Analog X=
Left Analog Y=
Left Thumb=0
Left Analog X DeadZone=0
Left Analog Y DeadZone=0
Left Analog Y- Button=0
Left Analog X- Button=0
Left Analog X+ Button=0
Left Analog Y+ Button=0
Left Trigger=7
TriggerDeadzone=0
PassThrough=0
RightMotorPeriod=120
Right Shoulder=6
Right Analog X AntiDeadZone=0
Right Analog Y AntiDeadZone=0
Right Analog X=
Right Analog Y=
Right Thumb=0
Right Analog X DeadZone=0
Right Analog Y DeadZone=0
Right Analog Y- Button=0
Right Analog X- Button=0
Right Analog X+ Button=0
Right Analog Y+ Button=0
Right Trigger=8
RightTriggerDeadZone=0
[IG_a335cc10e35611e18001444553540000]
ProductName=SideWinder Dual Strike USB version 1.0
ProductGuid=0028045e-0000-0000-0000-504944564944
InstanceGuid=a335cc10-e356-11e1-8001-444553540000
ControllerType=0
PassThrough=0
RightTriggerDeadZone=0
TriggerDeadzone=0
D-pad Up=UP
D-pad Down=DOWN
D-pad Left=LEFT
D-pad Right=RIGHT
AxisToDPad=1
AxisToDPadDeadZone=253
AxisToDPadOffset=0
Left Analog X+ Button=0
Left Analog X- Button=0
Left Analog Y+ Button=0
Left Analog Y- Button=0
Left Thumb=0
Left Analog X DeadZone=0
Left Analog Y DeadZone=0
Left Analog X AntiDeadZone=0
Left Analog Y AntiDeadZone=0
Right Analog X+ Button=0
Right Analog X- Button=0
Right Analog Y+ Button=0
Right Analog Y- Button=0
Right Thumb=0
Right Analog X DeadZone=0
Right Analog Y DeadZone=0
Right Analog X AntiDeadZone=0
Right Analog Y AntiDeadZone=0
UseForceFeedback=0
FFBType=0
SwapMotor=0
ForcePercent=0
LeftMotorPeriod=0
RightMotorPeriod=0
Right Trigger=8
Y=1
A=4
B=3
X=2
Left Analog Y=
Left Analog X=
Left Trigger=7
Left Shoulder=6
Right Shoulder=5

Original issue reported on code.google.com by bokisa.m...@gmail.com on 29 Sep 2012 at 12:02

GoogleCodeExporter commented 9 years ago
Any solution? :-(

Original comment by juanluis...@gmail.com on 29 Dec 2012 at 6:44

GoogleCodeExporter commented 9 years ago
This issue seems to be connected to devices that have less Axes than the actual 
360 pad.

Suggestion would be to use a control with atleast as many buttons and axis as 
the real thing.

Anyway, this is a duplicate of issue 321

Original comment by danialho...@gmail.com on 1 Feb 2013 at 6:32