Generic USB Gamepad - Right Stick Y Axis Doesn't Work

[TRUEvector]

A cheap generic USB gamepad Dialog. No drivers needed.
Works fine in non-Steam apps and games.
In Steam there is just ONE problem - it doesn't register Y-axis at all.
At the same time X-Axis behave itself like both Y and X axis assign to it.
So moving stick left the camera goes left and up, when moving right - right and down.
Moving Up or Down - nothing.
Can't calibrate, can't assign.

- it's not the problem with Axis 4 in assignments - it is saved all correct - Axis 3, no Axis 4 seen

Please help!

[kohadec]

i got this problem too, please help somebody :O

[tintingaroo]

So you're at the Define Layout screen, trying to define Right Stick Y and it doesn't register? Or it registers with the wrong axis? Or it looks all OK at Define Layout but is messed up elsewhere?


You can try setting the mapping manually.

- Fully quit Steam
- Navigate to and open with Notepad/text editor: [Steam Installation Folder]\config\config.vdf
- Do a search for: sdl_gamepadbind
You should be at the mapping section for the gamepads you've used with Steam.
- See if you can identify your controller, and see if there is an entry righty for its mapping
- Give it a value/change it to what you think is correct. If no righty, you can add it at the end of your controller's mapping string, e.g if its axis 3:
righty:a3,
- Save and close file


Example mapping for an individual controller

0300fd9c220d00002c0c000000000000,dev:ps4:msi GC20,platform:Windows,a:b1,b:b2,y:b3,x:b0,start:b9,guide:b12,back:b8,leftstick:b10,rightstick:b11,leftshoulder:b4,rightshoulder:b5,dpup:h0.1,dpleft:h0.8,dpdown:h0.4,dpright:h0.2,leftx:a0,lefty:a1,rightx:a2,righty:a5,lefttrigger:a3,righttrigger:b7,

If tricky to locate correct controller, try these steps

1. Get its Vendor ID and Product ID. One way to do that:
Windows key + R, type dxdiag, choose OK
In the diagnostic tool, go to the Inputs tab & they'll be listed alongside your controller

e.g.
VID= 0x0D22
PID = 0x0C2C

2. Remove 0x, and swap the bytes

VID= 0x0D22 -> [0D][22] -> [22][0D]
PID= 0x0C2C -> [0C][2C] -> [2C][0C]

3. those values should be part of the GUID for that controller, e.g.: 0300fd9c220d00002c0c000000000000,dev:ps4:msi GC20...

[Smearies]

Originally posted by tintingaroo:

So you're at the Define Layout screen, trying to define Right Stick Y and it doesn't register? Or it registers with the wrong axis? Or it looks all OK at Define Layout but is messed up elsewhere?


You can try setting the mapping manually.

- Fully quit Steam
- Navigate to and open with Notepad/text editor: [Steam Installation Folder]\config\config.vdf
- Do a search for: sdl_gamepadbind
You should be at the mapping section for the gamepads you've used with Steam.
- See if you can identify your controller, and see if there is an entry righty for its mapping
- Give it a value/change it to what you think is correct. If no righty, you can add it at the end of your controller's mapping string, e.g if its axis 3:
righty:a3,
- Save and close file


Example mapping for an individual controller

0300fd9c220d00002c0c000000000000,dev:ps4:msi GC20,platform:Windows,a:b1,b:b2,y:b3,x:b0,start:b9,guide:b12,back:b8,leftstick:b10,rightstick:b11,leftshoulder:b4,rightshoulder:b5,dpup:h0.1,dpleft:h0.8,dpdown:h0.4,dpright:h0.2,leftx:a0,lefty:a1,rightx:a2,righty:a5,lefttrigger:a3,righttrigger:b7,

If tricky to locate correct controller, try these steps

1. Get its Vendor ID and Product ID. One way to do that:
Windows key + R, type dxdiag, choose OK
In the diagnostic tool, go to the Inputs tab & they'll be listed alongside your controller

e.g.
VID= 0x0D22
PID = 0x0C2C

2. Remove 0x, and swap the bytes

VID= 0x0D22 -> [0D][22] -> [22][0D]
PID= 0x0C2C -> [0C][2C] -> [2C][0C]

3. those values should be part of the GUID for that controller, e.g.: 0300fd9c220d00002c0c000000000000,dev:ps4:msi GC20...

Hey man hope you're doing well, only issue i'm having is steam reverting to assignments back to the broken default ones after launching. Any tips?

[tintingaroo]

Hey Smearies :D

The process of retrieving and applying a mapping string is now implemented within the client, so we can try like this:

Steam > Settings > Controller > Test Device Inputs (Begin Test) > Copy to Clipboard

Paste the mapping into Notepad, do the edits then copy that mapping string.

Back in Steam's controller tester: Setup Device Inputs > Paste from Clipboard