Few certain button assignments not working on the retro PC

[dg410a]

First of all, loving the USB4VC that I just got in the mail today. Works almost perfectly, but I've been running into a couple of issues and a certain glitch so far.

So, here's the thing. I've got a PC KVM setup consisting of four machines ranging from MS-DOS to Windows XP. Although, I'm only using the USB4VC for the game port so that I can have proper joystick support, especially in pure DOS. So, here's my current setup of controllers as I write this:

Microsoft Sidewinder Force Feedback 2
Logitech MOMO Force Feedback Wheel
Logitech Rumblepad 2
Microsoft Sidewinder Freestyle Pro
Microsoft Sidewinder Dual Strike
Microsoft Sidewinder Strategic Commander

All joysticks are run through a USB KVM switch, which then would go right into the RPi on the USB4VC. Works just fine despite being unsupported and it does detect all of the buttons and axes according to the Event Log. I'm also using a custom configuration and have set these to work as USB generic devices.

Although, I've noticed with my Freestyle Pro that when pressing the sensor button to switch to digital mode from proportional mode, the USB4VC goes completely nuts (i.e. One of the LEDs on the IBM PC protocol card, which detects the axes and buttons I would assume, flashes continuously. It actually exited out the Event Log without holding + on the USB4VC and pressing a joystick button). But when I press any other button on the controller, it goes back to normal. Weird.

As soon as I started using it on my PCs via game port though, that's when I ran into issues. FIrst of all, the BTN_JOYSTICK assignment doesn't register with my PCs on all of my joysticks that utilize it (minus the Strategic Commander), whether I'm using a Windows 9x DOS Box or pure DOS. And on my Force Feedback 2 and Strategic Commander, the ABS_RZ axis doesn't register with the PCs either. Otherwise, everything else works just fine, and strangely enough, on my Rumblepad 2, the ABS_RZ axis does work on my PCs.

So, I'm not sure if it's a bug in the firmware or what. I even did a proper reset on the USB4VC, but to no avail. Any input is greatly appreciated.

EDIT: Another thing to add is that I tried to do combined petals on the Y-axis since my Logitech MOMO has two separate axes for the petals themselves, being the accelerator (ABS_Y) and the brake (ABS_Z). Unfortunately, with the way I set it up, being the positive Y axis for the accelerator and the negative Y axis for the brake, ABS_Z doesn't work and ABS_Y is completely non-proportional, all on the PC.

EDIT 2: Another thing to note is one of the LEDs on the IBM protocol card. which flashes when the axes are moved and buttons are pressed as I've mentioned previously. Considering that I've assigned BTN_JOYSTICK to Button 1 and ABS_RZ to the Joystick 2 X axis on the game port, the LED does not flash when pressing said button or moving said axis.

All the gameport button and axes assignments work just fine with further testing though. So, that does confirm that the communication within the game port itself is working properly.

[dg410a]

So, upon further testing, I've noticed that binding the BTN_TRIGGER to Button 1 on the Game Port does seem to work, despite the Event Log reporting BTN_JOYSTICK whenever I push Button 1 (the trigger) on my joystick. So, knowing this, it should work with all my controllers now. Though, I still couldn't get the rudder axis on the Force Feedback 2 to work so far.

[dg410a]

Was able to get the rudder on my Force Feedback 2 joystick to work, to some degree. JS2 Positive X gives me only a limited range when turning left or right. JS2 Negative X gives me full range, but is reversed. Previously tried using the JS2 X-Axis assignment, but couldn't get it to work properly.