Help us with new Blight Input feature

[guran]

I can't say that I like how the left and right trigger works in NRage, I think it's better like they work now in Mupen, assigning buttons to the analog stick in NRage sure works better though.

Anyway it would be great if you could assign custom deadzone values for every axis in Mupen, I think it would fix some of the problems.
Maybe have some global deadzone value (like AnalogDeadzone) you can set and then you can add a deadzone for some specific axis if you want by maybe adding something like AnalogDeadzoneAxis3 for axis(3*).

I think it would fix the problem in almost the same way as NRage does it, but NRage might do something more then just that (like "deadzones" between the axis, but I don't really know that).

Tell me what you think, maybe it's a worthless idea.

[Richard42]

The AnalogDeadzone and AnalogPeak parameters only apply to the 2 analog axes of the emulated N64 controller. I could add a DigitalDeadzone parameter which would apply to any analog joystick axes which are mapped to buttons. From looking at the code, currently this value is fixed at 6000.

[guran]

Sounds nice! Even if it affect all the axis (I would just want to change the right analog stick and not the left and right trigger buttons), but I don't even know if this would completely fix the too sensitive analog stick anyway, but it's still worth a try.

[Acidnine]

I have a wired XBox 360 Wired Controller... Hopefully this helps someone.

;;;Explanation of the Controller Keys
;axis(1-) == Left Analog Up
;axis(1+) == Left Analog Down
;axis(0+) == Left Analog Right
;axis(0-) == Left Analog Left
;axis(2+) == Left Trigger
;axis(2-) == Right Trigger
;axis(3-) == Right Analog Up
;axis(3+) == Right Analog Down
;axis(4+) == Right Analog Right
;axis(4-) == Right Analog Left
;hat(0 Up) == DPad Up
;hat(0 Down) == DPad Down
;hat(0 Right) == DPad Right
;hat(0 Left) == DPad Left
;button(9) == Right Analog Click
;button(8) == Left Analog Click
;button(7) == Start Button
;button(6) == Back Button
;button(5) == Right Bumper
;button(4) == Left Bumper
;button(3) == Y Button
;button(2) == X Button
;button(1) == B Button
;button(0) == A Button

;My Config

[XBOX 360 For Windows (Controller)]
plugged = True
plugin = 2
mouse = False
AnalogDeadzone = 4096,4096
AnalogPeak = 32768,32768
DPad R = hat(0 Right)
DPad L = hat(0 Left)
DPad D = hat(0 Down)
DPad U = hat(0 Up)
Start = button(7)
Z Trig = axis(2-)
B Button = button(1)
A Button = button(0)
C Button R = axis(4+)
C Button L = axis(4-)
C Button D = axis(3+)
C Button U = axis(3-)
R Trig = button(5)
L Trig = button(4)
Mempak switch = button(6)
Rumblepak switch = axis(2+)
X Axis = axis(0-,0+)
Y Axis = axis(1-,1+)

[guran]

I would just like to add that the config from Hulkenstrong (that recently was commited to the Mupen64plus project) doesn't work with my Xbox 360 controller, it doesn't have the same name and the DPad buttons needs to be hat(*) or it wont work, also the Z-trigger is on the right side, but that does of course not make it unusable.

This is the config I modified from the [Microsoft X-Box 360 pad] to work with Windows a while ago.

[hulkenstrong]

I would just like to add that the config from Hulkenstrong (that recently was commited to the Mupen64plus project) doesn't work with my Xbox 360 controller, it doesn't have the same name and the DPad buttons needs to be hat(*) or it wont work, also the Z-trigger is on the right side, but that does of course not make it unusable.

This is the config I modified from the [Microsoft X-Box 360 pad] to work with Windows a while ago.

There seem to be many different types of this controller going around. All I know is this is an original Xbox360 wired controller. Using Windows 7 x64 with drivers from Microsoft. There where already a Xbox auto config before I reported my changes to get my controller working (I copied and modified the first one to fit my controller).

Start = Start button
Z = Right second button
A = A
B = X
L =Left button
R = Right button
Analogue = Left stick
C buttons = Right stick
D pad = Digital Pad/Pov buttons

Thats how its setup on my Xbox controller after I modified the current one. Just how I love it (except for the earlier mentioned C-button problem).

[guran]

Yeah it sure looks that way, for my controller 360 controller the DPad wont work with those axis(*) setting instead of hat(*) though. Using the latest official drivers for Windows XP 32 bit..

[Richard42]

Okay, I have added both guran's and Acidnine's configs to the InputAutoCfg.ini file. Why are there so many different xbox360 controllers in Windows? Are these different versions of the Microsoft hardware, or different adapters?

[hulkenstrong]

Okay, I have added both guran's and Acidnine's configs to the InputAutoCfg.ini file. Why are there so many different xbox360 controllers in Windows? Are these different versions of the Microsoft hardware, or different adapters?

Did some testing and the conclusion is more likely to be driver related.

Windows 7 x64 reported as XBOX 360 For Windows
Mupen 1.5 under linux reported as Microsoft X-Box 360 pad(#1)
Linux using hwinfo Model: "Microsoft Xbox360 Controller"

So 3 different names for the same controller.

[Richard42]

Did some testing and the conclusion is more likely to be driver related.

Windows 7 x64 reported as XBOX 360 For Windows
Mupen 1.5 under linux reported as Microsoft X-Box 360 pad(#1)
Linux using hwinfo Model: "Microsoft Xbox360 Controller"

So 3 different names for the same controller.

It's not too surprising that the devices have different names on different operating systems, but what about the fact that Acidnine wrote a config for a controller named [XBOX 360 For Windows (Controller)], while guran wrote one for [Controller (XBOX 360 For Windows)]? That's pretty strange.