Hello

I was talking about it with BSzili, and in short he's not able to fix this now, maybe he can do some more explanation. But maybe someone have ideas how to solve this?

Problem is with joysensors plugin in FPSE. It was done when MorphOS was in older version and USB hid class was working slightly different. It was based on X-Box joypad support, which is not working correctly now.

X-Box joypad problem

In my case all buttons are working, just directions don't. Sometimes "up" direction is working in config, but after this only this up direction works under emulation.

Well, what is the problem exactly? What gamepad are you using?

I’ll try to check the class with the pads I have... haven’t really touched this in a while.

I'm using standard hid joypad with PS joypad look and 10 buttons. Manta MM812 to be exact.

i-manta-mm812.jpg

Every other apps which use joypad (even Amiga classic one, e.g. MacJoy) have no problem.

Problem is that during config i cannot use directions when i'm trying to config them. Only up direction works sometimes.

[ Edited by Solo_Kazuki 25.05.2019 - 18:39 ]

Just in case, here's the source code of the plugin:
http://bszili.morphos.me/ports/joysensors-src.zip
It can be compiled inside the FPSE SDK source tree:
https://www.amidog.com/amiga/fpse/

[ Edited by BSzili 25.05.2019 - 18:19 ]

@Solo_Kazuki

Pulled out a random USB gamepad - works, but you generally need to make sure the mappings in USB preferences make sense. In the list on the bottom/left on the config window you'll see a 'Sensors' entry and you generally have to try and fix this by hand. Most joysticks have a totally bogus HID descriptor (they fix it by installing Windows filter drivers)...

To check what the sensors API sees on the other side, download and run https://tunkki.dk/~jaca/waitandhid utility.

I've also just tested an XBox 360 Wireless pad and an XBox One pad using waitandhid and they both work correctly. There's some issue with the 2 analog triggers in the 360 pad, so I'll make sure to correct that. The rest works just fine.

@BSzili

I'll try to review your code soon...

Anyway, I recommend using XBOne/360 or PS4 gamepads and not the crappy random USB stuff.

My config of joypad is that:

9O7o1OrQ_o.png

ZNmZDnF8_o.png

Report current values option act ok, proper values are changing. I don't know what is not right.

Edit: Your program report all buttons but only up direction, like FPSE plugin. Other directions are not reported at all. It's weird, because all other apps which use joypad works without problem.

[ Edited by Solo_Kazuki 25.05.2019 - 19:34 ]

Try setting the Grouping to 1 for both axes.

This does not solve problem, moreover now even up direction doesn't work.

I was trying also change type to analog joystick and this is also not working.

Analog wouldn't help since this is not an analog stick (well, it'd simply go between -1.0/0/1.0 values). Can you post a screenshot of the waitandhid application?

Screen03.png

As i mentioned all buttons work ok, direction only up.

Hello

Is anything going on in this case?

As per your request, I've ordered a Manta MM812 gamepad. The first one was dead on arrival (yay, quality QC!) and the second one is actually a newer version. The new version does NOT have the problems you've mentioned. I guess they've fixed the HID descriptor or went for a different chip entirely. Note the different vendor/pid.

jacadcaps : I found an another problem with FPSE/Joysensors and the xbox360.class (confirmed by a friend too).

With the xbox360.class of 3.11 (version 4.10, 8.10.2006) and a XBox360's controller (a wired and a wireless version), equivalent of L2 and R2 buttons aren't working with joysensors.
I tried an old xbox360.class (version 51.1 7.1.2014) and two button work.

This should be fixed in 3.12.

Quote:

I've had a quick look at the source of your plugin and there's one thing you should probably add there: there seems to be no support for 3d sticks (SensorType_HIDInput_3DStick). While a bit misleading, it may just map to a bidirectional joystick with Z always set to 0.0.

Does that mean I can read SENSORS_HIDInput_NS_Value and SENSORS_HIDInput_EW_Value, like I do for SensorType_HIDInput_Stick and SensorType_HIDInput_AnalogStick?

By the way Manta is not part of the Poseidon vendors, maybe this should be extern like pci.ids.

Quote:

No, these will report SENSORS_HIDInput_X_Index and SENSORS_HIDInput_Y_Index normally (they may have more).

Quote:

Well, we've identified 2 different vendor IDs they use... are these even registered? :)

0x81f is Totsu Engineering, Inc. and 0x0810 is Personal Communication Systems, Inc. I don't think Manta has a VID of their own. I have a feeling they mostly just slap their own logo on random Chinese designed and built electronics.


[ Edited by jacadcaps 20.08.2019 - 14:41 ]

Hello

Any news regarding subject?

Well, if it's not registered, register it yourself
https://usb-ids.gowdy.us/read/UD/081f

Can You also add 0810 as Manta?

Screen03.png

Quote:

You should be contacting BSzili about this...

The plugin works fine with the XBox 360 controller, that's the only thing it was tested with. If a specific gamepad is not compatible with the MorphOS drivers, then I can't do anything about it.