One of the two analog axes does not work correctly

[rtek1000]

Is there an existing issue for this?

• I searched the existing issues and did not find anything similar.

Current Behavior

The left side works normally, but the right side does not work well. When you position the entire axis horizontally, the AntimicroX program activates both the horizontal and vertical buttons. And when you position the entire axis vertically, the AntimicroX program does not activate any buttons. The control was tested on the hardwaretester website and is working correctly.

AntimicroX 3.3.2:

AntimicroX 3.5.0:

Generic USB Joystick (Vendor: 0079 Product: 0006):

Expected Behavior

Both axes should only trigger one button when they are completely vertical or horizontal.

Steps To Reproduce

No response

Environment

Program Version 3.5.0
Compiled from packaging: GitHub Windows Release
Built Against SDL 2.30.6
Running With SDL 2.30.6
Using Qt 6.7.3
Using Event Handler: SendInput
Host OS: windows Version: 11 Architecture: x86_64

Anything else?

I'm looking for a driver (like AntimicroX) that can click on specific coordinates on the screen, to control cameras on the PTZ panel, unfortunately the developers of these programs (and there are several programs, all the same) don't have the reasoning to include accessibility via keys.

VSM (XMEye for pc)

[pktiuk]

Could you collect some logs when this issue happens?

[rtek1000]

Could you collect some logs when this issue happens?

antimicrox.log

[pktiuk]

[22:22:24.999] 🟢INFO	Created new Joystick:
			Index:            1
			  UniqueID:         03004f027900000006000000000000001216
			  GUID:             03004f02790000000600000000000000
			  VendorID:         121
			  ProductID:        6
			  Serial:           
			  Product Version:  0
			  Name:             Generic USB Joystick
			  Game Controller: No
			  # of Axes:       5
			  # of Buttons:    12
			  # of Hats:       1
			  Accelerometer:   0
			  Gyroscope:       0
			 (file /src/joystick.cpp:44)

Interesting. An app should detect 6 axes (2x2analogs + 1x2 triggers)

Did you try to use controller mapping?
Could you also provide log for 3.3.2 version?

[rtek1000]

[22:22:24.999] 🟢INFO	Created new Joystick:
			Index:            1
			  UniqueID:         03004f027900000006000000000000001216
			  GUID:             03004f02790000000600000000000000
			  VendorID:         121
			  ProductID:        6
			  Serial:           
			  Product Version:  0
			  Name:             Generic USB Joystick
			  Game Controller: No
			  # of Axes:       5
			  # of Buttons:    12
			  # of Hats:       1
			  Accelerometer:   0
			  Gyroscope:       0
			 (file /src/joystick.cpp:44)

Interesting. An app should detect 6 axes (2x2analogs + 1x2 triggers)

Did you try to use controller mapping? Could you also provide log for 3.3.2 version?

I haven't tried controller mapping before. But I also noticed that controller mapping doesn't fit the controller I have. The controller is a Playstation 2 type.

---

About version 3.3.2, there is only version 3.3.0 on the home page link:

Installation > Windows > Just download antimicrox-X.X.X-AMD64.exe from Release site and install it.

[rtek1000]

About version 3.3.2, there is only version 3.3.0 on the home page link:

Installation > Windows > Just download antimicrox-X.X.X-AMD64.exe from Release site and install it.

Now I noticed that it has version 3.5.0

[rtek1000]

About version 3.3.2, there is only version 3.3.0 on the home page link:
Installation > Windows > Just download antimicrox-X.X.X-AMD64.exe from Release site and install it.

Now I noticed that it has version 3.5.0

Ok, I found version 3.3.2 again, I didn't remember to open the Assets part to show the files

[rtek1000]

3.3.2 debug log:
antimicrox.log

[pktiuk]

I haven't tried controller mapping before. But I also noticed that controller mapping doesn't fit the controller I have. The controller is a Playstation 2 type.

It does not matter all the gamepads on Windows are mapped to the xbox ones.
Did mapping help?

If mapping does not help then it seems to be an SDL issue. In that case you can try to check what is the latest version which displays analogs properly. And then we could report this problem to the developers of SDL.