dragon rise game pad

[thebuzz]

dragonrise inc. generic usb joystick axis not configured right linux mint 18...axes are mixed up there is some issue with the driver ...works with wondows

[thebuzz]

linux mint 18 32bit Kernel Linux 4.4.0-210-generic i686 MATE 1.14.1

[1000]

It may seem funny, but it seems that it probably working properly.

I was supposed to make a YouTube video on this topic, but I always have other things to do.
Maybe I tested 3-4 different gamepads. For PS3 and Xbox.
The situation looks bad on both Linux and W... systems ...
- There are sites online for testing gamepads, the same problem and each site works a little differently.
- I'm not sure, I heard that the newer Xbox gamepad now works properly on W... system.
- For Linux You have Joystick , QJoyPad , apps
and inside inside Steam --> Settings --> Controller --> options for test game pad.

One of the applications allows you to swap buttons,
I don't remember now. I hope you can handle it. Good luck.

[thebuzz]

thanks for reply but the axes are messed up...two axes are moved at the same time it is an issue with the driver ...i read something about commits and kernals but i dont know what to with it ..horizontal movement of the first stick activates two different axis: Axis 0 and Axis 2. While the vertical movement of the second stick also activates two axis: Axis 2 and Axis 4

[1000]

I noticed this too.
But I didn't find a solution or a reason.

I already gave the hardware to someone other,
but I still have a video that was supposed to go to YouTube.
The behavior varies depending on the application.

On apps.nektro.net/gamepad/ Axis 0 and Axis 2 they worked together.

I tried to compare gamepad on devicetests.com/controller-tester with Steam test controller
and the left joystick looks works identically, but I'm not sure
As you wrote above, one movement of one axis causes a little movement on another axis.
Due to this, the joystick does not work properly - I don't remember which one. It's hard to see in my video.
but in right joystick - left right joystick controls didn't work on Steam

I suspected a short circuit in one of the joysticks, but I didn't find anything.
( I didn't check the integrated circuits. Only visually inside )
and the gamepad was already worn out / old, so I left the topic.
Especially since only this gamepad had the biggest problems.

[thebuzz]

thanks again...it is definitely a driver issue...it works with windows... linux mint 18 is also pretty old ... i could not try with a newer version ....below is something found but dont know what to with



commit 18339f59c3a6698ee17d32970c9e1e450b16e7c3 upstream.

Fixed HID descriptor for DragonRise Joystick. Replaced default descriptor
which doubles Z axis and causes mixing values of X and Z axes.

Signed-off-by: Maciej Zuk <gzmlke@gmail.com>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
---
drivers/hid/hid-dr.c | 58 ++++++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 58 insertions(+)

--- a/drivers/hid/hid-dr.c
+++ b/drivers/hid/hid-dr.c
@@ -236,6 +236,58 @@ static __u8 pid0011_rdesc_fixed[] = {
0xC0 /* End Collection */
};

+static __u8 pid0006_rdesc_fixed[] = {
+ 0x05, 0x01, /* Usage Page (Generic Desktop) */
+ 0x09, 0x04, /* Usage (Joystick) */
+ 0xA1, 0x01, /* Collection (Application) */
+ 0xA1, 0x02, /* Collection (Logical) */
+ 0x75, 0x08, /* Report Size (8) */
+ 0x95, 0x05, /* Report Count (5) */
+ 0x15, 0x00, /* Logical Minimum (0) */
+ 0x26, 0xFF, 0x00, /* Logical Maximum (255) */
+ 0x35, 0x00, /* Physical Minimum (0) */
+ 0x46, 0xFF, 0x00, /* Physical Maximum (255) */
+ 0x09, 0x30, /* Usage (X) */
+ 0x09, 0x33, /* Usage (Ry) */
+ 0x09, 0x32, /* Usage (Z) */
+ 0x09, 0x31, /* Usage (Y) */
+ 0x09, 0x34, /* Usage (Ry) */
+ 0x81, 0x02, /* Input (Variable) */
+ 0x75, 0x04, /* Report Size (4) */
+ 0x95, 0x01, /* Report Count (1) */
+ 0x25, 0x07, /* Logical Maximum (7) */
+ 0x46, 0x3B, 0x01, /* Physical Maximum (315) */
+ 0x65, 0x14, /* Unit (Centimeter) */
+ 0x09, 0x39, /* Usage (Hat switch) */
+ 0x81, 0x42, /* Input (Variable) */
+ 0x65, 0x00, /* Unit (None) */
+ 0x75, 0x01, /* Report Size (1) */
+ 0x95, 0x0C, /* Report Count (12) */
+ 0x25, 0x01, /* Logical Maximum (1) */
+ 0x45, 0x01, /* Physical Maximum (1) */
+ 0x05, 0x09, /* Usage Page (Button) */
+ 0x19, 0x01, /* Usage Minimum (0x01) */
+ 0x29, 0x0C, /* Usage Maximum (0x0C) */
+ 0x81, 0x02, /* Input (Variable) */
+ 0x06, 0x00, 0xFF, /* Usage Page (Vendor Defined) */
+ 0x75, 0x01, /* Report Size (1) */
+ 0x95, 0x08, /* Report Count (8) */
+ 0x25, 0x01, /* Logical Maximum (1) */
+ 0x45, 0x01, /* Physical Maximum (1) */
+ 0x09, 0x01, /* Usage (0x01) */
+ 0x81, 0x02, /* Input (Variable) */
+ 0xC0, /* End Collection */
+ 0xA1, 0x02, /* Collection (Logical) */
+ 0x75, 0x08, /* Report Size (8) */
+ 0x95, 0x07, /* Report Count (7) */
+ 0x46, 0xFF, 0x00, /* Physical Maximum (255) */
+ 0x26, 0xFF, 0x00, /* Logical Maximum (255) */
+ 0x09, 0x02, /* Usage (0x02) */
+ 0x91, 0x02, /* Output (Variable) */
+ 0xC0, /* End Collection */
+ 0xC0 /* End Collection */
+};

[1000]

This is just a mention that there was a driver patch in kernel 3.12-stable a long time ago.
Because the gamepad is supported by the kernel.
You can test the gamepad before and after this version and on another Linux distribution if you want.
Support is available on the website https://bugzilla.kernel.org/buglist.cgi ... dragonrise

I noticed at least 2 problems, if not 3 with this gamepad.
So you need to provide them with as much data as possible.
You can even provide them with a video.
From W ... system for example with web devicetests.com/controller-tester
or with web apps.nektro.net/gamepad/
with inscriptions which button you press exactly.
The same video on Linux.
And add output of command

Code: Select all

inxi -Fxxrzc0

It is possible that they will want some system log when you connect the gamepad and control it (for example dmesg)
You can ask them what they need.

If a new patch comes out, you probably won't find it on an older version of the system.
You can ask / look for a system that has the latest kernel patches for test.
Because they compile the kernels " fast ", but it is a bit too complicated for an normal user.

[thebuzz]

thank you for your detailed reply ..much appreciated ...so much hassle for a cheap gamepad ..the funny thing is i had a microntek version of this game pad and it worked perfectly ...i may try buy it again ...i will try those links you sent me ...i was hoping for a quick fix...thanks again